Supported technology/Camera Trap
sentinel.conservationxlabs.com
| Direction | Data provider |
| Platform | Gundi v2 |
| Type | Push integration |
| Data | Events |
Sentinel sends camera trap detections to EarthRanger through Gundi. Each detection of a species you choose in Sentinel arrives as an EarthRanger event.
Prerequisites
Sentinel
You will need:
- A Sentinel account, with access to the Sentinel dashboard.
Gundi
You will need:
- A Gundi account.
- A Route using the Sentinel provider, with EarthRanger as the destination (steps below).
EarthRanger
You will need:
- An EarthRanger destination in Gundi for your site.
-
An event type with the value
sentinel_event, created before you connect — see Sentinel Event Type for how to set it up.
Configuration
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. Sentinel Settings
2.1 In the Sentinel dashboard, select which species detections should send an event to EarthRanger.
3. EarthRanger Settings
The following configurations are optional:
3.1. Select the data you want to see in the map.
3.1.1 Log in to EarthRanger as an admin (site.pamdas.org/admin).
3.1.2 Go to
Source Providers.
3.1.3 Select the
Source Provider created for this integration (e.g., "sentinel")
Gundi creates the Source Provider the first time it delivers Sentinel data to EarthRanger, which can take about 5 minutes. If it isn't there yet, check that your Route has a destination, and look in the Route Activity Logs for records showing that Gundi delivered data to EarthRanger.
3.1.4 Click on Subject Details Configuration.
3.1.5 Configure the
additional information you would like to see on the map.
3.2 Assign your Subjects to a Subject Group.
3.3 Rename your Subjects
Please refer to EarthRanger's documentation or contact Support.
Note on Latency
The time it takes for data to appear in your destination system depends on several factors, such as latency introduced by the source, network conditions, and intermediary systems. While these factors may vary, Gundi typically checks for available data at scheduled intervals (approximately every 5 minutes).
If data is not available in your system after this interval, please check the source of the data for its availability. If the issue persists, contact our Support team for assistance.
Characteristics
This is a "Push" type integration, meaning your data provider sends data to Gundi on their own schedule (for example, immediately or every 5 minutes), and Gundi then forwards it right away to the destination specified in your Route.
Only fresh data will be processed by Gundi, but a request can be made to the data provider for historic data.
Screenshots
Other Camera Trap
| ICUServer | TrapTagger | wpsWatch |
| TrailGuard |
| Back to the integration catalog | Need help setting this up? Contact us |