Overview#
During a security incident, the first question is always: where is the traveler right now? The DoC Location domain answers that question in real time. GPS positions update continuously, are stored with WGS84 precision, and are accessible through WebSocket subscriptions so that response teams always see the traveler's current position rather than the last-known position from a polling cycle. When an SOS activates, the location context is embedded in the alert automatically.
Key Features#
- Real-time GPS location tracking for duty of care travelers.
- Spatial queries for proximity and area-based searches.
- High-performance location update processing.
- WebSocket subscriptions for live location tracking.
- Location history with timeline playback capability.
- SOS alert integration with location context.
- WGS84 (EPSG:4326) coordinate standard support.
- Organisation-scoped location access control.
Use Cases#
Duty of care response teams track traveler locations in real time during security incidents, maintaining continuous situational awareness of where the traveler is as the incident evolves.
Security coordinators run proximity searches to identify which other travelers or contracted security resources are closest to an incident location, enabling rapid mutual support coordination.
Post-incident review teams replay location history timelines to reconstruct the sequence of events during an incident, supporting both operational learning and legal documentation requirements.
SOS response operators receive location context automatically with every SOS alert, eliminating the delay of having to establish the traveler's position as a separate first step in the response workflow.
Integration#
Integrates with SOS alerting, incident management, and geofencing services for location-aware duty of care operations.
Open Standards#
- WGS 84 (EPSG:4326): All traveller coordinates are stored and queried using the World Geodetic System 1984 datum with SRID 4326, ensuring interoperability with any GPS receiver or mapping platform.
- OGC Simple Features / ISO 19125: Spatial queries such as proximity searches and geofence intersection use PostGIS geometry functions (ST_DWithin, ST_GeogFromText) that implement the OGC Simple Features for SQL specification.
- RFC 6455 (WebSocket Protocol): Real-time location updates are pushed to response-team dashboards over persistent WebSocket connections, eliminating polling and delivering sub-second position refreshes.
- GraphQL (June 2018 specification): The primary API surface exposes location queries, mutations, and subscriptions via GraphQL, allowing clients to request exactly the fields they need and subscribe to live streams.
- GeoJSON (RFC 7946): Geofence boundaries associated with location-based alert triggers are stored and exchanged in GeoJSON format, supporting import and export of polygon, linestring, and point geometries.
- ISO 8601: All timestamps in location history records and time-range query parameters are represented as ISO 8601 strings, ensuring unambiguous date-time interchange across time zones.
- OAuth 2.0 / JWT (RFC 7519): Access to location data is gated on bearer tokens issued per the OAuth 2.0 framework; separate token types distinguish traveller-device credentials from platform-operator credentials.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14