--
Ticket URL: <https://code.djangoproject.com/ticket/25583>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
added PR https://github.com/django/django/pull/5457
--
Ticket URL: <https://code.djangoproject.com/ticket/25583#comment:1>
Comment (by claudep):
I'm not sure about that. I think requiring the SRID being set for a
geometry to be transformed is some sort of safeguard against badly written
code.
Maybe you could tell me about a use case where this behavior is
problematic and where defining the proper SRID beforehand is not possible?
--
Ticket URL: <https://code.djangoproject.com/ticket/25583#comment:2>
Comment (by sir-sigurd):
This behavior is problematic when you have coordinates in some custom SRS
with no SRID assigned and you need to transform these coordinates.
--
Ticket URL: <https://code.djangoproject.com/ticket/25583#comment:3>
* version: 1.8 => master
* type: Uncategorized => New feature
* stage: Unreviewed => Accepted
Comment:
OK, fair.
--
Ticket URL: <https://code.djangoproject.com/ticket/25583#comment:4>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"a7bb5af50be7b0efbb784011a41fd25fdfe4d42c" a7bb5af5]:
{{{
#!CommitTicketReference repository=""
revision="a7bb5af50be7b0efbb784011a41fd25fdfe4d42c"
Fixed #25583 -- Allowed calling `transform` with `CoordTransform` even if
SRID is invalid.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25583#comment:5>