ICUServer

Supported technology/Camera Trap

icuserver.com

Direction Data provider
Platform Gundi v2
Type Push integration
Data Events

Setup You, in the portal

ICU Server sends camera trap images, with the AI detections found in them, and periodic camera status reports to EarthRanger through Gundi. Each one arrives as an EarthRanger event.

Prerequisites

ICU Server

You will need:

  • Cameras registered with ICU Server, and a contact at ICU Server to complete the connection on their side.

Gundi

You will need:

  • A Gundi account.
  • A Route using the API provider, with EarthRanger as the destination (steps below).

EarthRanger

You will need:

  • An EarthRanger destination in Gundi for your site.
  • The Camera Trap (icu_cameratrap_rep) and Camera Status Report (camera_status_report) event types — see ICU Server Event Types for their fields and a ready-to-apply spec.

Configuration

1. Create the Route in Gundi

1.1 Log in to Gundi and click Create Route.
1.2 Choose the API provider.
1.3 Select your Workspace and enter a name for this Route (e.g., “ICU Server - SiteName”).
1.4 Click Add destination on the flow map and select your EarthRanger site. Please consult our guide.
1.5 Save the Route, then select the data provider node and copy the API key shown under Connect API key.

2. Send the API key to ICU Server

2.1 Email the Gundi API key and your EarthRanger site name to ICU Server. They complete the connection on their side.

Suggested Contacts:

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

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.

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.

Other Camera Trap

Sentinel (Conservation X Labs) TrapTagger wpsWatch
TrailGuard
Back to the integration catalog Need help setting this up? Contact us