Visibility Hub can confirm stop visits in two main ways:

Scenario: A stop visit is triggered based on an event (case 2 above) and later, the vehicle is, based on it's GPS data, also coming close to this stop.

--> There is a timing mismatch, which is expressed in this warning. All stops that are effected are mentioned in this warning.

In practice that means: One of the two sources is potentially wrong: Either the GPS data or the event received was not correct, timing or location wise. We recommend investigating what the problem could be by contacting the party who sent the event and/or the GPS data.

To see the event details, head over to the "Log" view in the transport details. When you hover with your mouse over the icon next to the "Arrived to stop" message, you can see the source and the event type.

Given the event details, you can now start further investigation what led to the wrong timing of the event.

For a deep dive into how Visibility Hub manages stop visit detections by GPS data, have a look here.

While the tracking itself might complete and from a first glance, everything looks good, the reported stop arrival and departure times might be wrong. Also, if the timestamps of the conflicting sources are far apart from each other, it can cause a stop arrival to be wrongly marked as "on time", while in reality, it was visited "delayed" and vice versa. This can cause problems at your customer in case they rely on having accurate times to plan or optimize their logistics workflows.