From 0ba0e5bf2b43b5076c6dc89ca10149fc015f220a Mon Sep 17 00:00:00 2001 From: Sandro Santilli Date: Tue, 8 Mar 2011 10:43:21 +0000 Subject: [PATCH] Some (poor) documentation for ST_Relate(g1,g2,boundaryNodeRule) git-svn-id: http://svn.osgeo.org/postgis/trunk@6883 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/reference_measure.xml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/doc/reference_measure.xml b/doc/reference_measure.xml index a42de87db..85ea348cd 100644 --- a/doc/reference_measure.xml +++ b/doc/reference_measure.xml @@ -3524,6 +3524,13 @@ SELECT ST_AsEWKT(ST_PointOnSurface(ST_GeomFromEWKT('LINESTRING(0 5 1, 0 0 1, 0 1 geometry geomA geometry geomB + + + text ST_Relate + geometry geomA + geometry geomB + int BoundaryNodeRule + @@ -3547,15 +3554,19 @@ SELECT ST_AsEWKT(ST_PointOnSurface(ST_GeomFromEWKT('LINESTRING(0 5 1, 0 0 1, 0 1 index call. Version 2: Takes geomA and geomB and returns the + + Version 3: same as version 2 bu allows to specify a boundary node rule (1:OGC/MOD2, 2:Endpoint, 3:MultivalentEndpoint, 4:MonovalentEndpoint) Do not call with a GeometryCollection as an argument not in OGC spec, but implied. see s2.1.13.2 - Both Performed by the GEOS module + Performed by the GEOS module &sfs_compliant; s2.1.1.2 // s2.1.13.3 &sqlmm_compliant; SQL-MM 3: 5.1.25 + Enhanced: 2.0.0 - added support for specifying boundary node rule (requires GEOS >= 3.0). + -- 2.50.1