Skip to content
  • There are no suggestions because the search field is empty.

Inspect Raw GPS Data and Tracker Self Check

Review source GPS uploads, timing, accuracy and tracker health when investigating a location or reporting issue.

Use Raw GPS Data to inspect the source location records behind Map playback, journeys and other reports. It can help you distinguish inaccurate location data from a delayed mobile-network upload. Use Tracker Self Check for a current hardware diagnostic summary when the selected tracker supports it.

Choose the right check

Was a location recorded at the expected time?
Raw GPS Data: compare Recorded At, coordinates and nearby rows.

Did the tracker record a point promptly but upload it later?
Raw GPS Data: compare Recorded At, Uploaded At and Upload Delta.

Was GPS or mobile reception poor around an incident?
Raw GPS Data with Include extra tracker details enabled. The on-screen option is labelled Include metadata.

What is the tracker's current diagnostic state?
Tracker Self Check, when available for that hardware.

Before you start

Note the vehicle, affected date and approximate time. Use the shortest date range that includes several points before and after the event; one row by itself rarely provides enough context.

Recorded At is when the tracker created a point. Uploaded At is when Track My Ride received it. Always use Recorded At when deciding where the vehicle was at a particular time.

Raw data includes coordinates and technical details about tracker activity. Treat it as sensitive location information. Export only what you need and share it only with authorised people.

Steps

Run the Raw GPS report

  1. Open Reports > Raw GPS Data.
Raw GPS Data report tab showing date and vehicle filter controls.
Raw GPS Data report tab showing date and vehicle filter controls.
  1. Select a short date range around the issue.
  2. Select the affected vehicle. Avoid All vehicles and devices unless you need a fleet-wide result.
  3. Open Options and enable Include metadata when you need extra GPS, mobile-network, ignition or sensor details. Apply a zone filter only when you intentionally want to leave out points outside those zones.
  4. Select Run Report and confirm that the expected vehicle and recorded times appear.
Raw GPS Data results showing example recorded and uploaded times position speed accuracy power ignition and metadata.
Raw GPS Data results showing example recorded and uploaded times position speed accuracy power ignition and metadata.

Investigate a location or delay

  1. Find the row nearest the incident using Recorded At.
  2. Compare it with several rows before and after it. Look for a repeated pattern rather than treating one unusual value as conclusive.
  3. Compare Recorded At with Uploaded At. A much larger Upload Delta than surrounding rows can indicate that the tracker stored data until mobile coverage returned.
  4. Select the latitude and longitude link to inspect that recorded position on a map. Coordinates are more useful for diagnosis than the nearest displayed street address.
  5. Compare speed, bearing, satellite count and power with nearby rows. A sudden change confined to one row is different from a sustained pattern.
  6. When metadata is included, expand the row with its green + control and compare GPS status, network signal, ignition state and trigger event.
  7. Replay the same period on Map. Raw GPS shows the recorded table data; Map playback shows how those points appear in context.

Understand the main columns

Use these values as diagnostic clues, not guarantees. The expected result can vary with the tracker model, configuration, vehicle electrical system, installation and operating conditions.

Recorded At
Time the tracker created the location record. Use this for the event timeline.

Uploaded At
Time Track My Ride received the record. This can be later when mobile coverage is weak or unavailable.

Upload Delta
Difference between recorded and uploaded time. A few seconds is common. Compare longer delays with surrounding rows before attributing them to coverage.

Lat, Lng
Recorded latitude and longitude. Select the coordinates to inspect that point on a map.

Speed
GPS-derived speed at the recorded time. Compare an unexpected value with nearby points and their accuracy.

Bearing
0° or 360° is north, 90° east, 180° south and 270° west.

Accuracy
The report presents the number of satellites used. Four is the minimum for a GPS position; 8–12 is generally stronger. Satellite count alone does not guarantee an accurate point.

Power
External supply voltage reported by supported hardware. Interpret it against the vehicle's nominal voltage, whether the engine was running and the tracker model.

Ignition
On/off state detected by the configured ignition source. It may not match the key position if engine detection is configured incorrectly.

Compare power readings from the same vehicle while parked and running rather than applying a universal voltage threshold. Battery chemistry, load, temperature, charging strategy and vehicle design all affect voltage. Use the vehicle manufacturer's specifications and a qualified technician for electrical diagnosis.

Understand the extra tracker details

These extra details vary by tracker model and setup. A blank or missing field does not by itself mean that the tracker has a fault.

Trigger Event
Why the tracker created the point, such as normal recording or an ignition-related event.

GPS Status
Whether the tracker reported a GPS position fix. Compare it with satellite count and nearby records.

Network Signal Level
Mobile signal reported on a 0–5 scale. Lower values can coincide with delayed uploads, but compare them with Upload Delta.

PDOP / HDOP
GPS positioning-quality scores based on the available satellites. Lower values generally indicate a stronger calculation. Do not use one universal pass/fail number; compare nearby records from the same tracker.

Ignition State / Ignition Input
The interpreted ignition state and, where supported, the electrical input used to determine it.

Movement Sensor / Deep Sleep
Whether the tracker detected movement or reported a power-saving state.

Digital inputs and outputs
States reported by connected sensors, switches, relays or other configured accessories.

External / internal battery
Vehicle supply and tracker backup-battery readings where supported.

Network / operator
Mobile technology and operator information reported by the tracker.

iButton ID
Driver ID key detected by hardware configured with a compatible reader.

GPS point frequency varies by tracker model, settings and operating state. Compare the observed interval with the selected tracker settings; extra points can also be triggered by events such as ignition changes.

Run Tracker Self Check

  1. Open Reports > Tracker Self Check.
  2. Select the affected tracker and run the check.
  3. Review the reported diagnostics together with recent Raw GPS rows. A current self check does not describe every condition that existed at an earlier incident time.
  4. If the tab or tracker is unavailable, the hardware or account may not support this check.

Export or schedule the report

After running the report, select Export and choose an offered format. Use CSV when you need to sort or compare rows in a spreadsheet; use PDF for a fixed, readable copy. Check the active date and vehicle filters before sharing the file.

Use Schedule only when recipients have an ongoing need for the location data. Review the recipients, vehicles and delivery frequency carefully because scheduled reports can expose sensitive movement history.

What happens next

The comparison should tell you whether to investigate GPS reception or installation, mobile coverage and delayed uploads, ignition configuration, external power, or only the way a point appears in Map playback. Keep the vehicle name, account timezone and exact Recorded At times when asking Support to review the same records.

Troubleshooting

  • If no rows appear, confirm the vehicle, date range, account timezone and any zone filter. Then widen the range. No rows means there are no records matching the current filters.
  • If the extra details are absent, run the report again with Include metadata enabled. Some fields remain unavailable on trackers that do not report them.
  • If Uploaded At is much later than Recorded At, compare several nearby rows and the mobile-network details. The recorded timestamp still represents when the location was captured.
  • If one point appears inaccurate, compare its coordinates, satellite count and extra details with nearby points before changing settings or tracker placement.
  • If ignition does not match vehicle operation, review the configured engine-detection method rather than assuming the Raw GPS row is incorrect.
  • If Tracker Self Check is unavailable, confirm that the selected tracker is supported.
  • If exported times appear unexpected, compare them with the account timezone and the on-screen report before treating them as delayed uploads.