Dear all,
when reading netCDF files generated by openEO platform with GDAL version 3.5.0, or software like QGis that uses this version, the netCDF may not be placed correctly on the map, because the georeferencing metadata is now handled differently.
We’ll be working on a fix, trying to improve compatibility with both old and new GDAL version. This should also improve compliance with CF conventions.
Further details are tracked in this ticket:
opened 06:15AM - 12 Oct 22 UTC
GDAL 3.5.0 introduced changes to netCDF CF attributes handling.
As a result, geo… rferencing of openEO geotrellis netCDF files is wrong, we probably need to review our attributes and make them work with both old and new gdal versions.
https://github.com/OSGeo/gdal/blob/v3.5.0/NEWS.md
```
netCDF driver:
- handle 'crs_wkt' attribute
- always use WKT when found, without comparing with CF params (#4725)
- limit SetFromUserInput() use to non file input
- disable filename recoding to ANSI on Windows for netCDF >= 4.8
- add WRITE_GDAL_VERSION and WRITE_GDAL_HISTORY creation option
- add a VARIABLES_AS_BANDS=YES/NO open option
- allow update mode of raster datasets
- implement SetMetadataItem()/SetMetadata()
- avoid warnings when CreateCopy() a non-georeferenced dataset, and opening a 1x1 non-georeferenced dataset
- add a IGNORE_XY_AXIS_NAME_CHECKS=YES open option (https://github.com/qgis/QGIS/issues/47158)
- recognize x/y axis from GMT generated files as geospatial axis (#5291, https://github.com/qgis/QGIS/issues/47158, https://github.com/qgis/QGIS/issues/45704)
- read CF attributes giving CRS component names (#5493)
- add support for writing/reading geolocation array without a grid_mapping variable
```
Note that the issue seems to be fixed now on openeo-dev.vito.be. The fix will also be rolled out on the platform!