Changes between Version 10 and Version 11 of BluePrint/CAPMobileApp
- Timestamp:
- 01/17/16 21:57:03 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/CAPMobileApp
v10 v11 67 67 68 68 == Current Implementation == 69 {{{#!comment 69 70 <Leave open for a list of existing implementation of this solution in Sahana Eden:> 70 71 <*a brief description of the implementation (date/time, name, design options chosen)> … … 73 74 <*links to case studies> 74 75 <*short analysis of achievements/problems> 76 }}} 75 77 76 Step 1. Test the current SAMBRO GUIs for its responsiveness to mobile 77 handhelds. If necessary suggest some GUI tweaks to harmonize the 78 desktop version with the mobile screens. 78 Currently, there is no implementation within Sahana Eden. 79 79 80 Step 2. Design hazard specific alert authoring and issuing GUIs. For81 example, Alerting Authorities, in a local area (Barangay,82 Gramaniladari, Thaluk, etc) do not need the full CAP message but a few83 attributes like the area and water level. We will target on delivering84 3-5 mobile GUIs for Landslide, Flood, Accident,85 86 Step 3. Develop the requirements/design for using the concept of87 Pictographs in Alerting and other features such as a wake up function88 to sound an Audible Alarm etc. I think we should do the same with the89 web GUI such that we can set a siren audio to sound for a specific90 warning_priority threshold.91 92 We may have to look for funding outside of the ESCAP project for step 3.93 80 94 81 == Planned Implementation ==