The Process
...
There is no “one size fits all” approach when applying the Best Available Data Standard to humanitarian preparedness and operational response countries. Regional and country context matters, as well as, the population data landscape and humanitarian context which shape's shapes the approach to constructing a COD-PS. Specifically, the following are key factors in determining how to apply the best available data standard to a given population data landscape:
...
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.
|
...