Skip to content

Integration: WatchDuty app alerts#175

Open
chrisdavis2110 wants to merge 2 commits intoagessaman:devfrom
chrisdavis2110:watchduty
Open

Integration: WatchDuty app alerts#175
chrisdavis2110 wants to merge 2 commits intoagessaman:devfrom
chrisdavis2110:watchduty

Conversation

@chrisdavis2110
Copy link
Copy Markdown

I found a public API for the WatchDuty app. I have it set up so that it polls the API at a configurable time (default 5 min) within a bounding box and sends messages when it finds new events. You can set a single channel where all the messages are sent, but with WatchDuty sending a lot of reports for a single fire, and if there are multiple fires going at once, it gets overwhelming, so I also included a "feed" channel and a "report" channel. The feed channel just gets stats (Fire name | acreage | containment % | location | link to fire) as the acreage or containment gets updated. The reports channel gets the notifications of the detailed reports WatchDuty sends out (example: Carbon Fire: The Red Cross is staffing a care and reception center at the Chino Hills Community C... | https://app.watchduty.org/i/95436).

I've also added two commands: fire and evac. Fire with no args returns a list of active fires. Fire with either the list number, fire name, or fire id will return the stats of the fire. Evac is similar to fire, but lists the evacuation info for the fire. Still need to test that more, just waiting on more big fires to happen.

Feed channel:

IMG_6933

Report channel:

IMG_6932

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant