NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
>From: HANKIN@xxxxxxxxxxxx >Date: Thu, 24 Sep 1992 17:13:13 -0800 >Subject: RE: netCDF conventions >Hi Rich, > >If you get a concise answer to this please pass it along. We have written sty > le >guides for our own interpretation of "nice" based on the netCDF Users' Guide. > > steve > >=================================== > > >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! > > ------- End of Forwarded Message
netcdfgroup
archives: