#29239: GEOSGeometry treats WKB and WKT input differently (former fails)
----------------------------+--------------------------------------
Reporter: MatBurnham | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: 2.0
Severity: Normal | Resolution: invalid
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: new => closed
* resolution: => invalid
Comment:
Problem seems to originate from GEOS library itself (native library) which
apparently treats different types of data slightly differently.
In any case, you geometry is not valid thus Django is not at fault. If
problem persists with a valid geometry please reopen the ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/29239#comment:1>
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.4a1c619aba1b351aff3617df8d9b919e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
