TrackSolid Pro

Website: https://www.tracksolidpro.com 

Prerequisites

TrackSolid Pro

You will need:

  • TrackSolid Pro Account, Password, “App Key”, “App Secret”
  • TrackSolid Pro Base URL

EarthRanger

To send movement data to EarthRanger, you will need:

  • A special EarthRanger user (e.g., “Gundi Service Account”) for this integration. Please refer to EarthRanger's documentation or contact Support.
  • A long-lived token for authentication assigned to the user created in the previous step. Please refer to EarthRanger's documentation or contact Support.

Configuration

GUIDES

1. Gundi Connection Settings

1.1 Login to Gundi.

1.2 Click on Create Connection.

1.3 Select TrackSolid Pro.

1.4 Select your Workspace.

1.5 Enter a name for this Connection (e.g., “Vehicle Tracker - AccountName”)

1.6 Configure your TrackSolid Pro account details (User ID, Password, App Key, App Secret, Base URL).

1.7 Click Next.

1.8 Select a Destination. Please consult our guide.

2. EarthRanger Settings

The following configurations are optional:

2.1. Select the data you want to see in the map.

2.1.1 Log in to EarthRanger as an admin (site.pamdas.org/admin).
2.1.2 Go to Source Providers.
2.1.3 Select the Source Provider created for this integration (e.g., "gundi_tracksolidpro_UUID")

The “Source Provider” is automatically created after Gundi successfully retrieves data from this integration and pushes it to EarthRanger. If you don't find it, please ensure your Connection includes a Destination, and review the Connection Activity Logs for additional details. You should see some records mentioning that Gundi successfully delivered data to EarthRanger.
Important Note:  The integration might take 5 minutes to run. Please verify your connection after this period.

2.1.4 Click on Subject Details Configuration.
2.1.5 Configure the additional information you would like to see on the map.

2.2 Assign your Subjects to a Subject Group.

Please refer to EarthRanger's documentation or contact Support.

How location data is delivered

This integration uses two complementary processes to ensure complete GPS coverage.

Near real-time positions are pulled every 2 minutes. Each run captures the latest known location for every device. This keeps the map current but only records one position per device per run — if a device moves multiple times between polls, only the most recent position is captured immediately.

Full track history is pulled twice a day (midnight and noon UTC). Each run fetches the complete movement history for the last 24 hours for every device. This fills in any positions that were missed between real-time polls, ensuring the full route is eventually recorded.

What this means in practice:

  • The map reflects each device's last known position within ~2 minutes.
  • Complete routes and all intermediate waypoints are available within 12 hours at most.
  • There is no permanent data loss — any position not captured in real time will be backfilled by the next track history run.

Example: a vehicle that makes 10 stops between 8:00 and 8:10 AM will show its 8:10 position on the map by 8:12 AM. All 10 stops will appear in the full track by noon.

 

Data Provider,  Vehicle Tracking, Movement Data, Pull Integration
March 24, 2026