Supported technology/Animal Tracking
| Type | Push integration |
| Direction | Data provider |
| Platform | Gundi v2 |
AWT collars send their positions to EarthRanger through Gundi. Positions show up as tracks on the map.
What you'll receive
We add details here as we confirm what AWT sends. If you know something we're missing, let us know.
| Positions | Yes |
| Alerts and events | Not documented yet |
| Sensor readings | Not documented yet |
| Photos and files | No |
| Past data | Not documented yet |
How this integration works
This is a push integration. The data provider sends data to Gundi whenever it has something new, on its own schedule. Gundi passes each piece on to your destination as soon as it arrives.
Who's involved
- You create the Route in Gundi and share its API key with the data provider.
- The data provider turns on sending to Gundi with that key.
- Your destination, for example EarthRanger, is where the data shows up.
- Gundi support helps only when the setup badge at the top of this page says so.
Historical data
Gundi passes on whatever the provider sends, old or new. Gundi can't ask the provider for past data, so if you need history, ask the provider whether they can send it again.
When data doesn't show up
Gundi doesn't check the provider for new data; it waits for the provider to send it. If nothing arrives, check with the provider first that they are sending, then look at your Route Activity Logs.
How often data arrives
That depends on how often the provider sends it. Some send each reading right away, others in batches every few minutes or hours.
Prerequisites
AWT
You will need:
- AWT Account.
EarthRanger
To send event 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 our Support team. -
A long-lived token for authentication assigned to the user created in the previous step.
Please refer to EarthRanger's documentation or contact our Support team.
Configuration in Gundi
1. Gundi Connection Settings
1.1 Visit our portal.
1.2 On the Routes page, click Create Route.
1.3 Under What would you like to connect?, search for your technology, select it and click Next.
1.4 Under Route details, enter a Route Name (e.g., “TechnologyName - AreaName”).
1.5 Choose the Route Workspace.
1.6 Click Create Route. Gundi creates the Route and opens its flow map.
1.7 Click Add destination on the flow map and select a destination. Please consult our guides.
1.8 Click the data provider node on the flow map and open Connect → Push API key.
Under API key, click the copy
icon. Only workspace admins can see and copy the key.
1.9 Under Send data to this Route, choose what the provider will send (Observations, Events or Events with attachments) and copy the Endpoint. Send the API key, the endpoint and your account identifier to your contact at the data provider, and ask them to set up an integration with Gundi. If you have access to their system, you can enter these settings there yourself.
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., "awt")
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.
2.3 Rename your Subjects
Please refer to EarthRanger's documentation or contact Support.
Other Animal Tracking
| Argos | Advanced Telemetry Systems (or ATS) | Ceres Wild |
| digitanimal | Ecotopia |
| Back to the integration catalog | Need help setting this up? Contact us |
