Versions Compared

Old Version 201

changes.mady.by.user FIS

Saved on

compared with

New Version Current

changes.mady.by.user FIS

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Special note about COD use versus COD development

Since about 2020 COD administrative boundary development has evolved to be less of a burden on a wide group of stakeholders and more focused on OCHA Regional and Country Offices, while more and more strategically required CODs have become available and routinely updated. At the same time population statistics COD development became the responsivity of UNFPA. The emphasis of the IM Toolbox has therefore moved away from COD development roles and responsibilities and toward humanitarian COD use. The exception is the section describing development of Country-specific CODs which can be identified and launched by field teams at short notice.

CODs

  • are authoritative reference datasets needed to support operations and decision-making for all actors in a humanitarian response.

  • pertain to a recognized country or territory1.

  • are standardized datasets that are commonly used and referenced by all operations.

  • are of four types of COD2:

  • reflect the local hierarchical administrative structure,2 are annotated with place names and P-codes, and are generally accompanied by a tabular gazetteer.

  • are best available datasets that ensure consistency and simplify the management of key data.

  • are accepted in country3 or in their region by the relevant Information Management Working Group.

  • are catalogued at the COD Portal [LINK SUBJECT TO CHANGE SOON].

  • are disseminated at the Humanitarian Data Exchange (HDX). ; COD-AB and COD-EM datasets are also available as live GIS geoservices.

  • enable consistency and harmonization among actors working on humanitarian preparedness and response by providing:

    • a common operational picture of the crisis

    • a geographic framework (P-codes) for data collection, analysis, and visualization.

  • are available in two quality classifications:

    • ‘enhanced CODs’ with full quality control, compatibility, and reliability

    • ‘standard CODs’ not yet fully quality controlled.

  • facilitate informed decision making both pre- and post-crisis.

  • reduce duplication of work on baseline data by partnering organizations.

  • strengthen valuable humanitarian networks and relationships.

  • drive API look-up information

1 CODs are generally prepared for sovereign states recognized by the UN Secretariat, but in some cases reflect sub-national territories. For example, there are CODs for Puerto RicoSint Maarten, which is a part of the Kingdom of USAthe Netherlands, but not for Taiwan, which is not a recognized member state.

2 Previously a ‘Humanitarian Profile’ COD-HP type existed, which presented tabular People-in-Need information derived from Humanitarian Needs Overviews. This information is now provided in country-specific ‘Humanitarian Needs’ (non-COD) datasets disseminated in HDX by OCHA Humanitarian Programme Cycle Tools (HPC Tools). For further information see HPC Tools.

1 Except some COD-CS datasets

Terminology

Term

Explanation

Administrative level

CODs (and administrative structures) are hierarchical with administrative levels numbered from zero (the entire country or territory) down as far as appropriate. Because the names of administrative levels vary so much between countries and territories, and because a particular country and administrative level may contain features of more than one administrative type, the generic term ‘administrative level’ is preferred in COD management. Administrative levels may be abbreviated ADM1 etc.

Administrative structure

The heart of any COD is its adherence to and echoing of the accepted administrative structure of the country or territory. The administrative structure of a country or territory consists of the administrative features comprising each administrative level.

Country-Specific COD

Feature

An individual geographic unit within the set of units comprising an administrative level in a COD. For instance “California” is an administrative level 1 feature in USA.

P-code

There are four general types of COD:

There are two quality levels of COD:

  • Enhanced CODs

  • Standard CODs

Criterion

COD-AB and COD-EM enhanced (green dot in COD Portal)

COD-AB and COD-EM standard (grey dot in COD Portal)

COD-PS enhanced

COD-PS standard

Quality control

ITOS

OCHA FIS

UNFPA

OCHA FIS

Schema

Standardized

Not guaranteed to be standardized

Standardized

Not guaranteed to be standardized

Feature names

Complete and unique within administrative level. Latin alphabet and any other local alphabet

Complete and unique within administrative level. Latin alphabet and any other local alphabet

P-codes

Alphanumeric, complete, unique, and incorporated into ITOS database

Alphanumeric, complete, unique, and incorporated into ITOS database

Alphanumeric, complete, unique, and incorporated into ITOS database

Alphanumeric, complete, unique, and incorporated into ITOS database

Feature name and P-code hierarchical nesting

Guaranteed

Not guaranteed

Guaranteed

Not guaranteed

Boundary topology

Guaranteed

Not guaranteed

(not applicable)

(not applicable)

Live geoservices

Provided

Provided

(not applicable)

(not applicable)

Geographic hierarchical nesting

Guaranteed except for specially justified cases

Not guaranteed

(not applicable)

(not applicable)

Features cover entire country

Guaranteed except for specially justified cases

P-codes

CODs for a particular country should be linked by P-codes to each other and to other humanitarian data.

Suggested styling. It is recommended that feature names be contained in quotes and P-codes be contained in square brackets. For instance:

“Lavengatonga” [TO1407]

Enhanced CODs

Enhanced CODs have undergone improved development and quality control. Enhanced COD-AB and COD-EM datasets have been quality controlled and standardized by ITOS. Enhanced COD-PS datasets have been prepared (and therefore quality controlled and standardized) by UNFPA. Enhanced CODs are identified in HDX datasets views and on their HDX dataset pages with a “COD+” icon.

image-20241001-203238.pngImage Removed

Most new or recently updated COD-AB, COD-EM, and COD-PS datasets are enhanced.

Standard CODs

Standard CODs are those that are not Enhanced. These include older COD-AB datasets, older COD-PS datasets (not contributed by UNFPA), and all COD-CS datasets.

Standard CODs are identified in HDX dataset views and on their HDX dataset pages with a “COD” icon.

image-20241001-203723.pngImage Removed

Finding CODs

CODs are available for download from the Humanitarian Data Exchange (HDX). Approximately six hundred HDX datasets are CODs. All HDX dataset views contain a filter near the top-left for all CODs and a sub-filter for “Standard CODs” and “Enhanced CODs”. (These distinctions are described below.)

image-20241001-195140.pngImage Removed

All COD datasets visible in any HDX dataset view have a “COD” icon (for Standard CODs) or a “COD+” icon for Enhanced CODs.

image-20241001-195850.pngImage Removed

HDX provides a ‘Common Operational Database’ page (found in the “PRODUCTS” pull-down near the top of any page) which is merely a dataset view of CODs held on HDX.

HDX datasets contain ‘Data and Resources’ and ‘Metadata’. The Data and Resources are the actual files (shapefiles, spreadsheets, etc.) or external links (ITOS live geoservices) comprising a COD. Resources can be individually downloaded.

Image Removed

COD Portal

COD branding and visibility

COD development, reviews and management

COD development

Stakeholder validation

Annual COD-AB reviews

COD governance, responibilities, and development document

Tutorial

Advocacy Resources

View file
nameCOD_promo_final_2016.pdf

COD Flyer FR (2016) 

View file
nameCOD poster_March2018.pdf

COD Flyer EN (2016) 

View file
nameCOD_promo_2pager_2016_FR.pdf

COD Poster (2018)

  • COD song (music video - mentions COD endorsement which is now less formal)

  • How a dataset becomes a COD (music video - emphasises COD endorsement which is now less formal)

  • 50 things OCHA IMOs are responsible (iceberg) (infographic)

  • 50 things OCHA and Core CODs (chart) (infographic)

  • Introduction to COD Webinar

    • https://data.humdata.org/dashboards/cod

    [????]

    For further information see the Common Operational Datasets subsections and additional articles at left.