Global Ocean Accounts Partnership Secretariat · GOAP Technical Guidance on Ocean Accounting · circular

Data Harmonisation and Interoperability

Responsible officer: Dr Jordan GacutanDrafting: AI-assisted drafting from GOAP Secretariat source materials; source list to be published at the close of consultation.
GOAP Technical Guidance

Version 0.7.1 · 1 September 2026Draft for consultation — not final guidance and not to be cited as adopted
CC BY-NC 4.0

After completing this Circular, practitioners will be able to harmonise and integrate ocean accounting data from diverse sources, formats, and domains, applying interoperability standards that address the technical and methodological challenges of multi-source data integration. Data harmonisation underpins three decision contexts for ocean accounting: cross-agency data sharing within national statistical systems, international comparability of ocean accounts across jurisdictions, and dissemination of ocean accounting data to external users through standardised exchange platforms.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Cross-agency data sharing: Ocean accounts draw upon data from national statistical offices (economic statistics), environmental agencies (ecosystem monitoring), hydrographic organisations (bathymetry), fisheries management authorities (catch and effort data), and maritime administrations (vessel tracking). Without harmonised classifications, coordinate reference systems, and exchange formats, each bilateral data transfer requires bespoke transformation procedures. The standards described in this Circular enable agencies to establish common data integration protocols that reduce transaction costs and improve data quality through systematic quality checks.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

International comparability: Countries implementing ocean accounts require comparable indicators for benchmarking, knowledge exchange, and coordination of regional ocean governance. The SDMX framework provides the international standard for exchanging statistical data, enabling ocean accounting indicators to be disseminated through the same infrastructure as national accounts, environmental-economic accounts, and SDG indicators. Alignment with geospatial standards from the Open Geospatial Consortium and International Hydrographic Organization ensures that spatial data components of ocean accounts can similarly be exchanged across jurisdictions.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Standardised dissemination: Publication of ocean accounting data through SDMX-compliant data repositories enables automated discovery and retrieval by policy analysts, researchers, and decision-support systems. Classification concordances ensure that data collected under national frameworks can be mapped to international reference classifications, so that national detail is preserved and the data remain reusable.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

This Circular covers the principal international standards for statistical data exchange, including (1) the Statistical Data and Metadata Exchange (SDMX) framework, (2) geospatial interoperability standards from the Open Geospatial Consortium (OGC) and International Hydrographic Organization (IHO), and (3) classification concordance mechanisms that enable mapping between different classification systems. By applying the principles and protocols described here, compilers can establish data integration workflows that raise data quality and reduce manual processing.

Essential prerequisites:

  • TG-0.1 General Introduction to Ocean Accounts: conceptual framework and key components of Ocean Accounts.

Helpful background:

  • TG-0.7 Quality Assurance Principles: quality dimensions and assessment frameworks, particularly coherence and comparability.
Data Harmonisation and Interoperability / GOAP Technical Guidance

Note

Framework Position

This Circular addresses data harmonisation and interoperability across the accounting domains. Harmonisation ensures consistent measurement across edges linking economic flows to environmental stocks and ecosystem services to economic activity. In the Ocean Accounts Framework (TG-0.1 Figure 0.1.2):

EdgeDirectionDescription
E3FG1↔SG1Monetary flows between assets and economic sectors
E9SG3→FG1Ecosystem services to economy (SEEA)

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Ocean accounts draw upon a diverse range of sources: fisheries catch statistics from national statistical offices, bathymetric surveys from hydrographic agencies, satellite observations from earth observation programmes, ecosystem condition assessments from environmental monitoring networks, and economic statistics from national accounts. Each of these data streams has evolved within its own institutional context, employing different standards, classifications, formats, and temporal and spatial reference systems. Ocean accounting must harmonise these disparate data streams into a coherent accounting framework whilst preserving data quality and provenance. For guidance on spatial delineation of accounting units, see TG-2.12 Spatial Data Frameworks Sections 3.2 and 3.3. For temporal considerations, see TG-2.12 Spatial Data Frameworks Section 3.4.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

This section examines four interrelated dimensions of data harmonisation and interoperability: data standards that define common structures and semantics, exchange formats that enable machine-readable data transmission, interoperability protocols that support automated data discovery and retrieval, and classification concordances that enable translation between different coding systems. Together, these elements form the technical infrastructure for integrated ocean accounting.

Figure 4.6.1 shows how economic data (SDMX), geospatial and marine data (OGC/IHO S-100), and classification concordances feed an integration layer that produces coherent ocean accounts.

Data Harmonisation and Interoperability / GOAP Technical Guidance

· Figure 4.6.1

Statistical, geospatial and marine standards, with classification concordances, converge on an integration layer that yields ocean accounts on one classification, spatial and temporal basis. Colour marks role, not family. The system that runs this integration is Figure 4.6.2.

