Also known as “ER2ER”, "DAS2DAS", or “EarthRanger to EarthRanger”, event sharing allows you to share events and subjects between two EarthRanger sites.
Website: https://www.earthranger.com/
Integration Requires Assistance
This integration requires assistance from our support team for setup and configuration. Please contact our support team at support@earthranger.com and we’ll guide you through the process to ensure everything is set up correctly.
We are actively working to make this integration self-service in the future. Stay tuned for updates!
I. Audience
- EarthRanger Support Team.
- Deployment Partners.
II. Prerequisites
Source Site
- Subject Group. Create a subject group that includes all the subjects intended for sharing.
- User and Permissions. Create a dedicated user with permission to access only the subject group that will be shared with the destination.
-
Authentication Token. Create a session token for this special user.
Destination Site
- User and Permissions. Create a special user to allow Gundi to create the necessary subject group, subjects and observations.
- Authentication Token. Create a session token for this special user.
III. Configuring Gundi v1
Outbound Configuration
Audience: Support Team
Go to Gundi v1.
Set up an Outbound Configuration for the EarthRanger site that will receive the data.
Use a dedicated token generated specifically for this integration. Ensure the token belongs to a user account with permissions to create subject groups, subjects, sources, and observations.
Inbound Configuration
Audience: Support Team
Go to Gundi v1.
Go to the Inbound Integrations and select Add Integration.
Follow the steps below to configure the integration:
Name: Provide an appropriate name for this connection (e.g., ER Site 1 to ER Site 2)
Organization: Select the organization that owns the data.
Type: Choose “ER2ER Subject Sharing”.
Endpoint: Source endpoint (e.g., https://your_site.pamdas.org/api/v1.0)
Token: Authentication token at the source site.
State:
{
"feature_groups":[
{
"id":"{{string}}"
}
],
"look_back_window_hours":{{number}},
"provider_key":"{{string}}",
"schedule_interval_minutes":{{number}},
"subject_additional":{{boolean}},
"subject_group":"{{string}}"
}Additional Guidance
Provider Key (provider_key): This value will be used as "Provider Key" in the replicated subject(s).
Subject Group (subject_group): All the replicated subject(s) will be grouped in this value in the destination site.
Feature Group (feature_groups): (Optional) Provide the feature group(s) ID to enable geo-filtering. Each of the IDs will point a specific feature (geoJSON) for filtering the replicated observations to be contained within the feature. If more than one ID is provided, the geo-filtering logic will validate if the observations are within any of the provided features.
Subject Additional (subject_additional): Whether the replicated subject(s) will include "additional" data
Look Back Window Hours (look_back_window_hours): How many hours back we will look for subjects on the source site.
Example:
{
"feature_groups":[
{
"id":"76f970b9-bf3e-4946-8b6d-0c94dd55544a"
}
],
"look_back_window_hours":12,
"provider_key":"er2er_subjects_from_sitea",
"schedule_interval_minutes":5,
"subject_additional":true,
"subject_group":"ER2ER - Lions from SiteA"
}Click Save.
Device Group
Audience: Support Team
Modify the Device Group to assign the Outbound Configuration set up in a previous step.
VI. Additional Resources
Legacy Documentation
Continue Learning
Tags: ER2ER, EarthRanger to EarthRanger, Gundi v1, Subject Sharing
Last Update: July 21, 2025