Changes between Version 37 and Version 38 of BluePrint/CrisisMap
- Timestamp:
- 05/04/14 10:24:33 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/CrisisMap
v37 v38 93 93 94 94 Discussed approach: 95 * a form for publishers to register their RSS/Atom feed 95 * a form for publishers to register their RSS/Atom feed in the Sahana-Eden Crisis Map 96 96 * use the msg_rss_channel resource 97 * schedule a Poll of these channels (e.g. like in NYC Prepared)97 * schedule a Poll of these channels to monitor the feed for new content (e.g. like in NYC Prepared) 98 98 * write a Parser (again NYC Prepared has a Parser for the incoming RSS feed, although that converts msg_rss posts to cms_post resources) 99 99 * parse the data into a resource to configure onto the map 100 100 * have a Folder called 'Alerts' & then each RSS feed would be a separate layer within that folder 101 101 * the resource could be simple cms_post of type 'Alert' (which is what TL DRMP uses) 102 * determine the POI values to display in the Crisis Map 102 103 * [optional] create a new event_alert resource (this is planned at some point & can then have an integration built into CAP) 103 104 == Future Extensions ==