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.
The NetCDF files we have make use of many conventional (NetCDF defined) and unconventional (we made them up) global attributes. The NetCDF manual states that generic/third-party NetCDF applications use the conventional attributes. I have found some applications that will not recognize a NetCDF file if it has unconventional attributes (Envision from NCSA for example). Is this a common problem with generic applications? If there are any plans to use generic NetCDF applications, should home-made attributes be avoided? My immediate thought would be that if an application sees an attribute that it doesn't recognize, it can be ignored by that application. Is this not possible with global attributes, or are generic apps not programmed well enough do perform this? Thanks, ----------------------------------------------------------------------------- | | | _ | Tom Glaess ______________|_( )_|______________ tgl@xxxxxxxxxxxx o +|+ [ ( o ) ] +|+ o *[_]---[_]* -----------------------------------------------------------------------------
netcdfgroup
archives: