Coordination & Context
Who is Doing What Where - Operational Presence
The Who is Doing What Where (3W) is a core humanitarian coordination dataset that contains the geographic and sectoral spread of humanitarian activities and partners. It is critical to know where humanitarian organizations are working and what they are doing in order to ensure collaboration and efficient resource allocation, avoid duplication of efforts, identify gaps, and plan for future humanitarian response.
Summary
| Attribute | Details |
|---|---|
| Data provider | OCHA country and regional offices |
| Dataset | Operational Presence tag on HDX |
| Time series | Not available for this subcategory. While older resources are available on HDX, HDX HAPI currently only supports the latest resource. |
| Update frequency | Irregular, depending on the country. Common update frequencies include quarterly and annually. Please check individual resources for more information. |
| Related tables | Org, OrgType, Sector |
Parameters Returned
The table below describes the parameters returned from this endpoint. For available query parameters, please see the API sandbox.
| Parameter | Description | Source |
|---|---|---|
resource_hdx_id |
Unique resource UUID on HDX | Resource |
org_acronym |
The organization acronym | Org |
org_name |
The organization name | Org |
org_type_code |
The code referring to the organization type, derived either from the OCHA Digital Services organization types list , or created for HDX HAPI | Org Type |
org_type_description |
A description of the org type | Org Type |
sector_code |
The sector code, derived either from the Global Coordination Groups dataset, or created for HDX HAPI | Sector |
sector_name |
The name of the sector | Sector |
reference_period_start |
The start date for which the data are applicable | |
reference_period_end |
The end date for which the data are applicable | |
location_code |
Location p-code, based on the ISO-3 (ISO 3166 alpha-3) standard | Location |
location_name |
Location name, based on the "short name" from the UN M49 Standard | Location |
location_ref |
A reference to the id of the associated entry in the location table |
Location |
admin1_code |
Admin 1 p-code | Admin 1 |
admin1_name |
Admin 1 name | Admin 1 |
provider_admin1_name |
Admin 1 names provided in the original source data | |
admin1_ref |
A reference to the id of the associated entry in the admin 1 table |
Admin 1 |
admin2_code |
Admin 2 p-code | Admin 2 |
admin2_name |
Admin 2 name | Admin 2 |
provider_admin2_name |
Admin 2 names provided in the original source data | |
admin2_ref |
A reference to the id of the associated entry in the admin 2 table |
Admin 2 |
Transformations applied
- For consistency and interoperability, we aggregate to an operational presence level (3W:OP, per org, sector, and admin 2), even if the original 3W data is more detailed (e.g. the source lists individual activities)
- Countries that are not p-coded are aggregated to the national level
- Organization deduplication is a long-running challenge with this data, since
there are no unique identifiers, and organization names may be spelled
different ways by different OCHA offices, or sometimes even within the same
3W. See the
orgsection below for more information on how we handle these details. - The sector name strings in the 3W data are normalised and then aligned to the sector table, using the “sector_map” section of this configuration file if needed. In the absence of a direct match, phonetic matching is used for strings > 5 characters.
- Rows without an associated sector are skipped
- The reference period is derived manually per resource based on the resource metadata
Usage notes
- Available at either Admin 0, 1, or 2 depending on the country. Please check data coverage for further information
- We cannot guarantee org consistency over time; for example, if an IMO changes, the 3W might change the spelling or the whole name of an org between releases
Funding
OCHA Financial Tracking Service (FTS) publishes data on humanitarian funding flows as reported by donors and recipient organizations. It presents all humanitarian funding to a country as well as funding that is reported or that can be specifically mapped against funding requirements stated in Humanitarian Response Plans.
Summary
| Attribute | Details |
|---|---|
| Data provider | OCHA FTS |
| Dataset | OCHA FTS - Requirements and Funding Data series |
| Time series | Data contains funding since 2006, but the timepoints are not regular |
| Update frequency | Annually |
| Related tables | None |
Parameters Returned
The table below describes the parameters returned from this endpoint. For available query parameters, please see the API sandbox.
| Parameter | Description | Source |
|---|---|---|
resource_hdx_id |
Unique resource UUID on HDX | Resource |
appeal_code |
A unique code given by FTS to each appeal | |
appeal_name |
Name of the appeal | |
appeal_type |
The type of appeal, such as flash or HRP | |
requirements_usd |
The funding requirements in US dollars | |
funding_usd |
The actual funding in US dollars | |
funding_pct |
A reference to the id of the associated entry in the location table |
Location |
reference_period_start |
The start date for which the data are applicable | |
reference_period_end |
The end date for which the data are applicable | |
location_code |
Location p-code, based on the ISO-3 (ISO 3166 alpha-3) standard | Location |
location_name |
Location name, based on the "short name" from the UN M49 Standard | Location |
location_ref |
nan | nan |
Transformations applied
- The present version of the API currently captures only funding associated with an appeal. Funding data without associated appeals will be added in a future version.
- The reference period is taken from the start and end date provided in each row of the original data
Conflict Events
ACLED collects real-time data on the locations, dates, actors, fatalities, and types of all reported political violence and protest events around the world. HDX HAPI leverages ACLED’s publicly accessible data, aggregated on a monthly basis and to administrative regions. To learn more about their methodology, please consult the ACLED Codebook.
Summary
| Attribute | Details |
|---|---|
| Data provider | ACLED |
| Dataset | ACLED Conflict Events Data series |
| Time series | Monthly |
| Update frequency | Weekly |
| Related tables | EventType |
Parameters Returned
The table below describes the parameters returned from this endpoint. For available query parameters, please see the API sandbox.
| Parameter | Description | Source |
|---|---|---|
resource_hdx_id |
Unique resource UUID on HDX | Resource |
event_type |
ACLED's public dataset is compiled into non-mutually exclusive event-type categories. Please see the ACLED Codebook for their methodology. | Event Type |
events |
The number of events with the given event_type |
|
fatalities |
The number of fatalities due to the given event_type |
|
reference_period_start |
The start date for which the data are applicable | |
reference_period_end |
The end date for which the data are applicable | |
location_code |
Location p-code, based on the ISO-3 (ISO 3166 alpha-3) standard | Location |
location_name |
Location name, based on the "short name" from the UN M49 Standard | Location |
location_ref |
A reference to the id of the associated entry in the location table |
Location |
admin1_code |
Admin 1 p-code | Admin 1 |
admin1_name |
Admin 1 name | Admin 1 |
provider_admin1_name |
Admin 1 names provided in the original source data | |
admin1_ref |
A reference to the id of the associated entry in the admin 1 table |
Admin 1 |
admin2_code |
Admin 2 p-code | Admin 2 |
admin2_name |
Admin 2 name | Admin 2 |
provider_admin2_name |
Admin 2 names provided in the original source data | |
admin2_ref |
A reference to the id of the associated entry in the admin 2 table |
Admin 2 |
Transformations applied
- The data for political violence events, civilian targeting events, and demonstrations are in separate resource on HDX, but are combined into a single endpoint in the API
- Any duplicate rows in the original data are removed
- The reference period is constructed using the full range of the month presented in the “Month” and “Year” columns of the original data
Usage notes
- The three event categories are not mutually exclusive, see
Event Typefor more details - Data is either national or disaggregated to admin 2, see individual resources for more details
National Risk
The INFORM Risk Index is a global, open-source risk assessment for humanitarian crises and disasters. It can support decisions about prevention, preparedness and response. For more information on the methodology, see here.
Summary
| Attribute | Details |
|---|---|
| Data provider | INFORM |
| Dataset | INFORM Risk Index |
| Time series | Not available for this subcategory |
| Update frequency | Annually |
| Related tables | Risk Class |
Parameters Returned
The table below describes the parameters returned from this endpoint. For available query parameters, please see the API sandbox.
| Parameter | Description | Source |
|---|---|---|
resource_hdx_id |
Unique resource UUID on HDX | Resource |
risk_class |
The final INFORM risk score (overall_risk) is grouped into one of five risk classes, with the objective of systemically identifying risk in a consistent manner |
Risk Class |
global_rank |
The rank of the country based on overall_risk. Higher rank (smaller number) is associated with more risk. |
|
overall_risk |
The INFORM composite risk index, based on a combination of 54 indicators into three dimensions of risk: hazard and exposure, vulnerability, and lack of coping capacity. Risk score is given out of 10. | |
hazard_exposure_risk |
Risk due to events that may occur, and exposure to them. Risk score is given out of 10. | |
vulnerability_risk |
Risk due to hazard susceptibility. Risk score is given out of 10. | |
coping_capacity_risk |
Risk due to lack of coping capacity to alleviate hazard impact Risk score is given out of 10. | |
meta_missing_indicators_pct |
The percentage original indicators missing, including any that have been estimated | |
meta_avg_recentness_years |
The average of the total number of years older than the reference year per indicator, to account for any older data used as a proxy | |
reference_period_start |
The start date for which the data are applicable | |
reference_period_end |
The end date for which the data are applicable | |
location_code |
Location p-code, based on the ISO-3 (ISO 3166 alpha-3) standard | Location |
location_name |
Location name, based on the "short name" from the UN M49 Standard | Location |
location_ref |
A reference to the id of the associated entry in the location table |
nan |
Transformations applied
- The reference period is obtained from the HDX dataset