[postgis-devel] Call for 1.4.2 and 1.5.1 (Handling of Invalid Geometries)

strk strk at keybit.net
Wed Feb 17 13:19:32 PST 2010


On Wed, Feb 17, 2010 at 10:18:08PM +0100, strk wrote:
> On Wed, Feb 17, 2010 at 01:15:54PM -0800, Kevin Neufeld wrote:
> > Interesting.  So does this mean that a 2-ordinate polygon would get 
> > converted to a LINESTRING and a 3-ordinate polygon would automatically have 
> > a fourth point added, thus closing the ring?
> > 
> > What would these clean to?
> > 'POLYGON((0 0),(1 1 2 2))'
> > 'POLYGON((0 0),(1 1 2 2),(3 3, 4 4, 5 5))'
> 
> Can you provide them in HEXWKB form for me to check ?
> PostGIS won't let me write that in the db.... 

Beside the sarcasm, the plan is for the above to become
'GEOMETRYCOLLECTION(POINT(0 0),LINESTRING(1 1, 2 2))'
'GEOMETRYCOLLECTION(POINT(0 0),LINESTRING(1 1, 2 2),LINESTRING(3 3, 4 4, 5 5))'

--strk; 

  ()   Free GIS & Flash consultant/developer
  /\   http://foo.keybit.net/~strk/services.html



More information about the postgis-devel mailing list