TG-4.6 -- Standards, formats and concordances feeding coherent ocean accounts A convergence diagram in four tiers. The top tier holds three standard families side by side, each carrying the same three rows, labelled in a left-hand gutter as the standard (Section 3.1), the exchange format (Section 3.2), and the interoperability protocol (Section 3.3). The statistical family is SDMX 3.1, ISO 17369, with its Data Structure Definition; formats SDMX-ML, SDMX-JSON and SDMX-CSV; and the SDMX REST API with registry subscribe and notify. The geospatial family is GSGF 2.0 with ISO 19115 and ISO/TS 19139 metadata; formats GeoJSON, JSON-FG, GML and GeoPackage; and the OGC services WFS, WMS and SOS. The marine family is IHO S-100 Edition 5.2.0 with the S-101, S-102, S-104 and S-111 product specifications; formats HDF5, GML and ISO 8211; and the Part 16 Interoperability Catalogue Model. All three families converge on a bus that feeds the second tier: an integration layer, in which the harmonisation workflow of Section 3.5 applies common concepts and codelists, a common spatial frame, a common reference period, and combined ISO and SDMX metadata; it is annotated that semantic alignment is the binding constraint, because the statistical and geospatial communities carry different data models. Classification concordances (Section 3.4) enter the integration layer from the left as a separate input: ISIC to CPC, ISIC Revision 4 to Revision 5, CPC Version 2.1 to Version 3.0, and national habitat classifications to the IUCN Global Ecosystem Typology. The integration layer produces the third tier: coherent ocean accounts on one classification basis, one spatial frame and one reference period, implemented by the lakehouse architecture of Figure 4.6.2. A cross-cutting band at the base sets out the four interoperability dimensions of GSGF 2.0 after the European Interoperability Framework -- legal, organisational, semantic and technical -- with the semantic and technical dimensions shaded as the two the standards above deliver, and the legal and organisational dimensions drawn unfilled and dashed because they are institutional agreements rather than anything the standards can supply. Standards, formats and concordances → coherent ocean accounts §3.1 Standard §3.2 Format §3.3 Protocol Statistical national accounts & official statistics SDMX 3.1 · ISO 17369 Data Structure Definition (DSD) SDMX-ML · SDMX-JSON · SDMX-CSV SDMX REST API structure · data · availability registry: subscribe / notify Geospatial statistical–geospatial integration GSGF 2.0 · ISO 19115 / 19139 Principle 4 · metadata schema GeoJSON · JSON-FG · GML · GeoPackage OGC WFS · WMS · SOS spatial & attribute filtering map tiles · sensor observations Marine domain hydrography & the sea floor IHO S-100 Ed. 5.2.0 S-101 / S-102 / S-104 / S-111 HDF5 · GML · ISO 8211 S-100 Part 16 Interoperability Catalogue common interfaces agreed structures & semantics Classification concordances §3.4 · UNSD official tables ISIC ↔ CPC (activity ↔ product) ISIC Rev.4 → Rev.5 CPC Ver.2.1 → Ver.3.0 national habitat → IUCN GET Integration layer the harmonisation workflow of §3.5 applies these agreements Common concepts & codelists (DSD) Common spatial frame — CRS, grid, units Common reference period & vintage Metadata: ISO 19115 / 19139 + SDMX Semantic alignment is the binding constraint: the two communities carry different data models. produces Coherent ocean accounts one classification basis · one spatial frame · one reference period SDMX-structured for dissemination implemented by the lakehouse architecture → Figure 4.6.2 Interoperability dimensions — GSGF 2.0, after the European Interoperability Framework Legal Organisational Semantic Technical Legal and organisational interoperability are institutional agreements; the standards above deliver the semantic and technical dimensions (shaded). Standard (§3.1) Format / protocol (§3.2–3.3) Classification concordance Integration layer Compiled ocean accounts

Source TG-4.6 §3.1 (data standards, Tables 3.1.1–3.1.2), §3.2 (exchange formats), §3.3 (interoperability protocols) and §3.4 (classification concordances); SDMX 3.1 information model (May 2025), ISO 17369; GSGF v2.0 (UN-GGIM / UNSC 2025); ISO 19115 / ISO/TS 19139; IHO S-100 Edition 5.2.0 (June 2024) and the S-101 / S-102 / S-104 / S-111 product specifications (December 2024); UNSD ISIC Rev.4–Rev.5 and CPC Ver.2.1–Ver.3.0 correspondence tables; IUCN Global Ecosystem Typology.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Data standards provide the foundational agreements on how data should be structured, described, and interpreted. For ocean accounting, three families of standards are particularly important: statistical data standards, geospatial data standards, and marine domain-specific standards. The application of these standards supports the quality dimensions described in TG-0.7 Quality Assurance Principles, particularly coherence and comparability.

Statistical Data and Metadata Exchange (SDMX)

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The Statistical Data and Metadata Exchange (SDMX) initiative provides the international standard for exchanging statistical data and metadata. Developed by the seven sponsor organisations (BIS, ECB, Eurostat, IMF, OECD, United Nations, and World Bank), SDMX has been designated as an ISO International Standard (ISO 17369). The SDMX 3.1 version, released in May 2025, introduces enhanced support for geospatial data, microdata, and improved data structure definitions.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

SDMX is built around an information model that defines the structural metadata needed to describe statistical data. At its core is the Data Structure Definition (DSD), which specifies the dimensions, attributes, and measures that characterise a particular data collection. For ocean accounting, DSDs would define the structure of fisheries statistics, marine economic activity data, and environmental flow accounts. The structure of physical flow accounts is described in TG-2.6 Ocean Economy Investment.

The SDMX framework supports three process patterns for data exchange:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  1. Bilateral exchange — counterparties agree on specific formats and processes
  2. Gateway exchange — multiple organisations agree on a common exchange format
  3. Data-sharing exchange — open standards enable any organisation to access and use data

For ocean accounting, the data-sharing model is particularly relevant as it enables national statistical offices, environmental agencies, and research institutions to publish data in standard formats that can be automatically discovered and integrated.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

SDMX provides three transmission formats (SDMX-ML, SDMX-JSON, SDMX-CSV), detailed in Section 3.2 below. The CSV format is particularly accessible to non-specialist users whilst remaining losslessly convertible to the other formats. SDMX registry services provide “visibility into the data and metadata existing within the community, and support the access and use of this data and metadata by providing a set of triggers for automated processing”. A registry-based architecture enables ocean accounting compilers to discover available data sources, retrieve structural metadata, and automate data collection workflows.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The Global Statistical Geospatial Framework (GSGF), version 2.0 released by UN-GGIM and the Statistical Commission in 2025, provides the overarching framework for integrating statistical and geospatial information. The GSGF defines five principles, of which Principle 4 on “Statistical and geospatial interoperability” is directly relevant to ocean accounting data integration.

Data interoperability, as defined in the GSGF, refers to “the ability of different systems, organizations, and applications to exchange, interpret, and use data in a coordinated manner”. The framework identifies four interoperability dimensions derived from the European Interoperability Framework (EIF). Table 3.1.1 below summarises these dimensions.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

For ocean accounting, semantic interoperability is particularly challenging as statistical and geospatial communities have “evolved their own general data models, metadata capabilities, architectures, and data infrastructures, creating differences in fundamental terminology over time”.

The Open Geospatial Consortium (OGC) provides the principal geospatial interoperability standards relevant to ocean accounting. Table 3.1.2 below summarises those standards.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Two additional ISO standards are essential for geospatial metadata management. ISO 19115 (Geographic information — Metadata) provides the standard schema for describing geographic datasets and services, defining the metadata elements needed for data discovery, evaluation, and use. Its XML implementation, ISO/TS 19139, specifies the encoding format in which ISO 19115 metadata should be stored and exchanged, enabling machine-readable metadata interchange between systems. Together, these standards ensure that geospatial data used in ocean accounts carry sufficient provenance and quality information for informed integration.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The GSGF recommends that organisations “host appropriate technical infrastructures which support the use of the relevant standards where systems and services are linked through standard interfaces, services, and data formats”.

Marine Domain Standards: IHO S-100

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The International Hydrographic Organization (IHO) S-100 standard provides the Universal Hydrographic Data Model for marine geospatial data. S-100 Edition 5.2.0, adopted in June 2024, builds upon the earlier Edition 5.1.0 (October 2023) and establishes “a contemporary hydrographic geospatial data standard that can support a wide variety of hydrographic-related digital data sources, and is fully aligned with mainstream international geospatial standards, in particular the ISO 19100 series”. In December 2024, IHO Member States approved operational editions of key S-100-based Product Specifications, including S-101 (Electronic Navigational Charts), S-102 (Bathymetric Surface), S-104 (Water Level Information), and S-111 (Surface Currents).

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

