EarthRanger
Send detections and camera alerts to an EarthRanger site as events on the ranger map. Each alert becomes one event with the annotated photo and a link back to the full record. It is a notification channel, like email and Telegram: an event is sent once and never changed. Connect is the record, EarthRanger is the alert feed.
Before you start
This page connects AddaxAI Connect to an EarthRanger site you already run. EarthRanger is a separate platform; if your organisation does not use it yet, start at earthranger.com ↗ first, this integration only sends to an existing site.
You need:
- An EarthRanger site, and admin access to it.
- A Gundi account. Gundi is EarthRanger's integration service, free for conservation use (projectgundi.org ↗).
- Project admin access in AddaxAI Connect.
How it works
- A live image finishes classification.
- The rules you set in AddaxAI Connect decide whether it goes through.
- One event is posted to Gundi with the annotated image.
- Gundi forwards it to EarthRanger, usually within a minute.
Camera alerts work the same way: a low battery, a full SD card, silence, rejected files, or a theft watch trigger posts one event at the camera's site.
Never sent: bulk uploads (an SD card carried in is history, not an alert), images that match no rule, and updates. Correct a species in Connect later and the EarthRanger event keeps the original label.
Set up
Steps 1 and 2 are done once on the EarthRanger side. Steps 3 and 4 are done by a project admin.
1. Create the connection in Gundi
On the EarthRanger side, one time.
- Log in at gundiservice.org/connections ↗ and click
Create Connection. - Choose the
APIprovider. - Pick your workspace and name the connection, for example "AddaxAI Connect - Reserve name".
- Add
EarthRangeras the destination. Enter the site name from your EarthRanger URL and either the built-in Gundi Service Account or a token from your EarthRanger admin. - Save. (You copy the connection's API key in step 3.)
2. Prepare the EarthRanger site
On the EarthRanger side, one time.
The site needs the two event types below. An EarthRanger admin adds them under Admin > Activity > Event Types with Add Event Type and pastes the schema. Put them in the event category your camera trap reports live in (Monitoring is common), and give the Gundi connection's user permission on that category. Without it, Gundi accepts the event but EarthRanger refuses it.
Detections. Display name "AddaxAI detection", value addaxai_connect_detection. The type and its keys carry the addaxai_connect_ prefix, EarthRanger's way to keep one namespace per source.
{
"schema": {
"$schema": "http://json-schema.org/draft-04/schema#",
"title": "AddaxAI detection",
"type": "object",
"properties": {
"addaxai_connect_species": {"type": "string", "title": "Species"},
"addaxai_connect_scientific_name": {"type": "string", "title": "Scientific name"},
"addaxai_connect_category": {"type": "string", "title": "Category"},
"addaxai_connect_count": {"type": "integer", "title": "Count"},
"addaxai_connect_confidence": {"type": "number", "title": "Confidence (0-1)"},
"addaxai_connect_camera_id": {"type": "string", "title": "Camera"},
"addaxai_connect_site_name": {"type": "string", "title": "Site"},
"addaxai_connect_link": {"type": "string", "title": "Link to AddaxAI"}
}
},
"definition": [
{"key": "addaxai_connect_species", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_scientific_name", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_category", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_count", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_confidence", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_camera_id", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_site_name", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_link"}
]
}
Camera alerts. Display name "AddaxAI camera alert", value addaxai_connect_camera_alert.
{
"schema": {
"$schema": "http://json-schema.org/draft-04/schema#",
"title": "AddaxAI camera alert",
"type": "object",
"properties": {
"addaxai_connect_alert": {"type": "string", "title": "Alert"},
"addaxai_connect_summary": {"type": "string", "title": "Summary"},
"addaxai_connect_camera_id": {"type": "string", "title": "Camera"},
"addaxai_connect_site_name": {"type": "string", "title": "Site"},
"addaxai_connect_link": {"type": "string", "title": "Link to AddaxAI"}
}
},
"definition": [
{"key": "addaxai_connect_alert", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_camera_id", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_site_name", "htmlClass": "col-lg-6"},
{"key": "addaxai_connect_summary"},
{"key": "addaxai_connect_link"}
]
}
The event type's default priority sets the colour of the dot on the map. People and vehicles arrive with addaxai_connect_category set to person or vehicle.
3. Connect the project
By a project admin.
- Copy the API key from your Gundi connection, under
Connections > your connection > API key(open Gundi ↗). Gundi may ask to save unsaved changes when you switch section; discard it.
- In AddaxAI Connect, open
Integrations > EarthRanger, clickConnect, paste the key, and save.
- Click
Send test event. It posts a real event titled "Test from AddaxAI Connect" at the centre of your project area or your first site, and shows the result. Check that it appears in EarthRanger, then resolve it there.
4. Choose what to send
In AddaxAI Connect, by a project admin.
The same page has three rule lists.
- Detection rules: which labels, at which sites, at what time of day, minimum group size, cooldown, and an "absent for days" filter for rare visitors. The cooldown starts at the project's independence interval.
- Camera rules: battery below, SD card above, silent for more than, rejected files per day. Once per incident.
- Theft watch rules: a person unusually close to a camera, or a camera silent longer than its own rhythm.
These rules belong to the project, not to you. Any project admin can change them, and they send to the ranger team. Your personal email and Telegram rules on the Notifications page are separate.
What an event contains
| Field | Detection | Camera alert |
|---|---|---|
| Title | "Red fox at Site 4" | "Camera alert at Site 4" |
| Time | Capture time of the image, in the server timezone | Time of the check |
| Location | The image's GPS, or the site | The camera's current site |
| Details | species, scientific name, category, count, confidence, camera, site, link to the image | alert, summary, camera, site, link to the cameras page |
| Attachment | The annotated image, 1280 px, with boxes and the project's privacy blur | None |
When something does not arrive
- Gundi returns 403 when saving or testing: the API key is wrong or was revoked. Copy it again from your connection's
API keysection in Gundi. - The test passes but nothing shows in EarthRanger: open the connection in Gundi and check its activity log. The usual causes are a missing event type on the site, or the Gundi user without permission on the event category.
- Events stop after a while: the connection shows the last error. A camera without a site or GPS cannot be placed on a map, so its alerts are skipped and logged.
- Nothing sends at all: check that a key is saved. Disconnect forgets the key; the rules stay and resume when a key is saved again.