Changes between Version 46 and Version 47 of BluePrint/CrisisMap


Ignore:
Timestamp:
06/24/14 13:10:08 (11 years ago)
Author:
Hemant Kumar Singh
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/CrisisMap

    v46 v47  
    2323* [http://eden.sahanafoundation.org/wiki/BluePrint/CAPBroker#Description CAP Broker user story; sepcifically the 5th - ... view the current situation ...]
    2424== Requirements ==
    25 TBC
    26 
    27 ==== CAP Broker requirements ====
    28 
    2925'''The audience of Crisis Map are divided into three categories :'''
    3026* Organisations : Situational awareness, Inventory management, catering to requests amongst other organizational operations
    … …  
    3430* Population : making requests, seeing resources on map, volunteering, local community communication
    3531
     32==== CAP Broker requirements ====
    3633* 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].
    3734* 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]