From: Sandro Santilli Date: Tue, 3 Apr 2012 12:05:45 +0000 (+0000) Subject: Add note about input noding for ST_Polygonize and ST_BuildArea X-Git-Tag: 2.0.0~13 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=dd4741901329d19e9ccc157355d30e44d0056366;p=postgis Add note about input noding for ST_Polygonize and ST_BuildArea git-svn-id: http://svn.osgeo.org/postgis/trunk@9591 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/reference_processing.xml b/doc/reference_processing.xml index ce6747213..b39542eac 100644 --- a/doc/reference_processing.xml +++ b/doc/reference_processing.xml @@ -288,6 +288,11 @@ POLYGON((236057.59057465 900908.759918696,236028.301252769 900838.049240578,235 form polygons NULL is returned. The inputs can be LINESTRINGS, MULTILINESTRINGS, POLYGONS, MULTIPOLYGONS, and GeometryCollections. This function will assume all inner geometries represent holes + + + Input linework must be correctly noded for this function to work properly + + Availability: 1.1.0 - requires GEOS >= 2.1.0. @@ -353,6 +358,7 @@ FROM (SELECT ST_Buffer( See Also + , , wrappers to this function with standard OGC interface @@ -1753,6 +1759,11 @@ POLYGON((135.59714732062 115,134.384753327498 102.690357210921,130.79416296937 9 Geometry Collections are often difficult to deal with with third party tools, so use ST_Polygonize in conjunction with to dump the polygons out into individual polygons. + + + Input linework must be correctly noded for this function to work properly + + Availability: 1.0.0RC1 - requires GEOS >= 2.1.0. @@ -1788,7 +1799,10 @@ geomtextrep See Also - + + , + +