S-100 is designed to support applications “that go beyond the scope of traditional hydrography — for example, high-density bathymetry, seafloor classification, marine GIS”. The standard comprises multiple parts covering conceptual schema, feature catalogues, spatial schemas, metadata, portrayal, and encoding formats including ISO 8211, GML, and HDF5.

Part 16 of S-100 specifically addresses the Interoperability Catalogue Model, which “enables interoperability between disparate technologies through the use of common interfaces”. For ocean accounts that integrate hydrographic data (bathymetry, tides, currents) with ecosystem and economic data, S-100 provides the interoperability framework for the marine domain component.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Standardised exchange formats enable data to be transmitted between systems in machine-readable form. The choice of format affects both the technical ease of data integration and the preservation of semantic content.

The three SDMX transmission formats introduced in Section 3.1 serve distinct use cases:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • SDMX-ML (XML-based) provides the most complete expression of the SDMX information model. The Structure Specific Data format is “the sole XML format for data exchange” following the deprecation of legacy formats in SDMX 3.0. Appropriate for formal data exchanges where complete metadata preservation is required.
  • SDMX-JSON is “well-suited to web-based applications and modern programming environments” and is increasingly preferred for API-based data access.
  • SDMX-CSV provides a “simple columnar format” that offers accessibility for practitioners without specialised tools whilst still enabling conversion to other SDMX formats “without loss”. CSV may serve as a practical intermediate format for data validation and review.

For geospatial ocean accounting data, several format standards are relevant:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

GeoJSON and JSON-FG (OGC Features and Geometries JSON) provide JSON-based formats for geographic features that are “well-suited to web mapping applications”. These formats are appropriate for ecosystem extent boundaries, marine protected area polygons, and other vector features.

GML (Geography Markup Language) provides the full XML encoding for geographic information conforming to ISO 19136. GML is required for formal data exchange in contexts where complete geometry representation and coordinate reference system information must be preserved.

HDF5 (Hierarchical Data Format version 5) is adopted by IHO S-100 for gridded and imagery data. HDF5 is appropriate for bathymetric grids, ocean temperature fields, and other multi-dimensional environmental data.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

GeoPackage provides an SQLite-based container format that can store both vector and raster data. GeoPackage is increasingly used for distributing compiled geospatial datasets.

Interoperability protocols define how systems communicate to discover, query, and retrieve data. Effective protocols enable automation of data collection workflows. Automation reduces manual processing and improves timeliness.

SDMX RESTful Web Services

SDMX defines a RESTful web services API for querying data and structural metadata. The API enables:

  • Structure queries — retrieving Data Structure Definitions, codelists, concept schemes
  • Data queries — retrieving data observations filtered by dimension values
  • Availability queries — discovering what data exists for given parameters
Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The RESTful API design means queries are expressed through URL patterns, enabling integration with standard web tools. For example, a query for fisheries catch data might specify the dataflow, reference area, time period, and species codes through URL parameters.

The SDMX registry architecture supports “automated processing” through subscription and notification services. Compilers can subscribe to data updates and receive notifications when new data becomes available, enabling near-real-time data integration workflows.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The OGC web services introduced in Section 3.1 (Table 3.1.2) function as interoperability protocols: WFS supports spatial and attribute filtering for retrieval of ecosystem assets within specified bounds, whilst WMS supports rendered map visualisation of spatial context. The Sensor Observation Service (SOS) complements these by providing access to sensor data and observations, relevant for integrating ocean monitoring data (water quality, temperature, wave height) into ocean accounts.

The GSGF emphasises that technical infrastructure should support “standard interfaces, services, and data formats, including metadata standards”. Implementation of OGC services enables ocean accounting systems to integrate with national spatial data infrastructures.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The FAIR Principles (Findability, Accessibility, Interoperability, Reusability) provide guiding principles for scientific data management that are increasingly applied to statistical data. The GSGF explicitly incorporates FAIR principles, noting that the Interoperability principle “emphasises metadata” and that “(meta)data should be ready to be exchanged, interpreted and combined in a (semi)automated way”.

For ocean accounting, FAIR principles translate to practical requirements summarised in Table 3.3.1 below.

The FAIR principles align with quality dimensions in TG-0.7 Quality Assurance Principles and should guide the design of ocean accounting data management systems.

Classification concordances (also called crosswalks or mapping tables) enable translation between different classification systems. For ocean accounting, concordances are essential for:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Linking economic activity data (ISIC) with product data (CPC)
  • Mapping national ecosystem classifications to international reference classifications
  • Converting between historical and current classification versions
  • Integrating data collected under different classification frameworks

The classification systems relevant to ocean accounting are described in TG-0.2 Overview of Relevant Statistical Standards.

Activity and Product Classifications

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The relationship between ISIC (activity classification) and CPC (product classification) is fundamental to economic statistics. As the CPC documentation explains, “each subclass of the CPC consists of goods or services that are generally produced in a specific class or classes of the ISIC”. The CPC documentation includes explicit correspondences to ISIC, enabling ocean accounting compilers to link product flows with producing industries.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The CPC serves as a “central” classification providing “a framework for international comparison and promotes harmonization of various types of statistics related to goods and services”. The classification was “developed primarily to enhance harmonization among various fields of economic and related statistics and to strengthen the role of national accounts as an instrument for the coordination of economic statistics”.

With the endorsement of ISIC Rev.5 and CPC Ver.3.0 by the UN Statistical Commission in March 2024, compilers should note that the division-level structure for ocean-relevant activities has been maintained, though with increased detail at lower classification levels. For ocean accounting, key concordance relationships include:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • ISIC Division 03 (Fishing and Aquaculture) corresponds to CPC Division 04 (Fish and Other Fishing Products)
  • ISIC Division 50 (Water Transport) corresponds to relevant groups within CPC Divisions 64-67 (Transport and Supporting Services), with specific correspondence at the group and class level documented in official UNSD concordance tables

The UNSD has developed official correspondence tables for the ISIC Rev.4-to-Rev.5 and CPC Ver.2.1-to-Ver.3.0 transitions. These tables should be used when bridging data compiled under different classification versions. Compilers working with historical data collected under ISIC Rev.4 and CPC Ver.2.1 should apply these official correspondence tables rather than constructing ad hoc mappings, to ensure consistency and comparability across time.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Detailed guidance on ocean-relevant economic classifications is provided in TG-0.2 Overview of Relevant Statistical Standards.

