Opened 6 years ago
Last modified 6 years ago
#29793 new Cleanup/optimization
GeometryField with Oracle always assume that axes are named as long and lat in geometry metadat — at Version 1
| Reported by: | Jani Tiainen | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | 2.1 |
| Severity: | Normal | Keywords: | oracle |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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.
Change History (1)
comment:1 by , 6 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | GeometryField with Oracle always assume that axis are named as long and lat in geometry metadata → GeometryField with Oracle always assume that axes are named as long and lat in geometry metadat |
Note:
See TracTickets
for help on using tickets.