| | 4 | |
| | 5 | == Current Status == |
| | 6 | |
| | 7 | [https://docs.google.com/spreadsheets/d/1N9xUqZQhignq7QM_7CtrV4zv86sq4lMdJj81IQuch3Y/edit?usp=sharing Fit-Gap analysis spreadsheet] |
| | 8 | ==== Available features: ==== |
| | 9 | |
| | 10 | ==== Missing features: ==== |
| | 11 | 1. built on the Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) version 1.2 '''[1]''' |
| | 12 | 1. manage templates, manage messages [[BR]] |
| | 13 | 1. manage CAP Profiles (multiple languages, identifier format, etc) in ../cap/000_config file |
| | 14 | 1. receive CAP feeds '''[2]''' to serve as an aggregator and a pubhub |
| | 15 | 1. approve or reject a CAP message prior to dissemination |
| | 16 | 1. delivery options: HTTP, RSS/Atom, SMS, Email, FTP (dynamic labels) |
| | 17 | 1. visualize CAP feeds on a map ("common operating picture") |
| | 18 | 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) |
| | 19 | 1. subscription management (who, what, when, and where) serve as a subhub |
| | 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 |
