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

[THREDDS #PXS-613580]: issue reading TDS file in 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 #PXS-613580]: issue reading TDS file in OPeNDAP
  • Date: Tue, 26 Jul 2016 10:30:26 -0600
Thanks for the reminder.
Periods in opendap names technically must be escaped.
The reason it works here is because it is in the DAS
and there is no ambiguity.
Unidata and Opendap have both deliberately interpreted the
spec a bit loosely.
In practice, the only place where escaping is required is if
an opendap name containing periods appears in a constraint expression.

p.s. I am surprised that NCO has problem with this.
My assumption is that NCO is accessing this thru the netcdf-c
library, and periods are legal in netcdf identifiers.
You might check with the NCO people. There may be a separate
bug in NCO or netcdf-c that needs to be addressed as a separate
issue.

=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: PXS-613580
Department: Support THREDDS
Priority: Normal
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.