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

PostGIS trac at osgeo.org
Thu Dec 10 06:01:09 PST 2009

#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):


 I disagree with you on this point and mostly your train of thought rather
 than we should or shouldn't keep this.  Well I don't think we should keep
 this as Paul refer's to it "Anal retentive check" now that I have heard
 your argument.

 The reason being.  The spec details the minimum that we should support.
 So any valid geometry we need to support with what we claim to be
 compliant :).

 However the spec doesn't say anything about extending said support and
 databases do it all the time -- hell we are guilty of it in a number of
 functions.  For example we go way beyond what the spec says we should
 support with ST_PointOnSurface and ST_Centroid (I discovered this when
 trying to figure out why the hell can't I do yeh in IBM and SQL Server and
 eh certainly not Oracle because, well they decided to not go further than
 what the spec dictated in yeh or neh or stick (I think Oracle stuck to the
 letter on those 2)).

 The spec says nothing about support ST_Union for aggregates -- I don't
 think ST_Union is defined for aggregates and we even state that in our
 docs, and sure many spatial dbs decided that was hmm stupid.

 So my general argument -- as long as we can support at least the minimum
 of what the spec says is valid, we are okay and its our liberty to go
 beyond that.  IBM for one in all their examples I believe has propercase
 and all their examples show that.  -- so I think its a no-brainer that we
 have to fix this to support all types of cases people who haven't
 discovered the cap lock may use or if they are just used to typing in a
 different case.   That is clearly a bug and while we are fixing it, we
 might as well make our code shorter and easier to maintain.

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

More information about the postgis-devel mailing list