Changes between Version 45 and Version 46 of BluePrint/CrisisMap


Ignore:
Timestamp:
06/24/14 13:09:29 (7 years ago)
Author:
Hemant Kumar Singh
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/CrisisMap

    v45 v46  
    2626
    2727==== CAP Broker requirements ====
     28
     29'''The audience of Crisis Map are divided into three categories :'''
     30* Organisations : Situational awareness, Inventory management, catering to requests amongst other organizational operations
     31* Public reporters :
     32 - tool for easy and quick reporting (pic upload, location marking on map)
     33 - the reporting tool should be designed such that the report should be automatically structured before sending to the database
     34* Population : making requests, seeing resources on map, volunteering, local community communication
     35
    2836* The CAP Broker should reuse available code from the crisis mapping project to serve its purpose of offering [http://eden.sahanafoundation.org/wiki/BluePrint/CAPBroker#Description multi-agency situational-awareness features].
    2937* To keep the situational-awareness simple, the CAP Broker must leverage certain interactive controls for [http://eden.sahanafoundation.org/wiki/BluePrint/CAPBroker#Visualization alert visual analytics]
     
    6371
    6472'''* Allow requests & tasks to be generated and linked from incidents'''
     73
     74'''New ideas by participants of the Sahana Barcamp @ IOTX 2014 :'''
     75- There should be focus on improving usability to reduce training time
     76- there should be inter organization communication. Every organization should be aware of other organization activities. This would help in better allocation and deployment of help/resources
     77- time to time quick report generation for every volunteer in the field for situational awareness
     78- decision making can be crowdsourced, which will help in quick decision making
     79- people should be able to report by SMS also (or maybe tweet the situation through SMS)
     80- the location data should also have data source ( GPS or wifi location or tower triangulation) which will help in separating accurate information. This will help in decision making for organizations as accurate data is high priority data.
     81- the number of steps for reporting should be minimized. For mobile devices we can have a simple click UI where by few clicks user can report a situation (this will also have optional field of description in the end)It will also matter which questions are being asked by the user first. e.g. Asking for type of disaster and photos should come before asking for location. Such kind of click UI will also help in having a structured report.
     82- Organizations should be update status for requests in bulk. e.g. by selecting all markers of a particular area by drawing a polygon or circle and then marking them complete.
     83- The data on the map should be aggregated (e.g. heat maps). Aggregated data gives better situational awareness and can play a important role in deploying group of resources.
     84
     85'''Problems seen in crisis maps :'''
     86- Data overload (can be solved by using AI or call center models)
     87- Outdated data
     88- No quick scalable solution for verification of data
     89- multiple requests for same situation from different sources
     90- there is confusion between implementers on the permission level for different types of users
    6591
    6692== Design ==
     
    107133<List of features which could be included, but are outside of the scope of this extension>
    108134
    109 == Keypoints of Brainstorming session at Barcamp@IOTX 2014 ==
    110 
    111 '''The audience of Crisis Map are divided into three categories :'''
    112 * Organisations : Situational awareness, Inventory management, catering to requests amongst other organizational operations
    113 * Public reporters :
    114  - tool for easy and quick reporting (pic upload, location marking on map)
    115  - the reporting tool should be designed such that the report should be automatically structured before sending to the database
    116 * Population : making requests, seeing resources on map, volunteering, local community communication
    117 
    118 '''Problems seen in crisis maps :'''
    119 - Data overload (can be solved by using AI or call center models)
    120 - Outdated data
    121 - No quick scalable solution for verification of data
    122 - multiple requests for same situation from different sources
    123 - there is confusion between implementers on the permission level for different types of users
    124 
    125 '''New ideas by participants of the barcamp:'''
    126 - There should be focus on improving usability to reduce training time
    127 - there should be inter organization communication. Every organization should be aware of other organization activities. This would help in better allocation and deployment of help/resources
    128 - time to time quick report generation for every volunteer in the field for situational awareness
    129 - decision making can be crowdsourced, which will help in quick decision making
    130 - people should be able to report by SMS also (or maybe tweet the situation through SMS)
    131 - the location data should also have data source ( GPS or wifi location or tower triangulation) which will help in separating accurate information. This will help in decision making for organizations as accurate data is high priority data.
    132 - the number of steps for reporting should be minimized. For mobile devices we can have a simple click UI where by few clicks user can report a situation (this will also have optional field of description in the end)It will also matter which questions are being asked by the user first. e.g. Asking for type of disaster and photos should come before asking for location. Such kind of click UI will also help in having a structured report.
    133 - Organizations should be update status for requests in bulk. e.g. by selecting all markers of a particular area by drawing a polygon or circle and then marking them complete.
    134 - The data on the map should be aggregated (e.g. heat maps). Aggregated data gives better situational awareness and can play a important role in deploying group of resources.
    135 
    136 
    137 
    138135== Outstanding Questions ==
    139136<Questions about the features or design that haven't been (and need to be) answered>