Versions Compared

Key

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

...

COD-PS Required Characteristics (minimum requirements in red)

Metadata

  • Source organization must be clearly identified, and acceptable for humanitarian use.

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

  • Reference year (of the projections/estimates) must be clearly stated.

Tabular Attributes

  • Field names are clear and understandable.

  • Field names are 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.

  • The sum of data matches the value of a 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 is 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.

...