A location is displayed on the map, and it is easy to think that it represents the current location of the vehicle. Positioning may be affected by network, terminal status, or interface latency. The TMS in-transit page should clearly indicate the location, time and data source, and treat no update as a status that needs to be verified.

How to arrange records and operations

Save positioning occurrence time, reception time and positioning quality information. After exceeding the business-agreed interval, it will prompt that the data needs to be updated, and it will not automatically determine that the vehicle is stopped. Transportation nodes can be supplemented by authorized manual confirmation, and manual information and equipment information are identified separately to avoid confusion with the same type of evidence.

The positioning page can display the current location, the latest confirmed transportation node and the estimated arrangement respectively. When a location has not been updated for a long time, the map marker has a clear time, so viewers do not have to open the details to find out that the data has expired. Preserve this information when the interface provides accuracy or positioning type, and avoid over-interpretation of low-quality data. Historical track playback is arranged by occurrence time, and the current status is judged by valid new records. Manual confirmation of arrival requires the source to be stated, and cannot be disguised as equipment collection results and written back to the track.

Specific scenarios that need to be checked

For example, when the positioning interface is interrupted and resumes uploading historical tracks, the test cannot allow old points to cover newer locations. The arrival judgment also needs to consider the site scope and business confirmation. The customer service query page presents an interpretable state, allowing personnel to distinguish transportation abnormalities from data abnormalities, reducing miscommunication based on old locations.