Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#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 strk, 11 years ago

Owner: changed from pramsey to strk
Status: newassigned

comment:3 by strk, 11 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 strk, 11 years ago

Resolution: fixed
Status: assignedclosed

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 ? :>

comment:5 by robe, 11 years ago

Will do.

comment:6 by strk, 11 years ago

Keywords: history added

NEWS file updated

Note: See TracTickets for help on using tickets.