= !BluePrint: Crisis Mapping =
[[TOC]]

== Introduction ==
Sahana Eden can be used as a Crisis Mapping Platform to allow incidents and other information to be mapped during a crisis. Most of the building blocks for Crisis Mapping are already in place in Sahana Eden, and the goal of this project would be to bring these pieces together in a usable solution. This will allow Crisis Mapping to be integrated into other Sahana Eden solutions. The focus of this project is building an easy to use solution. 

This project will involve developing a custom [DeveloperGuidelines/Templates Template]: {{{Crisis_Map}}}

Michael Howden from the Sahana Community is able to help mentor this project. If you have any questions, please contact the [https://groups.google.com/group/sahana-eden Sahana Eden Mailing List]

== Stakeholders ==
TBC
<Who will be the users of the solution?>
<Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?>
<How will stakeholders be affected?>
Tip: Engage these stakeholders in the development of your !BluePrint.

== User Stories ==
TBC
* A person in the community wants to be able to report the impact of a disaster to get assistance
* An emergency manager wants to be able to view the needs across the community

== Requirements ==
TBC
=== Phase I ===
* Custom homepage & menu
* Form to upload incidents to the map (using {{{irs_ireport}}} )
* Map showing incidents
* Ability to select different icons (See: [wiki:DeveloperGuidelines/GIS])
* Summary Pages for Incident reports & Charts

=== Phase II ===
* Import feeds from different social media platforms (See: DeveloperGuidelines/Messaging)
* Configure feeds to import
* Create incidents from clicking on map points
 * Integrated form to allow easy creation of different types of resources (PoI, Resources, Requests, Tasks, Alerts)

=== Phase III ===
* Analyse Data Over Time 
 * [wiki:BluePrint/GIS/TimePlay]
 * [wiki:BluePrint/TimePlot]
* Allow "voting" to prioritize 
* Control voting by different permissions
* Allow requests & tasks to be generated and linked from incidents

== Design ==
TBC - But having some wireframes for the solution would be useful
<Where relevant include alternative design options>
=== Data Model ===
(e.g. EER or class diagrams)
=== Workflows ===
<Diagrams or Pseudocode> 
=== Site Map ===
<for User Interface solutions>
=== Wireframes ===
<for User Interface solutions>
=== Technologies ===

== Current Implementation ==
TBC
<Leave open for a list of existing implementation of this solution in Sahana Eden:>
<*a brief description of the implementation (date/time, name, design options chosen)>
<*a link to the code>
<*list of deployments of the implementation>
<*links to case studies>
<*short analysis of achievements/problems>

== Planned Implementation ==
TBC
<List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>

== Future Extensions ==
<List of features which could be included, but are outside of the scope of this extension>

== Outstanding Questions ==
<Questions about the features or design that haven't been (and need to be) answered>

== References ==
* Other Crisis Mapping Software:
 * [http://www.ushahidi.com Ushahidi]
* Similar Functionality is described here: BluePrint/SocialMedia

----
BluePrint