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

[THREDDS #YSH-159378]: Unable to access NEXRAD data

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 #YSH-159378]: Unable to access NEXRAD data
  • Date: Tue, 18 Jun 2019 16:15:03 -0600
Hi,

Sorry you ran into trouble. Can you try again? Thanks.

Best,

Unidata Support

> Hello,
> 
> I am writing because I have been having issues accessing NEXRAD data this
> week. I am using the same code that I have used in the past to access and
> analyze level 2 data, but this week I am getting the following error:
> 
> HTTPError: Error accessing
> http://thredds-aws.unidata.ucar.edu/thredds/cdmremote/nexrad/level2/S3/2019/06/18/TJUA/TJUA20190618_165900_V06?req=header
> Server Error (500: )
> 
> From my web search, I found out that other users reported this issue in the
> past and it was resolved by restarting the AWS NEXRAD THREDDS server (here's
> an example
> <https://www.unidata.ucar.edu/support/help/MailArchives/thredds/msg02351.html>
> of the same issue reported in the past). I am wondering: are there any
> known issues with the server at the moment?
> 
> I am using this notebook
> <https://nbviewer.jupyter.org/gist/dopplershift/356f2e14832e9b676207> with
> some minor modifications. The error appears after cell #8: data =
> Dataset(ds.access_urls['CdmRemote']).
> 
> Thanks for any help you can provide,


Ticket Details
===================
Ticket ID: YSH-159378
Department: Support THREDDS
Priority: Urgent
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.