aboutsummaryrefslogtreecommitdiff
path: root/docs/source/development/reference/cpp
diff options
context:
space:
mode:
authorEven Rouault <even.rouault@spatialys.com>2019-11-09 12:22:48 +0000
committerEven Rouault <even.rouault@spatialys.com>2019-11-09 12:22:48 +0000
commit8fdd512ea8d9e0e788d93c5f356bc3d1728ba2aa (patch)
tree09f6fd9ba369a8b5a6856908014285c437e37e13 /docs/source/development/reference/cpp
parent6e58a6f906190099cbfcec63b9a68f1ef1d14d7c (diff)
downloadPROJ-8fdd512ea8d9e0e788d93c5f356bc3d1728ba2aa.tar.gz
PROJ-8fdd512ea8d9e0e788d93c5f356bc3d1728ba2aa.zip
Doc: document oddity related to identification of CRS from ESRI WKT
Or more generally formulations that don't have an explicit axis order. Refs https://github.com/pyproj4/pyproj/issues/475 projinfo 'GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]' returns EPSG:4326 with 100% confidence. But its axis order is not the same as EPSG:4326. I've pondered about this, like decreasing the confidence of the match, but this would have downstream effects on GDAL (shapefiles with the above content in a .prj would no longer be identified as EPSG:4326). So for now, document that oddity.
Diffstat (limited to 'docs/source/development/reference/cpp')
0 files changed, 0 insertions, 0 deletions