Other Country-Specific CODs

 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 centers, 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.

Step

Step Details

      Tips

1. Examine country's risks and hazards (or current emergency)

Review the country's risks and hazards or current situation

• Good idea for the IM Network lead to brainstorm this before the meeting

• Do this activity with partners (subject mater experts)

• Look at historical events that are similar (e.g. INOFRM - provides high level examination)

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

• Good idea for the IM Network lead to brainstorm this before the meeting

• The Data Prioritization Tool (from UNHCR)  should be used to help limit and prioritize the number of datasets based on time/effort/resources available. Use this as a tool to guide discussion with partners. (instructions are provided in the power point and a projector should be used... a flip chart can easily be used too) Example of output: Floods

• Consider the datasets used ion previous emergencies

3. Add dataset and details
to data plan

Add datasets identified and complete metadata to the COD Data Plan

• Use a projector so everyone can see the Data Plan and ask partners to bring laptops so they can contribute to the Data plan if required

• Consider the data sources used in previous emergencies

• Be sure to discuss who will acquire the datasets sharing permissions as it may impact if the dataset if chosen as a COD

• Have a draft data agreement ready to make negotiations easier

• Consider sub-offices  and other Working Groups (e.g. assessment working group) that are doing data work too

 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)

• Review datasets in a measured and documented way for ease of discussion

• DO not make the process to heavy or lengthy

• Consider MapAction's CUSTARD's methodology for review of spatial data. (Coordinate system, Units, Source, Triangulate, Absent values, Restrictions, Date)

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

•  Use the COD agreement template (modify as required) to identify the CODs, Guardians, data sources and delivery dates.

• Present the COD agreement to the HC or RC for endorsement on a annual basis. 

6. Start COD cycle on Other-country specific datasets identified

• Hold regular meetings to discuss status

• Create a temporary repository for datasets if HDX is not going to be used

• Consider the time it will take to acquire, process datasets!

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.