Start a free trial
Menu

AGeoP-08

AGeoP-08 NATO geospatial metadata profile

National defence geospatial services and organisations that produce or exchange geospatial information for NATO operations, exercises or national use

AGeoP-08 sets the NATO Geospatial Metadata Profile, requiring geospatial data produced or exchanged for NATO to carry metadata built on the DGIWG Metadata Foundation and four supporting NATO specifications, under the agreement recorded in STANAG 2586.

Edition
B
Published
2019-02

What it is

AGeoP-08 is the NATO Allied Geospatial Publication that sets out which metadata a geospatial dataset, map, chart or image plan has to carry when it is produced or exchanged for NATO use. It is Edition B, Version 1, promulgated in February 2019, and it was "approved by the nations in the Military Committee Joint Standardization Board" before promulgation. It does not define a metadata structure from first principles: clause 2.2 requires compliance with the DGIWG Metadata Foundation (DMF), the wider defence community's metadata profile built on the ISO 19100 series, and clauses 2.3 to 2.6 then add four further Standards Related Documents (SRDs) covering the DMF's use in a NATO environment, that environment's codelists, its Shapefile encoding, and the naming of hardcopy land maps, aeronautical charts and image plans. Nations record their agreement to use the publication "in STANAG 2586."

Who actually implements it

The document does not name a commercial audience. The entities it shows actually implementing it are national defence geospatial organisations: Germany's national reservation names "The Bundeswehr Geoinformation Service with the Bundeswehr Geoinformation Center in Euskirchen" as its single point of contact for providing and exchanging geospatial information for NATO activities, and restricts its own implementation of STANAG 2586 to that service's area of responsibility. Reservations from France, Croatia and Slovenia show the same pattern: each nation decides its own scope and timing. France ties full implementation to "increment 2 of the GEODE 4D program," due after 2022, applying only STANAG 2586 Edition 2 within a narrower national scope before that. A commercial supplier producing geospatial data for a NATO or national programme meets this profile because a contract or national programme requires it, not because AGeoP-08 addresses suppliers directly.

Five requirements, all the same shape

Chapter 2 is short, entirely normative, and made up of five requirements, each a "SHALL be compliant to" pointing at another document rather than a self-contained specification:

  • Clause 2.2 requires compliance with the DGIWG Metadata Foundation itself, described as "a

general Defence metadata profile for datasets, series, services, tiles, documents, products and non-geographic datasets."

  • Clause 2.3 requires compliance with SRD 08.1, which covers using the DMF "in a NATO

Environment (NATO lead operations, exercises or national use)."

  • Clause 2.4 requires compliance with SRD 08.2, the codelists used within that NATO environment.
  • Clause 2.5 requires compliance with SRD 08.3, the Shapefile implementation of the DMF.
  • Clause 2.6 requires compliance with SRD 08.4, the naming rules for hardcopy land maps,

aeronautical charts and image plans - content that used to be its own publication, AGeoP-9, before this edition absorbed it.

What is easy to miss: AGeoP-08 does not itself list a single metadata element. It is a profile of a profile, naming which DMF baseline and which four SRDs a NATO geospatial metadata record has to follow; the field-by-field requirements live in those referenced documents, not in this cover publication. An auditor checking conformance would need to check a dataset's metadata against those SRDs directly, not against AGeoP-08's own text.

What edition B replaced

Edition B, Version 1 is effective on receipt and supersedes AGeoP-08 Edition A, Version 2. It also absorbs a document that was previously separate: AGeoP-9, Edition A, Version 1, whose hardcopy-map naming rules were "formerly referenced as AGeoP-9 Edition A, Version 1 (STANAG 7136)" and now sit inside clause 2.6. The superseded editions are, per the promulgation letter, to be destroyed according to local document-destruction procedure rather than kept in circulation.

Prerequisites and related documents

Clause 1.2 names the ISO documents the DGIWG Metadata Foundation itself is built on: ISO 19115:2003, ISO 19115/Cor.1:2006, ISO 19115-1:2014, ISO 19115-2:2009, ISO/TS 19115-3:2016, ISO/TS 19139:2007, ISO 8601:2004, ISO 639-2:1998 and ISO 19106:2004, plus IETF RFC 3629, RFC 3986 and RFC 4122. Where a geospatial record needs confidentiality labelling, STANAG 4774 / ADatP-4774 supplies that syntax, and clause 1.2 also names AJP-3.17 Geospatial Support alongside NATO Geospatial Policy MC 296/3 as related reading.

How compliance is checked

AGeoP-08 does not name who checks compliance or how. It describes no certification scheme, no government-surveillance regime and no self-declaration mechanism; each of its five requirements is only ever the same "SHALL be compliant to" clause pointing at another document. What it sets is a structural condition on a dataset's or system's metadata, not an assessment process, and it says nothing about audits, inspections or formal sign-off.

Getting the document

AGeoP-08 is unclassified and free of charge. NATO's Standardization Document Database lists the current edition; we do not host a copy or sell it.

How we help

Structuring geospatial metadata to the DGIWG Metadata Foundation and the four SRDs AGeoP-08 names, and encoding it correctly in Shapefile, is production and engineering work carried out in the geospatial toolchain itself, not something a compliance platform performs. What ComplyTrain supports is the documentation and evidence trail around that work: a controlled procedure describing how staff structure and check metadata against the DMF baseline and the relevant SRDs, training records for people producing or reviewing geospatial products, and a record of which SRD version and which national reservation a given contract or programme has to meet.

ComplyTrain does not tag a geospatial dataset, validate a Shapefile against SRD 08.3, or produce metadata itself. Which tier of this profile, and which national reservation, applies to a given contract is set by the contract and the customer's quality clause, not by us. See what else sits alongside AGeoP-08, including STANAG 2586, in the standards explorer, and talk to us about the documentation trail behind adopting it.

Standards it references

Questions

Is AGeoP-08 mandatory for a supplier?

AGeoP-08 does not bind a supplier directly. Nations record their agreement to use it in STANAG 2586, and a supplier meets it only when a contract or a national programme requires geospatial deliverables built to this profile - not simply because the document has been published.

What does AGeoP-08 actually specify?

Almost nothing on its own page. Its normative chapter has five requirements, each pointing to another document to comply with: the DGIWG Metadata Foundation itself, and four Standards Related Documents covering its use in a NATO environment, that environment's codelists, its Shapefile encoding, and the naming of hardcopy maps and charts.

Is there a certification for AGeoP-08 conformance?

No certification, government-surveillance or self-declaration scheme is described. The document sets a structural requirement, that a dataset's metadata complies with the named SRDs, and says nothing about who checks that or how.

How does AGeoP-08 relate to STANAG 2586?

STANAG 2586 is the agreement NATO nations ratify; the promulgation letter states that "the agreement of nations to use this publication is recorded in STANAG 2586." AGeoP-08 is the technical publication that agreement covers.

What happened to AGeoP-9?

Edition B of AGeoP-08 absorbed it. AGeoP-9 Edition A, Version 1 (formerly covered by STANAG 7136) was a separate publication on naming hardcopy land maps, aeronautical charts and image plans; that content now sits in AGeoP-08's clause 2.6, and the earlier AGeoP-9 edition was superseded.