Overview#
Many location-based decisions depend on running a geospatial process rather than just displaying a layer: buffer the evacuation zone, test route suitability, calculate a service catchment, or run a terrain-derived analysis. If every process is hard-wired to one GIS tool, orchestration becomes brittle and difficult to reuse.
The OGC API Processes Orchestration module gives the platform a standards-based way to submit, track, and govern remote geospatial process jobs. Organisations can trigger processes against external engines, follow job progress, capture results, and reuse those results across operations and analytics without building a separate connector for every processing service.
Last Reviewed: 2026-03-18 Last Updated: 2026-03-18
Key Features#
- Standards-Based Process Submission: Trigger remote geospatial jobs without binding the workflow to one vendor's private API.
- Job Tracking: Follow process status, progress, start time, and completion state from a governed internal view.
- Result Capture: Preserve the output so downstream users can work from the result instead of rerunning the analysis manually.
- Organisation Scoping: Keep process jobs within the correct tenant and command context.
- Sensitivity Controls: Apply visibility rules before results are surfaced to wider users.
- Process Statistics: Give administrators a view of process volume and process coverage across the organisation.
Use Cases#
- Flood or Hazard Buffering: A command team runs a remote process to generate an affected-area buffer around a live hazard.
- Access and Route Suitability: A planning team requests a route or terrain process to assess whether a vehicle or team can reach a site.
- Coverage and Catchment Analysis: A service models which population or facility footprint falls inside a response area.
- Planning and Exercise Support: Scenario designers precompute geospatial products that can later be reused during a live exercise.
- Operational Decision Support: Analysts run a process job and feed the result back into the shared operational picture.
Integration#
- Operational Mapping: Process outputs can be rendered directly into map and command workflows.
- Forms, Casework, and Planning Workflows: Geospatial process results can support decision-making in non-map-facing operational screens.
- Analytics and Reporting: Saved results can be reused in briefings, dashboards, and after-action analysis.
- Open Geospatial Intelligence Services: Process jobs can operate on the same standards-based geospatial layers used elsewhere in the platform.
Open Standards#
- OGC API - Processes: the module aligns to the OGC standard for submitting and managing geospatial processes over the web.
- GeoJSON: process inputs and outputs can be represented using a common open geospatial payload format.
- RFC 8259 JSON: job submissions and results can be exchanged in a standard structured format.
- CRS84 / EPSG:4326: spatial inputs and outputs can align with the common web-mapping coordinate reference model.
- ISO 8601: process start, finish, and audit timestamps use a standard date-time format.