Visibility Hub can confirm stop visits in two main ways:

Scenario: A stop visit was only confirmed by an event (case 2 above) and the vehicle, based on GPS data, is not close by.

--> Stop visit was already triggered, but no GPS data is available for this stop, this warning is shown incl. all affected stops.

In practice that means: GPS data was received for some part of the transport, but not all stop visits were confirmed by GPS data.

Note that if no GPS data was received for this transport at all and the stop visits were just confirmed by events, this warning will not be shown.

The GPS data provider should investigate what the underlying problem is: Either GPS data was provided too late, sending stopped too early or both. Depending on how GPS data is provided (for an overview, see here), different resolutions will apply:

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 "real time aspect" of the tracking services that we provide might suffer: ETA can be incorrect or misleading when the actual stop visit was triggered by an event and not the GPS data. Also, the vehicle locations can't be seen for all the route and especially near or at the stop, where it's usually most important. Depending on your use case, this might be of higher or lower importance.