The IUCN Global Ecosystem Typology (GET) provides the reference classification for ecosystem types in SEEA Ecosystem Accounting. However, “countries may have their own national classification system of ecosystems (or ecological areas) that could be used for the extent accounts. In such cases, developing a bridge or concordance (often called a schema crosswalk in GIS) of this national classification system with the GET reference classification may facilitate comparability across countries”.

For marine ecosystems specifically, concordances may be required between:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • National marine habitat classifications and GET Marine Realm types
  • EUNIS habitat classification and GET Ecosystem Functional Groups
  • National land cover classifications and GET transitional realm types (for coastal areas)

The SEEA Biophysical Modelling Guidelines note that the GET “represents a global typological framework that applies a process-based approach to ecosystem classification across the whole planet”. The hierarchical structure (Realms, Biomes, Ecosystem Functional Groups) provides natural aggregation levels for concordance development.

Guidance on ecosystem classification for ocean accounts is provided in TG-4.1 Remote Sensing and Geospatial Data Section 3.2.4 and TG-3.1 Asset Accounts.

Developing classification concordances involves:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  1. Structural comparison — examining the hierarchical structure and level of detail in each classification
  2. Conceptual alignment — identifying where definitions align or diverge
  3. Mapping relationships — defining one-to-one, one-to-many, or many-to-many relationships
  4. Documentation — recording mapping rationale and any approximations
  5. Validation — testing concordances with actual data

The UNFC (United Nations Framework Classification for Resources) provides an example of formalised concordance development: “mapping schemes have been developed showing the link between the UNFC2009 and the SPE and CRIRSCO classifications” for mineral and petroleum resources.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Classification systems evolve over time through revision processes. ISIC has progressed through Revisions 3, 3.1, 4, and now 5. The CPC has progressed through Versions 1.0, 1.1, 2.0, 2.1, and now 3.0. The UN Statistics Division maintains official correspondence tables between versions to enable time series compilation across classification changes.

For ocean accounting, temporal concordances are required when:

  • Compiling time series that span classification revisions
  • Integrating historical data collected under previous classifications
  • Comparing international data collected under different version implementations
Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The ISIC documentation emphasises that “continuity, i.e., comparability between the revised and preceding versions of ISIC, has always been a major concern expressed by the Commission”. The official ISIC Rev.4-to-Rev.5 correspondence table, developed between March and October 2024 following the endorsement of ISIC Rev.5 explanatory notes, should be consulted when compiling time series that bridge these classification versions. Similarly, the CPC Ver.2.1-to-Ver.3.0 correspondence table is available through the UNSD classifications portal.

3.5 Data Harmonisation Workflow

Implementing data harmonisation for ocean accounts requires a systematic workflow that transforms heterogeneous source data into consistent, integrated accounting tables. This section describes the compilation procedure and provides a worked example.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The data harmonisation workflow consists of four sequential phases:

Phase 1: Classify — Assign source data to standardised classifications. For ocean accounting, this involves:

  • Mapping economic activity data to ISIC Rev.5 divisions and groups
  • Mapping product flows to CPC Ver.3.0 categories
  • Mapping ecosystem types to IUCN GET Ecosystem Functional Groups
  • Mapping spatial units to the national spatial framework and coordinate reference system

Classification mappings should be documented in concordance tables that record the source classification, target classification, mapping type (1:1, 1:many, many:1, many:many), and any assumptions or approximations.

Phase 2: Map — Transform source data values to common units and temporal reference periods. This includes:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Converting spatial coordinates to the accounting area’s coordinate reference system (typically WGS84 for horizontal coordinates)
  • Aligning temporal references to accounting period start/end dates (calendar year, fiscal year)
  • Converting physical units to standard measurement units (e.g., tonnes for biomass, hectares for extent, cubic metres for water volumes)
  • Converting monetary values to constant prices using deflators where time series require comparability

Mapping transformations should preserve source values in metadata to enable quality checks and re-transformation if specifications change.

Phase 3: Validate — Check integrated data for consistency, completeness, and plausibility. Validation includes:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Range checks: values fall within plausible bounds (e.g., catch cannot exceed vessel capacity)
  • Balance checks: supply equals use in flow accounts
  • Spatial checks: geometries are valid, no gaps or overlaps in exhaustive spatial frameworks
  • Temporal checks: time series are continuous, no unexplained breaks
  • Cross-source confrontation: data from multiple sources describing the same phenomena are reconciled

Validation should generate exception reports that flag issues for resolution. The quality assurance framework in TG-0.7 Quality Assurance Principles provides detailed validation procedures.

Phase 4: Integrate — Compile validated data into accounting tables. Integration produces:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Asset accounts combining physical extent, condition indicators, and monetary valuations
  • Flow accounts recording extractions, emissions, and ecosystem service flows
  • Supply-use tables linking ocean economy production and consumption
  • Combined presentations integrating environmental, economic, and social dimensions (see TG-3.8 Combined Presentations)

Table 3.5.1: Data harmonisation workflow phases

Worked Example: Harmonising Fisheries Data Using SDMX

This synthetic example demonstrates the data harmonisation workflow for integrating fisheries catch data from multiple agencies into ocean accounts. The scenario: a national statistical office is compiling fisheries accounts and must integrate data from three sources with different reporting frameworks:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Source A: National fisheries agency — species-level catch data by fishing zone, reported quarterly in tonnes live weight
  • Source B: Port authority — landing declarations by vessel and port, reported monthly in various product forms (whole fish, fillets, processed)
  • Source C: Customs administration — seafood export data using national tariff codes, reported monthly in kilograms and monetary value (FOB)

Phase 1: Classify

The compiler establishes an SDMX Data Structure Definition (DSD) for fisheries flow accounts with the following dimensions:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • REF_AREA: Fishing zone (territorial waters, EEZ zones by bathymetry, high seas)
  • TIME_PERIOD: Accounting period (annual, with quarterly detail available)
  • SPECIES: Fish species using FAO ASFIS codes
  • ACTIVITY: Producing industry using ISIC Rev.5 codes (Group 031: Marine fishing)
  • PRODUCT: Output product using CPC Ver.3.0 codes (Division 04: Fish and other fishing products)

For each source, the compiler develops classification mappings:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Source A reports species using national codes, and a concordance table maps these to FAO ASFIS codes (mostly 1:1)
  • Source B records product forms, and a concordance table maps these to CPC Ver.3.0 with conversion factors to derive live weight equivalent (1:many mapping: one product code may correspond to multiple CPC classes depending on processing level)
  • Source C uses HS 2022 tariff codes, and the official UNSD concordance table maps these to CPC Ver.3.0 (many:many mapping requiring allocation based on supplementary information)

Phase 2: Map

