Overview#
A dispatcher handling a structure fire needs to know, in seconds, where the nearest hydrant is, which road is currently closed, and whether the building has a known hazmat storage flag. They don't have time to wait for a tile to load or click through three layers to find it. The PSAP Mapping & GIS module is purpose-built for that environment: fast, authoritative, and always current.
The module provides a high-performance web mapping platform optimised for emergency dispatch operations. Rapid tile rendering, smooth navigation, and instant layer toggling work across all dispatcher consoles without performance degradation under load. GIS data layers provide authoritative context for every emergency, from street addresses and building footprints to fire hydrants and hazmat sites. Automated update pipelines ensure dispatchers work with current information at all times.
Key Features#
High-Performance Interactive Mapping#
Web mapping platform optimised for emergency dispatch with rapid tile rendering, smooth pan and zoom, and instant layer toggling. Dispatchers navigate quickly to incident locations, toggle between aerial imagery and street maps, and overlay operational data without performance degradation. Multi-monitor support enables dedicated map displays alongside other dispatch applications. Configurable bookmarks and quick-navigation features provide one-click access to frequently referenced locations.
Multi-Layered GIS Data Integration#
Comprehensive GIS data layers provide authoritative context for every emergency response:
- All public and private streets with accurate geometry, road names, and address ranges
- Building footprints with floor plans for critical facilities
- Fire hydrant locations, water supply points, and utility infrastructure
- Hazardous materials sites, flood zones, and environmental hazard areas
- School zones, hospital locations, and other critical community facilities
- Law enforcement jurisdictional boundaries including patrol beats and districts
- Aerial imagery and satellite photography with configurable update schedules
Automated Geocoding & Address Validation#
Address geocoding converts caller-provided addresses into precise map coordinates with real-time validation, error correction, and confidence scoring. The system handles common misspellings, abbreviations, and alternate address formats to reduce dispatcher workload and prevent wrong-address dispatches.
- Multiple address databases queried simultaneously for highest accuracy matching
- Confidence scoring indicates reliability of each geocoding result
- Dispatcher visual confirmation with alternative candidate locations displayed
- Common misspelling and abbreviation correction applied automatically
Geofencing & Proximity Analysis#
Automated geofencing monitors unit and incident positions relative to jurisdictional and operational boundaries, triggering alerts for jurisdiction violations, mutual aid activations, and proximity-based dispatch optimisation. Dispatchers receive automatic notifications when units cross boundaries or when incidents require coordination with neighbouring agencies.
Route Calculation & Navigation#
Real-time route calculation provides estimated travel times and optimal paths for responding units, accounting for current traffic conditions, road closures, and construction zones. Turn-by-turn directions are delivered to mobile data terminals, ensuring responding units reach incidents by the most efficient route. Multi-unit routing simultaneously calculates optimal paths for all dispatched units, identifying potential routing conflicts and suggesting alternative approaches.
Audit Trail & Documentation#
Every map interaction, geocoding result, and geofence alert is captured in a tamper-evident audit log supporting quality reviews and legal discovery requirements. Map session recordings can be replayed for incident reconstruction and training purposes. Configurable retention policies ensure compliance with state and federal record-keeping mandates.
Standards Compliance#
The system supports compliance with NENA, APCO, NFPA, and state-specific regulatory requirements for mapping and GIS in emergency communications. Automated compliance checking validates data quality against current standards and generates documentation for accreditation reviews.
Use Cases#
- Emergency dispatch centres requiring reliable, high-performance mapping operations
- Multi-agency coordination during complex, multi-unit incidents crossing jurisdictional boundaries
- Quality assurance programs validating address accuracy and response routing
- Regional dispatch consolidation requiring unified mapping across multiple jurisdictions
- Mutual aid coordination with automated boundary detection and agency notification
- Disaster response operations requiring real-time resource tracking and staging area management
- Island and remote emergency services where accurate GPS-based mapping is the primary navigational reference
Integration#
- CAD systems with bidirectional incident and unit data exchange
- Automatic Vehicle Location (AVL) systems for real-time unit position tracking
- County and city GIS departments for authoritative parcel, address, and street data
- NOAA weather services for radar overlays and severe weather alert display
- State DOT systems for highway, traffic, and road closure information
- Commercial mapping providers for supplementary imagery and geocoding services
- Federal agency data sources including FEMA flood zones and EPA hazmat sites
- Utility company infrastructure mapping for gas, electric, and water systems
Open Standards#
- NENA-STA-006.3 (NG9-1-1 GIS Data Model): The system models all ten canonical NENA GIS layers (PSAPBoundary, RoadCenterline, SiteStructureAddressPoint, administrative boundaries, and others), enforces the required field vocabulary, and runs the full topology and CRS validation suite defined by this standard.
- NENA-STA-021 (NG9-1-1 GIS Data Provisioning): Inbound GIS data bundles are ingested, parsed, and persisted using the STA-021 provisioning workflow, supporting GeoJSON, GeoPackage, and Shapefile source formats.
- OGC GeoPackage (OGC 12-128r19): GIS layers are both imported from and exported to GeoPackage files; the binary geometry header and Well-Known Binary encoding are parsed per the OGC specification.
- GeoJSON (RFC 7946): GeoJSON FeatureCollections are the primary geometry interchange format for layer ingestion, export, geofence import/export, and all internal PostGIS round-trips via ST_AsGeoJSON and ST_GeomFromGeoJSON.
- LoST, Location-to-Service Translation (RFC 5222): Routing URIs stored on each PSAPBoundary feature follow the RFC 5222 service URN format (urn:service:sos), enabling downstream ECRF-based call routing directly from the GIS boundary data.
- WGS-84 Geodetic Datum (EPSG:4326): All geometry is stored and validated in WGS-84; the validation service raises a CRS_NOT_WGS84 error for any layer feature that does not conform, ensuring consistent global coordinate reference across all map layers.
- Mapbox Vector Tiles (MVT): GIS layers are served as slippy-map tiles using PostGIS ST_AsMVT with the application/vnd.mapbox-vector-tile media type, enabling smooth browser-side rendering of large datasets at any zoom level.
- NMEA 0183: Automatic Vehicle Location feeds from responding units are ingested via an NMEA 0183 v4.11 parser, normalising GPS sentences (GGA, RMC, VTG) to WGS-84 position observations displayed on the live dispatch map.
Last Reviewed: 2026-02-04 Last Updated: 2026-04-14