OCHA COD-AB unreviewed
OCHA Common Operational Datasets for administrative boundaries.
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 vocabularies covered: 0 value mapping. 1 property mapping.
Properties
| Vocabulary | System name | Coverage | Gaps |
|---|---|---|---|
| administrative_level | COD-AB AdminN | 5/5 mapped |
Concept matches
Entities in OCHA COD-AB that align with PublicSchema concepts.
| PublicSchema concept | System entity | Match | Notes |
|---|---|---|---|
| Location | COD-AB feature (one row per admin unit) | Close | 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. |
Documented gaps
PublicSchema items that OCHA COD-AB does not model, with the documented reason.
| PublicSchema item | Reason |
|---|---|
| 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. |
Help improve this page
Highlight any text on this page to leave an annotation. Join our review group to get started.
If you have a GitHub account, click the feedback icon next to any section heading to report a specific issue.