[postgis-devel] [PostGIS] #1806: Extremely slow and CPU-intensive ST_MakeValid (ST_BuildArea) case

[PostGIS]

#1806: Extremely slow and CPU-intensive ST_MakeValid (ST_BuildArea) case
----------------------+-----------------------------------------------------
  Reporter:  strk     |       Owner:  strk         
      Type:  defect   |      Status:  closed       
  Priority:  high     |   Milestone:  PostGIS 2.0.1
 Component:  postgis  |     Version:  2.0.x        
Resolution:  fixed    |    Keywords:               
----------------------+-----------------------------------------------------

Comment(by hugoledoux):

 I agree that keeping all the geometries can be useful, but we decided to
 have an *automatic* method where the user presses one button and gets a
 valid geometry. Our method is predictable since it can be explained in 3
 simple steps, so the user knows what to expect.

 I believe that if the user wants to manually edit a polygon (with a GUI
 for instance), she can always go back to the original geometry.

 Our design choice makes our algorithm very fast and scalable to very large
 polygon, modifying it to return all the geometries would make it use more
 memory and would slow it down...

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1806#comment:22>
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.