[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #JZN-949284]: NC_CHAR coordinates via DAP


The netcdf dap code supports NC_CHAR (modulo bugs, of course).
The transparency issue is tricky. If you mean does the result coming
out of the netcdf dap code look the same as the original .nc file,
then no. The two versions will vary in a number of ways because the mapping
into dap and then out of dap is not completely transparent.

One place in particular where this occurs is when the dap uses its string type
(look at this url in your browser

Since netcdf-3 has no string type, the string is converted to an NC_CHAR array.
The string as stored in that array may be truncated.

There is an additional problem with the data set your provided.
If you do a wget on this url:
you will get this:
Dataset {
    String fl_dmn[fl_dmn = 3];
} testdods/in.nc;

Error {
    code = 500;
    message = "[C cannot be cast to [Lopendap.dap.BaseType;";
So indeed, the data is not readable. That error is coming from the server.
Why that error occurs, I do not know yet.

Other, non-string data is apparently readable.

=Dennis Heimbigner

Ticket Details
Ticket ID: JZN-949284
Department: Support netCDF
Priority: Normal
Status: Open

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.