netCDF conventions

Part of the driving force behind netCDF is the possibility of writing
applications that access generic netCDF files and operate on them to do
whatever they will.  Graphics applications seem like an obvious
possibility.  However, it is likely that novices (like myself) will leave out
"necessary" attributes or other information that effectively limit that use
of generic applications.  Have there been writings or discussions concerning
what a "well-behaved" netCDF files look like?  If so, I'd like to hear about
it!



  • 1992 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the netcdfgroup archives: