[postgis-tickets] [PostGIS] #3332: PostGIS 2.x doesn't allow to store some invalid polygon kinds

PostGIS trac at osgeo.org
Thu Oct 15 08:28:25 PDT 2015


#3332: PostGIS 2.x doesn't allow to store some invalid polygon kinds
------------------------------+--------------------------
 Reporter:  fcaa              |      Owner:  strk
     Type:  defect            |     Status:  new
 Priority:  high              |  Milestone:  PostGIS GEOS
Component:  liblwgeom         |    Version:  2.2.x
 Keywords:  invalid geometry  |
------------------------------+--------------------------
 I've found that since PostGIS 2.0, some invalid invalid polygon kinds
 (reported as having unclosed rings, with error code XX000 in lwgeom_pg.c,
 line 162) cannot be stored, which in turn aborts the transaction at next
 insertion (error code 25P02). Using PostGIS 1.5 everything is stored with
 no hiccups.

 After researching if this is a 'feature', 'breaking change' or 'bug' since
 PostGIS 2.0 and having found no documentation, I'd like to know if this is
 a known issue that could be resolved or not.

 I've reproduced this again with PostGIS 2.2 x64 ("POSTGIS="2.2.0 r14208"
 GEOS="3.5.0-CAPI-1.9.0 r4090" SFCGAL="1.2.0" PROJ="Rel. 4.9.1, 04 March
 2015" GDAL="GDAL 2.0.1, released 2015/09/15" LIBXML="2.7.8" LIBJSON="0.12"
 TOPOLOGY RASTER") and PostgreSQL 9.4.5 x64.

 Thanks in advance.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3332>
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-tickets mailing list