Unit conversions and temporal alignment:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Source A data are already in tonnes live weight, and temporal alignment aggregates quarterly data to annual totals for stock accounts whilst preserving quarterly detail for seasonal analysis
  • Source B landing weights require conversion to live weight equivalent using species-specific factors (e.g., fillets to whole fish factor 2.5 for snapper, 2.8 for tuna). Conversion factors documented in metadata
  • Source C export data in kilograms converted to tonnes product weight, and to live weight equivalent using the same species- and product-form factors as Source B, with monetary values (FOB) converted to national currency constant prices using fish price deflator

Spatial mapping:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Source A fishing zones map to ocean accounting spatial framework using GIS overlay of zone boundaries
  • Source B port locations geocoded using national address gazetteer, with landings attributed to fishing zones using vessel logbook data on fishing grounds (where available) or pro-rata allocation based on Source A zone proportions for species
  • Source C export port locations geocoded, with spatial attribution to production zones inferred from Source A and B integration

Phase 3: Validate

Validation checks applied:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Range check: No individual vessel catch exceeds vessel hold capacity (cross-reference with vessel register)
  • Balance check: Total catch (Source A) equals total landings (Source B) plus estimated at-sea discards, within tolerance threshold of 5%
  • Cross-source confrontation: Export volumes (Source C) reconciled with landing volumes (Source B) accounting for domestic consumption, processing losses, and stock changes

Discrepancies identified:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • Source A reports 15,200 tonnes tuna catch in EEZ, whilst Source B records 14,100 tonnes landings. The difference is attributed to unreported landings (estimated 600 tonnes based on observer coverage) and at-sea discards (estimated 500 tonnes, 3.3% discard rate consistent with observer data)
  • Source C reports 8,200 tonnes tuna exports in product weight, or 9,100 tonnes live weight equivalent (the 900-tonne difference is weight removed in processing), which reconcile with Source B after accounting for 4,800 tonnes domestic consumption and 200 tonnes cold storage stock increase

Validation produces exception report documenting assumptions and highlighting areas requiring further investigation (unreported catch estimation method).

Phase 4: Integrate

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Validated data compiled into SDMX-compliant fisheries flow account table with dimensions:

The DSD includes attributes documenting data sources, estimation methods, and quality flags. The compiled data structure enables:

  • Dissemination through SDMX registry for automated retrieval by analysts
  • Integration with economic accounts using ISIC and CPC concordances
  • Comparison with international fisheries statistics using FAO ASFIS species codes
  • Spatial analysis of catches by zone for marine spatial planning

The worked example demonstrates how SDMX Data Structure Definitions provide a standardised framework for harmonising heterogeneous source data. That framework supports systematic quality checks and produces interoperable outputs for ocean accounting.

3.6 Modular Data Architecture Patterns

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The technical infrastructure supporting ocean account data harmonisation must accommodate diverse data sources, multiple processing workflows, and varied dissemination requirements. This section describes modular architecture patterns that enable national statistical offices and ocean accounting programmes to build scalable, maintainable data systems. The guidance draws on established practices in statistical data management and modern data engineering, adapted to the specific requirements of environmental-economic accounting.

Data lake versus data warehouse

Two architectural paradigms are relevant for ocean accounting data infrastructure: data lakes and data warehouses. Each serves a distinct purpose, and many implementations will employ both in combination.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

A data lake stores data in its original format (raw satellite imagery, CSV files from monitoring stations, spreadsheets from fisheries agencies, GIS shapefiles) without imposing a predefined schema. The data lake preserves full provenance and enables re-processing when methodologies change. For ocean accounting, a data lake is appropriate for ingesting heterogeneous source data from the diverse agencies described in Section 3.1, including remote sensing products (TG-4.1 Remote Sensing and Geospatial Data), survey microdata (TG-4.2 Survey Methods for Ocean Economic Activity), administrative records (TG-4.3 Administrative Data Sources), and citizen science observations (TG-4.4 Citizen Science).

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

A data warehouse stores data in a structured, schema-enforced format optimised for analytical queries and reporting. The warehouse contains harmonised data that has passed through the classify-map-validate-integrate workflow described in Section 3.5. For ocean accounting, the data warehouse holds the compiled account tables in SDMX-compliant structures, ready for dissemination and analysis. The data warehouse enforces the classification concordances (Section 3.4) and accounting identities that ensure internal consistency.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The recommended pattern for ocean accounting is a lakehouse architecture that combines both approaches: source data are ingested into a data lake, processed through harmonisation pipelines, and loaded into a structured warehouse layer for dissemination. This pattern provides the flexibility to accommodate new data sources without redesigning the warehouse schema, whilst maintaining the rigour required for official statistical products. Figure 4.6.2 sets out the end-to-end lakehouse data architecture, in which heterogeneous source systems feed a data lake, a classify-map-validate-integrate harmonisation pipeline processes the lake’s data into a schema-enforced warehouse, and the warehouse publishes through a tiered dissemination layer, with international standards and the metadata, quality and governance framework as cross-cutting rails.

Data Harmonisation and Interoperability / GOAP Technical Guidance

· Figure 4.6.2

Lakehouse architecture moves ocean-account data from source systems through lake, warehouse, and dissemination layers under cross-cutting standards rails. Warehouse holds SDMX-structured Ocean Accounts. No adopted SEEA Ocean standard; GOAP TG is the interim framework.

