Opened 4 years ago
Last modified 3 years ago
#4847 new enhancement
ST_Union(topogeometry, topogeometry)
Reported by: | robe | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS Fund Me |
Component: | topology | Version: | 2.5.x -- EOL |
Keywords: | Cc: |
Description
Unioning of topogeometries would return another topogeometry.
Change History (4)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
Forget the previous comment, ST_Union, by contract, will NOT change the inputs, so the function I'm chasing in #4851 is different (and now I found a good name for that one)
comment:3 by , 4 years ago
Now that TopoGeom_addTopoGeom is implemented, this function could just be a wrapper for that one, with the only difference that it should first make a COPY of one of the TopoGeometries received in input to avoid changing them in the database
comment:4 by , 3 years ago
Milestone: | PostGIS 3.2.0 → PostGIS Fund Me |
---|
Note:
See TracTickets
for help on using tickets.
Regina: I've actually started a work basically DOING this in #4851, named 'toTopoGeom'. But while I was adding documentation I realized
toTopoGeom
is probably NOT a good name, while ST_Union might. This is because toTopoGeom is documented to "convert simple geometry into a topo geometry" while what I'm doing (https://gitlab.com/postgis/postgis/-/merge_requests/20) doesn't do any conversion, rather it does an actual Union.Now I've mixed feelings about the ST prefix though, because under the
topology
schema all ST prefixed functions do actually follow the ISO SQL/MM standard and it would be annoying to add exceptions (although I think it would not be the first one, given we do have ST_Simplify for TopoGeometry).