nco_err_exit(): ERROR Short NCO-generated message (usually name of function that triggered error): nco_get_vara()
nco_err_exit(): ERROR Error code is -90. Translation into English with nc_strerror(-90) is "NetCDF: file not found"
nco_err_exit(): ERROR NCO will now exit with system call exit(EXIT_FAILURE)
I can grab the latitude and longitude variables from the file (and strides of it), but when requesting the chl variable, ncks failed miserably. I think this is related to netcdf groups, since the headers are the following:
Hello ocehugo,
This message slipped from my attention while traveling.
Sorry for the late response.
I am unable to reproduce the problem you describe.
Retrieval of chl_oc3 works for me.
Suggestion is to be sure you're using latest NCO.
If problems persist, send exact commands, versions, etc.
cz
doublelatitude(latitude);latitude:_Netcdf4Dimid=1;latitude:units="degrees_north";latitude:long_name="latitude";latitude:standard_name="latitude";doublelongitude(longitude);longitude:_Netcdf4Dimid=2;longitude:units="degrees_east";longitude:long_name="longitude";longitude:standard_name="longitude";doubletime(time);time:_Netcdf4Dimid=0;time:units="days since 1800-01-01 00:00:00.0";time:calendar="gregorian";time:long_name="time";time:standard_name="time";
data:
chl_oc3 = _ ;
latitude = 10 ;
longitude = 70 ;
time = 77367 ;
} // group /
zender@givre:~$
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm trying to get some files from the following server:
http://thredds0.nci.org.au/thredds/dodsC/u83/modis/oc.mosaics.70/2011/10/29/A20111029.70.austocean.20130813192425.chl_oc3.nc4
But nco return me an error of the type:
nco_err_exit(): ERROR Short NCO-generated message (usually name of function that triggered error): nco_get_vara()
nco_err_exit(): ERROR Error code is -90. Translation into English with nc_strerror(-90) is "NetCDF: file not found"
nco_err_exit(): ERROR NCO will now exit with system call exit(EXIT_FAILURE)
I can grab the latitude and longitude variables from the file (and strides of it), but when requesting the chl variable, ncks failed miserably. I think this is related to netcdf groups, since the headers are the following:
Dataset {
Grid {
ARRAY:
Float32 chl_oc3[time = 1][latitude = 8001][longitude = 11001];
MAPS:
Float64 time[time = 1];
Float64 latitude[latitude = 8001];
Float64 longitude[longitude = 11001];
} chl_oc3;
Float64 time[time = 1];
Float64 longitude[longitude = 11001];
Float64 latitude[latitude = 8001];
} u83/modis/oc.mosaics.70/2011/10/29/A20111029.70.austocean.20130813192425.chl_oc3.nc4;
Cheers
Hello ocehugo,
This message slipped from my attention while traveling.
Sorry for the late response.
I am unable to reproduce the problem you describe.
Retrieval of chl_oc3 works for me.
Suggestion is to be sure you're using latest NCO.
If problems persist, send exact commands, versions, etc.
cz
zender@givre:~$ ncks --cdl -v chl_oc3,latitude,longitude -d latitude,0 -d longitude,0 http://thredds0.nci.org.au/thredds/dodsC/u83/modis/oc.mosaics.70/2011/10/29/A20111029.70.austocean.20130813192425.chl_oc3.nc4
netcdf A20111029.70.austocean.20130813192425.chl_oc3 {
dimensions:
latitude = 1 ;
longitude = 1 ;
time = 1 ;
variables:
float chl_oc3(time,latitude,longitude) ;
chl_oc3:_Netcdf4Dimid = 0 ;
chl_oc3:_FillValue = -999.f ;
chl_oc3:long_name = "Chlorophyll Concentration, OC3 Algorithm" ;
chl_oc3:units = "mg/m^3" ;
data:
chl_oc3 = _ ;
} // group /
zender@givre:~$
Hi charlie
Is this also possible to download MODIS HDF files using nco? or only the netCDF files are supported?
thanks
Yes HDF files will work fine so long as netCDF and NCO are built with the appropriate support.
http://nco.sf.net/nco.html#hdf4