Gundi can send data to EarthRanger, Garmin InReach, SMART Connect, TrapTagger, wpsWatch, and Movebank. These systems are considered Destinations in Gundi.
Prerequisites
EarthRanger
You will need:
- URL - EarthRanger site URL (eg., https://yoursite.pamdas.org/).
- User - An EarthRanger user created for the integration(s) you need. We recommend creating one user per integration (e.g., “cameratrap_integration”).
Please refer to EarthRanger's documentation or contact Support.
- Permissions - Ensure that the user created for your integration has the appropriate permissions. Most sites include a “Gundi Service Account” permission set suitable for standard integrations; however, in certain cases (e.g., ER2ER), this permission set can cause issues. If you are uncertain, consult our support team for guidance.
Quick Checklist:
These permissions are not required in all integrations, but we recommend considering the following when assigning permissions.
If the integration is intended for events/alerts:
If the integration is intended for tracking Subjects:
Warning
Ensuring the user has the correct permissions is essential to prevent both oversharing and insufficient access. Please consult our Support team for guidance.
Finally, you will need:
- Token - An authentication token created for the user.
Please refer to EarthRanger's documentation or contact Support.
SMART Connect
You will need:
- SMART Connect server URL (e.g., https://example.smartconservationtools.org/server)
- Server account (username and password)
- Conservation Area UUID.
Movebank
You will need:
- Movebank username.
Please note that usernames on Movebank are case-sensitive.
wpsWatch
You will need:
- Authentication Token
- Server URL
TrapTagger
You will need:
- TrapTagger account
- TrapTagger API Key
Garmin InReach
You will need the following parameters as configured in https://explore.garmin.com/ , under IPC Inbound settings.
- Inbound URL
- IPC User Name
- IPC Password
Step 1. Configuring a new data destination
Choose one of the following methods:
Method 1: Configuring a data destination from a Connection.
Guide (click to expand)
While creating or editing a Connection, Gundi will ask you to select a Destination.
Select + New Destination
From the list of available technologies or services, choose the one you want to connect to.
After selecting the desired technology, you will be directed to a form where you must input the required information, including a unique name, connection details (e.g., token, credentials, endpoint URLs), and any specific configuration settings relevant to the Destination.
If you need help configuring a destination with one of our supported technologies, please visit our guides.
Select Add to save the Destination in Gundi.
Method 2: Configuring a data destination from the destination section.
Guide (click to expand)
Using the top navigation bar, select Destinations.
Click Create Destination.
From the list of available technologies or services, choose the one you want to connect to.
After selecting the desired technology, you will be directed to a form where you must input the required information, including a unique name, connection details (e.g., token, credentials, endpoint URLs), and any specific configuration settings relevant to the Destination.
If you need help configuring a destination with one of our supported technologies, please visit our guides.
Select Add to save the Destination in Gundi.
Step 2. Connecting your data source and your destination
Configuring a data destination makes it available, but you must include it in a Connection to use it. To update your Connections, follow the next steps:
- Go to Connections.
- Select your desired Connection.
- Open the Destinations tab.
- Click + Existing Destinations.
- Find the Destination you created, check the box, and click Add Destinations.
- Gundi will automatically save the Connection, and it will now be fully set up.
Continue Learning