Native maps that work connected or offline.
Use internet-connected Esri/ArcGIS and open GIS services when available, then keep working with locally stored map packages when coverage is limited or unavailable—across iOS, Android, and Windows.
Android
Supported platform or deployment profile.
iOS
Supported platform or deployment profile.
Windows
Supported platform or deployment profile.
Mac Catalyst
Supported platform or deployment profile.
Online + offline
Supported platform or deployment profile.
One native map workspace from live services to disconnected field work.
The field application can consume connected map services, open locally stored packages without internet access, and use incident coordinates or a selected map location to launch supported navigation applications. Available services and apps vary by platform and deployment.
Assigned-incident map
01
Open the dispatched location with its priority, status, address, assignment, and relevant operational context.
Navigation-app handoff
02
Launch supported native navigation applications such as Google Maps, Apple Maps, Waze, or other configured choices with the selected coordinates.
Map interaction
03
Use long-press, click-to-navigate, placemarks, waypoints, search results, and selected features as navigation targets.
Offline-native map packages
04
Open raster and vector tiles, MBTiles, GeoPackage, PMTiles, VTPK, TPKX, and cached content locally on iOS, Android, and Windows when internet access is unavailable.
Positioning
05
Use device GPS or supported external Bluetooth GNSS sources with NMEA parsing and field position workflows.
Situational awareness
06
Combine incidents, units, facilities, zones, hazards, annotations, and customer-controlled operational layers.
Connected Esri and open GIS
07
When online, connect the native map to configured ArcGIS services, Esri-compatible FeatureServer or StreamServer interfaces, OGC API Features, vector tiles, PostGIS, and MapLibre sources.
TAK Server and TAK apps
08
Coordinate web and native platform users with ATAK, iTAK, WinTAK, and other TAK-enabled teams through bidirectional positions, missions, CoT markers, GeoChat, and emergency context.
Dispatch, field, command, and partner systems see the same geography.
The platform preserves customer ownership of operational layers while supporting native field navigation, internet-connected Esri mapping services, open geospatial integration, and offline continuity.
- Live and historical resource-location pathways
- Incident and receiving-facility destinations
- Customer-controlled Esri, open GIS, and local spatial sources
- Offline continuity for constrained or disconnected environments
- Authentication for external live feeds and services
Location connects response, care, destination, and partner teams.
Mapping supports dispatch choices, crew travel, hospital selection, command awareness, TAK coordination, analytics, and partner integration.
CAD
DISPATCH
Use resource and incident location in the assignment workflow.
TAK interoperability
TAK
Share PLI/BFT, missions, markers, GeoChat, and emergency context.
Hospital coordination
DESTINATION
Connect facility choice, ETA, advance notice, and arrival.
Documents & live video
AWARENESS
Pair the map with plans, field content, cameras, and UAS feeds.
Show us the incidents, units, posts, facilities, hazards, and GIS layers you rely on.
We will map the field navigation behavior, offline packages, authoritative sources, live feeds, and access controls required for deployment.