[postgis-devel] [PostGIS] #332: WKT geometry tag match and mismatch

[PostGIS]

#332: WKT geometry tag match and mismatch
----------------------+-----------------------------------------------------
  Reporter:  mloskot  |       Owner:  pramsey      
      Type:  defect   |      Status:  new          
  Priority:  medium   |   Milestone:  PostGIS 1.5.0
 Component:  postgis  |     Version:  trunk        
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Comment (by robe):

 Yes I'm aware of what I'm signing on to. I think for this whole OGC
 discussion -- its really more relevant what we do in output functions --
 and for inputs that we accept at a minimum what the OGC/MM requires given
 OGC/MM inputs.

 If we loosen our constraint a little -- it doesn't change prior behavior
 -- old apps work unchanged and behave exactly the same (except possibly
 they won't be whining so when given extended input or binary -- does
 anyone care? :)) .  So new apps can get away with passing in 3D or SRID or
 binary.  I don't see that as big enough issue to complicate our code over.

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