#7579 closed (fixed)
Saving into SRID=-1 field causes st_transform error
Reported by: | Robert Coup | Owned by: | jbronn |
---|---|---|---|
Component: | GIS | Version: | gis |
Severity: | Keywords: | srid | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | yes | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Currently if you define a GeometryField(srid=-1)
then save a value with a srid != -1
, then Django will attempt to transform the geometry to -1, causing a DB error.
I've attached a simple patch for Postgis but I suspect the same issue will occur in the other backends - is geoapp
the best place to add tests for this?
Attachments (1)
Change History (6)
by , 16 years ago
Attachment: | django_-1_srid_patch.postgis.diff added |
---|
comment:1 by , 16 years ago
Needs tests: | set |
---|---|
Status: | new → assigned |
comment:2 by , 16 years ago
Yes, geoapp
would be the right place. A new model should be added with a geometry field that has a -1 srid.
comment:3 by , 16 years ago
milestone: | → 1.0 beta |
---|
comment:4 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Initial patch for postgis backend