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

[python #VOC-640241]: siphon filter_time_nearest : No datasets with times found

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: [python #VOC-640241]: siphon filter_time_nearest : No datasets with times found
  • Date: Tue, 29 Sep 2020 16:46:41 -0600
Greetings!

So for latest/best/full:

Full: the full dataset with two time coordinates: runtime and forecast time. 
This is all of the Grib data available in a single virtual dataset.
Best: the "best timeseries" of the collection dataset, one time coordinate 
(forecast time)
Latest: the most recent single model run

This poster is a good way to visualize the difference between Full and Best:

  
https://www.unidata.ucar.edu/software/tds/current/tutorial/files/FmrcPoster.pdf

Using any one of those provides direct access methods without the need to scan 
through the catalog to match a date string.

Hope that helps,

Ryan

> On Mon, Sep 28, 2020 at 8:53 PM Unidata Python Support
> <address@hidden> wrote:
> 
> > Due to the way the grib collections are structured by the THREDDS Data 
> > Server, you need to use `.catalog_refs` rather than `.datasets`.
> 
> OK ... that works.
> 
> > Also, if you're accessing model data, you just might be better off using 
> > the 'Full Collection (Reference / Forecast Time) Dataset', 'Best GFS 
> > Quarter Degree Forecast Time Series', or 'Latest Collection for GFS Quarter 
> > Degree Forecast' datasets that *are* available within the `.datasets` 
> > attribute.
> 
> OK ... FYI, I don't quite get the latest / best / full thing, but I'll
> work on it ...
> 

Ticket Details
===================
Ticket ID: VOC-640241
Department: Support Python
Priority: Low
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.