The problem is that the file has double lat(lat=94); :standard_name = "grid_latitude"; :long_name = "Latitude"; :units = "degrees_north"; :axis = "Y"; double lon(lon=192); :standard_name = "grid_longitude"; :long_name = "Longitude"; :units = "degrees_east"; :axis = "X"; But standard_name "grid_latitude"; and "grid_longitude" is used for rotated lat lon, see: http://cfconventions.org/standard-names-26.html the CDM is interpreted this as "rotated lat lon" projection, but fails because it needs a grid_mapping. so 1) is this latlon or rotated lat/lon". 2) did original file have these standard_names or did CDO add them? John > It doesn't like the standard_name for latitude and longitude (using ncml > to remove them makes the grid readable). I don't have the ability to > remove them in the workflow, and this seems like a bug. > > Don > > On 5/16/14 3:35 PM, Unidata netCDF Java Support wrote: > > There's confusion somewhere, ToolsUI is looking for a projection instead > > of recognizing the lat lon coords. > > > > -Lansing > > > > On 5/16/2014 12:55 PM, Don Murray (NOAA Affiliate) wrote: > >> New Ticket: why can't this be read as a grid > >> > >> Hi- > >> > >> I have a netCDF file that I created using the Climate Data Operators > >> (CDO) package by subsetting a larger file. The original file can be > >> read into the IDV/ToolsUI, but the subset cannot (is not recognized as a > >> grid). I don't see anything obviously wrong with the file, except that > >> maybe the CDM is getting confused by the use of x and y? > >> > >> Why doesn't the CDM recognize this as a grid? > >> > >> Don > > > > > > > > Ticket Details > > =================== > > Ticket ID: RIZ-451320 > > Department: Support netCDF Java > > Priority: Normal > > Status: Open > > > > -- > Don Murray > NOAA/ESRL/PSD and CU-CIRES > 303-497-3596 > http://www.esrl.noaa.gov/psd/people/don.murray/ > > Ticket Details =================== Ticket ID: RIZ-451320 Department: Support netCDF Java Priority: Normal Status: Open
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.