| 11 | | ==== View ==== |
| 12 | | Display position tracks of objects or object groups on maps, additionally indicate or link other data (such as speed and course, or even |
| 13 | | non-discrete such as triage/recovery status, member count in groups, free-text, wiki-text, or other URL) |
| | 10 | === Added Value === |
| | 11 | -Instantaneously access location information of resources on a map |
| | 12 | -Location information in the form of images to put across information cognitively |
| | 13 | -Improve inter-organization and intra-organization co-ordination at the site of incident |
| 18 | | ==== Client system ==== |
| 19 | | Capture and send real-time position/object data to the backend (e.g. from a mobile phone), this could happen via HTTP, URL |
| | 19 | === Affects === |
| | 20 | The developers of Sahana-Eden, requires additional code implementation in Model,View,Backend and Client System(elaborated below) |
| | 21 | |
| | 22 | == User Stories == |
| | 23 | |
| | 24 | -Member of a NGO Emergency Response Team at the site of a flood taking part in rescue operations, enters a perilous zone and immersed in his task does not hear his alert go off, and finds himself in an unfortunate situation. Another member tracking his movements notices this and informs concerned authorities so that necessary directions can be passed down the command structure. |
| | 25 | |
| | 26 | -A volunteer goes offline and is out of reach of all communication efforts from the incident command center, tracker maybe used to review the volunteers last movements while still online and search efforts may begin in the forecasted position zones. |
| | 27 | |
| | 28 | == Requirements == |
| | 29 | |
| | 30 | === Functional === |
| | 31 | -Use GeoFencing to trigger notifications when users enter perilous zones. |
| | 32 | |
| | 33 | -Authorize user check permissions to allow viewing of tracking details (If making use of existing framework no work is required but in case of writing custom functions to access the database, relevant framework functions maybe used to maintain security) |
| | 34 | |
| | 35 | -Add a function to modules/s3/s3gis.py or static/scripts/s3.gis.js to generate forecasted position |
| | 36 | |
| | 37 | -Take up position data of the objects in real time and update the database. This may be multiple controllers |
| | 38 | |
| | 39 | -Capture and send real-time position/object data to the backend (e.g. from a mobile phone), this could happen via HTTP, URL |
| | 46 | -Enable users to check-in/check-out through SMS refer to http://eden.sahanafoundation.org/wiki/UserGuidelines/Messaging |
| | 47 | === Non Functional === |
| | 48 | -Store different position-related data like average speed,current position,past position(before a certain time interval),approximate direction of movement |
| | 49 | -The framework required to store position along with timestamp is present here.[https://github.com/flavour/eden/blob/master/modules/s3db/gis.py#L95 ] |
| | 50 | |
| | 51 | -All other attributes are to be made part of a different table which can then be made a 'component' of the main table here http://eden.sahanafoundation.org/wiki/S3/S3Model/ComponentResources |
| | 52 | |
| | 53 | -Documentation |
| | 54 | |
| | 55 | == Design == |
| | 56 | === Technologies === |
| | 57 | -Python |
| | 58 | |
| | 59 | -Web2Py Framework |
| | 60 | |
| | 61 | -Jquery |
| | 62 | |
| | 63 | -OpenLayers (For advanced features) |
| | 64 | |
| | 65 | == Future Extensions == |
| | 66 | -Enable the use of TimeSlider proposed in another GSOC Project |
