Darryl, you are reading my mind :-D
more or less, the SpatiaLite own support
for Topology will follow exactly the above
guidelines, i.e.:
* a coordinate set of relationally joined Topology
tables (Nodes, Edges, Faces / Curves, Surfaces)
* to be easily transformed into "materialized views",
i.e. "ordinary" Spatial Tables based on conventional
OGC-SFS Geometries (Points, Linestrings, Polygons ..)
Your idea about applying any subsequent update only
to 'child' objects strictly depending on the changed
'topological parent' (and not to the dataset as a whole)
is really great.
Not really sure if this could be actually implemented
immediately in v.3.0: but surely a big suggestion for
any further development to come: thanks a lot.
bye Sandro
Hi Darryl,
Very good question !
I'm new to SQL and GIS, learning by myself and by the lists. I,
yesterday, posted in a QGIS forum, the same question. About foreign
land borders of properties from a cloud of points of an adjused GPS
network. (If correcting a GPS point, automatically correct the
competing lines). If there is duplication of coordinates between
layers, this can lead to disastrous inconsistencies (in my view).
I will be follwing this thread,
In a sense GNU, this time, I want to thank Sandro for his fine work.
** tks Sandro **
regards,
julio menezes ( from BraSil )
(__)
(oo)
\../
Hi,
the topology approach of postgis approach is fully compliant to the
ISO13249 specs.