title: "Geospatial Radius Search and Spatial Query Engine" description: "Fast point-in-polygon detection, distance-based queries, and bounding box operations for spatial searches across large geographic datasets" category: "geospatial" icon: "radius-search" audience: ["Emergency Dispatchers", "GIS Analysts", "Fleet Operations", "Resource Coordinators"] capabilities:

• "Point-in-polygon detection"
• "Distance-based radius queries"
• "Bounding box spatial operations"
• "Geodesic distance calculations"
• "Combined spatial and attribute filtering" integrations: ["Dispatch Systems", "Fleet Management", "GIS Platforms", "Mapping Applications"]

Geospatial Radius Search and Spatial Query Engine#

Overview#

Determining which county an incident falls in, finding every registered sex offender within half a mile of a school, verifying whether a vehicle has entered a restricted port zone: these questions share a common structure. They are all spatial queries, and they all need to answer in time for the result to be operationally useful. A query that takes thirty seconds to complete is not useful to a dispatcher with a caller on hold.

The Radius Search and Spatial Query Engine delivers fast point-in-polygon detection, distance-based radius queries, and bounding box operations across large geographic datasets. Geodesic accuracy ensures results are correct at any scale, from a local jurisdiction to global maritime operations. Spatial indexes maintain consistent performance as data volumes grow, and combined spatial-plus-attribute filtering lets operations teams ask precise questions rather than pulling broad result sets and filtering manually afterwards.

Key Features#

Distance-Based Queries#

• Circular radius search from any geographic point with configurable distance
• Geodesic calculations provide accurate distance accounting for Earth's curvature, critical for long-range maritime and border security queries
• Multiple distance unit support: meters, kilometres, miles, and nautical miles
• Distance-sorted results with precise distance values for each match
• Minimum and maximum distance bounds for ring-shaped search areas

Point-in-Polygon Detection#

• Determine whether geographic points fall within defined polygon boundaries
• Support for complex polygons with multiple rings and holes
• Batch point-in-polygon testing for large datasets processed in a single operation
• Pre-computed polygon indexes for fast containment queries
• Multi-polygon search tests points against multiple boundaries simultaneously, returning all containing polygons

Bounding Box Operations#

• Rectangular area queries for fast initial geographic filtering before more expensive operations
• Efficient pre-filter for complex spatial queries, cutting computation time significantly
• Cross-meridian bounding box support for global queries spanning the date line
• Nested bounding box hierarchies for progressive spatial refinement
• Viewport-based queries return only entities visible in the current map view for responsive rendering

Spatial Filtering#

• Combine radius search with attribute filters for targeted results
• Entity type, status, availability, and capability filtering
• Temporal filters limit results to specific time windows
• Multi-geometry queries combine radius, polygon, and bounding box criteria in a single operation
• Exclusion zones filter out entities within specified areas from results

Performance Optimisation#

• PostGIS spatial indexing enables fast queries across large datasets
• Cached results for repeated queries on stable datasets
• Streaming results for large result sets without memory constraints
• Query plan optimisation selects the most efficient execution strategy
• Performance monitoring tracks query latency and throughput to detect degradation early

Use Cases#

Closest Unit Dispatch#

Dispatchers find the nearest available resources within a specified radius of an incident, filtered by capability and availability, for immediate deployment. Results appear in under a second even across fleets of hundreds of units.

Geographic Analysis#

Analysts query geographic datasets to identify entities within areas of interest, supporting investigation, planning, and assessment workflows where the question is fundamentally spatial.

Territory and Jurisdiction#

Operations teams verify that incidents and service requests fall within appropriate jurisdictional boundaries through point-in-polygon testing against territory definitions, resolving cross-boundary situations automatically.

Coverage Assessment#

Planners evaluate resource coverage by analysing how many assets fall within response-time radius thresholds of population centres and critical facilities, identifying gaps that need addressing.

Map Viewport Queries#

Applications load and display entities visible in the current map view using bounding box queries, enabling responsive map interaction with large datasets without loading everything upfront.

Integration#

Connected Systems#

• Dispatch and CAD systems for closest-unit and area-search operations
• Fleet management platforms for vehicle location queries
• PostGIS for spatial database query execution
• ArcGIS and GeoServer for enterprise GIS platform integration
• Interactive mapping with multiple layer support for spatial query visualisation

Open Standards#

• GeoJSON (RFC 7946): All spatial boundaries, polygon definitions, and query results are exchanged and stored as GeoJSON geometry objects, enabling interoperability with mapping clients and GIS platforms.
• OGC Simple Features Access (ISO 19125 / SFA): Point-in-polygon, radius containment, and intersection operations are implemented using the OGC SFA geometry model via PostGIS predicates such as ST_Contains, ST_Within, ST_Intersects, and ST_DWithin.
• WGS 84 / EPSG:4326: All coordinates are stored and queried in the WGS 84 geographic coordinate reference system (EPSG:4326), the global standard for GPS and web mapping.
• OGC Web Feature Service (WFS): The engine ingests vector feature layers from OGC-compliant WFS endpoints, including GeoServer and DGIWG-profile services, allowing spatial datasets from enterprise GIS platforms to be queried directly.
• OGC Web Map Service (WMS): Tile and layer metadata from WMS-compliant sources can be registered and used as reference layers for viewport bounding-box queries and map rendering.
• PostGIS Geography Type (geodesic distance model): Radius queries use the PostGIS GEOGRAPHY type with ST_DWithin, which computes distances on the WGS 84 ellipsoid rather than a flat plane, ensuring accuracy for long-range maritime and cross-border operations.
• GraphQL (June 2018 specification): All spatial query operations, radius search, point-in-polygon, bounding-box, and combined attribute filters, are exposed through a typed GraphQL API, enabling precise field selection and composable queries for dispatch and GIS client integrations.
• ISO 8601: Temporal filter bounds passed to spatial queries use ISO 8601 date-time strings, ensuring unambiguous time-windowed searches across time zones.

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