5 | | == Current Status == |
6 | | |
7 | | [https://docs.google.com/spreadsheets/d/1N9xUqZQhignq7QM_7CtrV4zv86sq4lMdJj81IQuch3Y/edit?usp=sharing Fit-Gap analysis spreadsheet] |
8 | | ==== Available features: ==== |
9 | | 1. built on the Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) version 1.2 '''[1]''' |
10 | | 1. manage templates, manage messages [[BR]] |
11 | | 1. manage CAP Profiles (multiple languages, identifier format, etc) in ../cap/000_config file |
12 | | 1. receive CAP feeds '''[2]''' to serve as an aggregator and a pubhub |
13 | | 1. approve or reject a CAP message prior to dissemination |
14 | | 1. delivery options: HTTP, RSS/Atom, SMS, Email, FTP (dynamic labels) |
15 | | 1. visualize CAP feeds on a map ("common operating picture") |
16 | | 1. Use GIS-based risk assessment techniques to develop predefined (hazard, event, and severity specific) CAP alert area templates\1. delivery options: HTTP, RSS/Atom, SMS, Email, Voice-text (audio) |
17 | | 1. subscription management (who, what, when, and where) serve as a subhub |
18 | | |
19 | | ==== Missing features: ==== |
20 | | 1. Feed in to Google Alerthub '''[3]''' and [http://preparecenter.org/activities/universal-app-program IFRC Universal Hazard App] |
21 | | 1. support multiple language CAP message publication |
22 | | 1. digitally sign the messages |
23 | | 1. Mobile application to server as a publisher and a subscriber |
24 | | 1. Pictographs for Alerting |
25 | | 1. Event specific SOP check list |
| 233 | |
| 234 | == Current Status == |
| 235 | |
| 236 | [https://docs.google.com/spreadsheets/d/1N9xUqZQhignq7QM_7CtrV4zv86sq4lMdJj81IQuch3Y/edit?usp=sharing Fit-Gap analysis spreadsheet] |
| 237 | ==== Available features: ==== |
| 238 | 1. built on the Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) version 1.2 '''[1]''' |
| 239 | 1. manage templates, manage messages [[BR]] |
| 240 | 1. manage CAP Profiles (multiple languages, identifier format, etc) in ../cap/000_config file |
| 241 | 1. receive CAP feeds '''[2]''' to serve as an aggregator and a pubhub |
| 242 | 1. approve or reject a CAP message prior to dissemination |
| 243 | 1. delivery options: HTTP, RSS/Atom, SMS, Email, FTP (dynamic labels) |
| 244 | 1. visualize CAP feeds on a map ("common operating picture") |
| 245 | 1. Use GIS-based risk assessment techniques to develop predefined (hazard, event, and severity specific) CAP alert area templates\1. delivery options: HTTP, RSS/Atom, SMS, Email, Voice-text (audio) |
| 246 | 1. subscription management (who, what, when, and where) serve as a subhub |
| 247 | |
| 248 | ==== Missing features: ==== |
| 249 | 1. Feed in to Google Alerthub '''[3]''' and [http://preparecenter.org/activities/universal-app-program IFRC Universal Hazard App] |
| 250 | 1. support multiple language CAP message publication |
| 251 | 1. digitally sign the messages |
| 252 | 1. Mobile application to server as a publisher and a subscriber |
| 253 | 1. [http://eden.sahanafoundation.org/wiki/BluePrint/Pictographs Pictographs for Alerting] |
| 254 | 1. Event specific SOP check list |