TwoWeeksReady
TwoWeeksReady copied to clipboard
Tsunami Alert Module
Add in Tsunami alerting module.
When the TWC (Tsunami Warning Center) sends out an a tsunami alert that affects the geo location of the user (mostly in WA/OR) send/push an alert to the end user.
Grabbing from [https://www.tsunami.gov/events/xml/PAAQCAP.xml]
- Parsing the XML
- Check if the message has already been pushed
- Storing a new message if needed
- Sending out the notification
**Need to review the XML and see how it defines the alerts (information statement, possible threat, no threat, immediate) This review needs to be a conversation. More to discuss.
The NANOOS app is an example of this working.
?s - Ping @schuback
@schuback, please excuse my ignorance, but where is the message pushed to?
No worries @rfalanga - The tsunami alert should trigger users along any water ways (Washington coast and Puget Sound) and if not able to do that, just ping all users in a larger geographic footprint (Most of Western Washington). Does this help?
@rfalanga - Also, I am not too sure of the capabilities we have available at this time. Happy to discuss more.
I am bringing in @MaximilianDixon as he is part of WAEMD and can help shape discussion.
@rfalanga @schuback It would also be great if we could filter out tsunami warnings from the other three alerts (advisory, watch, and information statement), so that people who just want to receive warnings have that option. Not sure if this is possible.
@rfalanga @schuback Here are the notes from the point of contact for the Nanoos app. “ Our script checks the tsunami bulletin CAP XML every 15 minutes: https://www.tsunami.gov/events/xml/PAAQCAP.xml
From there it is just parsing the XML, checking if we have already processed the message, storing a new message if necessary, and sending out the notification.
The most difficult part for us is converting what is essentially an XML/messaging structure for emergency managers into something more useful for the public. Unfortunately, the XML structure they use doesn't make it easy to determine the threat level for certain categories. For example, an "Information Statement" can either be a "Possible Threat" or "No Threat", but that is not an explicit parameter in the XML, so we have to analyze the message as well to determine the appropriate threat level.”
Thank you @schuback and @MaximilianDixon, your feedback helps. 👍
https://github.com/HTBox/TwoWeeksReady/wiki/Tsunami-Alerting should be updated with a summary of this information.