| | 1 | == Real-Time Tracking == |
| | 2 | |
| | 3 | This is proposed to be done using the [wiki:BluePrintGISSOSLayers SOS Layer]. |
| | 4 | |
| | 5 | ==== Model ==== |
| | 6 | Storing different positions of objects (and some other dynamic information) related to time into the database (first/past/current/forecasted |
| | 7 | positions) |
| | 8 | |
| | 9 | ==== View ==== |
| | 10 | Display position tracks of objects or object groups on maps, additionally indicate or link other data (such as speed and course, or even |
| | 11 | non-discrete such as triage/recovery status, member count in groups, free-text, wiki-text, or other URL) |
| | 12 | |
| | 13 | ==== Backend ==== |
| | 14 | Take up position data of the objects in real time and update the database. This may be multiple controllers |
| | 15 | |
| | 16 | ==== Client system ==== |
| | 17 | Capture and send real-time position/object data to the backend (e.g. from a mobile phone), this could happen via HTTP, URL |
| | 18 | (RESTlike controller), SMS, E-Mail, file transfer (CSV or XML), or other/multiple methods - but should be as easy, portable and reliable as |
| | 19 | possible. |
| | 20 | |
| | 21 | * Example UI: http://www.opengts.org |
| | 22 | |
| | 23 | ---- |
| | 24 | [wiki:BluePrintGeographicInformationSystems GIS BluePrints] |
