Common Operational Dataset tutorials may be found in the IM Toolbox > Tutorials > Common Operational Database tutorials section.

OCHA routinely evaluates the quality and availability of Common Operational Databases.

Administrative boundary (COD-AB) and population statistics (COD-PS) dashboard

This dashboard documents the quality and availability of the administrative boundary (COD-AB) layers and live services and population statistics (COD-PS) tables on HDX. The dashboard has four tabs:

Usability Evaluation Overview

Detailed Evaluation

The 'Status and Rating by Country and Region' matrix groups countries by region and 'operational' vs 'preparedness' status, and depicts the attributes in the following groups:

'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

Indicators 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.

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 indicator group

Indicator	Criterion	Applicability	Guidance	Fully usable	Needs improvement
HDX upload	Is the COD-AB published on HDX?	Dataset		At least one indicator is satisfied	No indicators 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
IMWG endorsement	Is the dataset endorsed by the IMWG?	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. Best Practice
Gazeteer	Are the COD-AB attribute tables for all administrative levels available as an Excel file on HDX?	Dataset	CAN THIS BE REMOVED? IT IS REPEATED IN THE ATTRIBUTE SECTION.
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	A metadata file (in .txt format) or gazeteer tab must be available to provide 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 Best Practice
Shapefile nameing	Is the shapefile naming convention followed?	Administrative layer	The SHP files should follow the naming convention (standards). Best Practice

Attribute criteria

Indicator	Criterion	Applicability	Guidance	Fully usable	Needs improvement
Feature count	Are there the correct number of features?	Administrative layer	Consult reliable sources, particularly COD-PS datasets	Two indicators are satisfied	Fewer than two indicators are satisfied
Complete feature names	Are there any missing feature names?	Administrative layer
Clear field names	Column names must make sense and be clear to prevent any confusion. Is there any explanation/document about standardization of items?	Administrative layer
Latin alphabet names	Are the feature names written in the Latin alphabet?	Administrative layer	If names are written in any 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	Do any features have duplicate names (within the same higher administrative levels)?	Administrative layer	Duplicates attributes check tutorial

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?

P-codes	Parentage
Are there names in all records? Do the P-codes incorporate values from higher levels? Are there any duplicate P-codes within the level?	Does each admin level have upper level P-codes? Is the hierarchy the same between levels? Does each admin level have upper level names? Is the hierarchy the same between levels?

Common Operational Database evaluation and dashboard