This page shows how OCHA COD-AB vocabulary codes map to PublicSchema canonical values. If you work with OCHA COD-AB and spot an error, please report it.

0 vocabulaires covered: 0 correspondance de valeurs. 1 property mapping.

Propriétés

Vocabulaire Nom dans le système Couverture Lacunes
administrative_level COD-AB AdminN 5/5 correspondances

Correspondances de concepts

Entités de OCHA COD-AB alignées sur des concepts PublicSchema.

Concept PublicSchema Entité du système Correspondance Remarques
Location COD-AB feature (one row per admin unit) Proche A COD-AB feature is an administrative boundary at a specific level. PublicSchema Location is broader (also covers non-administrative named places and bounded regions like flood zones and program coverage areas), so the relationship is: every COD-AB feature is a Location, but not every Location is a COD-AB feature. Each COD-AB layer holds one admin level; multi-level country coverage is split across files (adm0.shp, adm1.shp, ...). Hierarchy between levels is encoded redundantly in the lower-level rows (an adm2 row carries adm0_pcode, adm1_pcode, and adm2_pcode), and Location's `parent_location` reference reconstructs that hierarchy on the v2 side.

Lacunes documentées

Éléments de PublicSchema que OCHA COD-AB ne modélise pas, avec la raison documentée.

Élément PublicSchema Raison
latitude COD-AB features are polygons, not points; no centroid is published. Derivable from geometry if needed.
longitude Same as latitude.
level_name COD-AB does not carry the localized name of the level itself (e.g., 'Region', 'District'); only the unit's own name.