Improve usage of non-standard netCDF(and other format) files

[mug_admin]

On November 17th, a McIDAS-V Brainstorming session was held for all scientists at SSEC and CIMSS. At the session, one basic question was asked of the users: What would you like to see in McIDAS-V?

The following discussion is from that brainstorming session:

Improve ways to use or fix non-standard netCDF (and other format) files (KabaB)

* KabaB said that many of the netCDF and HDF files he receives cannot be read into McV so he spends lots of time trying to fix them to work, typically using ncview and ncdump. He would like to see tools added to McV that make it easier to view/read the data (even if it's missing nav or other components) and easier to "fix" the file. He also pointed out that McV's diagnostic error messages could be much clearer and more helpful.
* TomW agreed that we should improve the diagnostic error messages so it helps the user figure out what the issue is with the file that prevents McV from reading it.
* JonB and others suggested that it might be relatively easy to integrate ncview and ncdump into some type of McV GUI so that if you can't read the netCDF file in McV, it helps you fix it rather than forcing you to go outside of McV to run utilities like ncview and ncdump.
* KabaB and others said that it would be useful for McV to not just error out if it can't read the file, but instead give you an option to display whatever it can for a variable (even if it can't find any nav, etc).
* CaitlinH said that she has used ITT's ENVI software that, if it can't find navigation in the netCDF file, pops up a window that lets the user specify the corner point lat/lons, then displays it with that nav. She said it's very useful for scientists who know the domain but would prefer to specify it in the GUI rather than try to fix the original file.
* TomW said he likes the idea of adding a popup GUI when McV can't read a netCDF file, and having the GUI give three choices: (1) view the parameter as is [without nav, etc], (2) let the user specify the lat/lon points then display it [ like Kaitlyn mentioned], or (3) let the user attempt to fix the file via ncview and ncdump utilities.

[beckys]

There is an inquiry actively being worked on for this, #936 - http://mcidas.ssec.wisc.edu/inquiry-v/?inquiry=936

[kbedka1]

or a 4th option to Tom's comment could be to have the user tell Mc-V the nav, rather than assuming the user knows how to "fix" their file with ncml

[nickb]

Hi Kris. Do you mean, say, the user has a file with variable names like "kris_latitude_13" and "kris_longitude_27" that they want to use to display their data?

I'm thinking something along the lines of a pull-down menu that gives you options to use any of your file's variables for the lat and lon, is that what you had in mind?

[kbedka1]

yes, that is exactly what I was thinking. This would be very beneficial, for both NetCDF and HDF format data. Have Mc-V open the file and present the user with a list of available variables.