Administrative Boundary CODs (COD-AB)

Owned by FIS (Unlicensed)
Aug 28, 2017
2 min read

COD-AB Introduction

Administrative Boundary CODs are baseline geographical datasets that are used by humanitarian agencies during preparedness and response activities.  They are preferably sourced from official government boundaries but when these are unavailable the IM network must develop and agree to a process to develop an alternate dataset.

COD-AB Purpose

Administrative boundaries provide humanitarians with:

  • a spatial dataset that can: 
    • inform a common operational picture 
    • provide a base layer for maps
    • provide a dataset for spatial analysis (e.g., when linked to the COD-PS allows estimates of affected people in a storm path or near an earthquake epicenter, or assessment locations)
  • a dataset that can provide a framework in all phases of the Humanitarian Program Cycle (HPC)
    • data collection (e.g., 3W monitoring data)
    • analysis (e.g., secondary data analysis)
    • for assessment locations in collection tool (e.g., Kobo Collect)
    • for humanitarian systems (e.g., Humanitarian Response, Humanitarian ID, Response, Planning and Monitoring)

COD-AB Required Attributes

  • All administrative boundary CODs must include P-codes and names.
  • The administrative hierarchy (P-codes and names) must be included in each level provided.
  • More information about standards can be found in the quality checklists (Quick Check, ITOS Gold Standard Checklist)


COD-AB and Partners

  • Government:  main / default source of administrative boundaries
  • OCHA:  generally responsible for Core COD development for countries that fall into its area of responsibility
  • ITOS:  to assist in processing (cleaning, standardizing, multiple format creation including web services)



COD-AB Resources

Q&A

Q: In OCHA regional office, the main problem we have with the dataset is the countries’ boundaries are never match, even if the country data are correct, clean and validated. Do I correct them to create a regional dataset or not?        

A: Generally we shouldn't change the international boundaries of country datasets provided by government, as they can get quite upset! But one solution is to create a separate regional dataset which you can edge-match and use just for regional mapping. The important thing is to use the same attribute data (names, p-codes). Be sure to explain the purpose of the dataset and methodology used to create it and state that international boundaries are not 100% accurate


Q: Are OCHA regional office's responsible for Core CODs for countries that fall in their area?        

A: OCHA regional offices  are not responsible for countries that have an OCHA country office and are responsible for those countries that do not have an office. The OCHA Regional Office should check with partners that are already working in countries where there is no OCHA office to check what core CODs they using; the office should then work with these partners to go through the COD cycle.