TG-4.6 -- Ocean account data architecture (lakehouse pattern) A layered system architecture for compiling ocean accounts in a national statistical office. A central processing spine runs left to right in five numbered layers: (1) heterogeneous source systems -- economic statistics, remote sensing, marine and hydrographic data, environmental monitoring and surveys, and research and citizen science -- feed into (2) a data lake that ingests raw data in any format with schema-on-read and preserved provenance; the lake feeds (3) a harmonisation pipeline of four sequential stages -- classify, map, validate, integrate; the pipeline loads (4) a data warehouse holding SDMX-structured Ocean Accounts (asset, extent, condition, ecosystem-service-flow and monetary tables) with schema-on-write and enforced accounting identities; the warehouse publishes to (5) a dissemination and access layer offering discovery, metadata and data tiers via SDMX REST and OGC APIs and a registry, serving analysts, policy users and international exchange. Two cross-cutting bands span every layer: a standards rail (SDMX 3.1, OGC, IHO S-100, ISO 19115/19139, GSGF 2.0, FAIR) at the top, and a metadata, quality and governance rail (metadata catalogue, FAIR principles, quality tiers, uncertainty reporting) at the bottom. Each layer notes an example open-source tool; the tools are illustrative, not prescriptive. No SEEA Ocean standard has been adopted; GOAP Technical Guidance provides the interim methodological framework. Cross-cutting standards — apply across every layer below SDMX 3.1 · OGC (WFS / WMS / API) · IHO S-100 Ed. 5.2 · ISO 19115 / 19139 · GSGF 2.0 · FAIR 1 · Sources 2 · Data lake 3 · Harmonisation 4 · Warehouse 5 · Dissemination Economic stats SNA 2025 · ISIC / CPC Remote sensing TG-4.1 · OGC Marine & hydro IHO S-100 Env. & surveys TG-4.2 / 4.3 Research / citizen TG-4.4 / 4.5 ingest Raw ingest any format schema-on-read provenance preserved CSV · GIS HDF5 · imagery process 1 · Classify → standard codes 2 · Map units · CRS · time 3 · Validate range · balance · spatial 4 · Integrate compile account tables load Ocean Accounts SDMX-structured Asset · Extent Condition ES flow · Monetary schema-on-write accounting identities enforced publish Discovery tier Metadata tier Data tier SDMX REST · OGC API registry: subscribe / notify Consumers analysts · policy international exchange Example tools (illustrative, not prescriptive): e.g. MinIO · Parquet e.g. Python / R · GDAL e.g. PostgreSQL + PostGIS e.g. .Stat Suite · GeoServer Cross-cutting: metadata, quality & governance Metadata catalogue — ISO 19115 / 19139 (geospatial) + SDMX (statistical); example tools: GeoNetwork, Fusion Metadata Registry FAIR principles · Quality tiers: T1 official / T2 administrative / T3 research · Uncertainty reporting L1–L3 Source systems Data lake (raw ingest) Harmonisation pipeline Warehouse · Ocean Accounts Dissemination & access Cross-cutting layer (standards & governance)

Source TG-4.6 draft §3.5 (data harmonisation workflow, Table 3.5.1) and §3.6 (modular data architecture patterns, Tables 3.6.1–3.6.2); SDMX 3.1 information model (May 2025); GSGF v2.0 (UN-GGIM / UNSC 2025); IHO S-100 Edition 5.2.0 (June 2024); ISO 19115 / 19139; SEEA CF (2012); SNA 2025.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Table 3.6.1: Architecture pattern comparison for ocean accounts

API design for data access

Application Programming Interfaces (APIs) enable automated data exchange between ocean accounting systems and external users. The API design should follow the SDMX RESTful web services specification (Section 3.3) for statistical data access, supplemented by OGC API standards for geospatial data. Key design principles include:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

APIs should provide three access tiers: a discovery tier (what data are available, covering which areas and periods), a metadata tier (data structure definitions, classification codelists, quality reports), and a data tier (observation values with full dimensional context). This mirrors the SDMX architecture of structure queries, availability queries, and data queries. Each tier should support standard HTTP methods and return responses in both SDMX-JSON and SDMX-CSV formats to accommodate different client capabilities.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Versioning is essential for APIs serving official statistics. Each API version should be maintained for a minimum of two years after a successor version is released, enabling downstream systems to migrate without disruption. Version identifiers should appear in the URL path (e.g., /api/v2/data/ocean-accounts/...) following REST conventions.

Authentication and access control should follow the data governance policies established by the national statistical office. Public-use indicators may be served without authentication, whilst microdata or geographically detailed data may require registration and licence acceptance, consistent with the FAIR principles described in Section 3.3.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Complete metadata is essential for data discovery, evaluation, and reuse. Ocean accounting data should carry metadata conforming to two complementary standards:

Geospatial metadata follows ISO 19115 / ISO 19139 (introduced in Section 3.1). All geospatial data products used in ocean accounts (ecosystem extent maps, bathymetric grids, spatial unit boundaries) should carry ISO 19115-compliant metadata encoded in ISO 19139 XML, documenting the coordinate reference system, spatial resolution, temporal coverage, processing history, and quality assessment results.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Statistical metadata follows the SDMX information model (Section 3.1). All compiled ocean account tables should be accompanied by SDMX structural metadata defining the dimensions, attributes, and measures of each dataset. Reference metadata (quality reports, methodological descriptions) should follow the SDMX metadata structure definition format.

Where ocean accounting data combines geospatial and statistical components (as is typical), both metadata standards should be applied. The GSGF (Section 3.1) provides guidance on achieving interoperability between ISO 19115 and SDMX metadata, recommending that organisations maintain metadata catalogues that link geospatial and statistical metadata for the same underlying datasets.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

National statistical offices and ocean accounting programmes with constrained budgets can implement the lakehouse architecture using open-source software. The following stack has been demonstrated in environmental-economic accounting contexts and aligns with the standards described in this Circular:

Table 3.6.2: Open-source technology stack for ocean accounting data infrastructure

The SDMX community maintains the .Stat Suite, an open-source platform for SDMX data dissemination that is already used by several national statistical offices and international organisations. For geospatial data, GeoServer provides OGC-compliant web services. These tools can be deployed on standard server infrastructure or cloud platforms, with costs scaling according to data volume and user load.

3.7 Science-to-Accounts Translation Protocols

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Ocean accounts depend on data from scientific research programmes (oceanographic surveys, ecological monitoring, biodiversity assessments, and fisheries stock assessments) that are produced for scientific purposes and must be translated into the structured formats required by accounting frameworks. This section provides protocols for converting research datasets into account-ready inputs, managing uncertainty, and establishing quality tiers that reflect the maturity and reliability of different data sources.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Scientific datasets differ from administrative and statistical data in several respects that affect their suitability for ocean accounts. Research data may cover irregular spatial domains (transects, sampling stations) rather than exhaustive spatial frameworks, may use non-standard temporal reference periods (field seasons, project durations) rather than accounting years, and may employ bespoke classification schemes in place of international standard classifications. The conversion protocol addresses each of these differences systematically.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Spatial harmonisation: Research data collected at point locations (monitoring stations, sampling sites) must be interpolated or modelled to produce estimates for the exhaustive spatial units used in ocean accounts. The biophysical modelling guidance in TG-2.1 Aggregate Biophysical Indicators of Environmental State describes interpolation and modelling techniques. Compilers should document the interpolation method, the spatial support (area over which each estimate applies), and the estimation uncertainty. Remote sensing data (TG-4.1 Remote Sensing and Geospatial Data) can provide spatially complete coverage to supplement point-based research data.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Temporal alignment: Research datasets with non-standard temporal coverage must be adjusted to accounting periods. Where research data cover a different period (e.g., a biological survey conducted from March to November), compilers should assess whether temporal adjustment is needed (for stocks that change slowly, the survey period may be a reasonable proxy for the annual average) or whether correction factors should be applied (for seasonally variable quantities such as biomass or water quality). The temporal alignment should be documented in metadata, including any assumptions about seasonal patterns.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Classification mapping: Research datasets often use scientific taxonomic or habitat classification schemes that differ from the standard classifications used in ocean accounts. Compilers should develop and maintain concordance tables mapping research classifications to accounting classifications (IUCN GET for ecosystem types, FAO ASFIS for species, ISIC/CPC for economic activities). The concordance development process described in Section 3.4 applies. Where research classifications provide finer detail than accounting classifications, the mapping is straightforward (aggregation). Where research classifications are coarser or use different conceptual categories, expert judgement is required and should be documented.

