Skip to main content

Warning: GPS data missing at stop

When a stop's arrival was confirmed with an event only but not with GPS data.

Florian Ransmayr avatar
Written by Florian Ransmayr
Updated over a month ago

Overview

Visibility Hub can confirm stop visits in two main ways:

  1. GPS based stop visit: Vehicle takes a break at a transport stop

  2. Event based stop visit: Visibility Hub receives events/statuses provided by external systems/platforms/providers, such as arrived or departed

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.

Potential Root Causes

Several factors can cause missing GPS data at a stop. To identify the root cause, investigate the following:

Stop Location Accuracy

If the stop location is incorrect, Visibility might not detect the stop visit by GPS. Despite having built-in features to account for inaccurate address data and nearby GPS pings, not all cases can be captured.

Action: Confirm that the stop location is correct

  • Validate your provided stop address (or if you provide GPS positions directly, verify that these positions are accurate)

  • Check the placement on the map

GPS Data Transmission Issues

Verify that the GPS data was provided consistently, began early enough (before the first stop was visited), and continued for a sufficient duration (until the vehicle left the last stop).

Action: Confirm that there are no issues with GPS data transmission.

Depending on how GPS data is provided (for an overview, see here), different resolutions apply:

  • Direct telematics (GPS) provider connection: Reach out to your provider and report the problem so they can investigate

  • Mobile app: Reach out to our support here

  • Interface (API) connection: Work with your in-house IT department to resolve potential issues. If you still need assistance, reach out to our support team here.

For more details on how Visibility manages stop visit detections using GPS data, see here.

Wrong Or Insufficient Vehicle Allocation

If the wrong vehicle was allocated to the transport, GPS data might be received, but some or all stops will not be visited.

Action: Verify that all correct vehicles involved in the transport were allocated.

  • Compare the license plate(s) shown in Visibility with those recorded in your system.

  • For transports involving multiple vehicles, ensure you've allocated all of them. To learn how, have a look here. In these cases, you might also see the Insufficient tracking data received tracking cancellation reason.

Note: If you're only sending vehicle GPS data from your in-house system to Visibility (without providing license plates), verify you're transmitting the correct data.

Potential Tracking Problems

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.

Did this answer your question?