title: "Geospatial Map Layers & Overlays" description: "Multi-source visualisation infrastructure supporting 50+ layer types for combining diverse spatial datasets into interactive intelligence maps" category: "geospatial" icon: "layers" audience: ["GIS Analysts", "Operations Teams", "Intelligence Analysts", "Emergency Planners"] capabilities:

• "50+ layer types from multiple sources"
• "Satellite imagery and street map base layers"
• "Custom business intelligence overlays"
• "Real-time data layer updates"
• "Layer management and sharing" integrations: ["Mapping Services", "Weather Data", "Traffic Data", "Satellite Imagery", "Custom Data Sources"]

Geospatial Map Layers & Overlays#

Overview#

During a major flood response, the operations room needs to see current flood extent overlaid on road network data, with shelter locations marked, evacuation routes highlighted, and a population density layer underneath it all. No single data source provides that picture. The value comes from combining layers from different systems, updated at different rates, into one coherent display that a commander can read quickly under pressure.

Map Layers & Overlays provides the visualisation infrastructure for exactly that kind of multi-source display. More than 50 layer types from authoritative providers, real-time streaming updates, team-shared configurations, and straightforward layer management give operations teams the flexibility to build the precise map they need for any scenario, without relying on GIS specialists to assemble it each time.

Key Features#

Base Layer Options#

• Multiple street map styles for different operational contexts, including styles optimised for emergency services and field operations
• Satellite and aerial imagery for terrain assessment, infrastructure reconnaissance, and site verification
• Terrain models with elevation contours and hillshading for topographic situational awareness
• Hybrid views combining satellite imagery with labels and road overlays
• Dark and light modes for different viewing environments, including vehicle-mounted and command room displays

Data Overlay Layers#

• Point, line, and polygon data visualisation for operational entities
• Heat map overlays for density and concentration analysis
• Choropleth layers for thematic area-based data display
• Real-time position tracking layers for assets and personnel
• Custom marker and icon layers with data-driven styling

Real-Time Data Layers#

• Weather radar, forecast, and condition overlays updated on live feeds
• Traffic flow and congestion visualisation for route planning and response time estimation
• Live event and incident markers with status updates
• Streaming position updates for tracked entities
• Maritime AIS vessel positions for domain awareness and port operations

Layer Management#

• Layer visibility toggling for focused analysis without discarding configuration
• Opacity control for transparent overlaying of multiple datasets
• Layer ordering management controls draw priority for complex multi-layer displays
• Saved layer configurations for repeatable analysis setups that can be shared across shifts
• Team-shared layer groups ensure consistent views across users in the same operation

Custom Layer Creation#

• Import geographic data in standard formats (GeoJSON, KML, Shapefile) from ArcGIS, GeoServer, and other GIS platforms
• Draw custom boundaries, routes, and areas of interest directly on the map
• Connect to external WMS/WFS data services for live layer updates
• Configure layer styling, labelling, and interaction behaviour
• Publish custom layers for organisation-wide availability

Use Cases#

Situational Awareness#

Operations centers overlay real-time incident data, unit positions, weather conditions, and jurisdictional boundaries on a single map for comprehensive situational awareness during active operations. All layers update live, so the picture remains current throughout the incident.

Investigation Analysis#

Investigators layer case-related geographic data including entity locations, movement trails, communication patterns, and incident history to discover spatial relationships across investigation elements that would be invisible in separate data views.

Emergency Planning#

Emergency planners combine flood zones, evacuation routes, facility locations, and population density layers to develop and evaluate response plans for potential scenarios, testing assumptions before an event rather than during it.

Resource Deployment#

Operations managers overlay service demand heat maps with current resource positions and territory boundaries to identify deployment gaps and coverage shortfalls that need addressing before the next high-demand period.

Integration#

Data Sources#

• Satellite imagery providers for base layer and change detection overlays
• ArcGIS and GeoServer for enterprise GIS layer publishing and consumption
• Weather services for real-time meteorological data
• Traffic data providers for road condition overlays
• Maritime AIS data feeds for vessel tracking layers
• CesiumJS for 3D terrain layer visualisation where elevation context matters
• Standard geographic data formats (GeoJSON, KML, Shapefile) for bulk layer import

Open Standards#

• OGC Web Map Service (WMS) 1.3 / Web Feature Service (WFS) 2.0: Layer data is fetched and served via OGC WMS (raster tile requests) and WFS (vector feature queries) endpoints, with explicit OGC-WMS-1.3 and OGC-WFS-2.0 standard references enforced across GeoServer and DGIWG-profiled service clients.
• GeoJSON (RFC 7946): All vector overlay geometries are encoded as RFC 7946 GeoJSON; the platform ingests, stores via ST_GeomFromGeoJSON, and emits GeoJSON for every point, line, polygon, and feature-collection layer type.
• OGC API Features (OGC 17-069r4): Live feature-collection layers are synchronised from remote OGC API Features endpoints using a dedicated async REST client, with CRS defaulting to the standard http://www.opengis.net/def/crs/OGC/1.3/CRS84 URI.
• OGC 3D Tiles 1.0: Three-dimensional terrain and building layers are registered and streamed as OGC 3D Tiles tilesets via the CesiumJS integration, with asset_type tracked as 3DTILES in the tileset registry.
• EPSG Geodetic Parameter Registry / WGS 84 (EPSG:4326, EPSG:3857, CRS84): All map projections and bounding-box coordinates reference named EPSG CRS identifiers; OpenLayers configurations default to EPSG:3857 (Web Mercator) and geographic layers default to EPSG:4326 (WGS 84).
• ITU-R M.1371 (Automatic Identification System): Maritime vessel-position overlay layers consume real-time AIS feeds via a WebSocket connector, with vessel identity resolved through standard MMSI numbers as defined in ITU-R M.1371.
• OGC KML 2.3: KML files are accepted as a named import format for custom overlay creation alongside GeoJSON and Shapefile, enabling interoperability with ArcGIS, Google Earth, and other KML-producing platforms.
• OGC API Processes (OGC 18-062r2): Geospatial processing tasks that generate or transform overlay datasets can be submitted to and monitored on remote OGC API Processes endpoints via a dedicated async integration client.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14