This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Michael, > > 2) The variable "lon" has valid_max,min of 90,-90 instead of 180, > > -180. > If you look at the grib example, then you see why we have limited it > to 90,-90, since that’s the range we only cover with the satellite. I just double checked this because I thought I had seen numbers outside of the 90,-90 range when I looked yesterday. If I get every 10th value of "lon" in row 1250: http://gsics.eumetsat.int/thredds/dodsC/mfg15NetCDF/W_XX-EUMETSAT-Darmstadt,VIS+IR+IMAGERY,MET7+MVIRI_C_EUMS_20091031173000.nc.asc?lon[1250][0:10:2499] I see missing data and values between -18,132. Dataset { Float32 lon[lat = 1][lon = 250]; } mfg15NetCDF/W_XX-EUMETSAT-Darmstadt%2cVIS+IR+IMAGERY%2cMET7+MVIRI_C_EUMS_20091031173000.nc; --------------------------------------------- lon[1][250] [0], -999.0, -999.0, -999.0, -999.0, -999.0, -17.62363, -14.456724, -12.102727, ... 126.10272, 128.45673, 131.62363, -999.0, -999.0, -999.0, -999.0 Ethan Ticket Details =================== Ticket ID: DRR-610037 Department: Support THREDDS Priority: Normal Status: Open