| | 90 | To meet the time constraints given above, the plan is as follows: |
| | 91 | |
| | 92 | * Use a stripped-down version of the mobile4D mobile client (for Android) |
| | 93 | * enhance the functionality by the needed report types not supported yet |
| | 94 | * have the client deliver valid CAP directly from the device (the current implementation uses the mobile4D protocol and converts this to CAP server-sided) |
| | 95 | |
| | 96 | The current functionality includes: |
| | 97 | |
| | 98 | * Send hazard reports: |
| | 99 | * filling in needed fields (numbers, contact details, urgency, etc.) |
| | 100 | * detect the current location |
| | 101 | * alternatively give a location and specifying a polygon on a map |
| | 102 | |
| | 103 | * Buffer issued reports and re-send them upon network connectivity. |
| | 104 | |
| | 105 | * Retrieve alerts and display them as list and map. This will most probably not be included. |
| | 106 | |
| | 107 | * Many more communication features that might not be included either. |
