[gdal-dev] Fwd: RE: [gdal 2.2.2] different result with gdal 2.1.0

[Even Rouault]

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 <vincent.bernat at magellium.fr>
To: Even Rouault <even.rouault at spatialys.com>

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 <even.rouault at spatialys.com>
Envoyé : mardi 7 novembre 2017 22:30
À : Vincent BERNAT
Cc : gdal-dev at lists.osgeo.org
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20171114/88346ef1/attachment.html>