Hi folks
I discovered django.contrib.gis support for 3d geometries is pretty patchy. I realised that the database stuff only worked in postgis, etc, but it turns out even the serialisation methods on GEOSGeometry don't work properly. Here's a small test script that demonstrates the problem: https://gist.github.com/2594905 And here's the output: https://gist.github.com/2594926 In summary, all these properties return 2d-only output for 3d geometries (the Z dimension gets stripped): - wkt - ewkt - hex - wkb - json - geojson Yet these others produce correct 3d output: - ewkb - hexewkb - kml Is there any reasoning behind this, or should I create a ticket and try to fix them? I tried posting this to the geodjango list (here)<https://groups.google.com/forum/#!msg/geodjango/XQkkeDmsCDI/ZBYq1XZ6SngJ>, but I'm not sure if anyone actually reads those posts, as I haven't got a response in 10 days. Thanks Craig de Stigter -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/s4smWq7j4xIJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
