#844 closed enhancement (fixed)
Allow specifying BoundaryNodeRule in ST_Relate*
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.0.0 |
| Component: | postgis | Version: | master |
| Keywords: | history | Cc: |
Description
GEOS/JTS support different interpretations of linearwork boundaries [1]. Allowing specifying an interpretation from SQL might speed up some operations which currently require convoluted checks for closed linestrings and start/end points. In particular topology functions (see ticket #770)
See previous discussion here: http://postgis.refractions.net/pipermail/postgis-devel/2011-January/011422.html
[1] http://tsusiatsoftware.net/jts/javadoc/com/vividsolutions/jts/algorithm/BoundaryNodeRule.html
Change History (6)
comment:1 by , 14 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 14 years ago
comment:3 by , 14 years ago
Ready as of r6882. Tests included.
Lacks documentation, see http://geos.osgeo.org/doxygen/classgeos_1_1algorithm_1_1BoundaryNodeRule.html for semantics.
Values are:
1 For OGC/MOD2 2 For ENDPOINT 3 For MULTIVALENT ENDPOINT 4 For MONOVALENT ENDPOINT
comment:4 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
r6883 has some documentation too, but nothing deep about the actual semantic of those boundary node rules.
Robe: I'm sure you're happy to go deeper about it, right ? :>
Will need http://trac.osgeo.org/geos/ticket/399