Le 27/07/2022 à 17:03, Matthew Savoie a écrit :
Hi Andrew,
> I have run this command with gdal 3.4.3 and gdal 3.5.1 and get
different output files.
Can you compare the output of the two versions of gdalinfo ?
This should determine whether the difference is when reading or writing.
Good idea, I did that and there is no difference in the output of
gdalinfo between 3.4.3 and 3.5.1 on the test.nc file.
Are you 100% sure about that ? It is highly unlikely that the difference
would be on the side of the output driver (GeoTIFF), and much more
likely on the reading side (netCDF). There have been adjustments
recently in the netCDF driver to be a bit more restrictive regarding
exposing geotransforms (the driver could expose non relevant
geotransforms), that have had side effects on some files where they
could be legitimate.
You can likely workaround the issue by definining the configuration
option / environment variable GDAL_NETCDF_IGNORE_XY_AXIS_NAME_CHECKS to
YES (cf https://gdal.org/drivers/raster/netcdf.html#georeference). Buf
if you can provide a link to the file that could be used to examine
further whether the file is defective (an expected attribute missing),
or the driver could be enhanced to recognize it better.
Even
Thanks,
Matt Savoie
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
