Also, the fully expanded path for SDS does work already: gdalinfo HDF5:"A2015069000500.L2_LAC_OC.nc"://geophysical_data/Kd_490
Cheers, Mike. On Tue, 30 Jun 2015 at 19:50 Michael Sumner <mdsum...@gmail.com> wrote: > Or rename to .h5 which triggers the right driver in GDAL. > > It would be good if the format auto-detect could determine that the file > was HDF5 instead ? > > > > On Tue, 30 Jun 2015 at 19:47 Anton Korosov <anton.koro...@nersc.no> wrote: > >> You can use 'ncdump -h A2015069035500.L2_LAC_OC.nc' >> ncdump is not part of gdal, but it will show you the contents of the >> dataset. >> >> In Python you can use netcdf4.Dataset to open HDF5 files. >> >> On 30/06/15 11:08, oz wrote: >> > By specifying the chlor_a, it will just display all the info on >> chlor_a. But >> > how will I able to display the info or all the subdatasets of that file? >> > >> > >> > >> > -- >> > View this message in context: >> http://osgeo-org.1560.x6.nabble.com/Getting-warning-when-opening-NetCDF-file-using-gdal-tp5213484p5213534.html >> > Sent from the GDAL - Dev mailing list archive at Nabble.com. >> > _______________________________________________ >> > gdal-dev mailing list >> > gdal-dev@lists.osgeo.org >> > http://lists.osgeo.org/mailman/listinfo/gdal-dev >> > >> >> _______________________________________________ >> gdal-dev mailing list >> gdal-dev@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/gdal-dev >> >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
