CMORE

Supported technology/Conservation Technologies

cmore.csir.co.za

DirectionData destination
PlatformGundi v2
TypeScheduled
DataEvents, Movement data, Attachments

CMORE is a situational-awareness and collaboration platform from CSIR. With this integration, Gundi delivers your EarthRanger data into a CMORE share group: reports arrive as tagged, geolocated events (with their photos as comments), tracked subjects appear as live positions on the CMORE map, and later edits or notes on a report are added as comments on the CMORE event. Every CMORE event links back to the original in EarthRanger.

Prerequisites

CMORE

You will need:

  • A dedicated CMORE account for this integration (not a personal login), with the Integration permission in your share group. Your CMORE Organization Admin creates it.
  • Your CMORE web address (e.g., https://cmore.csir.co.za) and your share group's numeric ID.
  • Access for your share group to the tag domains you want to use (e.g., "Wildlife"); the CMORE team grants this.

Gundi

You will need:

EarthRanger

You will need:

  • A service account and token for Gundi. Please refer to EarthRanger's documentation or contact Support.
  • A list of the report types you want to share, and the CMORE tag each should become.

Configuration

1. Prepare CMORE

1.1 Sign in to the CMORE web portal with the dedicated account and open the Admin Site (the gears icon, "Manage Users").
1.2 Under Service, click Create New Service, give it an ID and name (e.g., earthranger-prod / EarthRanger) and click Create.
1.3 Open the service, copy its Auth Token and keep it safe.
1.4 Click Edit, set Target Group ID to your share group's ID, set State to Active and save.
1.5 Under Manage Tags, confirm your share group is assigned to the tag domains you need.

2. Create the Route in Gundi

2.1 Log in to Gundi and create a Route with EarthRanger as the provider.
2.2 Click Add destination on the flow map and select CMORE. Please consult our guide.
2.3 Open the CMORE destination's configuration. Under Auth, enter your CMORE web address followed by /za/WebAPI/api, the Auth Token from step 1.3 and the share group ID, then click Save and Test Connection. You should see "Valid Credentials".

3. Map report types to CMORE tags

3.1 Under Deliver, add one entry per report type: pick the EarthRanger report type and the CMORE tag it should become.
3.2 Optionally match the report's details to the tag's fields, and translate values that differ between the two systems (e.g., "Black Rhino" "Black").
3.3 Click Save.

4. Choose what EarthRanger shares

4.1 On the EarthRanger provider node, open Pull Events and make sure the report types you mapped are included (or leave the list empty to share all).
4.2 Keep Run On Schedule on.
4.3 Optionally enable Forward Event Attachments to include photos.

5. Verify

5.1 Create a report of a mapped type in EarthRanger.
5.2 After a few minutes, it appears at the top of the CMORE message feed with its tag, fields, location and a link back to EarthRanger.
5.3 The Route's Activity Logs in Gundi show each delivery.

Good to know: a report arriving in CMORE without its tag usually means the tag name is misspelled or the share group lacks access to that tag domain; an empty field usually needs a value translation (step 3.2).
Technical reference

Field-by-field settings, mapping details and troubleshooting for administrators and developers.

Open the CMORE integration docs

Other Conservation Technologies