Opened 7 years ago
Closed 7 years ago
#15915 closed enhancement (fixed)
code for esri projections should be ESRI:NNNN
Reported by: | bastiK | Owned by: | bastiK |
---|---|---|---|
Priority: | normal | Milestone: | 18.04 |
Component: | Core | Version: | |
Keywords: | projection esri epsg | Cc: |
Description
Continuation of #11687 and #15880: ArcGIS has forked the EPSG database and they call it WKID (well known id). It would be more precise to use prefix ESRI:
for the new projection codes, like on spatialreference. After all, EPSG is not the authority that specified these codes.
As seen in #15880, WMTS servers use EPSG:102630 for the esri WKID 102630 regardless. So we would need an alias at some level.
Attachments (0)
Change History (8)
comment:1 by , 7 years ago
Keywords: | esri epsg added |
---|
comment:2 by , 7 years ago
Owner: | changed from | to
---|
comment:3 by , 7 years ago
comment:4 by , 7 years ago
See #16129 and https://github.com/OSGeo/proj.4/issues/904. It seems the epsg/esri files in proj.4 are mixed up. They probably need some cleaning and update before we implement this.
comment:6 by , 7 years ago
Milestone: | → 18.04 |
---|
I'd say that change is enough? More would be complex without much benefit.
follow-up: 8 comment:7 by , 7 years ago
It is not enough, when we see an imagery server in the wild that is properly configured, i.e. reports ESRI:NNNN
as supported projection. But we can wait for that to happen. :)
comment:8 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to bastiK:
It is not enough, when we see an imagery server in the wild that is properly configured, i.e. reports
ESRI:NNNN
as supported projection. But we can wait for that to happen. :)
Never seen that. But in this case we can replace ESRI by EPSG, as luckily the numbers are not overlapping.
Fixed for not until issues come up.
I'm not sure about the "ESRI:" I do so now in the mapsview preview pages title, but I don't believe this a working way. What about that:
In BuildProjectDefinitions.java our projection specification is built. Why not add "ESRI: " before the name for each entry form esri file, so in JOSM the ESRI entries are clearly visible, but the code itself stays EPSG as used by the servers?