Opened 10 years ago
Closed 10 years ago
#25583 closed New feature (fixed)
GEOSGeometry.transform should impose no constraints on SRID if called with CoordTransform
| Reported by: | Sergey Fedoseev | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Change History (5)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
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?
comment:3 by , 10 years ago
This behavior is problematic when you have coordinates in some custom SRS with no SRID assigned and you need to transform these coordinates.
comment:4 by , 10 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Type: | Uncategorized → New feature |
| Version: | 1.8 → master |
OK, fair.
Note:
See TracTickets
for help on using tickets.
added PR https://github.com/django/django/pull/5457