I’m a Postgis novice..i worked few years with arcgis ‘s geodatabase in order to define between data capture: relations before tables & define strict topology rules. is it possible to do that in Postgis? Regarding my big project in Africa, i need to define strict rules. For instance, i have several faces tables and i would like define before data capture rules : edges communs to several faces would be topologic and honest (of integrity)…Could you throw light for me ?
On my side, i will try to read your exemples and tutorials in order to understand Postgis Topology…Up to now, i have created topolgy schema…Thank you…kind regards.Laurent

Of course you can always build your own topology model with fully custom rules.

The only graphical editing tool I’m aware of is a work in progress for GRASS 7: http://trac.osgeo.org/grass/wiki/Grass7/VectorLib/PostGISEditing

Regarding a big project in Cameroon,I’m trying to test Postgis topology support.
Is it possible to define with postgis topology rules before data capture? (Following the example of the geodatabases Arcgis).

Is there a qgis extension to defining rules, validate or correct the topology?

In your opinion, what is the best PostGIS-QGIS client (qgis,grass, open jump, Udig …) to manage, validate and rectify topology?

Thank you to throw light for me.

Celati.

Something analogous to ArcSomething topology tools: a (1) topology layer (in memory or else), where we can define the intervening layers/postgis tables, (2) rules (overlaps, gaps, covers, contains), (3) a list of errors, and (4) tools to merge/subtract/create feature/mark as exception or error.

This would a plus (++++) if created. Add this to (fast) raster reprojection and good cartographic production tools and say good bye to proprietary software.

This is a great news.
Congratulations!

I’m not sure the GRASS toolbar would be appropriate for PostGIS topology editing.
A toolbar oriented toward ISO SQL/MM editing functions would allow:
adding an isolated node, adding an edge, splitting an edge, modifying an edge, removing an edge, removing a node. Topologies constructed through such functions would always be valid as invalidity would be caught by the functions themselves.

Such editing would need to be in sync with DB in order to make use of the functions, so would benefit from some locking and possibly versioning support.

I guess the next step here would be drafting design on a qgis wiki page…