ncks -a -4 -O --mk_rec_dmn time -d time,1992-03-16T11:10:00.000Z,1992-03-16T11:10:00.000999Z -d lon,129.0,134.0 -d lat,-34.0,-31.0 -v time,lat,lon,dt_analysis,l2p_flags,quality_level,satellite_zenith_angle,sea_surface_temperature,sses_bias,sses_count,sses_standard_deviation,sst_dtime 19920331111000-ABOM-L3S_GHRSST-SSTfnd-AVHRR_D-1m_dn_Southern.nc
ncks: ERROR User-specified coordinate value range 129 <= lon <= 134 does not fall within valid coordinate range 2.51 <= lon <= -157.51
Looking at this file the defined min/max range for longitude is:
Looks like ncks expects longitude values crossing the anti-meridian to use values in the range 180 -> 360 not -180 -> 180. Do the files need to be corrected or do we need to handle these files somehow?
If I remember correctly, the first file is not correct (not CF) because the dimension should be monotonic. So ncks can't really work. I'll contact Edward.
Looking at this file the defined min/max range for longitude is:
Actual longitude values are:
Compare this to SRS files which can be spatially subsetted e.g. 19950630032000-ABOM-L3S_GHRSST-SSTskin-AVHRR_D-1m_night.nc
Looks like ncks expects longitude values crossing the anti-meridian to use values in the range 180 -> 360 not -180 -> 180. Do the files need to be corrected or do we need to handle these files somehow?