Shapely is using the GEOS WKB reader, which apparently doesn't
understand 2.5D WKB.
On Mar 10, 2010, at 12:09 PM, Oliver Christen wrote:
Hi Sean
after some more research, my colleague noticed the data was in fact
multipolygon 3D, which shapely (in the the version we are using
1.0.14) doesnt seem to understand.
converting the data set to multipolygon 2D solved my problem
sorry for the troubles
best regards
Oliver
I doubt it's a bug in PostGIS. Use ST_AsBinary since it seems to
be more
reliable than depending on the internal representation which may
or may
not be exactly hex-encoded WKB.
On Mar 10, 2010, at 10:38 AM, Oliver Christen wrote:
Hi Sean
the postgis installed on the server is 1.3.5
so it's quite old, could it be some kind of bug in postgis which
would
make the geometry string unreadable ?
are there some known incompatible postgis version ?
regards
Oliver
What version of PostGIS are you using? The latest? Did the project
change the format in which it stores geometries? If so,
ST_AsBinary is
what you'll want to use now.
Cheers,
--
Sean
--
Sean
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community
--
Sean
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community
