Opened 13 years ago
Last modified 7 years ago
#1236 new enhancement
topology.IsValid*(TopoGeometry)
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Fund Me |
| Component: | topology | Version: | master |
| Keywords: | Cc: |
Description
TopoGeometry objects are references into a topology's structure. Such references may become dangling if the referee is destroyed.
Hierarchical TopoGeometry objects may be defined to be formed by overlapping lower-level compoments. Such composition should likely be also seen as an invalidity.
Non-hierarchical TopoGeometry objects may refer to missing primitives (corrupted topology).
Beside these structural invalidities there's likely no way for a TopoGeomety-derived Geometry to be invalid.
Change History (5)
comment:1 by , 13 years ago
| Summary: | ST_IsValid*(TopoGeometry) → topology.IsValid*(TopoGeometry) |
|---|
comment:2 by , 13 years ago
| Milestone: | PostGIS 2.0.0 → PostGIS 2.1.0 |
|---|
comment:3 by , 12 years ago
| Milestone: | PostGIS 2.1.0 → PostGIS 2.2.0 |
|---|
comment:4 by , 10 years ago
| Milestone: | PostGIS 2.2.0 → PostGIS Future |
|---|
Note:
See TracTickets
for help on using tickets.
Following the rules under topology. this function shouldn't start with ST_ as it's not an ISO/SQLMM function. BTW, SQL/MM doesn't even have the concept of a TopoGeometry.