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

[netCDF #RVK-949505]: in.nc on Unidata DAP server?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #RVK-949505]: in.nc on Unidata DAP server?
  • Date: Tue, 24 May 2011 15:52:39 -0600
I figured out how to properly generate
an NC_ECANTREAD error (equivalent to the missing
NC_ENOFILE) when the dap url
is accessing data that does not exist.

So now, the rule is roughly:
1. if the url does not exist: return NC_ECANTREAD
2. if the server returns other kinds of errors,
   then return NC_EDAPSVC.
3. If the server returns a response, but it is
   malformed, return NC_EDDS (or DAS, etc).
=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: RVK-949505
Department: Support netCDF
Priority: Critical
Status: Closed