[postgis-tickets] [PostGIS] #3332: PostGIS 2.x doesn't allow to store some invalid polygon kinds
PostGIS
trac at osgeo.org
Tue Nov 17 04:13:53 PST 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 2.2.1
Component: liblwgeom | Version: 2.2.x
Resolution: | Keywords: invalid geometry
------------------------+------------------------------
Comment (by fcaa):
Hi:
I've attached a sample of the invalid geometries, as SHP and as a
SQLite/SpatiaLite database.
My use case is the following:
1.- The geometries are stored in a SQLite/SpatiaLite database.
2.- The geometries are read using SpatiaLite's ST_AsBinary() function
(used 4.3.0a version, with LWGeom 2.1.7 and GEOS 3.5.0-CAPI-1.9.0 r4084).
3.- The geometries are inserted using PostGis's ST_GeomFromWkb() function.
The former steps work seamlessly with PostGIS 1.5, but not with PostGIS
2.x.
In the meantime, I've tried to reproduce it using PostGIS Shapefile Loader
2.2 and the SHP attached, and with a SQL script generated with ogr2ogr,
but the geometries were loaded as expected. So, at this time I'm
suspecting also of an issue with SpatiaLite's ST_AsBinary().
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3332#comment:8>
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