[postgis-tickets] [PostGIS] #2587: CompoundCurve with empties parses differently from WKB and WKT

[PostGIS]

#2587: CompoundCurve with empties parses differently from WKB and WKT
---------------------+------------------------------------------------------
 Reporter:  mloskot  |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.1.2
Component:  postgis  |     Version:  2.1.x        
 Keywords:  wkt,wkb  |  
---------------------+------------------------------------------------------

Comment(by pramsey):

 We've always had different rules for WKB and WKT inputs (try, for example,
 an unclosed WKB polygon and WKT polygon, one gets int the other does not).
 So this is not really a huge deal, IMO (except insofar as our general
 policy is a bit of a huge deal, but we've lived with it for a long long
 time).

 I'd like to examine the last case, if only to try and catch it more
 cleanly that it looks like it's being caught.

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