...
Version française disponible en bas de page
...
Overview
...
Common Operational Datasets (CODs) are authoritative reference datasets needed to support operations and decision-making for all actors in humanitarian response. CODs CODs are 'best available' datasets that ensure consistency and simplify the discovery and exchange of key data. There are two types of CODs: Core CODs are required in and Country-specific CODs.
Core CODs Core CODs are critical for information and data products and to underpin effective coordination and should be prepared for all disaster-prone countries as a preparedness measure, including . Core CODs comprise administrative boundaries (COD-AB), sex and age-disaggregated population data (COD-PS), and humanitarian profile profiles (caseloadcaseloads) (COD-HP). Core CODs are critical for information and data products and to underpin effective coordination. They are essential for effective risk analysis, needs assessment, decision-making, and reporting by OCHA and partners on all aspects of the response. Of these, the most critical datasets to support response are the basic administrative boundaries (COD-AB) and population statistics (COD-PS). This data is typically provided by the government or national authority. Caseload figures are available after an emergency and can come from a number of sources. A dashboard that illustrates Refer to the COD Portal for information about the availability and quality of the Core CODs is available here: https://cod.unocha.org/and for metadata for COD-ABs and COD-PS data sets.
Country-specific CODs are defined at a country-level based on represent local hazards and operational requirements . Examples include such as key infrastructure that could be impacted or used during relief operations such as schools, health facilities, and refugee camps; , or topographical data such as rivers, land cover , and elevation. This technical support package recommends CODs for each disaster type as well as detailed technical information on each dataset to help ensure they meet minimum standards for quality and accuracy.
...
.
...
CODs are
...
Authoritative reference datasets needed to support operations and decision-making for all actors in a humanitarian response
Best available datasets that ensure consistency and simplify the management of key data.
Two Of two types of CODs: 1) Core, 2) Other Country-Specificspecific
Endorsed Accepted in -country (agreement amongst stakeholders to use same thematic dataset)
To see the status of Core CODs see: COD Dashboard
Purpose of CODs
Datasets country or in their region by the relevant Information Management Working Group
Catalogues at the COD Portal
COD achieve
...
Standarization of datasets that are commonly used and referenced by all operations
Provide consistency Consistency and harmonization among all actors working on humanitarian preparedness and response and enable:
a common operational picture (COP) of the crisis
a geographic framework for data collection, analysis, and visualization (P-codecodes)
P-codes facilitate the exchange and harmonization of data and information
Facilitate CODs facilitate informed decision making both pre- and post-crisis
Reduce Reduced duplication of work on baseline data by partnering organizations
The development of CODs creates/strengthen Strengthened networks and relationships (which are just as valuable as the datasets themselves)
The country-specific CODs should be:
country risk/emergency specific
commonly required by all partners
be practical in term of what is available (time and effort required may affect the data source or detail of datasetdiscussed in a rational manner with partners as they are part of COD cycle and should be contributing CODs
the 'best available' for humanitarian operations
)
P-codes
...
Place Codes (P-codes) are found in Administrative Boundary CODs. They are unique geographic (geo) identification codes, represented by combinations of letters and/or numbers to identify a specific location or feature on a map or within a database. For a specific place, point, or positional locations, the geo-codes have come into common usages as P-codes (abbreviated for Place-code). These terms can be essentially interchanged as long as one recognizes the focus on “position or place” for P-codes. They are also used to provide unique reference codes to refer to settlements or administrative boundaries in other datasetscodes found in COD-AB and COD-PS datasets and are available for use by and linkage from any other humanitarian information that has a spatial component. For more information see the P-code page in the toolbox
The schematic below shows a basic structure of a pP-code system for a country with 2 two administrative boundary levels. When creating a P-code structure for a given country you will need to take into account the country's specific number of administrative levels.
...
...
Process
...
The life cycle of a COD is planning, collecting, processing, endorsing, communicating, maintaining.
  | CODs are identified by the IM network in a country or regionally. If there is no IM network in place and one cannot be created / sustained then all efforts should be made at higher levels (e.g., global) to identify if any agency is working on the desired dataset. The IM network is responsible for collecting and maintaining the CODs and revising the list /datasets as required (reviewed annually minimum). The list of CODs should be presented by the OCHA Head of Office to the HCT or RCT annually for endorsement. 
|
 | CODs should be made available on HDX if possible prior to an emergency or shortly after an emergency. If datasets cannot be placed on HDX they should be shared appropriately. The use of CODs and P-codes should be advocated by the IM network. More information about the process can be found in the COD of this toolbox. |
  | When working with P-codes. National coding schemes should always be used. If there is no national coding scheme, an informal coding scheme that has been adopted by some national or international organizations may be used. Creating a p-code system should only be done if no other system is available. |
...
Le cycle de vie des COD est constitué de 6 étapes : Planifier, Récolter, Traiter, Entériner, Communiquer et Entretenir.
| Les COD sont identifiés par le groupe de gestion d’information (à l’échelle nationale ou régionale). S’il n’existe pas de groupe de gestion d’information, et qu’il n’y a pas la possibilité d’en créer et/ou d’en maintenir un, alors les efforts doivent être déployés au niveau supérieur (par exemple : niveau global) pour identifier une agence travaillant sur l’ensemble de données désiré. Le groupe de gestion d’information est responsable de la collecte, de l’entretien des COD, mais également, de la révision des listes/données comme requis (révisées au minimum tous les ans). Le chef de bureau/service d’OCHA doit présenter la liste des COD à l’équipe Humanitaire du Pays (EHP/HCT) ou à l’équipe régionale du pays (RCT) et ce, tous les ans pour approbation. |
| Les COD doivent être mis à disposition sur HDX, et ce, si possible, avant une urgence ou peu de temps après une urgence. Si les données ne peuvent pas être ajoutées sur HDX elles doivent être partagées pertinemment. L’utilisation des COD et des P-codes doit être préconisée par le groupe de gestion d’information. Vous pouvez trouver plus d’informations concernant le processus sur la page « COD » de ce Toolbox. |
| Lorsque vous travaillez avec les P-codes : il convient d’utiliser les systèmes de codages nationaux. S’il n’existe pas de procédé de codage national, alors il est possible d’utiliser un système de codage informel qui a déjà été adopté par d’autres organisations nationales et/ou internationales. La création d’un système de P-codes ne doit avoir lieu que lorsqu’aucun autre système n’est disponible. |
...