Topology Components as global TopoElements access

Felipe Matas felipematas at yahoo.com
Mon Nov 25 10:08:14 PST 2024


 Hi, yes, we can use TopoElements, is just they lack of context, a TopoComponent which works at database level and do not need the Layer/Topology context would simplify a lot of workflows.
Also is easier verify the workflow because we can know the TopoGeometry parent and child, this can also be used for an Array similar for the TopoGometry I proposed time ago, but more useful when it comes to edit and handle inside of TopoGeometries.

Thx!
    El miércoles, 13 de noviembre de 2024, 04:40:14 a. m. GMT-3, Sandro Santilli <strk at kbt.io> escribió:  
 
 On Tue, Nov 12, 2024 at 08:46:16PM +0000, Felipe Matas wrote:
> Hi, latot here, I was thinking in TopoElements, they are nice and well
> organized in the relation's table, but to me makes noise in the actual
> SQL use, because the TopoElement do not store any information about the
> to which layer belongs, so can be hard to use it safely.

A TopoElement can represent *either* a primitive *or* a TopoGeometry.
In the latter case (TopoGeometry) you have the layer information in
the "type" attribute of the TopoElement.

See https://postgis.net/docs/topoelement.html

--strk;

  Libre GIS consultant/developer
  https://strk.kbt.io/services.html
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20241125/cd04aa18/attachment.htm>


More information about the postgis-devel mailing list