Closed dangoff closed 8 years ago
Since I started writing this up, SPC published the sounding page for 2015-05-18 00Z, and the application is starting correctly now. However, if the SPC issue is a frequent occurrence (I'm guessing it may be?), a fallback option would be nice.
Yeah, I have a fix for that in a local branch I might try to commit today. It's not usually this much of an issue, but it has been in the last couple days I've noticed.
Okay, there's a fix committed to the repository now. Let me know if it helps.
Windows 8.0 Enterprise, just installed SHARPpy 1.2.0 yesterday
Upon trying to run the application tonight:
As was mentioned in [https://github.com/sharppy/SHARPpy/issues/65](issue #65), the application will not start if SPC is in the middle of posting profiles - there's a page there (http://www.spc.noaa.gov/exper/soundings/15051800_OBS/), but it really wasn't there yet, which triggered the HTTP 403 error.
Rather than crashing, is it possible to have the URL fall back to the previous 6-hourly (or 12-hourly) standard synoptic time? In this case, falling back to to either 18Z or 12Z on 2015-05-17, so that the application would still load successfully?