[postgis-devel] [PostGIS] #693: POLYGONM non-closed rings

[PostGIS]

#693: POLYGONM non-closed rings
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.0.0
Component:  postgis  |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------
 Is this an intentional change that we are now checking higher dimensions
 for closedness?
 In 1.5, I could do this

 {{{
 SELECT geom  As the_geom
 FROM (VALUES ( ST_GeomFromEWKT('SRID=4326;POLYGONM((-71.1319 42.2503
 1,-71.132 42.2502 3,-71.1323 42.2504 -2,-71.1322 42.2505 1,-71.1319
 42.2503 0))') ),
         ( ST_GeomFromEWKT('SRID=4326;POLYGONM((-71.1319 42.2512 0,-71.1318
 42.2511 20,-71.1317 42.2511 -20,-71.1317 42.251 5,-71.1317 42.2509
 4,-71.132 42.2511 6,-71.1319 42.2512 30))') )
                 )       As g(geom);
 }}}

 In 2.0 it throws this error:

 ERROR:  geometry contains non-closed rings
 HINT:  "...71.1322 42.2505 1,-71.1319 42.2503 0)" <-- parse error at
 position 115 within geometry

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/693>
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.