[postgis-devel] [PostGIS] #681: ST_AsGML and ST_AsKML crashes on POLYGON EMPTY or acts really bizarre (was: ST_AsGML crashes on POLYGON EMPTY)

[PostGIS]

#681: ST_AsGML and ST_AsKML crashes on POLYGON EMPTY or acts really bizarre
----------------------+-----------------------------------------------------
  Reporter:  robe     |       Owner:  colivier     
      Type:  defect   |      Status:  reopened     
  Priority:  medium   |   Milestone:  PostGIS 2.0.0
 Component:  postgis  |     Version:  trunk        
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------

Comment(by robe):

 Okay -- now you have managed to make ST_AsKML on geography crash:

 This crashes:
 {{{
 SELECT ST_AsKML(geography(ST_GeomFromText('POLYGON EMPTY',4326))) ;
 }}}

 This returns NULL is that intentional?

 {{{
 SELECT ST_AsKML(ST_GeomFromText('POLYGON EMPTY',4326)) ;
 }}}


 ST_AsGML is still returning mysterious goo when inflicted with POLYGON
 EMPTY.


 {{{
 SELECT ST_AsGML(geography(ST_GeomFromText('POLYGON EMPTY',4326))) ;
 }}}

 The geography ST_AsGML on first call returns

 {{{
 lwgeom_free called with unknown type (111) Invalid type
 }}}
 and on subsequent calls returns mysterious goo.

 I feel like my database is haunted :).

 Though interestingly enough MULTIPOLYGON EMPTY is fine.  What's so special
 about POLYGON EMPTY?

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