...
COD-PS Required Characteristics
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 on-set 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 value of higher admin level
- Data is checked for inconsistencies
- Data is checked for outliers
- P-codes are the unique identifiers used in 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.
|
Process
...
The COD-PS follows the COD cycle, like all other CODs. The first step is to identify (possibly additional) partners in your IM Network who are 'experts' in population statistics/demographic data. The second step is to identify population datasets for a country that are available at different administrative levels and ideally age and sex disaggregated. If datasets require processing to improve them (e.g. projections, etc) the methodology should be agree to by the IM network and included in the metadata. This should be done during preparedness activities as it is expected that within 48 hours of an event triggering a humanitarian emergency, the COD-PS should be widely shared through national, regional and global channels to support data compatibility pertaining to the emergency.
...