Self Deployment Guide

The Self Deployment Guide is divided into key areas that match the setup process for your EarthRanger site. Each section builds on the last, helping you create a system that reflects your operations from the map to the data it collects and analyzes.

  • Map Layer Configuration – Define the visual foundation of your site by setting up the map, adding geographic layers, and organizing key locations so your team can easily navigate the environment.
  • Event Configuration – Design the data model that defines what your team records and reports on. You’ll decide what information matters, how it’s structured, and how users will capture it in the field.
  • Device Configuration – Connect your organization’s tracking and monitoring devices like animal collars, vehicle trackers, or aircraft sensors to EarthRanger, ensuring they transmit accurate data to your system.
  • User Permissions Configuration – Set up user accounts and access levels so everyone on your team can see and do exactly what they need, while keeping your data secure.
  • Analyzer Configuration – Automate detection and alerts by creating analyzers that identify movement patterns, proximity events, or environmental triggers, turning your live data into actionable insights.

Each section provides contextual guidance, and links to detailed resources. Together, they create a complete pathway for independently deploying EarthRanger.

If at any point you encounter challenges or find that you need additional support beyond what’s included here, please reach out to the EarthRanger Support Team for assistance.

Getting Started: Accessing the EarthRanger Admin Site

Before you begin configuring your deployment, make sure you can log in and navigate the EarthRanger Admin interface, where all configuration steps take place.

 

Map Layer Configuration

Map layers define the geographic context of your EarthRanger site. In this section, you’ll configure the layers that appear on the map, organize them into categories, and import your own shapefiles or GeoJSON. You’ll also learn how to apply styling and quicklinks so your operational map is both accurate and easy to navigate.
Before you configure map layers
 

  • Decide which categories and groups your features will belong to.
  • Ensure shapefiles or GeoJSON files are validated and ready for import.
  • Plan how map quicklinks will help users access important views.

Follow These Guides

Event Configuration

Events in EarthRanger capture and structure the information your team records in the field. This section walks you through setting up event categories, designing event types, and managing choices so that the data you collect is consistent and easy to analyze. By configuring events correctly, you’ll ensure that your workflows reflect your operational needs and that users can record the right information with minimal friction.
Before you configure Events:

  • Confirm whether an Event Category already exists or needs to be created for your new Event Types.
  • Use the Event Form Editor (EFE) to design and create the Event Types you require.
  • Add choices to EarthRanger (if needed) to support dropdown fields in your Event forms.
  • Validate that the permissions linked to the Event Category and Event Types are effective by testing with a user or test account.

Follow these guides: 

Device Configuration

Device Configuration connects your organization’s field technology to EarthRanger so data from collars, sensors, and tracking systems flows into your site. Depending on your provider, setup happens either directly in EarthRanger Admin or through Gundi, EarthRanger’s integration service.

This section starts with Device Integration in Self Deployment, which outlines both paths and helps you identify where your device setup belongs. If your tracking or telemetry provider is listed in Gundi’s Supported Technologies, follow the Gundi integration steps. If not, your configuration will be completed directly in EarthRanger Admin using the guides in this section.

For example, AWT collars and Spidertracks aircraft tracking are integrated through Gundi, while connections such as Garmin InReach, FIRMS fire alerts, or custom telemetry APIs are configured directly in EarthRanger Admin.

Once your devices are connected, you’ll learn how to group them, verify visibility in the map, and assign permissions so your team can securely access the data they need.

Before you configure devices

  • Gather prerequisites for integration from your provider (for Gundi-supported devices, see the Gundi Help Center).
  • Confirm that Gundi permission sets, DAS application, and access tokens are available in your system by default.
  • Plan how devices will be grouped into subject groups for easier management and visibility.


Follow these guides: 
Configure devices in EarthRanger Admin


Integrate supported devices through Gundi


Finalize and validate

User Permissions Configuration

User Permissions ensure that the right people (and groups) have the correct level of access to EarthRanger. In this section, you’ll configure user accounts, assign permission sets, and link those permissions to events, patrols, subjects, and map visibility. Properly setting permissions is critical to both security and usability, ensuring that staff can only view and act on the information relevant to them.
Before you configure permissions

  • Prepare a list of users and their required access levels.
  • Plan which roles or groups need visibility into events, patrols, subjects, or maps.
  • Optionally, decide whether to create profiles without password logins to reduce account sharing and improve security.
     

Follow these guides:

Analyzer Configuration

Analyzers allow EarthRanger to automatically detect and generate events when certain conditions are met, such as geofences being crossed, subjects becoming immobile, or external data (like FIRMS fire alerts) being received. This section walks you through setting up analyzers step by step, linking them to map features, subjects, and event categories so they can function correctly.
Before you configure analyzers

  • Understand how spatial and non-spatial analyzers work.
  • Import and group the map features needed for geofence or proximity analyzers.
  • Confirm that subjects you want to monitor are organized in subject groups.
  • Check that event types linked to analyzers are active and assigned to a visible category (commonly the Analyzer Event Category).


Here you’ll find how to: