Hi there,
I'm new to the group and pydap.
In playing with the server (Pydap-3.1.RC1), I'm finding differences between the behavior of a raw netcdf file and that same file served through pydap.
For example the dimensions look incorrect:
(using netCDF4==1.0.4)
Using the pydap server, projection and maxStrlen64 show up as dimensions, which doesn't seem right.
>>> y.dimensions
OrderedDict([(u'maxStrlen64', ), (u'projection', ), (u'time', ), (u'xgrid', ), (u'ygrid', )])
>>> len(y.dimensions)
5
>>> z.dimensions
OrderedDict([(u'xgrid', ), (u'ygrid', ), (u'time', )])
>>> len(z.dimensions)
3
As a result of this, none of the CF aware clients, panoply, idv, etc. are able to plot the data from these files.
Is this likely a bug with the netCDF handlers, or is it expected behavior and I will need to write separate handlers to provide the data in a CF compliant manner?
Thanks
Matt Savoie
NSIDC