...
Overview
OCHA routinely evaluates the quality and availability of Common Operational Databases. The results of this analysis can be found on the COD Portal.
| Table of Contents |
|---|
IN DEVELOPMENT
Administrative boundary (COD-AB) and population statistics (COD-PS) dashboard
...
...
...
Usability Evaluation Overview
Detailed Evaluation
...
...
'Administrative Boundary'
- 'ADM1', 'ADM2', 'ADM3', and 'ADM4': Administrative level 1, 2, 3, and 4 boundaries as 'fully usable' (green dot), 'partly usable' (orange dot), 'needs improvement' (red dot), or 'unavailable' (grey dot). The evaluation criteria are described below.
- 'HDX': availability on HDX (green tick) or unavailability (grey dot)
- 'LIVE': availability of live services (green tick) or unavailability (grey dot)
'LINK'
- 'AB-PS': compatibility of P-codes and records allows linkage between Administrative Boundary polygons and Population Statistics records
'Population Statistics'
- 'ADM1', 'ADM2', 'ADM3', and 'ADM4': Administrative level 1, 2, 3, and 4 population statistics as 'fully usable' (green dot), 'partly usable' (orange dot), 'needs improvement' (red dot), or 'unavailable' (grey dot). The evaluation criteria are described below.
- 'HDX': availability on HDX (green tick) or unavailability (grey dot)
ITOS Live Web Services
Frequently Asked Questions
Evaluation criteria
COD-ABs and COD-PSs are evaluated by FIS according to established criteria to maintain standardized levels of quality. Field IMOs are encouraged to use the same criteria for evaluation of candidate CODs and for periodic review of published CODs.
Each administrative level (except level 0 and any level below level 4) is evaluated individually, although some critera apply to entire COD-AB datasets (comprising multiple administrative levels). The evaluated levels are:
- Fully usable: The COD can be used for any purpose
- Partly usable: The COD has some problems that may limit its use
- Needs improvement: The COD is only useful for very limited purposes
Criteria are grouped. Each group has a rule for designation as 'Fully usable', 'Partly usable', or 'Needs improvement'. The evaluation of the entire administrative level is equal to the worst group evaluation.
Country statistics depend on the evaluation of the worst administrative level in the COD dataset.
Some COD-AB an COD-PS criteria are applicable to the entire COD-AB (an HDX 'datatset') or to the individual administrative layer. Evaluations for entire datasets are assigned to every component administrative layer.
COD-AB evaluation criteria
...
Metadata criteria group
...
...
HDX upload
...
Is the COD-AB published on HDX?
...
(not used)
Fewer than nine indicators are satisfied
...
Is the date clearly indicated on HDX?
...
Is there a short but complete description of the dataset?
...
Is the data source clearly indicated and defined on HDX?
...
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.
...
Zip file naming convention helps to standardize referencing of files NOTE LINK HAS NOT BEEN MIGRATED FROM TSP
Shapefile nameing
...
The SHP files should follow the naming convention (standards).
...
Attribute criteria group
...
If names are written in any alphabet which is not Latin, it must be translated into English in another column.
(Link to ITOS schema)
...
Lower levels should include higher levels to see the AB unit it falls in. Best Practice
...
COD-PS evaluation criteria
...
Metadata criteria group
...
...
HDX upload
...
Is the COD-PS published on HDX?
...
(not used)
No indicators are satisfied
...
Is the date clearly indicated on HDX?
...
Is there a short but complete description of the dataset?
...
Is the data source clearly indicated and defined on HDX?
...
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.
...
Zip file naming convention helps to standardize referencing of files NOTE LINK HAS NOT BEEN MIGRATED FROM TSP
...
Attribute criteria group
...
If names are written in any alphabet which is not Latin, it must be translated into English in another column.
(Link to ITOS schema)
...
Lower levels should include higher levels to see the AB unit it falls in. Best Practice
...
- 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
- Are there names in all records?
- Do the column names respect the naming convention?
- Are all the names transcripted into latin script when required if other script is local language? (e.g., Latin script name included with Arabic name)
- Is there a specific Excel file containing all the AB level units? (Excel - Gazetteer)
- Do the lower admin boundaries have the higher admin boundaries in the shp ?
- Are there any duplicate names within the level?
...
...
...
- Are there names in all records?
- Do the P-codes incorporate values from higher levels?
- Are there any duplicate P-codes within the level?
...