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.

Gundi creates the EarthRanger report types for you from the CMORE tags you choose, so rangers report straight into the right CMORE tag and fields.

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:

• A Gundi account.

EarthRanger

You will need:

• A service account and token for Gundi. Please refer to EarthRanger's documentation or contact Support.
• Permission for that account to create event categories, event types and dropdown choices.

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. Create the EarthRanger report types

3.1 On the CMORE destination, choose Create EarthRanger event types.
3.2 Select the CMORE tags your rangers will report, and name the EarthRanger category that will hold them (e.g., "Great Fish CMORE").
3.3 Tick Preview only and run it. Nothing changes in EarthRanger: the result lists what will be created and confirms the EarthRanger account has the permissions it needs.
3.4 Untick Preview only and run it again. The new report types appear in EarthRanger under the category you named, with a field for each CMORE property and the CMORE options in each dropdown.

Run it again whenever your tags change in CMORE. It updates the existing report types and never creates duplicates or removes anything. If you already report a tag through a report type you built yourself, the preview points it out so you can leave that tag out.

4. Choose what EarthRanger shares

4.1 On the EarthRanger provider node, open Pull Events and make sure the new report types are included.
4.2 Keep Run On Schedule on.
4.3 Optionally enable Forward Event Attachments to include photos.

5. Verify

5.1 Create a report with one of the new types 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.

What to expect

• Only tagged reports reach CMORE. Reports whose type has no CMORE tag stay in EarthRanger, and the Gundi activity log notes them.
• The reporter is shown on the event. CMORE lists the Gundi account as each event's creator. The person who reported it in EarthRanger appears in the tag's Reported by field, or in the comment that links back to EarthRanger.
• Dropdowns with several levels (e.g., Animal, then Hoof Animal, then Buffalo) bring over the top level only.
• Photo and message properties of a CMORE tag have no matching field in EarthRanger. Photos attached to a report are still sent.
• One EarthRanger site per CMORE destination. Each site that shares with CMORE needs its own destination.

Other Conservation Technologies