Replies: 1 comment
-
I completely agree that having both of these as part of one of the /gridpoints//<x,y> endpoints would be very helpful. For now, if it helps and you're using Javascript I'm parsing the geoJson files provided by the SPC at these locations: GeoJson was an intentional choice for my platform because I could easily parse and process it in the user's browser without needing a KMZ library to deal with unzipping and parsing that format. You can view my parsing code which processes the user's location and polygons to see if there is a hit within any of them. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
First, thanks for all the work y'all do!
I'm working on some projects that would benefit from data being added to the API:
For the categorical convective outlooks, it seems parsing outlook KMZ files may be the best current method (e.g. https://www.spc.noaa.gov/products/outlook/day1otlk_cat.kmz). For risk probabilities, I've used the NDFD endpoint in the past (e.g. https://graphical.weather.gov/xml/sample_products/browser_interface/ndfdXMLclient.php).
Are there plans to add these to api.weather.gov? If not, is there a better way to fetch these?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions