Opened 4 years ago
Last modified 3 years ago
#4867 new enhancement
topology.InteriorIntersects(TopoGeometry, TopoGeometry) — at Version 3
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Fund Me |
| Component: | topology | Version: | |
| Keywords: | Cc: |
Description (last modified by )
A function returning true if two TopoGeometry objects defined on the _same_ underlaying topology share at least a common element.
NOTE this is different from an && operator (#1290)
Change History (3)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
Important thing: the semantic of the function I want to make is NOT the same as ST_Overlap, I just realized, because ST_Overlap returns FALSE if an area is fully contained in the other. I don't know if an OGC defined predicate does exist to mean "areal geometries have some area in common". It's probably not ST_Intersects because that one also returns true for _linear_ intersections, and it's not ST_Overlap... do we want another function with a common meaning for this ?
comment:3 by , 4 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | topology.Overlap(TopoGeometry, TopoGeometry) → topology.InteriorIntersects(TopoGeometry, TopoGeometry) |
Note:
See TracTickets
for help on using tickets.
Calling it ST_Overlaps may greatly speed up existing code calling ST_Overlaps(TopoGeometry, TopoGeometry) but if we take that path we'll then have to support ANY TopoGeometry in order to retain semantic of existing calls (can't bail out if the TopoGeometry objects are not in the same topology...)