CC'ing Vincent's latest answer ---------- Forwarded Message ----------
Subject: RE: [gdal-dev] [gdal 2.2.2] different result with gdal 2.1.0 Date: mardi 14 novembre 2017, 10:04:51 CET From: Vincent BERNAT <[email protected]> To: Even Rouault <[email protected]> Even, Thanks for your reply. In fact, you were right : my dataset was wrongly georeferencing and with gdal 2.2.2, it's ok. I am sorry for the mistake! Thanks again Regards, Vincent ________________________________ De : Even Rouault <[email protected]> Envoyé : mardi 7 novembre 2017 22:30 À : Vincent BERNAT Cc : [email protected] Objet : Re: [gdal-dev] [gdal 2.2.2] different result with gdal 2.1.0 Vincent, digging into the GDAL 2.2.0 NEWS file, I see: """ ASRP driver: * fix georeferencing of polar arc zone images (#6560) """" So if there's an issue it is mostly related to that change, rather than on the gdalwarp / GDALSuggestedWarpOutput side of things And that fix was backported to GDAL 2.1.1, which explains I saw same results in the latest state of GDAL 2.1, 2.2 and trunk branchs, if you are on GDAL 2.1.0 which has not this fix You should already see the difference of georeferencing between GDAL 2.1.0 and later version by doing a gdalinfo on the source ASRP file. Do you have strong reasons to believe that GDAL 2.1.0 was really georeferencing correctly your dataset ? The change done in https://trac.osgeo.org/gdal/ticket/6560 seems at first sight to be an improvement regarding the previous behaviour Even -- Spatialys - Geospatial professional services http://www.spatialys.com ----------------------------------------- -- Spatialys - Geospatial professional services http://www.spatialys.com
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
