You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Just to tell you that there is a bad behaviour with GDAL 3 (at least <= 3.0.2).
In DTMCreation/tuilage_mnt_eau_S2.py, the coordinates tranformation from osr (line 104/105) returns opposite values : (y, x) instead of (x,y).
The consequence is a wrong intersection between S2 image and SRTM coordinates (wrong path of srtm file, line 118/119).
Hi,
Just to tell you that there is a bad behaviour with GDAL 3 (at least <= 3.0.2).
In DTMCreation/tuilage_mnt_eau_S2.py, the coordinates tranformation from osr (line 104/105) returns opposite values : (y, x) instead of (x,y).
The consequence is a wrong intersection between S2 image and SRTM coordinates (wrong path of srtm file, line 118/119).
Issue from OSGEO already identified : OSGeo/gdal#1546
For now, MAJA works fine with GDAL 2, my advice is do not update to GDAL 3 until issue is fixed.
Nicolas Ekicier
The text was updated successfully, but these errors were encountered: