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

[THREDDS #IUD-363917]: Another file that is fine locally, but won't read variables if accessed by OPeNDAP

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: [THREDDS #IUD-363917]: Another file that is fine locally, but won't read variables if accessed by OPeNDAP
  • Date: Thu, 18 Aug 2016 13:10:20 -0600
The problem is that the case sensitivity
of DAP2 keywords is not completely defined
in the spec. Type names (e.g. byte etc)
are specifically defined as case insensitive.
The situation with other keywords (e.g. error)
is not defined. So depending on the DDS parser,
the parse may fail or "Error" may be downcased
to "error".

I have asked opendap.org for a ruling on this.

=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: IUD-363917
Department: Support THREDDS
Priority: Critical
Status: Closed
===================
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.