Table 3.7.1: Science-to-accounts conversion steps

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Scientific data carry measurement uncertainty that must be propagated through the accounting framework. Ocean accounts should report uncertainty for key aggregates, enabling users to assess the confidence they can place in derived indicators. Three levels of uncertainty reporting are recommended, in order of increasing sophistication:

Level 1 — Qualitative assessment: Each data input is assigned a qualitative uncertainty rating (low, medium, high) based on expert judgement of the data source, collection method, and processing steps. This minimum level is feasible for all ocean accounting programmes and should be documented in metadata for every compiled account.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Level 2 — Confidence intervals: Key aggregates (total ecosystem extent, total fish stock biomass, ocean economy GVA) are reported with confidence intervals derived from the uncertainty of input data. Where input uncertainties are characterised as standard errors or confidence intervals, propagation follows standard statistical methods (error propagation for sums, products, and ratios). This level requires quantitative uncertainty estimates for the major input datasets.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Level 3 — Monte Carlo simulation: For accounts involving complex non-linear transformations (such as ecosystem service valuation using benefit transfer, or carbon stock estimation using allometric equations), Monte Carlo simulation provides the most rigorous uncertainty propagation. Input distributions are sampled repeatedly, the accounting calculations are performed for each sample, and the resulting distribution of outputs characterises the aggregate uncertainty. This level requires specification of probability distributions for all major inputs and is appropriate for high-priority accounts where uncertainty is a policy concern.

Table 3.7.2: Uncertainty reporting levels

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Not all data used in ocean accounts meet the standards of official statistics. To accommodate data of varying provenance and reliability whilst maintaining transparency, ocean accounts should classify data inputs into three quality tiers:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Tier 1 — Official statistics: Data produced by national statistical offices or designated official statistics producers, compiled according to the UN Fundamental Principles of Official Statistics. Tier 1 data have been through established quality assurance processes and carry the authority of the national statistical system. Examples include national accounts aggregates, population census data, and fisheries catch statistics compiled by the national statistical office. The quality assurance framework in TG-0.7 Quality Assurance Principles describes the quality dimensions applicable to official statistics.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Tier 2 — Provisional and administrative data: Data from government agencies (environmental ministries, fisheries authorities, port authorities) that follow documented collection and processing procedures but have not been formally designated as official statistics. Tier 2 data may be subject to revision and may not meet all quality dimensions of official statistics. Examples include environmental monitoring data, vessel tracking records, and protected area registries. Administrative data guidance is provided in TG-4.3 Administrative Data Sources.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Tier 3 — Experimental and research data: Data from research programmes, citizen science initiatives, remote sensing products, and modelled estimates that have been peer-reviewed or validated but are not part of the official statistical system. Tier 3 data are often the only source available for ecosystem condition indicators, ecosystem service estimates, and blue carbon stocks. Research data guidance is provided in TG-4.5 Research Data, and citizen science guidance in TG-4.4 Citizen Science.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Combined presentations and dashboards should display the quality tier for each indicator, enabling users to distinguish between well-established indicators based on official statistics and emerging indicators based on experimental estimates. Over time, investment in data systems should aim to progressively elevate key indicators from Tier 3 to Tier 2 and from Tier 2 to Tier 1.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Research data entering the ocean accounts should undergo peer review appropriate to the quality tier. For Tier 3 data, the minimum requirement is that the underlying research has been published in a peer-reviewed journal or technical report, or has been reviewed by a technical advisory committee with relevant domain expertise. For Tier 2 data, the data collection methodology should be documented and reviewed by the national statistical office or an equivalent quality assurance body. For Tier 1 data, the full quality assurance framework of the national statistical system applies.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Where ocean accounting programmes commission new research or monitoring to fill data gaps, the research design should be reviewed before data collection begins (to ensure the outputs will be compatible with accounting requirements) and the results should be reviewed before incorporation into accounts. The review should assess fitness for purpose (does the data measure what the account requires?), methodological rigour (is the collection and processing method sound?), and reproducibility (could another team replicate the results?).

3.8 Time-Series Data Investment Guidance

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Sustained monitoring and data collection are essential for compiling the time-series accounts that reveal trends in ocean health, economic activity, and social outcomes. This section provides guidance on identifying critical data gaps, evaluating the cost-benefit of sustained monitoring investments, and prioritising data collection to maximise the analytical value of ocean accounts.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

A systematic gap analysis should be conducted as part of the initial compilation of ocean accounts, and updated periodically (at least every three years) as data systems evolve. The gap analysis should assess data availability against the full indicator set specified in the combined presentation dashboard (TG-3.8 Combined Presentations, Section 3.7) and the thematic account requirements of each relevant Circular.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

For each indicator, the gap analysis should record: the current data source (if any), the quality tier (Section 3.7), the spatial and temporal coverage, the update frequency, the time lag between reference period and data availability, and the estimated cost of producing the indicator. Gaps should be classified into three categories:

Complete gaps: No data source exists for the indicator. Complete gaps are the most serious, as they prevent compilation of entire account components. Common complete gaps in ocean accounting include ecosystem condition indices for deep-sea ecosystems, monetary valuation of regulating services, and governance effectiveness indicators.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Partial gaps: Data exist but with insufficient spatial coverage (e.g., monitoring stations cover only a fraction of the coastline), temporal coverage (e.g., surveys conducted once rather than annually), or thematic detail (e.g., employment data available for the ocean economy as a whole but not disaggregated by industry). Partial gaps can often be addressed through statistical estimation or modelling, but sustained monitoring investment is needed for reliable time-series compilation.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Quality gaps: Data exist with adequate coverage but at an insufficient quality tier (e.g., Tier 3 experimental estimates where Tier 1 official statistics are needed for policy credibility). Quality gaps require investment in data collection methodology, quality assurance processes, or institutional capacity rather than new monitoring infrastructure.

Table 3.8.1: Gap analysis template

Cost-benefit of sustained monitoring

