Version 8 (modified by Hemant Kumar Singh, 9 years ago) ( diff )


BluePrint: Crisis Mapping


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 Template: Crisis_Map

Michael Howden from the Sahana Community is able to help mentor this project. If you have any questions, please contact the Sahana Eden Mailing List


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


  • 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



Phase I

* Custom homepage & menu

* Form to upload incidents to the map (using irs_ireport )

  • Due to rise in role of mobile phones for incident reporting, there can be alternative intuitive template of the form for mobile phones. The user should have a way to report incident while he/she is on the move. Camera and GPS can be accessed using a browser and this will increase the accountability of the data.
  • When user is filling the incident for a particular location, recent reports for that location will be displayed on the side. User can select those ones which are reports for the same incident. Initially these connections can be just stored, and after analyzing them we can develop a module which clusters such incidents based on these connections. Research papers on topics like "Crisis Map Mash-ups" and "Emergence of Neogeographic practices for incident reporting" have mentioned the problems current crisis mapping tools face is inability to remove duplicate data. Most tools use number of incoming reports as a measure of incident seriousness, but that is not proving to be effective. This feature will help us in solving this problem.

* Map showing incidents

  • Map will feature different layers for different incidents. User can select which layers he wants to deploy/view.
  • Simple functions will be made to create new layers or customize existing ones and add features to it as this will be the most used feature when deploying templates. The aim is to make inexperienced programmers use this template very easily for faster deployment.
  • On clicking a marker, the information displayed will depend on the user type, whether he is a volunteer looking places where his help maybe needed or a user looking for relief camps. The template will have functions to add user types and select which information should be displayed to which user type.
  • Various functions to give user full control over the customization of the template and map

* Ability to select different icons (See: 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


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)


<Diagrams or Pseudocode>

Site Map

<for User Interface solutions>


<for User Interface solutions>


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>



Note: See TracWiki for help on using the wiki.