[postgis-devel] [PostGIS] #399: ST_CleanGeometry

[PostGIS]

#399: ST_CleanGeometry
----------------------+-----------------------------------------------------
  Reporter:  strk     |       Owner:  strk         
      Type:  task     |      Status:  new          
  Priority:  medium   |   Milestone:  PostGIS 2.0.0
 Component:  postgis  |     Version:               
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Comment (by kneufeld):

 Replying to [comment:6 strk]:
 > Now to get INTO the debate... why returning MULTI* always ?
 > I'd rather get a SINGLE back if the input can be represented as such.
 > The user still have the option to force to a MULTI later after all...

 I agree, a SINGLE back would be best if the input can be represented as
 such.  I was just thinking of corner cases ... multipoints, multipolygons,
 geometrycollections.

 I suppose always returning a MULTI works if bordering polygons are always
 dissolved in multipolygons, and the same input (or null, or error) is
 returned for multipoints.

 Yeah, ok, you've convinced me.  Collections are definitely easier to work
 with than sets.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/399#comment:10>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.