Hi folks,
I downloaded a daily snapshot version of NetCDF 4.1 (4.1-
snapshot2010020100) today and built it with set:
./configure --enable-netcdf-4 --with-udunits --disable-f90 --with-
hdf5=...l --with-zlib=... --with-szlib=... --disable-shared
This seems to be setting "--enable-dap" internally, which is what I
want.
When I read some test NetCDF files off the http://test.opendap.org/
opendap/data/nc/ server, however, it seems that the coordinate
variables are missing. I'm not sure if the files are being served
this way, or if this is somehow the new OPeNDAP software that does this.
For example, if I do an "ncdump -h" on both the "served" file, and a
downloaded version of the file, I get the following:
% ncdump -h http://test.opendap.org/opendap/data/nc/123.nc
netcdf \123 {
dimensions:
i = 2 ;
j = 3 ;
l = 3 ;
maxStrlen64 = 64 ;
variables:
short l(l) ;
char bears(i, j, maxStrlen64) ;
bears:act = "text string\n",
"\t123" ;
bears:acs = -40s ;
bears:acl = 17000 ;
bears:acf = -2.f, 1.f, 0.f ;
bears:acd = -1., 0.75 ;
bears:string_length = 3 ;
short order(i, j) ;
int shot(i, j) ;
float aloan(i, j) ;
double cross(i, j) ;
// global attributes:
:history = "This is an example of a multi-line global
\n",
"attribute. It could be used for
representing the\n",
"processing history of the data, for
example." ;
}
netcdf \123 {
dimensions:
l = 3 ;
i = 2 ;
j = 3 ;
bears_len = 4 ;
variables:
short l(l) ;
int i(i) ;
float j(j) ;
char bears(i, bears_len) ;
bears:act = "text string\\\\012\\\\011123" ;
bears:acs = -40s ;
bears:acl = 17000 ;
bears:acf = -2.f, 1.f, 0.f ;
bears:acd = -1., 0.75 ;
bears:string_length = 3 ;
short order(i, j) ;
int shot(i, j) ;
float aloan(i, j) ;
double cross(i, j) ;
// global attributes:
:NC_GLOBAL.history = "This is an example of a multi-
line global\\\\012attribute. It could be used for representing the\\\
\012processing history of the data, for example." ;
:DODS_EXTRA.Unlimited_Dimension = "k" ;
}
Note that the following two variables:
int i(i) ;
float j(j) ;
are missing from the "served" version of the file.
Is this coming from a difference in the two files themselves, or does
the NetCDF software read them differently depending on whether they
are local or not?
Thanks,
--Mary