Investment in sustained ocean monitoring should be evaluated against the analytical value it generates for ocean accounts and the policy decisions it enables. The cost-benefit assessment should consider both the direct costs of data collection (equipment, personnel, survey operations, data processing) and the indirect benefits (improved policy decisions, avoided environmental damage, international reporting compliance).

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Three principles should guide the cost-benefit assessment. The first is marginal value: the value of an additional year of data increases non-linearly with the length of the existing time series. The first five years of a monitoring programme establish baseline conditions, years five to ten reveal short-term trends, and only after ten or more years can long-term trends be distinguished from natural variability. Discontinuing a monitoring programme after a few years therefore sacrifices most of the accumulated investment value. The second is the integration multiplier: data that serve multiple accounts and indicators have higher value per unit cost than data serving a single purpose. Ecosystem extent data, for example, feeds into extent accounts, condition accounts (as a pressure indicator), ecosystem service accounts (as a scaling factor), and governance accounts (as a baseline for protected area assessment).

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The third is substitutability: some data can only be collected through direct observation (e.g., deep-sea biodiversity surveys), whilst others can be estimated from proxies or models (e.g., wave energy potential from reanalysis products). Investment priority should favour non-substitutable observations.

Table 3.8.2: Monitoring investment priority matrix

Based on the gap analysis and cost-benefit assessment, ocean accounting programmes should develop a prioritised data investment plan. The investment plan should be aligned with the national statistics development strategy and the broader ocean governance priorities. Priority investments for most countries implementing ocean accounts will typically include:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Establishing annual ecosystem extent monitoring using satellite remote sensing, which provides the foundational spatial data for extent accounts, condition assessments, and ecosystem service estimation. The relatively low marginal cost of processing freely available satellite imagery (Sentinel-2, Landsat) makes this a high-value investment. Guidance on remote sensing methods is provided in TG-4.1 Remote Sensing and Geospatial Data.

Strengthening coastal water quality monitoring networks to provide consistent, spatially representative measurements of nutrients, sediments, and pollutants. Water quality data serve the residual flow accounts (TG-3.4), ecosystem condition accounts, and the water-marine quality integration protocol described in TG-3.8 Combined Presentations, Section 3.8.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Developing ocean economy satellite accounts within the national accounts framework, enabling consistent measurement of ocean economy GVA, employment, and trade. This requires collaboration between the national statistical office and sectoral ministries to agree on the scope of ocean-related industries and compile thematic accounts following TG-3.3 Economic Activity Relevant to the Ocean.

Investing in sub-national data disaggregation to support provincial and municipal ocean accounting, as described in TG-3.8 Combined Presentations, Section 3.9. Many national datasets can be disaggregated to sub-national level at relatively low additional cost if the disaggregation requirement is built into data collection design from the outset.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

The data investment priorities identified in this section should be integrated into the broader capacity development strategy described in TG-4.7 National Data Coordination Architectures. Sustained monitoring requires institutional capacity as well as financial investment: trained personnel, maintained equipment, quality assurance systems, and data management infrastructure. The capacity development Circular provides guidance on building and maintaining these institutional foundations, including workforce planning, training programmes, and partnerships with research institutions and international organisations. Data investment plans should be reviewed and updated alongside the capacity development strategy to ensure that monitoring ambitions are matched by implementation capacity.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Data harmonisation and interoperability underpin the integration of diverse data sources into coherent accounting frameworks. The main elements are:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  • SDMX provides the statistical data exchange standard, with DSDs defining data structures, transmission formats enabling machine-readable exchange, and registry services supporting data discovery
  • Geospatial standards from OGC and IHO S-100, supported by ISO 19115 metadata standards, enable integration of marine spatial data, with the GSGF providing the overarching framework for statistical-geospatial integration
  • FAIR principles guide data management to maximise findability, accessibility, interoperability, and reusability
  • Classification concordances enable translation between ISIC/CPC for economic data, between national and international ecosystem classifications, and across classification versions over time, with official UNSD correspondence tables available for the ISIC Rev.5 and CPC Ver.3.0 transitions
  • Data harmonisation workflow provides systematic procedures for classifying, mapping, validating, and integrating heterogeneous source data into ocean accounts
Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Implementation of these standards requires institutional investment in technical infrastructure, staff capacity building, and sustained collaboration across organisational boundaries. The GSGF notes that “both the statistical and geospatial communities operate their own general data models, metadata capabilities, architectures, and data infrastructures” and that bridging these requires “greater incorporation of geospatial processes, standards, and best practices in the statistical business processes and data management systems”.

For ocean accounting practitioners, a pragmatic approach involves:

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

  1. Adopting SDMX-CSV as an accessible intermediate format whilst building toward full SDMX-ML/JSON implementation
  2. Ensuring geospatial data conforms to OGC standards and carries ISO 19115-compliant metadata to enable integration with national spatial data infrastructures
  3. Documenting all classification concordances used, including rationale and limitations, and using official UNSD correspondence tables for transitions between ISIC and CPC versions
  4. Implementing FAIR principles progressively, prioritising persistent identifiers and standardised metadata
  5. Establishing data harmonisation workflows with systematic quality checks at each phase
Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

All ocean accounts benefit from harmonised data infrastructure. Asset accounts (TG-3.1 Asset Accounts) integrate physical and monetary data from diverse sources, requiring consistent classifications and units. Ocean economy investment accounts (TG-2.6 Ocean Economy Investment) depend on concordances between economic activity and product classifications. Combined presentations (TG-3.8 Combined Presentations) integrate environmental, economic, and social data, relying on interoperable formats and metadata standards. Data harmonisation and interoperability are therefore foundational to the ocean accounting framework.

Data Harmonisation and Interoperability / GOAP Technical Guidance

continued

Guidance on specific data integration challenges for individual account types is provided in the relevant thematic Circulars: TG-4.1 Remote Sensing and Geospatial Data, TG-4.2 Survey Methods for Ocean Economic Activity, TG-4.3 Administrative Data Sources, TG-4.4 Citizen Science, and TG-4.5 Research Data.

For minimum institutional capacity, data infrastructure, and human skills requirements for implementing these data methods, see TG-0.8 Implementation Readiness Assessment.

Authors: [To be confirmed]

Reviewers: [To be confirmed]

Data Harmonisation and Interoperability / GOAP Technical Guidance

Cite this report

Data Harmonisation and Interoperability

Data Harmonisation and Interoperability (2026) (GOAP Technical Guidance on Ocean Accounting, TG-4.6, v0.7.1). GOAP Secretariat. https://guidance.oceanaccounts.org/circulars/section-4/4-6-data-harmonisation/

guidance.oceanaccounts.org/circulars/section-4/4-6-data-harmonisation

© 2026 Global Ocean Accounts Partnership Secretariat · CC BY-NC 4.0 · The report, its PDF and this deck are built from the same source.

GOAP Technical GuidanceVersion 0.7.1 · 1 September 2026