Hey, Thank you all for the replies, i really appreciate the help.
@Anton, i have tried many different ways of refering to the file. Full path, file only, back and forward slashes, double slashes etc. All have the same result. I also would expect this to be platform dependent, but not file format dependent. So for a NetCDF file it should be similar as for Geotiff etc. The NETCDF prefix and subdataset are format specific, so this might be an issue. But if this is wrong, i would suspect the commandline utilities to be failing as well. @Etienne, Running gdalinfo with stats gives me exactly the same values as you, till the last decimal. This confirms that both the file is fine (gdal-proof), and that the pre-build command-line utilities are working as supposed to. Turning on 'CPL_DEBUG' (and adding the -q to supress progress) for the previous posted script results in: /D:\Projects\Python\TRMM_soilm>python debug.py GDAL: GDALOpen(LPRM-TMI_L3_DY_SOILM3_V001-20120503T175233Z_20120501.vrt, this=01883C90) succeeds as VRT. ERROR 4: `NETCDF:LPRM-TMI_L3_DY_SOILM3_V001-20120503T175233Z_20120501.nc:soil_moisture_x' does not exist in the file system, and is not recognised as a supported dataset name. GDAL: GDALClose(LPRM-TMI_L3_DY_SOILM3_V001-20120503T175233Z_20120501.vrt, this=01883C90) GDAL: GDALClose(NETCDF:LPRM-TMI_L3_DY_SOILM3_V001-20120503T175233Z_20120501.nc:soil_moisture_x, this=01884388)/ Besides the earlier error still being present i dont see anything which can be an indication of the problem. If anyone has any other ways of debugging this, i would appreciate it. Regards, Rutger -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Reading-a-NetCDF-file-with-python-not-recognised-as-a-supported-dataset-name-tp4979943p4980067.html Sent from the GDAL - Dev mailing list archive at Nabble.com. _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
