Done | Requirement |
---|---|
Title includes name of dataset and number of administrative levels represented | |
Endorsement date is included in the description | |
Source name is spelled out (and not just an acronym) | |
License is from HDX public list, 'other' and 'humanitarian use only'. (COD FOD Terms of Use are not considered valid anymore.) | |
Date of dataset makes sense. (it is not the date the dataset was processed, unless there were changes made to P-codes / administrative names.) | |
Expected frequency date should be 'yearly' or more frequent. (With the COD cycle COD-AB and COD-PS need to be reviewed yearly - even if there is no change to the data there should be a change to the endorsement date.) | |
Methodology makes sense and includes a note about ITOS processing the dataset (if ITOS used). | |
Caveats include any notes about the dataset (if required). ITOS provides caveats in it live feeds for each admin layer - these should be included in HDX metadata (Honduras example). include a note and link to historic COD (if applicable). | |
Tags include: COD, Administrative Boundaries or Population Statistics or dataset theme (e.g., roads, ports, ATMs, Telecommunication towers, etc.). | |
Resources COD-AB files include:
COD-PS files include:
|
Manage space
Manage content
Integrations