I have created a PR for this, but there are still issues: is Pixel Size = (0.099999991285714,-0.100000004000000) Corner Coordinates: Upper Left ( -25.0000122, 69.9999970) Lower Left ( -25.0000122, 29.9999954) Upper Right ( 44.9999817, 69.9999970) Lower Right ( 44.9999817, 29.9999954) Center ( 9.9999847, 49.9999962)
should be Pixel Size = (0.100000000000000,-0.100000000000000) Corner Coordinates: Upper Left ( -25.0000000, 70.0000000) Lower Left ( -25.0000000, 30.0000000) Upper Right ( 45.0000000, 70.0000000) Lower Right ( 45.0000000, 30.0000000) Center ( 10.0000000, 50.0000000) Markus M On Sat, Nov 24, 2018 at 6:24 PM Markus Metz <markus.metz.gisw...@gmail.com> wrote: > > > On Sat, Nov 24, 2018 at 5:56 PM Even Rouault <even.roua...@spatialys.com> > wrote: > > > > > This particular NetCDF file, PM10 analysis from CAMS > > > http://www.regional.atmosphere.copernicus.eu/, does not have a > longitude > > > variable, also no subdatasets. Resolution should be 0.1 degrees, but > GDAL > > > reports > > > Pixel Size = (-0.415021467959250,-0.100000003824258) > > > because west > east > > > > > > > ok, ncdump on it confirms there's a clean discontinuity, and regular > spacing > > before and after: > > > > longitude = 335.05, 335.15,[...], 359.85, 359.95, > > 0.04998779, 0.1499939, [...] 44.84998, 44.94998; > > ncdump also confirms that longitudes are increasing from west: > longitude = 335.05, 335.15 > this is correct, while GDAL assumes that longitudes are decreasing from > west > > The discontinuity 359.95, 0.04998779 is not a discontinuity with regard > to their location on earth, the spacing is still about 0.1 because > 0.04998779 = 360.04998779 > > > > the netCDF driver could detect and autocorrect this. Should be around > line > > 3174 of frmts/netcdf/netcdfdataset.cpp > > I will have a look. > > Thanks for your very fast feedback! > > Markus M >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
