Administrative Boundary
Population Statistics
Operational
doughnut chart with segments described above
doughnut chart with segments described above
Preparedness
doughnut chart with segments described above
doughnut chart with segments described above
'OTHER INDICATORS' lists
'Focus Countries List'
'Operational' countries
'Preparedness' countries
'Depth of Administrative Units Level'
Administrative Boundary
Population Statistics
Administrative level 1
Number of available files
Number of available files
Administrative level 2
Number of available files
Number of available files
Administrative level 3
Number of available files
Number of available files
Administrative level 4
Number of available files
Number of available files
'Live Web Services'
List of countries with available live services.
'Detailed Evaluation tab'
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
✔
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
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
'ITOS Live Web Services' tab
'ITOS CLEANING PROCESS' matrix
List name
Indication
HDX
Countries for which ITOS live services are available. Linkages are available on the COD-AB page on HDX.
n/a
Countries which are not ready to develop ITOS live services
QUEUE
Countries which are ready to develop ITOS live services
SUSPENDED
Countries for which ITOS live services may not be developed or published
'LIST OF ITOS LIVE SERVICES BY COUNTRY' matrix
Heading
Indication
Country
name
FeatureServer
link to feature server
MapServer
link(s) to map server(s). The two-character code indicates the language.
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 criteria 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 (see below)
For administrative boundary CODs this means that not all of the spatial criteria are satisfied
For population statistics CODs this means that the sex and age disaggregation is incomplete
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 and COD-PS criteria are applicable to the entire COD-AB (an HDX 'dataset') or to the individual administrative layer. Evaluations for entire datasets are assigned to every component administrative layer.
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
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
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
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
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
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
Both criteria are satisfied
(not used)
Neither criterion is satisfied
Unique P-codes
Are the P-codes unique?
Administrative level
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
Both criteria are satisfied
(not used)
Neither criterion is satisfied
Name parentage
Is the unit names hierarchy the same between levels?
Administrative level
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
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
Correct topology
Are there topological gaps and overlaps?
Administrative level
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
(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
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
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.
(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
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
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
(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?