A point on a map tells you where the source determined its position at a particular moment. To use that information in daily work, you need to see that moment. A clear marker without a recording time leaves the main question open: how fresh is the dispatcher’s information?
One point can have several timestamps
Distinguish at least three moments:
- Recording: the source determined and saved the position.
- Receipt: the server accepted the message containing it.
- Viewing: a person opened the map or received an update.
Position age runs from recording to viewing. The difference between receipt and recording shows delivery delay; it does not make the position fresher.
Illustrative example: the phone records a position at 12:40, connectivity returns at 12:48 and the dispatcher views the map at 12:50. The position is ten minutes old, even though the message arrived two minutes ago.
What changes without mobile data
Some applications can continue recording on the device and upload later. That depends on the particular application, permissions, device and recording state. A lack of mobile data alone does not prove either continued recording or a recording failure.
When connectivity returns, older observations may fill in the history. A useful view distinguishes a history update from a fresh position. The last delivered observation is not necessarily the latest by recording time.
An old point does not explain the cause
Position age cannot reliably explain why updates have stopped. Connectivity may be unavailable, the application may have stopped, the device may be unable to determine a position or work sharing may have ended.
A useful interface shows what is known: the last position, recording time, source and available connectivity information. A cause the system cannot establish should be checked with a participant.
How to read a gap in the route
If two observations are far apart in time, a straight line between them does not prove the vehicle’s actual path. It helps to distinguish recorded sections from connections between sparse observations.
When reviewing a gap, ask:
- How much time passed between neighbouring observations?
- Were recordings delivered later?
- Do participant reports add context for this part of the trip?
- Where does an observation end and an assumption begin?
These questions help prevent a gap from becoming a claim about a particular road, stop or driver action.
What to check before a pilot
Ask to see the agreed device handling normal recording, a temporary loss of connectivity, late delivery and the end of sharing. Look beyond the appearance of a marker: review timestamps, history and whether the dispatcher can understand the state.
Choose an attention threshold for position age around your working task. One universal interval can be inconvenient across different routes and connectivity conditions. Establish how missing updates lead to an action by the responsible person.
Cargo Polis is developing a trip view with recording timestamps and recorded routes. Recording and recovery reliability are confirmed for the particular pilot workflow. A permanently fresh position without connectivity is not promised.