Yearly Quality Check COD-AB
This quality check is used by OCHA-FIS when evaluating CODs and by field offices yearly when reviewing datasets on HDX.This evaluation is intended to help identify the best available dataset to become the COD-Administrative Boundaries. Use this to help make an informed decision when multiple datasets are available. It is not meant to be a long process.
The scoring system is included in the table. Each cell is populated with the available points. Some cells have more available points, reflecting the weight assigned to that criteria. The point provided should be either the maximum or zero points (but not in between).
Include comments about every criteria; just as important as score
| Indicator | Criteria | Comments | Instructions | Best Practice |
| Metadata | Minimum on HDX (should be part of the files) | |||
| COD AB Present | Is the COD-AB available on HDX? | |||
| Public data | Is the data public on HDX? | |||
| Date of dataset | Is the date of the dataset indicated on HDX? | Required metadata on HDX | ||
| Description | Is there a short but complete description of the dataset? | Required metadata on HDX | ||
| Clear Source | Is the data source clearly indicated and defined on HDX? | Required metadata on HDX | ||
| Clear Methodology/comments | Is there any methodology or comments containing clarified information? | Required metadata on HDX | ||
| Tagged as a COD | Is the file tagged as being a COD? | Required metadata on HDX | ||
| Endorsement by IMWG indicated | Is the COD-AB endorsed by IMWG? | |||
| License | Is the type of license/rights of use defined on the HDX website? | |||
| Grouped data | Are all the COD-AB files grouped as one unique entry on HDX? | Best Practice | ||
| No duplicate files (only one file per level) | Is there only one file per format per level? (e.g., only one SHP for each level) | ArcGIS support | Best Practice | |
| Separate excel file available | Is the COD-AB attribute table also available as an Excel file on HDX? | |||
| CPG file present | Is the .CPG file present within the zip (when needed : AB names in Arabic, Russian, French, Spanish)? | |||
| Metadata file | Is there a metadata file (txt) present with the COD-AB? | To do | ||
| Zip name convention | Is the zip naming convention followed? | File naming convention | Best Practice | |
| Shp name convention | Is the shapefile naming convention followed? | File naming convention | Best Practice | |
| Attribute structure | ||||
| Polygon count check | Is the count of polygons different between sources (GDAM, Wikipedia)? If yes put the number with the source in brackets and some eventual explanation in the comments | |||
| Shp is Polygon | Does the shapefile contain only polygons shapes? | polylines to polygons tutorial | ||
| No missing AB names | Are there names in all records? | |||
| Clear column names | Do the column names respect the naming convention? | |||
| Latin alphabet names | Are all the names transcribed into Latin script when required if other script is local language? (e.g., Latin script name included with Arabic name) | |||
| Tabular format provided | Is there a specific Excel file containing all the AB level units? (Excel - Gazetteer) | Best Practice | ||
| Lower levels have higher attributes included | Do the lower admin boundaries have the higher admin boundaries in the shp? | Best Practice | ||
| Only Unique Names | Is there any duplicate names within the level? | Duplicates attributes tutorial | ||
| P-codes | P-codes Score | |||
| No missing P-codes | Are there names in all records? | |||
| P-codes constructed | Do the P-codes incorporate values from higher levels? | Pcodes guidelines | ||
| Only Unique P-Codes | Is there any duplicate pcodes within the level? (automatic fail) | Duplicates attributes tutorial | ||
| Parentage checks | ||||
| Pcode Parentage Check | Does each admin level have upper level pcodes? Is the hierarchy the same between levels? | Parentage check tutorial | ||
| Name Parentage Check | Does each admin level have upper level names? Is the hierarchy the same between levels? | Parentage check tutorial | ||
| Spatial checks | ||||
| Projection consistent | Is the projection WGS1984 or consistent through out all shps? | |||
| Geometric nesting | Are they some geometric nests between the layers? | Nesting error tutorial | ||
| Topology errors | Are there any gaps or overlaps within the layers? | Topology check tutorial | ||
| Entire country is covered | Do the different level span the entire country? Or if not is the reason documented in the metadata? [Consider Klandestan in which Adm4 only covers urban areas] | |||
| Link to COD-PS check | ||||
| Same number of records in COD-AB and COD-PS (per admin level) | Is there the same number of overall entries (rows) in the PS and AB files? | |||
| P-code field in common | Do the PS and AB have a pcode field in common with the same construction to be able to make the join? | |||
| AB joins to PS | Did the PS join to AB work? | Join check tutorial | ||
| Maintenance Check | ||||
| Reviewed/updated if required | Has the COD-AB been updated within the last 12 months? | |||
| COD-PS was reviewed/updated at same time | Have all the COD-AB files been updated simultaneously? | |||
| Archiving done in metadata on HDX | Has the COD tag been removed from former dataset? Link provided to old/new dataset | |||
| Comments | ||||
| Information to note | ||||
| Updated on: | ||||
| Projection | ||||
| Zip Name | ||||
| Shape Name | ||||
| Code Column Name | ||||
| Name Column Name | ||||
| AB level Name | ||||
| Number of polygons | ||||