Page Comparison

The Process

...

When available, the most logical candidate dataset for a COD-PS is the latest set of subnational population projections compiled by the National Statistics Office or related competent authority. Such projections estimate the population at a baseline year (usually at the time of the last census) and project the population forward to the current year based on information about recent population dynamics (namely fertility, mortality, and migration patterns).

Government Data is available but outdate

When recent subnational population projections are not readily available, then to construct a COD-PS it is necessary to acquire the most recent census data and indicators on population dynamics to construct sex- and age-disaggregated population projections at either ADM-1 or ADM-2. In cases where recent population and demographic data can be utilized, the Bayesian population projection framework can be used - this will ensure consistency in the methodological approach of the UN’s official national population projections (known as the World Population Prospects) and COD-PS datasets constructed at lower administrative units (i.e. ADM-1 and below).

Government Data is not available unavailable (or too outdated)

When neither up-to-date subnational population projections (that are sex- and age-disaggregated) nor source data needed to compile such projections are available, then either a formal data request to the National Statistics Office is needed, or the use of model-based estimates needs to be considered (by either using the available WorldPop gridded population estimates or undertaking a hybrid census modeling exercise).

...

.

Info

title	END-USER GUIDANCE NOTE

To support humanitarian decision making and action, UNFPA document's individual country COD-PS datasets through an end-user guidance note. This document details the input data used to construct the COD-PS, documents any adjustments made to the underlying data during the estimation process, describes the demographic estimation and projection methods used and summarizes the COD-PS dataset by noting its strengths and limitations. The end-user guidance note also explicitly describes the reference population and reference year for which the COD-PS applies. It is designed to assist humanitarian decision-makers in understanding the strengths of limitations of the data and methods used to compile a COD-PS, as they use COD-PS data for needs assessment, humanitarian plan design, and assessments of humanitarian interventions.

Standards <NOT SURE ABOUT THIS SECTION>

...

The population statistics COD standards and guidance are currently in development at the global level with UNFPA. The minimum standards identified in the current evaluation checklist enable data interoperability and harmonization.

COD-PS Required Characteristics (minimum requirements in red)

Metadata

Source organization must be clearly identified, and acceptable for humanitarian use
Population data are endorsed by IM Network
The dataset must be able to be shared (at least once at the onset stage of an emergency)
P-codes from COD-PS match COD-AB (tables can link 1:1)

Tabular Attributes

Field names are clear and understandable
Field names used consistently across all Admin layers
Population breakdown exists for sex and age for each administrative unit (with sex disaggregation for every age cohort)
All values must be integers.
All values must be present
Sum of data matches the value of higher admin level
Data is checked for inconsistencies
Data is checked for outliers
P-codes are the unique identifiers used in the country (ideally government sourced)
P-codes are present and unique for each administrative unit
P-code attribution is consistent across all layers
P-codes for higher-level administrative units are included in lower levels
P-codes and feature names (and therefore feature counts) should conform to established and accepted administrative boundary datasets (COD-AB) - however, it may be that the COD-PS is the more reliable authority.

Identification of Datasets

...

.

...

Consider the following criteria when identifying sources for COD-PS:

COD-PS should be operationally relevant and useful.
What are partners currently using and why?
Is the data source authoritative? If not, what is the rationale for identifying it as a COD?
Can it be linked (via P-Code or name) to the COD Administrative Boundary (COD-AB)?
To what administrative level is the data provided? What is the lowest administrative level is operationally required?
Is it age and sex-disaggregated (can an estimation be made)?
Are various sources required to create a complete COD-PS?
Acquire as much metadata about the datasets and keep a data trail
If various sources are available or being used by partners compile these in a table for easy analysis and discussion with partners. (Example of the table)