Re: [gdal-dev] Discrepancy in reported Spatial Reference b/n gdalinfo and arcpy

2024-05-14 Thread Even Rouault via gdal-dev
Le 14/05/2024 à 18:08, Liyuneh Gebre a écrit : hi, thanks for your kind commitment.  I tried the docker version and unfortunately it shows the same result. That's expected. The fix has been done post 3.9.0. This will be available in 3.9.1 On Sun, May 12, 2024 at 4:02 PM Even Rouault wrote

Re: [gdal-dev] Discrepancy in reported Spatial Reference b/n gdalinfo and arcpy

2024-05-12 Thread Even Rouault via gdal-dev
Hi, fix in https://github.com/OSGeo/gdal/pull/9909 Le 12/05/2024 à 12:06, Javier Jimenez Shaw via gdal-dev a écrit : I do not know if there is any documentation from esri about that specific format for LAMBERT_AZIMUTHAL. It would be great. And also I am surprised that in 13 years nobody comp

Re: [gdal-dev] Discrepancy in reported Spatial Reference b/n gdalinfo and arcpy

2024-05-12 Thread Javier Jimenez Shaw via gdal-dev
Your file prj.adf is ProjectionLAMBERT_AZIMUTHAL Units METERS ZunitsNO Xshift0.0 Yshift0.0 Parameters6378137.0 6378137.0 6378137.0 /* radius of the sphere of reference 20 0 0.0 /* longitude of center of projection 5 0 0.0 /* latitude of center of p

[gdal-dev] Discrepancy in reported Spatial Reference b/n gdalinfo and arcpy

2024-05-11 Thread Liyuneh Gebre via gdal-dev
Hi, I've encountered a discrepancy in the outputs of GDAL and arcpy. While using gdalinfo on an arcGrid file with a user-defined projection, the reported latitude and longitude of natural origin and False easting seems to be incorrect. However, when accessing the same file with arcpy and examining