ICDE Agreement 003: an implementation path without misleading countdowns

A practical way to address Agreement 003 of 2025 is to turn it into a geospatial data governance programme: know which datasets exist, who is accountable for them, how they are described, which quality controls apply, how they are published and how they are reviewed. It does not begin by purchasing a catalogue or end by enabling WMS. It requires owners, evidence and recurring review of sources and decisions.

The decision this guide supports

The reference must be Agreement 003 as published by ICDE and its official materials. GeoSAT’s editorial register records ambiguity among dates communicated by the authority, so this guide does not display a countdown. Each institution must confirm its scope and schedule against the current source and document the verification date.

Begin with a register of datasets and services, not a technology purchase. For every asset, document custodian, purpose, coverage, update cycle, access classification, licence and operational dependency. Distinguish source data, derived products, metadata and published endpoints because they may have different owners and lifecycles. Then prioritise gaps by the decision they block, not by the number of blank fields. The roadmap should state what will be normalised, what may be published, what remains restricted and which cross-team agreement is missing. This turns interoperability into a governable programme rather than an open-ended migration.

Recommended workflow

1. Agree. Build an inventory of datasets, services, custodians, licences, restrictions and users.
2. Structure. Prioritise assets by public decision, reuse, risk and the cost of stale information.
3. Check. Define minimum metadata, quality checks and evidence for each asset class.
4. Document. Publish through documented interfaces and test access, response, filters and formats.
5. Operate. Assign editorial and technical review with version, verification date and next review.

Minimum controls before publishing or delivery

A useful review combines automated checks with expert judgement. At minimum, record:

• an institutional owner for each dataset.
• visible licence and restrictions.
• metadata tied to the published version.
• repeatable service and download tests.

Limits that must remain visible

Interoperability does not mean opening every dataset or copying files between portals. Some assets require legitimate restrictions, generalisation or controlled access. A responding endpoint does not prove semantic quality either. Assessment needs to separate availability, technical conformance, content, licence and governance. No local GeoSAT auditor certifies ISO, OGC or ICDE compliance.

To apply this method to a concrete project, review the GeoSAT sector service and compare its dependencies with the related service. These links serve different intents: this guide explains the process, while the service pages define scope, evidence and the appropriate commercial next step.