From: Regina Obe Date: Tue, 9 Jul 2013 16:29:14 +0000 (+0000) Subject: #2378 document that ST_CollectionExtract and ST_CollectionHomegenize are flawed when... X-Git-Tag: 2.2.0rc1~1455 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0e6e1dba03630b7c1c66b621a237087735421ae3;p=postgis #2378 document that ST_CollectionExtract and ST_CollectionHomegenize are flawed when dealing with polygons with shared edges git-svn-id: http://svn.osgeo.org/postgis/trunk@11645 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/reference_editor.xml b/doc/reference_editor.xml index 63ef413c0..690fe6cbb 100644 --- a/doc/reference_editor.xml +++ b/doc/reference_editor.xml @@ -713,6 +713,9 @@ Prior to 1.5.3 this function returned non-collection inputs untouched, no matter In 1.5.3 non-matching single geometries result in a NULL return. In of 2.0.0 every case of missing match results in a typed EMPTY return. + + When specifying 3 == POLYGON a multipolygon is returned even when the edges are shared. This results in an invalid multipolygon for many cases + such as applying this function on an result. @@ -763,9 +766,13 @@ MULTILINESTRING((0 0, 1 1), (2 2, 3 3)) Given a geometry collection, returns the "simplest" representation of the contents. Singletons will be returned as singletons. Collections that are homogeneous will be returned as the appropriate multi-type. + + When specifying 3 == POLYGON a multipolygon is returned even when the edges are shared. This results in an invalid multipolygon for many cases + such as applying this function on an result. - Availability: 2.0.0 + Availability: 2.0.0 +