Receiving data from TrapTagger

Supported technology/TrapTagger

wildeyeconservation.org/traptagger

Type Push integration
Direction Data provider
Platform Gundi v2

Setup You, in the portal

TrapTagger sends camera trap detections, with their images, to EarthRanger through Gundi. Each detection arrives as an EarthRanger report.

What you'll receive

We add details here as we confirm what TrapTagger sends. If you know something we're missing, let us know.

Positions No
Alerts and events Yes. Camera trap detections, as the event type traptagger_integration. See TrapTagger Event Type.
Sensor readings No
Photos and files Yes
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

TrapTagger

You will need:

  • TrapTagger Account.

Gundi

You will need:

  • API Key (Steps in this guide).

EarthRanger

1. Create an Integration User

In EarthRanger, create a dedicated user account (e.g., traptagger_integration) for this integration.

2. Create Authentication Token

Create a long-lived token for the user created in Step 1. This token will be used for authentication.

3. Configure Event Type and Schema

Ensure that the required event type and schema exist in EarthRanger. Confirm to the user and/or to Wild Eye the event type name and ID that will be used by the integration.

4. Assign Permissions

Edit the user created in Step 1 and assign the necessary permissions to post event data. Be sure to include permission for the Event Category that contains the event type (from Step 3).

Please refer to EarthRanger's documentation or contact Support.

Configuration

GUIDES

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., "traptagger")

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 Route includes a destination, and review the Route 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.

2.3 Rename your Subjects

Please refer to EarthRanger's documentation or contact Support.

Do you need to use different Event Types depending on the species detected?
If so, just reach out to the Gundi Team to set up the “Route Configuration.”

Other TrapTagger

Sending data to TrapTagger
Back to the integration catalog Need help setting this up? Contact us