I’ve had a couple requests over the past few months to add a webservice to my WeatherAlerts project, the code for this is now functional (and working quite well) but I’m doing some testing with it before I release the new version. If you’d like to experiment with the webservice you can either run an instance yourself (three lines of code to get up and running) or use my reference/test implementation. The new feature is on the development branch of WeatherAlerts on github and you can find the documentation for it here.
If you’d like to try out a live instance, you can experiment with mine which is located at http://wxalertws.zebpalmer.com/ take a look at the documentation for how it works, but currently there are only two endpoints. First hitting http://wxalertws.zebpalmer.com/all will give you json output of all active alerts in the US. If you want to get just your own area’s alerts, look up your SAMECODE and query the API like so: http://wxalertws.zebpalmer.com/samecodes/016027,016001 replacing those samecodes with one or more samecodes that you care about.
The data is downloaded from the National Weather Service CAP Emergency Alerts Feed via my WeatherAlerts python package and it’s updated every minute. I’ll leave this running for my own experimentation and use in my own automation projects (instead of running multiple instances of WeatherAlerts) so feel free to use if for tinkering. But standard disclaimer applies, DO NOT DEPEND ON THIS FOR IMPORTANT STUFF (including but not limited to your continued existence). Your primary source of data and alerting should be the National Weather Service and NWS Radio.
You may ask why I’m adding a webservice to WeatherAlerts when the NWS already provides a XML/CAP feed…. 1) because I am already parsing that feed via WeatherAlerts, adding a simple queryable WS API was easy, I’ll be adding other queryable fields soon 2) I hate XML 3) I’ve had several requests for it