Overview
...
OCHA routinely evaluates the quality and availability of Common Operational Databases. The results of this exploratory analysis can be found on the COD Portal.
...
This Portal documents: 1) the quality of administrative boundary (COD-AB) layers and population statistics (COD-PS) tables, and 2) their availability on HDX and for COD-AB as an ITOS geoservices. The dashboard is generally refreshed after any COD-AB or COD-PS is added or updated. The dashboard has the following four tabs: CHANGE
...
- Green segment: number of countries with at least one 'fully usable' administrative level
- Orange segment: number of countries with no 'fully usable' administrative levels but at least one 'partly usable' administrative level
- Red segment: number of countries with no 'fully usable' or 'partly usable' administrative levels but at least one 'needs improvement' administrative level
- Grey segment: only 'not evaluated' administrative levels. These refer to countries where there is only a COD of the other status ('Operational' or 'Preparedness')
...
| Major heading | Sub-heading | Symbol | Indication |
|---|---|---|---|
| Region | text | OCHA region names (modified) | |
| Status | 'Operational' | OCHA maintains a country office | |
| 'Preparational' | OCHA maintains no country office but the country is of interest because of actual or potential humanitarian needs | ||
| Country | text | UN preferred name | |
| Administrative Boundary | ADM1 | • | Fully useable |
• | Partly usable | ||
• | Needs improvement | ||
• | Unavailable | ||
| ADM2 | as per ADM1 | ||
| ADM3 | as per ADM1 | ||
| ADM4 | as per ADM1 | ||
| HDX | ✔ | The administrative boundaries shown for the levels with non-gray dots are available on HDX | |
| red padlock | Publishing of the administrative boundaries for the levels shown with non-gray dots has been prohibited by the source | ||
| • | No administrative boundaries are available | ||
| LIVE | ✔ | Live service is available. Linkages are available on the COD-AB page on HDX. | |
| red padlock symbol | Live service has been prohibited by the data source | ||
| (blank) | No live service is available | ||
| Link | AB-PS | green link symbol | The COD-AB and COD-PS can be linked at least one administrative level |
| red link symbol | The COD-AB and COD-PS cannot be linked at any administrative level | ||
| (blank) | The COD-AB and COD-PS are not both available | ||
| Population Statistics | ADM1 | • | Fully useable |
• | Partly usable | ||
• | Needs improvement | ||
• | Unavailable | ||
| ADM2 | as per ADM1 | ||
| ADM3 | as per ADM1 | ||
| ADM4 | as per ADM1 | ||
| HDX | ✔ | The population statistics shown for the levels shown with non-gray dots are available on HDX | |
| red padlock symbol | Publishing of the population statistics for the levels shown with non-gray dots has been prohibited by the source | ||
• | No population statistics are available | ||
...
COD-AB evaluation criteria | ||||||
COD-AB Metadata criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly Usable | Needs Improvement |
|---|---|---|---|---|---|---|
HDX upload | Is the COD-AB published on HDX? | Dataset | HDX available CODs | At least nine criteria are satisfied | (not used) | Fewer than nine criteria are satisfied |
| Public availability | Is the data available publicly? | Dataset | Options are 'public', 'private', or 'request data' | |||
| Dataset Date | Is the date clearly indicated on HDX? | Dataset | 'Providing Metadata For Your Datasets On HDX' | |||
| Description | Is there a short but complete description of the dataset? | Dataset | ||||
| Source | Is the data source clearly indicated and defined on HDX? | Dataset | ||||
| Methodology or comments | Is any clarifying information provided? | Dataset | ||||
| COD tag | Is the dataset tagged as a 'COD' on HDX for easy discovery? | Dataset | ||||
| Endorsement | Is the dataset endorsed by the IMWG or Humanitarian Coordinator? | Dataset | ||||
| License | Is the correct license specified on HDX? | Dataset | TO BE DISCUSSED WITHIN FIS | |||
| Single dataset | Are all the COD-AB files (HDX resources) grouped into one HDX dataset? | Dataset | Best Practice | |||
| Unique levels | Is there only one file (HDX resource) per file format per administrative level? | Dataset | Exceptions may be made. For instance, the Bangladesh COD-AB features layers with and without inland waters. Equivalent files should not be found elsewhere on HDX. | |||
| CPG file | Is a .cpg file available for each ArcGIS shapefile? | Administrative layer | A .cpg file is an ArcGIS codepage that comes with the other files extensions and that can be used to define the code. CPG file is not mandatory but should be present when needed. | |||
| Metadata file | Is there a metadata file (in .txt format) or gazeteer tab providing further information on data | Dataset | ||||
| Zip file naming | Is the zip naming convention followed? | Administrative layer | Zip file naming convention helps to standardize referencing of files NOTE LINK HAS NOT BEEN MIGRATED FROM TSP | |||
Shapefile nameing | Is the shapefile naming convention followed? | Administrative layer | The SHP files should follow the naming convention (standards). | |||
COD-AB Attribute criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly Usable | Needs Improvement |
| Feature count | Are there the correct number of features? | Administrative layer | Consult reliable sources, particularly COD-PS datasets | Two criteria are satisfied | (not used) | Fewer than two criteria are satisfied |
| Complete feature names | Are there any missing feature names? | Administrative layer | ||||
| Clear field names | Is there any explanation/document about standardization of items? | Administrative layer | Column names must make sense and be clear to prevent any confusion. | |||
| Latin alphabet names | Are the feature names written in the Latin alphabet? | Administrative layer | If names are written in an alphabet which is not Latin, it must be translated into English in another column. (Link to ITOS schema) | |||
| Gazetteer (tabular) file | Are the COD-AB attribute tables for all administrative levels available as an Excel file on HDX? | Administrative layer | Best Practice | |||
| Parentage | Lower levels have higher attributes included | Administrative layer | Lower levels should include higher levels to see the AB unit it falls in. Best Practice | |||
| Unique feature names | Feature names are unique within higher administrative unit | Administrative layer | Duplicates attributes check tutorial | |||
COD-AB P-code criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly Usable | Needs Improvement |
| P-codes constructed | Do the P-codes incorporate values from higher levels? | Administrative level | P-codes guidelines | Both criteria are satisfied | (not used) | Neither criterion is satisfied |
| Unique P-codes | Are the P-codes unique? | Administrative level | Duplicates attributes check tutorial | |||
| COD-AB Parentage criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly Usable | Needs Improvement |
| P-code parentage | Is the P-code hierarchy the same between levels? | Administrative level | Parentage check tutorial | Both criteria are satisfied | (not used) | Neither criterion is satisfied |
| Name parentage | Is the unit names hierarchy the same between levels? | Administrative level | Parentage check tutorial | |||
| COD-AB Spatial criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Party Usable | Needs Improvement |
| Features are polygons | Are all administrative boundaries represented as closed polygons? | Administrative level | How to convert polylines to polygons tutorial | All criteria are satisfied. | Some but not all criteria are satisfied | No criteria are satisfied |
| Consistent coordinate systems | Is the coordinate system WGS1984 or at least consistent? | Dataset | ||||
| Geometric nesting | Is the geometric nesting clean? | Dataset | Nesting error tutorial | |||
| Correct topology | Are there topological gaps and overlaps? | Administrative level | Topology check tutorial | |||
| Country coverage | Are there unjustified gaps in the country coverage? | Administrative level | ||||
COD-PS evaluation criteria | ||||||
COD-PS Metadata criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly usable | Needs Improvement |
| HDX upload | Is the COD-PS published on HDX? | Dataset | HDX available CODs | At least nine criteria are satisfied | (not used) | No criteria are satisfied |
| Public availability | Is the data available publicly? | Dataset | Options are 'public', 'private', or 'request data' | |||
| Dataset date | Is the date clearly indicated on HDX? | Dataset | 'Providing Metadata For Your Datasets On HDX' | |||
| Description | Is there a short but complete description of the dataset? | Dataset | ||||
| Source | Is the data source clearly indicated and defined on HDX? | Dataset | ||||
| Methodology or comments | Is any clarifying information provided? | Dataset | ||||
| COD tag | Is the dataset tagged as a 'COD' on HDX for easy discovery? | Dataset | ||||
| Endorsement | Is the dataset endorsed by the IMWG or Humanitarian Coordinator? | Dataset | ||||
| License | Is the correct license specified on HDX? | Dataset | ||||
| Single dataset | Are all the COD-AB files (HDX resources) grouped into one HDX dataset? | Dataset | Best Practice | |||
| Unique levels | Is there only one file (HDX resource) per file format per administrative level? | Dataset | Equivalent files should not be found elsewhere on HDX. | |||
| Excel file | Is there an Excel file? | Dataset | ||||
| CSV files | Are there CSV files for each administrative level? | Dataset | ||||
| CSV files zipped | Are all the CSV files zipped together? | Dataset | ||||
| Metadata file | Is there a metadata file (in .txt format) or gazeteer tab providing further information on data | Dataset | ||||
| File encoded | Is the file encoded in UTF-8? | Dataset | ||||
| Zip file naming | Is the zip naming convention followed? | Dataset | ||||
| Table file naming | Is the CSV and Excel naming convention followed? | Dataset | ||||
COD-PS Attribute criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly Usable | Needs Improvement |
| Clear field names | Is there any explanation/document about standardization of items? | Administrative layer | Column names must make sense and be clear to prevent any confusion. | At least two criteria are satisfied | (not used) | fewer than two criteria are satisfied |
| Latin alphabet names | Are the feature names written in the Latin alphabet? | Administrative layer | If names are written in an alphabet which is not Latin, it must be translated into English in another column. (Link to ITOS schema) | |||
| Metadata tab | Does the Excel table have a metadata tab? | Dataset | ||||
| No merged cells | Are any cells merged? | Administrative layer | In order to facilitate the use/reading of the tables, no cell must be merged | |||
| Top row | Does the top row contain only item names? | Administrative layer | ||||
| One tab per administrative level | Do the administrative levels have their own tabs? | Dataset | ||||
| Unique feature names | Do any features have duplicate names (within the same higher administrative levels)? | Administrative layer | ||||
| Higher level attributes | Do lower administrative levels have the higher level names and P-Codes? | Administrative layer | ||||
| Blank cells | Do all cells contain data? | Administrative layer | No cell should be. If there is a no data the cell must contain "NA" | |||
| Integer data | Are all data integer? | Administrative layer | No decimal values are permitted | |||
| Totals | Are there totals columns? | Administrative layer | Best practice | |||
| Individual cell values | Do any cells contain more than one piece of information or a range of values? | Administrative layer | ||||
| COD-PS P-code criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly Usable | Needs Improvement |
| No missing P-codes | Does every feature have a P-code? | Administrative layer | All criteria are satisfied | (not used) | Not all criteria are satisfied | |
| Hierarchical P-code structure? | Do the P-codes incorporate values from higher levels? | Administrative layer | P-codes guideline and Duplicates attributes check tutorial | |||
| Unique P-codes | Are the P-codes unique? | Administrative layer | ||||
| COD-PS Parentage criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly Usable | Needs Improvement |
| P-code parentage | Does each admin level have upper-level P-codes? Is the hierarchy the same between levels? | Administrative layer | forthcoming | Both criteria are satisfied | (not used) | One or more criteria are not satisfied |
| Name parentage | Does each admin level have upper-level feature names? Is the hierarchy the same between levels? | Administrative layer | ||||
| COD-PS Sex and age disaggregation criteria group | ||||||
| Criterion | Description | Applicability | Guidance | Fully Usable | Partly Usable | Needs Improvement |
| Sex disaggregation | Are the statistics disaggregated by sex? | Administrative layer | There must be integrated age-sex disaggregation with sex disaggregation for every age cohort. | There is overall sex and/or age disaggregation without sex disaggregation for every age cohort. | Neither sex nor age disaggregation is available. | |
| Age disaggregation | Are the statistics disaggregated by age? | Administrative layer | ||||
...