#29239: GEOSGeometry treats WKB and WKT input differently (former incorrectly)
----------------------------+----------------------------------------
Reporter: MatBurnham | Owner: Jani Tiainen
Type: Bug | Status: closed
Component: GIS | Version: 2.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+----------------------------------------
Changes (by Jani Tiainen):
* status: assigned => closed
* resolution: => wontfix
Comment:
From WKT you lose M data:
{{{#!python
>>> g1 = GEOSGeometry(wkt)
>>> g1.wkt
'MULTIPOLYGON Z (((0.0294007 51.2775369 0, 0.02942 51.2776632 0, 0.0295606
51.2776547 0, 0.0295413 51.2775285 0, 0.0294007 51.2775369 0)))'
}}}
As you see, fourth value is gone and you have lost some of your data.
Since Django supports only 3D (XYZ) coordinates and GEOS library is at the
fault closing as won't fix.
--
Ticket URL: <https://code.djangoproject.com/ticket/29239#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.209d92a60a773cc7dea4284123a2d527%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
