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

[THREDDS #HLI-624912]: MRMS Base Ref through Siphon

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 #HLI-624912]: MRMS Base Ref through Siphon
  • Date: Mon, 04 Nov 2019 08:20:57 -0700
Hi!

Can you share the script you've written so far to access the data, just so that 
I can see for sure what you're working with and trying to do? I think we should 
be able to set a tolerance if we can get the data into Xarray format pretty 
easily.

Thanks,
Zach Bruick

> Hi,
> 
> I'm trying to plot MRMS base ref (i.e.
> http://thredds.ucar.edu/thredds/ncss/grib/NCEP/MRMS/BaseRef/MRMS_BaseReflectivity_20191021_0100.grib2/dataset.html)
> via Python's Siphon package. It requires a datetime object as input.
> 
> For most things (model analyses, etc.) this is just the top of the hour.
> For the MRMS it looks like it's not just an even interval of minutes, but
> also a random number of seconds after the minute.
> 
> The first hour I tried plotting had times :10 seconds after the minute, but
> incrementing to the next hour throws an error because that next hour's
> times are apparently :13 seconds after the minute:
> 
> Server Error (400: Requested time 2019-10-21T22:00:10Z does not intersect
> actual time range 2019-10-21T22:00:13Z - 2019-10-21T22:58:13Z)
> 
> 
> The question is... how can I write a script to pull a relevant time without
> knowing what the exact time is (to the second) because the exact time
> constantly fluctuates?
> 
> Thanks,



Ticket Details
===================
Ticket ID: HLI-624912
Department: Support Python
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.