loadGrid returns an exception ucar.ma2.InvalidRangeException: Number of ranges in section (2) must be = 0.
Am I using the loadGrid command correctly? This exception occurs in Version 1.6 beta 1 build date 2015-07-20. It also occurs in McIDAS-V 1.5 stable version.
I am able to reproduce the problem. I did run the file through a CF compliance checker and there are some errors. I did note that I can load the data through the GUI. Both the GUI and background should work identically. If you get a chance, please see if you can correct the NC compliance errors and again try to display the data using loadGrid.
I have created inquiry 2127 to evaluate the problem.
Agreed that if the files work via the GUI, the system should allow them via background.
In theory, the DOE files can still change to be more CF complaint, but getting those changes in gets more difficult with each passing round of reviews.
I am aware of the issues with loadGrid and the ABI DOE files. I wrote some code a few months ago that demonstrates how to get these files loaded from a Jython script, which I attached below and is hopefully helpful. I intend to make loadGrid compatible with the ABI-DOE files using this strategy, but just haven't gotten to it yet. Hope this code is helpful for the time being (be sure to set the filename and filepath appropriately).
Thanks, this does work. Is there a way to pull the data description from loadGrid and the future loadAbiDoe (grid)? (i.e., if I load the 'Rad' field, can I get the description for that field, or will I have to somehow parse that information from listGridFieldsInFile. If so, what is the best way to do this?).
Sorry, I think I have the answer to my question. The resulting object is a MappedGeoGridFlatField, so I will be able to type something like dataGrid=loadGrid(file,**parms) and then use description=dataGrid['info'].