#29793: GeometryField with Oracle always assume that axes are named as long and
lat
in geometry metadat
-------------------------------+--------------------------------------
Reporter: Jani Tiainen | Owner: nobody
Type: Uncategorized | Status: new
Component: GIS | Version: 2.1
Severity: Normal | Resolution:
Keywords: oracle | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Description changed by Jani Tiainen:
Old description:
> GeometryField with Oracle always assume that axis are named as long and
> lat in geometry metadata.
>
> Even this is purely metadata there is currently no way to specify axis
> name to match axes used with SRID normally.
>
> For example when using SRID 3857 (spherical mercator) lang and lot
> doesn't really make sense but X and Y would.
New description:
GeometryField with Oracle always assume that axes are named as long and
lat in geometry metadata.
Even this is purely metadata there is currently no way to specify axes
names to match axes used with SRID normally.
For example when using SRID 3857 (spherical mercator) lang and lot doesn't
really make sense but X and Y would.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29793#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/063.47854ca10f2af18249379a2427df7719%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
