Overview
First Arriving's ESRI integration brings mapping onto your alerting screens: routing, hydrants, satellite imagery, standard basemaps, and — for agencies with their own ESRI account — custom GIS layers and existing ESRI dashboards. Some capabilities work for every agency with no ESRI account required; others need an ESRI account of your own.
Available to Every Agency
The following mapping capabilities work without an ESRI account of your own, and need nothing from you to enable:
- Standard ESRI basemap — we provide the basemap for agencies that do not have an ESRI account.
- Routing — the route from the station to the incident location.
- Nearest hydrants — an overhead view of the closest hydrants, pulled up automatically on dispatch.
- Satellite imagery — available on any map.
- GIS department maps — display of maps your GIS department has already built.
For ESRI Account Holders
Custom GIS Layers
Anything your GIS team publishes can be layered onto your alerting maps. Common examples include:
- Gas valves and lines
- Fire station locations
- Jurisdictional boundaries
- Hydrant maps
Additional ESRI Dashboards
Any ESRI dashboard you already maintain — response statistics, for instance — can be added to your screen rotation.
What We Need From You
The standard basemap, routing, and hydrants need nothing from you. The steps below apply only if you want your own layers or dashboards.
For custom layers
- Open a ticket at our support center and include the link to the REST web service on your account that holds the available layers. This is a public REST endpoint, so it can go straight into the ticket.
- In the same ticket, name the specific layers you want visible when a call comes in, so we only display what your crews need in that moment.
For additional dashboards
If you want another ESRI dashboard added to your rotation, send us its complete URL in your support ticket.
What You Don't Need to Send
You don't need to send common map data — street names and similar details are already part of your base map.
A Note on Dispatch Mapping
Secondary notification path: The hydrant and routing views that appear on dispatch are a secondary, informational display. Always rely on your CAD as the system of record.
Questions?
If you need help getting your layers or dashboards set up, open a ticket at our support center.
Adding Private Layers
Private layers: what we need to access them
If your layers are shared publicly, the REST link described above is all we require. Private layers will not render until the request is authenticated, which requires OAuth 2.0 credentials for app authentication issued from your own ArcGIS organization.
This applies to both ArcGIS Online and ArcGIS Enterprise organizations. The credential grants access only to the layers you designate. No account username or password is required, and we will not request one.
What we need from you
Open a ticket at our support center describing what you want set up. Submit the Client ID and Client Secret through the First Arriving Secrets Tool (https://secrets.firstarrivingdigital.com/) and paste the link it generates into that ticket — don't send them by email. The remaining non-secret values can go straight in the ticket.
- The Client ID and Client Secret generated with the credential (submit via the Secrets Tool).
- Item access granted to each layer to be displayed. A credential reaches up to 100 items, and only items owned by the account that created it. If your layers have different owners, each owner must create a separate credential.
- The referrer URL set to *firstarrivingdigital.com, the domain your dashboard is served from.
- The REST URL of each layer to be displayed. For example:
https://services1.arcgis.com/<org-id>/arcgis/rest/services/Hydrants/FeatureServer/0 - ArcGIS Enterprise only: your portal address. Enterprise tokens are issued by your own portal rather than arcgis.com, so the credential must be directed to your organization's token service. For example:
https://<your-portal>/sharing/rest/oauth2/token
How to create the credentials
Esri provides a step-by-step guide for each environment. Follow the one that matches your organization.
ArcGIS Online — Create OAuth credentials for app authentication. In your organization, go to Content › My content › New item › Developer credentials.
ArcGIS Enterprise — Create OAuth credentials for app authentication. Follow the same path within your own portal, and include your portal address when you send the credential.