Changes between Version 41 and Version 42 of BluePrint/CrisisMap

06/24/14 06:55:53 (9 years ago)
Hemant Kumar Singh



  • BluePrint/CrisisMap

    v41 v42  
    106106<List of features which could be included, but are outside of the scope of this extension>
     108==Keypoints of Brainstorming session at Barcamp@IOTX 2014 ==
     110The audience of Crisis Map are divided into three categories and their use cases :
     111* Organisations : Situational awareness, Inventory management, catering to requests
     112* Public reporters :
     113- tool for easy and quick reporting (pic upload, location marking on map)
     114- the reporting tool should be designed such that the report should be automatically structured before sending to the database
     115* Population : making requests, seeing resources on map, volunteering, local community communication
     117Problems seen in crisis maps :
     118- Data overload (can be solved by using AI or call center models)
     119- Outdated data
     120- verification of data
     121- multiple requests for same situation from different sources
     122- there is confusion between implementers on the permission level for different types of users
     124New ideas by participants of the barcamp:
     125- There should be focus on improving usability to reduce training time
     126- 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
     127- time to time quick report generation for every volunteer in the field for situational awareness
     128- decision making can be crowdsourced, which will help in quick decision making
     129- people should be able to report by SMS also (or maybe tweet the situation through SMS)
     130- 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.
     131- 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 should come before asking for location. Such kind of click UI will also help in having a structured report.
     132- 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.
     133- 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.
    108137== Outstanding Questions ==
    109138<Questions about the features or design that haven't been (and need to be) answered>