Troubleshooting Tracks, Trips and Odometer issues
- I track slow-moving vehicles: the tracking points data is not accurate.
- The distances displayed on screen don't match the report
- Event Rules always use unfiltered data to generate the events.
- Reports use always filtered data to display the data.
- Track filters are a set of rules that removes bad GPS data that the device has sent to the server. These rules will generate filtered tracks in your application.
- Filtered tracks are shown by default.
- Activate the filter reader. This should be the default value. The filter should only be deactivated for troubleshooting.
|Tracks with filter deactivated||Tracks with filter activated|
- Change the filter type according to the device usage: eg. for slow-moving vehicles/persons or city driving.
- Change the Trip Definition to the default value GPS Movement or a valid input.
- The Trips are displaying 0 km/miles when they should display higher values.
- Trip and Idle reports are showing wrong distance values (ex. 0 km/miles) on each trip.
- The trip definition defines the trip and idle of a vehicle.
- The default trip option is GPS movement which is based on the vehicle's speed.
- Verify which is your trip definition.
- If you are not using the default value (GPS movement), verify that you receive the signal of that input, for example, by adding that input as a column in your track points or by analyzing the terminal.
- The tracks distances are too high or do not look real
- After changing the device odometer the GUI and the report still showing the same distance
- There are two types of odometers in GpsGate: the device odometer and the server odometer.
- Not all GPS trackers have a built in odometer.
- If your device is compatible with its own odometer, you can select it in the Device Mapper of that device.
- If no device odometer is selected, the default server odometer will be used.
- Odometers are used in Event Rules, certain reports such as Trip and Idle, Dashboards and in the Driver Journal plugin.
- If you change the odometer, you need to reprocess your tracking data to recalculate the values.
- If you have changed the default odometer setting from the Device Mapper, verify you receive the right Odometer values looking into the Status panel or by analyzing the terminal.