Versions Compared

Old Version 26

changes.mady.by.user FIS (Unlicensed)

Saved on

compared with

New Version 27

changes.mady.by.user FIS (Unlicensed)

Saved on

Key

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

Standards

...

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
  • 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.

...

The primary data source of data should always be the government or in-country institution supporting a country’s mapping activities. Ideally, a partnership with UNFPA should be used rather than direct contact with the government to acquire a dataset.  Alternatives to government sources should be examined if there is Core CODs are not available or cannot be shared with the humanitarian community. The COD-PS should be identified and processed at the same time as the COD-AB as they need to have a one to one relationship, this may impact the dataset chosen. 

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 table)


Government Sources are the most authoritative sources.

...

In some situations, government sources may not be available  (e.g., there may be no data for a particular area of the country that is in conflict; the government is not able to share for various reasons, or a COD-AB is required quickly) and alternative sources need to be identified.  The first question to ask if government data is not available: what are operational (including development) partners using? Other considerations when contemplating alternative sources are: why is this source authoritative; will using a non-government source impact the humanitarian community's relationship with the government; is the sharing/distribution of the dataset the biggest challenge and can this be overcome with a "humanitarian only, for emergencies only" agreement required; is the government likely to release data if an emergency does occur (thus requiring the community to quickly analyze, clean, and share a new dataset); what are partners using and why; and will exposing an alternate source push the government to share data?  Some ideas of alternative datasets are below both categories may be acceptable but rational for choosing this source must be included in the metadata. 

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

  • 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 aggregated (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 table)

    Resources

    ...