Overview#
The FCOO Maritime Environment capability brings live and historical operational oceanography directly into the maritime operational picture, so naval and security operators see ocean currents, wave state, ice coverage, tides, and sea-surface conditions alongside their vessel tracks and sensor feeds.
Most maritime operations centres treat environmental data as a separate world: a standalone oceanography stack, its own viewer, its own login, and a manual step to reconcile what the water is doing with where the vessels are. This capability removes that gap. It synchronises maritime environment data layers from the Danish Defence Centre for Operational Oceanography (FCOO) and compatible services, persists every layer and observation point in a sovereign database, and serves it back through the same authenticated platform endpoint your analysts already use. The result is one operational view in which environmental context and tactical data sit side by side, with no second system to deploy or maintain.
Because the data is classification aware, a multi-clearance organisation can run a single integration while every user sees only the layers and observations they are cleared to see. That makes the capability practical for coalition, inter-agency, and mixed civil-military settings where the same oceanographic feed must serve audiences with very different access rights.
Key Features#
-
Operational oceanography layers: Synchronises ocean currents, wave heights, ice coverage, tides, and sea-surface conditions as named maritime environment layers, each carrying its region, temporal coverage, and spatial resolution.
-
Geo-referenced observation points: Stores every measurement as a discrete observation with latitude, longitude, depth, value, and unit, so layers can be queried as precise point data and not just as rendered imagery.
-
Classification-aware access: Applies clearance-level filtering to every layer and observation query, so a single integration safely serves users at different secrecy levels without exposing data above a user's authorisation.
-
Tenant isolation by default: Scopes all reads and writes to the requesting organisation, keeping each customer's synchronised environmental holdings fully separated from every other tenant.
-
Audited ingest pipeline: Records each synchronisation with its source, region, classification, and observation count, producing a verifiable trail of what was ingested, by whom, and when.
-
Unified situational awareness: Emits each synchronised observation as a maritime operational entity, so environmental data flows into the same situational-awareness picture as vessel tracks, sensor feeds, and tactical data.
-
Aggregate environmental statistics: Exposes layer counts, observation counts, and covered-region counts so operators and dashboards can gauge coverage and freshness at a glance.
-
Standards-based ingestion: Consumes layers and observations over OPeNDAP and OGC WMS, the open protocols already used across operational oceanography, so compatible services can be onboarded without bespoke connectors.
Use Cases#
Naval and Maritime Security Operations#
Overlay live and historical currents, wave state, ice, and tides directly on the operational picture to plan courses, time transits, and assess where conditions favour or constrain movement. Environmental context sits beside vessel tracks so watch teams reason about the sea and the traffic together.
Search and Rescue#
Use current and wind-driven sea-surface conditions to inform drift estimation and route planning, helping responders prioritise search areas and choose safer, faster approaches to a casualty position.
Ice and Mine-Risk Assessment#
Combine ice-coverage layers with tactical data to flag routes that carry ice risk, and use environmental context to support mine and obstacle risk assessment in contested or seasonal waters.
Maritime Crime Investigation#
Provide environmental context for maritime crime cases, correlating the sea state, tides, and currents at a given time and place with vessel behaviour and reported incidents during analysis.
Multi-Clearance and Coalition Organisations#
Run one environmental integration across teams that hold different clearances. Each analyst, dashboard, and partner sees only the layers and observations their clearance permits, while the organisation maintains a single source of synchronised oceanographic data.
Integration#
The capability is reached through the platform's authenticated API, so analysts and dashboards query environmental layers from the same endpoint that serves vessel tracks, sensor feeds, and tactical data. Operations expose synchronised layers, the observation points within a chosen layer, and aggregate coverage statistics, plus an operation to synchronise a new layer from a given FCOO service. Every operation requires authentication and is automatically scoped to the caller's organisation and clearance.
-
Single-endpoint querying: Environmental layers and observations are retrieved alongside other maritime data through one authenticated API, removing the need for analysts to switch tools to bring oceanography into their picture.
-
OAuth2 and JWT access: Access uses the platform's standard OAuth2 and JWT model, so existing identity, role, and clearance assignments govern environmental data without a separate credential set.
-
OPeNDAP and OGC WMS connectors: New FCOO and compatible services are onboarded over open operational-oceanography protocols, letting customers plug in additional environmental sources with minimal bespoke work.
-
Normalised observation model: Every source is reduced to a consistent observation shape (position, depth, value, unit, time), so downstream dashboards and correlation logic treat all environmental feeds uniformly.
-
Situational-awareness emission: Synchronised observations are published as maritime operational entities, making environmental data a first-class part of the shared operational picture rather than an isolated overlay.
Open Standards#
-
OPeNDAP (Open-source Project for a Network Data Access Protocol): Open protocol for remote access to scientific and oceanographic datasets; used to retrieve environmental layers and observation values from FCOO and compatible services.
-
OGC Web Map Service (OGC 06-042): Open Geospatial Consortium standard for serving geo-referenced map layers; used to consume FCOO environmental map layers such as currents, waves, ice, and tides.
-
OGC Web Coverage Service (OGC 09-110r4): Open Geospatial Consortium standard for accessing gridded coverage data such as ocean-current fields and wave-height grids; complements WMS by exposing raw values rather than rendered imagery.
-
CF Conventions for Climate and Forecast Metadata (CF-1.x): Community metadata standard for NetCDF and OPeNDAP datasets; defines how variables, coordinates, units, and temporal axes are described in operational oceanography data.
-
GeoJSON (RFC 7946): IETF standard encoding for geo-referenced features; used to represent discrete observation points with position, depth, value, and unit in a form consumable by mapping and analysis clients.
-
ISO 8601: International standard for date and time representations; used to express temporal coverage, observation timestamps, and synchronisation records consistently across all environmental data.
Security & Compliance#
-
Authenticated access only: Every layer, observation, and synchronisation operation requires an authenticated identity; anonymous access is rejected.
-
Tenant data sovereignty: All persistence and retrieval is scoped to the requesting organisation, so environmental holdings never cross tenant boundaries.
-
Classification-level filtering: Layers and observations are filtered against each user's clearance, ensuring users receive only data at or below their authorised secrecy level.
-
Audited ingestion: Each synchronisation is logged with its source, region, classification, and observation count, supporting accountability, review, and compliance reporting.
Last Reviewed: 2026-05-26 / Last Updated: 2026-05-26