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

[THREDDS #OKW-963505]: Problem accessing observations on THREDDS 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: [THREDDS #OKW-963505]: Problem accessing observations on THREDDS server
  • Date: Thu, 21 Jan 2016 16:49:14 -0700
Luke,

Thanks for the report.  You're not doing anything wrong, that query should 
work. It's an issue I recently hit while trying to put together some examples.

We're working on the issue currently, and you can track its progress here: 
https://github.com/Unidata/thredds/issues/378

Thanks!

Ryan

> Hello,
> 
> I've been trying to use the Unidata Siphon package for Python to download
> surface observations from the current day from the Unidata THREDDS server.
> Specifically, I'm accessing this catalog:
> 
> http://thredds.ucar.edu/thredds/catalog/nws/metar/ncdecoded/catalog.html?dataset=nws/metar/ncdecoded/Metar_Station_Data_fc.cdmr
> 
> Visiting that page, it tells me that the times when data are available go
> through the current time, and checking the files  there shows me that files
> exist up through the current time.
> 
> However, when I format a query to get observations within a lat-lon box in
> Siphon, it gives me the following error message:
> 
> requests.exceptions.HTTPError: Error accessing
> http://thredds.ucar.edu/thredds/ncss/nws/metar/ncdecoded/Metar_Station_Data_fc.cdmr?var=air_temperature&time_start=2016-01-21T10%3A37%3A36.011117&time_end=2016-01-21T22%3A37%3A36.011141&west=-124.9&east=-66.8&north=49.4&south=24.3&accept=netcdf:
> Requested time range 2016-01-21T10:37:36.011Z - 2016-01-21T22:37:36.011Z
> does not intersect actual time range 2015-11-17T00:00:00Z -
> 2016-01-16T00:00:00Z
> 
> 
> Which is implying that the "actual time range" of data available only has
> data up until five days ago, even though more recent files seem to be
> available on the server.  Am I using the right catalog?  Any thoughts on
> the problem?

Ticket Details
===================
Ticket ID: OKW-963505
Department: Support THREDDS
Priority: Normal
Status: Closed