Country-Specific CODs Overview
Country-specific CODs are a subset of the CODs that are specific to each country’s risk profile. They are datasets for which it is essential that the humanitarian community use the same version of the data as a reference. The purpose of a country-specific COD is to provide a common reference for the humanitarian community to create a common operational picture (spatial datasets); to allow for further understanding of the situation (statistical data, tabular data etc); or to aid with assessments. Ideally Country-specific CODs are identified and agreed to as a preparedness activity but the list should be reviewed and revised (if required) at the on-set of a crisis based on situation at that time and the humanitarian needs).
To help identify CODs from the many datasets required in an emergency see: Identifying a COD
List of commonly used operational datasets:
Commonly used operational datasets | Potential uses |
Populated places (cities, villages, towns, villages, etc) | Identify locations or affected people or resources |
Transportation (roads, ports, railways, airports, helipads) | Logistics, determining access, tracking population movement. |
Hydrology (lakes, rivers, ponds, marshes, etc) | Logistics, bridge locations, potential flood areas, |
Hypsography (elevation points, contour lines) | Access challenges to locations, potential landslide areas, weather, population movement |
Education facilities (kindergartens, primary and secondary schools, private and public schools, colleges, universities, etc) | Potential site for evacuation/resource centres, location to target children or others in need, educational needs |
Medical facilities (clinic, medical centers, hospitals, etc) | Location of people in need, medical needs |
Telecommunication infrastructure (radio/mobile phone towers, phone lines, etc) | Logistics, understanding of how to communicate with affected people |
Government buildings (courts, prisons, town halls, military locations, etc) | Logistics, access to government officials and potentially affected people, locations of military operations/personnel |
Access and security constraints (check points, barriers, boarder crossings, road closures, etc) | Logistics, better understanding of movement of people |
Crisis Infrastructure (structures that could be impacted or used during relief operations refugee/IDP camps, evacuation centers,temporary camps, etc) | Logistics, access to affected people |
Points of interest (banks, ATMs, Markets, boreholes, water pumps, stadiums, malls, etc.) | Logistics - sites may be used as crisis centers, Banks/ATMs are being used more frequently for Cash programming), locations for assessments or communicate with large number of affected people |
Demographic data (physically challenged, pregnant women, literacy rates, languages spoken, etc) | Better understanding of people. identification of potential vulnerable groups. |
Ideas for datasets that may be CODs
Steps
Step | Step Details | Tips |
1. Examine country's risks and hazards (or current emergency) | Review the country's risks and hazards or current situation |
|
2. Identify and prioritize datasets would be required to respond to the specific risks and hazards | Make a list of the risks and hazards and then identify datasets that would be required to respond. Use the Data Prioritization Tool (from UNHCR) to help prioritize datasets |
|
3. Add dataset and details | Add datasets identified and complete metadata to the COD Data Plan |
|
4. Evaluate datasets to identify the CODs | Evaluate the datasets if there are multiple being suggested for a database theme so only one is chosen (e.g multiple datasets identified for roads) |
|
5. Develop data agreement | Create a COD agreement to be used to guide the work of other CODs and to be presented to the HC/RC |
|
6. Start COD cycle on Other-country specific datasets identified |
| |
Minimum requirements for Other Country-Specific CODs (To be discussed)
Spatial Data | Tabular data | |
P-codes for admin levels the features fall into (see P-code Guidance) Review specific guidance for Other CODs (camps roads, schools) | x | x |
HXL standards if possible (note that this will impact the use of tabular data in GIS applications but the hashtags (#) can easily be removed prior to joining. | x | |
Projection same as Core COD-AB | x | |
Metadata (especially data sources and methodology) | x | x |
Endorsement from IM Network | x | x |
WILL THIS STILL BE A STANDARD? Event data is often disaster GLIDE number. GLIDE NUMBERS are part of http://vocabulary.unocha.org/ and are used (behind the scenes) by ReliefWeb, HR.info, Events, Assessment Registry, etc. Checking with HDX is they are moving towards this at all. |
Resources
- COD Work Plan Template.xlsx
- COD data Plan Template Example.xls / COD data plan template WFP / OCHA / MapAction
- Data prioritization tool (from UNHCR)
- IMWG COD Agreement Template (for ICCG, HC endorsement)
- Lists of datasets often required for Natural Disasters and Complex Emergencies
- Humanitarian eXchange Language HXL
- Ideas of datasets that could be needed from MapAction product catalog
Other CODs may needed to support operations the following pages offer some ideas and a process (Coordinated Data Scramble) to help IM networks identify what they needed