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.
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.
>Date: Thu, 22 Oct 1992 09:47:44 -0700
>From: Joe Sirott <sirott@xxxxxxxxxxxxxxxxxxxx>
>To: netcdfgroup@xxxxxxxxxxxxxxxx
>Subject: Re: Coordinate mapping conventions...
In the above message, Joe Sirott wrote:
>It seems to me that support for components and data to coordinate mapping
>can be solved by adding a small extension to the netCDF language. Why not
>add support for something analogous to C structures. For instance, we might
>have the following definition:
>
> float u(lat,lon,depth);
> float v(lat,lon,depth);
> float w(lat,lon,depth);
> struct velocity { u,v,w };
When performing I/O, would the above structure be dimensioned
[lat,lon,depth,3] or [3,lat,lon,depth]?
--------
Steve Emmerson <steve@xxxxxxxxxxxxxxxx>
netcdfgroup archives: