<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="2.5" ID="BFA_2010-2025_JMR_v01_M" xml-lang="en" xmlns="ddi:codebook:2_5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="ddi:codebook:2_5 https://ddialliance.org/Specification/DDI-Codebook/2.5/XMLSchema/codebook.xsd">
<docDscr>
  <citation>
    <titlStmt>
      <IDNo>BFA_2010-2025_JMR_v01_M</IDNo>
      <titl>Joint Food Security Monitor - Burkina Faso</titl>
    </titlStmt>
    <prodStmt>
      <producer abbr="" affiliation="World Bank, Development Data Group (DECDG)" role="Lead modeler">Mathijs Lomme</producer>
      <producer abbr="" affiliation="World Bank, Development Data Group (DECDG)" role="Technical lead">Bo Pieter Johannes Andrée</producer>
      <producer abbr="" affiliation="World Bank, Agriculture and Food Global Practice" role="Technical coordinator">Zacharey Carmichael</producer>
      <producer abbr="" affiliation="World Bank, Agriculture and Food Global Practice" role="Co-investigator">Steve Penson</producer>
      <prodDate date="2025-10-20">2025-10-20</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version></version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Joint Food Security Monitor - Burkina Faso</titl>
      <subTitl>Burkina Faso, 45 areas, 2010-01-01 - 2025-09-01, version 2025-10-20</subTitl>
      <altTitl>Joint Monitoring Report (JMR) data</altTitl>
      <parTitl/>
      <IDNo>BFA_2010-2025_JMR_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="World Bank, Development Data Group (DECDG)">Lomme, Mathijs</AuthEnty>
      <AuthEnty affiliation="World Bank, Development Data Group (DECDG)">Andrée, Bo Pieter Johannes</AuthEnty>
      <othId role="Multi-partner" affiliation="iNGO" email="">
        <p>IPC</p>
      </othId>
      <othId role="Source of FEWS NET IPC data" affiliation="USAID" email="">
        <p>FEWS NET</p>
      </othId>
      <othId role="Source of conflict data" affiliation="iNGO" email="">
        <p>ACLED</p>
      </othId>
      <othId role="JMR drafting team Source of market prices Source of the Agricultural Stress Index" affiliation="United Nations" email="">
        <p>FAO</p>
      </othId>
      <othId role="Source of administrative boundaries data" affiliation="United Nations" email="">
        <p>OCHA</p>
      </othId>
      <othId role="JMR drafting team Source of market prices Source of Rainfall data Source of NDVI data" affiliation="United Nations" email="">
        <p>WFP</p>
      </othId>
      <othId role="JMR drafting team" affiliation="United Nations" email="">
        <p>UNICEF</p>
      </othId>
      <othId role="JMR drafting team" affiliation="United Nations" email="">
        <p>WHO</p>
      </othId>
      <othId role="JMR drafting team" affiliation="Non-profit, non-governmental project" email="">
        <p>ACAPS</p>
      </othId>
      <othId role="Source of population data" affiliation="School of Geography and Environmental Science, University of Southampton" email="">
        <p>WorldPop</p>
      </othId>
      <othId role="Source of food insecurity data" affiliation="United States Agency for International Development, and the US Department of State" email="">
        <p>FEWS NET</p>
      </othId>
    </rspStmt>
    <prodStmt>
      <copyright>For details on the terms and conditions for usage of the data, please refer to the Terms and Conditions when accessing the microdata.</copyright>
      <software version="beta" date="2025-10-20">MetadataEditor</software>
      <prodDate/>
      <prodPlac/>
      <fundAg abbr="" role="Support to methodological development. Support to data analytics. Data documentation and dissemination. Expansion of coverage and maintenance.">World Bank's Food Systems 2030</fundAg>
      <fundAg abbr="" role="Support to methodological development. Support to data analytics. Data documentation and dissemination. Expansion of coverage and maintenance.">World Bank's Food Systems 2030</fundAg>
      <grantNo>TF0C0728</grantNo>
      <grantNo>TF0C0828</grantNo>
    </prodStmt>
    <distStmt>
      <contact affiliation="World Bank, Development Data Group" URI="" email="https://datahelpdesk.worldbank.org/">Data Help Desk</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Ongoing food security assessement in Burkina Faso</serName>
      <serInfo><![CDATA[The Joint Food Security Monitor country pages provide live datasets compiled and updated monthly by the World Bank–led Joint Monitoring Report (JMR) team. These datasets draw on publicly available food-security-related data and statistical modeling techniques.

Each dataset provides a combination of raw data, transformed indicators, binary alerts, and population exposure estimates. The alerts are raised using the transformed indicator data at thresholds that best anticipate historical food insecurity escalations. The alert levels are categorized as Typical (no alert), Heightened, or Critical risks of escalation. The population estimates are generated using regression techniques.

The datasets are continually updated and refined as new data become available.

The following country pages are part of this series:

•World: https://microdata.worldbank.org/index.php/catalog/study/WLD_2010-2025_JMR_v01_M
•Afghanistan: https://microdata.worldbank.org/index.php/catalog/study/AFG_2010-2025_JMR_v01_M
•Burkina Faso: https://microdata.worldbank.org/index.php/catalog/study/BFA_2010-2025_JMR_v01_M
•Cameroon: https://microdata.worldbank.org/index.php/catalog/study/CMR_2010-2025_JMR_v01_M
•Democratic Republic of the Congo: https://microdata.worldbank.org/index.php/catalog/study/COD_2010-2025_JMR_v01_M
•Haiti: https://microdata.worldbank.org/index.php/catalog/study/HTI_2010-2025_JMR_v01_M
•Mali: https://microdata.worldbank.org/index.php/catalog/study/MLI_2010-2025_JMR_v01_M
•Mozambique: https://microdata.worldbank.org/index.php/catalog/study/MOZ_2010-2025_JMR_v01_M
•Malawi: https://microdata.worldbank.org/index.php/catalog/study/MWI_2010-2025_JMR_v01_M
•Niger: https://microdata.worldbank.org/index.php/catalog/study/NER_2010-2025_JMR_v01_M
•Nigeria: https://microdata.worldbank.org/index.php/catalog/study/NGA_2010-2025_JMR_v01_M
•Sudan: https://microdata.worldbank.org/index.php/catalog/study/SDN_2010-2025_JMR_v01_M
•Somalia: https://microdata.worldbank.org/index.php/catalog/study/SOM_2010-2025_JMR_v01_M
•South Sudan: https://microdata.worldbank.org/index.php/catalog/study/SSD_2010-2025_JMR_v01_M
•Chad: https://microdata.worldbank.org/index.php/catalog/study/TCD_2010-2025_JMR_v01_M
•Yemen: https://microdata.worldbank.org/index.php/catalog/study/YEM_2010-2025_JMR_v01_M]]></serInfo>
    </serStmt>
    <verStmt>
      <version date="2025-10-20"/>
      <verResp>Joint Monitoring Report (JMR) team</verResp>
      <notes><![CDATA[This version is based on the Joint Food Security Monitor of October 2025. Data cut-offs for the are set to October 20, 2025. The data do generally not reflect the impact of events up to the cut-off date as there is varying delay with which official data is published. Joint Food Security Monitor data are not directly comparable across different versions. Indicators are selected based on data availability and may be revised to improve the performance in predicting food security deteriorations using calibration methods outlined by Penson et al. (2024). Consequently, alert thresholds are also re-evaluated based on the updated data and may change over time. Historical versions of Joint Food Security Monitor data are preserved for transparency and research purposes.]]></notes>
    </verStmt>
    <biblCit format=""><![CDATA[]]></biblCit>
    <notes><![CDATA[Model is based on Penson, Steve; Lomme, Mathijs; Carmichael, Zacharey Austin; Manni, Alemu; Shrestha, Sudeep; Andree, Bo Pieter Johannes. A Data-Driven Approach for Early Detection of Food Insecurity in Yemen&#039;s Humanitarian Crisis (English). Policy Research working paper ; no. WPS 10768; PEOPLE;RRR Washington, D.C. : World Bank Group. http://documents.worldbank.org/curated/en/099709505092462162]]></notes>
  </citation>
  <studyAuthorization date="">
    <authorizationStatement><![CDATA[]]></authorizationStatement>
  </studyAuthorization>
  <stdyInfo>
    <studyBudget><![CDATA[]]></studyBudget>
    <subject>
      <keyword vocab="" vocabURI="">Burkina Faso</keyword>
      <keyword vocab="" vocabURI="">Joint Monitoring Report</keyword>
      <keyword vocab="" vocabURI="">Integrated Food Security Phase Classification</keyword>
      <keyword vocab="" vocabURI="">Threshold modeling</keyword>
      <keyword vocab="" vocabURI="">FEWS NET</keyword>
      <keyword vocab="" vocabURI="">Food prices</keyword>
      <keyword vocab="" vocabURI="">Exchange rates</keyword>
      <keyword vocab="" vocabURI="">Drought rainfall</keyword>
      <keyword vocab="" vocabURI="">Conflict</keyword>
    </subject>
    <abstract><![CDATA[This dataset provides high-frequency food security alerts and metrics of key indicators relevant to food security crises, offering critical insights into localized risks in areas prone to food insecurity. The dataset includes metrics such as food price inflation, agricultural productivity shocks, and economic indicators, designed to support the identification of emerging food crises.

Generated using a data-driven approach, food security alerts are calibrated for accuracy and reliability, capturing granular trends often missed by traditional, infrequently updated assessments. The dataset aims to enhance the ability of policymakers, humanitarian organizations, and researchers to monitor and respond to food security risks promptly, supporting proactive interventions to mitigate impacts on vulnerable populations.]]></abstract>
    <sumDscr>
      <timePrd date="2010-01-01" event="start" cycle="monthly"/>
      <timePrd date="2025-09-01" event="end" cycle="monthly"/>
      <collDate date="2010-01-01" event="start" cycle="monthly"/>
      <collDate date="2025-09-01" event="end" cycle="monthly"/>
      <nation abbr="BFA">Burkina Faso</nation>
      <geogCover>Burkina Faso, down to sub-national level, 13 admin 1 areas and 45 admin 2 areas</geogCover>
      <geogCoverNote>The sub-national levels follow the COD standard (https://knowledge.base.unocha.org/wiki/spaces/imtoolbox/pages/2557378679/Administrative+Boundaries+COD-AB)</geogCoverNote>
      <geogUnit>Sub-national level, admin 2</geogUnit>
      <anlyUnit><![CDATA[Sub-national level, admin 2, monthly basis]]></anlyUnit>
      <universe><![CDATA[]]></universe>
      <dataKind>Alert levels for each indicator that drives food insecurity in Burkina Faso, where the level can be Typical (no alert raised), Heightened or Critical</dataKind>
    </sumDscr>
    <qualityStatement>
      <standardsCompliance>
        <complianceDescription>World Bank Group. (2024). Development Data Quality Policy. https://ppfdocuments.azureedge.net/de65051a-a1ee-410e-aba8-9c302f59be2f.pdf</complianceDescription>
      </standardsCompliance>
      <otherQualityStatement/>
    </qualityStatement>
    <notes><![CDATA[The indicator groups selected by the model for Burkina Faso, with their respected possible indicators are:

Conflict: conflict fatalities, conflict fatalities neighbouring areas
Drought rainfall: rainfall
Exchange rates: exchange_rate_unofficial
Food prices: beans, maize, millet, sorghum, food_price_index]]></notes>
    <exPostEvaluation completionDate="" type="">
      <evaluationProcess/>
      <outcomes/>
    </exPostEvaluation>
  </stdyInfo>
  <method>
    <dataColl>
      <timeMeth>time-series</timeMeth>
      <frequenc>monthly</frequenc>
      <sampProc><![CDATA[]]></sampProc>
      <sampleFrame>
        <sampleFrameName/>
        <custodian/>
        <universe/>
        <frameUnit isPrimary="">
          <unitType numberOfUnits=""/>
        </frameUnit>
        <updateProcedure/>
      </sampleFrame>
      <deviat/>
      <resInstru><![CDATA[]]></resInstru>
      <instrumentDevelopment type=""/>
      <sources>
        <dataSrc>ACLED CONFLICT</dataSrc>
        <srcOrig>ACLED (Armed Conflict Location and Event Data), is an independent, impartial, international non-profit organization collecting data on violent conflict and protest in all countries and territories in the world.Link: https://acleddata.com/data-export-tool/</srcOrig>
        <srcChar/>
      </sources>
      <sources>
        <dataSrc>WFP RAINFALL</dataSrc>
        <srcOrig>WFP publishes this dataset on HDX, where it contains dekadal rainfall indicators computed from Climate Hazards Group InfraRed Precipitation satellite imagery with insitu Station data (CHIRPS) version 2, aggregated by subnational administrative units.Link: https://data.humdata.org/dataset/bfa-rainfall-subnational</srcOrig>
        <srcChar/>
      </sources>
      <sources>
        <dataSrc>WORLD BANK RTFX</dataSrc>
        <srcOrig>The World Bank's Real Time Exchange Rates, contains monthly exchange rate estimates by product and market, using FAO and WFP data as input.Link: https://microdata.worldbank.org/index.php/catalog/study/BFA_2023_RTFX_V01_M</srcOrig>
        <srcChar/>
      </sources>
      <sources>
        <dataSrc>WORLD BANK RTFP</dataSrc>
        <srcOrig>The World Bank's Real Time Food Prices, contains monthly food price estimates by product and market, using FAO and WFP data as input.Link: https://microdata.worldbank.org/index.php/catalog/study/BFA_2021_RTFP_V02_M</srcOrig>
        <srcChar/>
      </sources>
      <collSitu><![CDATA[]]></collSitu>
      <actMin><![CDATA[]]></actMin>
      <ConOps><![CDATA[]]></ConOps>
      <weight><![CDATA[]]></weight>
      <cleanOps><![CDATA[]]></cleanOps>
    </dataColl>
    <notes><![CDATA[The Joint Food Security Monitor datasets consist of four components: raw data, transformed indicators, binary alerts, and population exposure estimates. The transformation and alert framework is developed by Penson et al. (2024). For each indicator, multiple transformation methods and time windows are evaluated, and the best-performing ones are automatically selected. These transformations normalize time-varying risk into a stable range and include methods such as z-scores, moving average divergences, and the Relative Strength Index (RSI).

Alert levels (Heightened or Critical) are determined by applying thresholds to the normalized indicators so as to best reproduce historical food insecurity patterns. Thresholds are optimized by minimizing a loss function that balances the False Positive Rate (FPR) and the False Negative Rate (FNR). The loss formulations follow Andrée et al. (2020). The Heightened threshold minimizes the weighted loss with a two-thirds emphasis on false negatives, while the Critical threshold uses a more conservative calibration that places a two-thirds weight on false positives.

Binary alerts from different indicators are combined into a Generalized Linear Model (GLM) to produce population-at-risk estimates. The GLM is estimated using weighted maximum likelihood estimation (WMLE). The weights are calibrated so that the sum of probability-weighted populations best matches each country’s historical total of populations exceeding IPC cutoff phases.

Across the literature, several approaches exist. Andrée et al. (2020) develop a GLM using lagged continuous indicator data and optimize it for prediction of escalations only, defined as transitions from non-critical IPC phases. Training and validation are done on panel data to ensure sufficient escalation events. Penson et al. (2024) develop a GLM using only binary alerts, trained and validated against escalation events. Gbadegesin, Andrée, and Braimoh (2024) fit a GLM using lagged continuous indicators in Afghanistan against all phase data rather than escalation events only.

Because the Joint Food Security Monitor spans many countries with differing prevalence of escalation events, these methods are unified into a hybrid framework. In the first stage, recursive feature elimination (RFE) is used to select binary alerts following the Penson et al. (2024) approach. In the second stage, lagged continuous indicators from the Andrée and Gbadegesin models are added, while keeping the binary indicators fixed, and RFE is reapplied. The calibration and validation frameworks are also unified. Specifically, the escalation-only validation logic of Andrée and Penson is merged with the full-sample validation of Gbadegesin by combining loss functions as follows: loss1 = 1 - x / log(2), where x = w * loss(escalations) + (1 - w) * loss(all), and w = log(N_escalations) / log(N_all). When escalation events are scarce, this combined loss approximates that of Gbadegesin et al. (2024), while when escalation events are plentiful, it converges toward Andrée et al. (2020) and Penson et al. (2024).

The final GLM is estimated using WMLE with positive-class weights calibrated to match historical country-level population totals. A second loss function, loss2 = 1 - (pooled_rmse^2) / (pooled_rmse_baseline^2), measures fit between estimated and observed country-level population exposures, pooling values above and below the median. This acts as a balanced pseudo R-squared, sensitive to errors in both high and low exposure regimes.

The overall loss combines loss1 (admin-level balanced loss) and loss2 (country-level balanced loss). The weights are determined by effective sample sizes that account for spatial and temporal correlation: N_eff = N / (1 + (N - 1) * rho_s) and T_eff = T / (1 + (T - 1) * rho_t). The combined loss is calculated as loss = 1 - sqrt(w * (1 - loss1)^2 + (1 - w) * (1 - loss2)^2), where w = N_eff / (N_eff + T_eff). This mirrors the weighted error logic of Andrée et al. (2020). When the time series is short, model optimization prioritizes cross-sectional fit (loss1); when the time series is long, it prioritizes temporal consistency (loss2). The correlation adjustments prevent over-weighting in cases where many administrative units are identical (e.g., due to coarse IPC assessment levels) or where country-level totals vary little over time.

References:
Andrée, B. P. J., Chamorro, A., Spencer, P., Kraay, A., &amp; Wang, D. (2020). Predicting food crises (Policy Research Working Paper No. 9412). World Bank. https://hdl.handle.net/10986/34510
Gbadegesin, T. K., Andrée, B. P. J., &amp; Braimoh, A. (2024). Climate shocks and their effects on food security, prices, and agricultural wages in Afghanistan (Policy Research Working Paper No. 10999). World Bank. https://hdl.handle.net/10986/42552
Penson, S., Lomme, M., Carmichael, Z., Manni, A., Shrestha, S., &amp; Andrée, B. P. J. (2024). A data-driven approach for early detection of food insecurity in Yemen’s humanitarian crisis (Policy Research Working Paper No. 10768). World Bank. https://hdl.handle.net/10986/41534]]></notes>
    <anlyInfo>
      <respRate><![CDATA[]]></respRate>
      <EstSmpErr><![CDATA[]]></EstSmpErr>
      <dataAppr><![CDATA[]]></dataAppr>
    </anlyInfo>
    <stdyClas><![CDATA[]]></stdyClas>
    <dataProcessing type="FEWS NET">Data is provided by livelihood zone, which is transformed to admin level 2 areas by using the population percentages in the different livelihood zones. The IPC phases are rounded to the nearest integer adjusted for whether or not humanitarian assistance was available in that admin level 2 area.</dataProcessing>
    <dataProcessing type="WorldPop">Data is provided in .tif files on a yearly basis. The gridded data is aggregated to the admin level 2 areas by taking the sum by area. Monthly population numbers are kep constant throughout each year.</dataProcessing>
    <dataProcessing type="ACLED CONFLICT">All events contain a date, a lat/lon location and the number of fatalities. We map the lat/lon locations to an admin level 2 area and we aggregated to a monthly level per admin level 2 area by taking the sum of the total fatalities. Additionally, we keep track of neighbouring conflict by taking the sum of all fatalities in directly neighbouring admin level 2 areas per admin level 2 area.</dataProcessing>
    <dataProcessing type="WFP RAINFALL">The total rainfall, which is given in mm by admin level 2 area by dekad, is aggregated to a monthly level by taking the sum. Admin level 2 areas with missing data are filled in by taking the average total rainfall of all direct neighbouring admin level 2 areas.</dataProcessing>
    <dataProcessing type="WORLD BANK RTFX">Exchange rates are provided on a monthly basis for various markets. These markets are mapped onto admin level 2 areas using their lat/lon coordinates. Admin 2 areas without a market take the average of all markets found in the corresponding admin 1 area. If there are still admin 2 areas with missing exchange rates, we take the average of all neighbouring admin 2 areas.</dataProcessing>
    <dataProcessing type="WORLD BANK RTFP">Food prices are provided on a monthly basis for various markets. These markets are mapped onto admin level 2 areas using their lat/lon coordinates. Admin 2 areas without a market take the average of all markets found in the corresponding admin 1 area. If there are still admin 2 areas with missing food prices, we take the average of all neighbouring admin 2 areas.</dataProcessing>
    <codingInstructions relatedProcesses="TODO" type="TODO">
      <txt>TODO</txt>
      <command formalLanguage="TODO">TODO</command>
    </codingInstructions>
  </method>
  <dataAccs>
    <setAvail>
      <accsPlac URI="https://microdata.worldbank.org">World Bank Microdata Library, JMR Collection</accsPlac>
      <origArch/>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty>4 per country page</fileQnty>
      <notes><![CDATA[]]></notes>
    </setAvail>
    <useStmt>
      <restrctn>The values presented in these datasets are all based on publicly-available data.
The datasets are published as open data.</restrctn>
      <contact affiliation="World Bank, Development Data Group" URI="" email="https://datahelpdesk.worldbank.org/">Data Help Desk</contact>
      <citReq><![CDATA[Please cite this dataset as follows: Lomme, M. and Andrée, B. P. J. (2025). Joint Food Security Monitor - Burkina Faso (Version 2025-10-20). BFA_2010-2025_JMR_v01_M. Washington, DC: World Bank Microdata Library. DOI: TBC]]></citReq>
      <deposReq><![CDATA[]]></deposReq>
      <conditions><![CDATA[]]></conditions>
      <disclaimer><![CDATA[The JMR data and metadata provided as is and as available, and every effort is made to ensure their timeliness, accuracy, and completeness. When errors are discovered, they are corrected as appropriate and feasible. For details on the terms and conditions for usage of the JMR database, please refer to the license details]]></disclaimer>
    </useStmt>
    <notes><![CDATA[]]></notes>
  </dataAccs>
  <notes><![CDATA[]]></notes>
</stdyDscr>
<fileDscr ID="F1">
  <fileTxt>
    <fileName>BFA_JMR_data.csv</fileName>
    <fileCont>The main dataset, showing for each month/admin level 2 area in Burkina Faso, per indicator, the original value, the indicator value and the alert level</fileCont>
    <dimensns>
      <caseQnty></caseQnty>
      <varQnty></varQnty>
    </dimensns>
    <dataChck></dataChck>
    <dataMsng></dataMsng>
    <verStmt>
      <version>2025-10-20</version>
    </verStmt>
  </fileTxt>
  <notes>The indicator value follows from applying a certain method on the original value, which can be found in the BFA_JMR_model_details.csv file. Breaching thresholds on this indicator value result in the given alert levels.</notes>
</fileDscr>
<fileDscr ID="F2">
  <fileTxt>
    <fileName>BFA_JMR_model_details.csv</fileName>
    <fileCont>Details about the indicators used in the JMR model for Burkina Faso</fileCont>
    <dimensns>
      <caseQnty></caseQnty>
      <varQnty></varQnty>
    </dimensns>
    <dataChck></dataChck>
    <dataMsng></dataMsng>
    <verStmt>
      <version>2025-10-20</version>
    </verStmt>
  </fileTxt>
  <notes>For all used indicators, this dataset shows the alert thresholds determined by the model and the corresponding scoring metrics. Information about which method was used on the original value to determine the indicator value is listed in the description.</notes>
</fileDscr>
<fileDscr ID="F3">
  <fileTxt>
    <fileName>BFA_JMR_pcodes.csv</fileName>
    <fileCont>The sub-national, admin 2, areas for Burkina Faso</fileCont>
    <dimensns>
      <caseQnty></caseQnty>
      <varQnty></varQnty>
    </dimensns>
    <dataChck></dataChck>
    <dataMsng></dataMsng>
    <verStmt>
      <version>2025-10-20</version>
    </verStmt>
  </fileTxt>
  <notes>BFA_JMR_data.csv is pcoded. That dataset links to this dataset through the admin2_pcode variable. This dataset holds all additional information regarding the admin level 2 areas, like name and admin level 1 information.</notes>
</fileDscr>
<fileDscr ID="F4">
  <fileTxt>
    <fileName>BFA_JMR_country_level.csv</fileName>
    <fileCont>Country level wide number of alerts and population living in areas at risk for Burkina Faso</fileCont>
    <dimensns>
      <caseQnty></caseQnty>
      <varQnty></varQnty>
    </dimensns>
    <dataChck></dataChck>
    <dataMsng></dataMsng>
    <verStmt>
      <version>2025-10-20</version>
    </verStmt>
  </fileTxt>
  <notes>This dataset is the aggregated version of BFA_JMR_data.csv, where all alerts are summed by indicator and date. Furthermore, the population living in areas at risk is aggregated in order to give a quick country level overview.</notes>
</fileDscr>
<dataDscr>
<var ID="V1" name="iso3" files="F1">
  <labl>Country code</labl>
  <notes>ISO3C codes, also known as ISO 3166-1 alpha-3 codes, are three-letter country or territory codes that are part of the ISO 3166 international standard. These codes are used to uniquely represent and identify countries and dependent territories in a standardized manner. Each ISO3C code corresponds to a specific country or territory and is often used in various applications, such as international trade, banking, internet domain names, and statistical analysis, to simplify and standardize country and territory references.</notes>
  <txt>Country code in ISO 3166-1 alpha-3 format</txt>
</var>
<var ID="V2" name="ipc phase cutoff" files="F1">
  <labl>IPC phase cutoff</labl>
  <notes>The FEWS NET IPC phases are integers from 1 to 5, where the higher the number, the higher the level  of food insecurity. This cutoff value means that the model was trained on values below the high risk cutoff vs values of the cutoff and above. A value of three thus indicates a model that was trained on IPC3+ risk.</notes>
  <txt>The FEWS NET IPC phase cutoff for high risk</txt>
</var>
<var ID="V3" name="adm2_pcode" files="F1">
  <labl>Admin 2 pcode</labl>
  <notes>P-codes (Place codes) are unique geographic identification codes, usually represented by combinations of letters and numbers to identify a specific place, point, positional location or feature on a map or within a database. There is only one P-code per administrative unit. The COD-AB standard is used (Common Operational Datasets).</notes>
  <txt>Administrative boundary level 2 pcode</txt>
</var>
<var ID="V4" name="year" files="F1">
  <labl>Year</labl>
  <notes>The year variable represents the year associated with each data point, provided in numerical format (e.g., 2023).</notes>
</var>
<var ID="V5" name="month" files="F1">
  <labl>Month</labl>
  <notes>The month variable indicates the month number (1-12) corresponding to each data point, presented in a numerical format.</notes>
  <txt>Administrative boundary level 2 pcode</txt>
</var>
<var ID="V6" name="indicator" files="F1">
  <labl>Indicator</labl>
  <notes>Different indicators are measured against historical known escalations in food security. Examples of possible indicators are: Food prices, Fuel prices, Exchange rate, Conflict, Drought rainfall, Drought NDVI and Drought ASI.</notes>
  <txt>The indicator name used in the JMR model</txt>
</var>
<var ID="V7" name="grouping" files="F1">
  <labl>Grouping</labl>
  <notes>For each indicator, this column groups into:
Original value: The raw value of the indicator, before any modeling has occuered. For instance, for the indicator Drought rainfall, the Original value will show the rainfall in mm
Indicator value: The value of the indicator after the modeling/transformation has occurred. For instance for the indicator Drought rainfall, the Indicator value could be the Standard Precipitation Index of the total rainfall in mm. The methods that were used for each indicators can be found in the model details datafile.
Alert level: The alert level corresponding to the given Indicator value. A 0 corresponds to Typical, a 1 corresponds to Heightened and a 2 corresponds to Critical. The thresholds for each indicator can be found in the model details datafile.
For the indicator GLM, which is the combined model indicator, an additional option for grouping is added; Population living in areas at risk, which is an indication of the people living in that specific admin 2 area at the certain date that are at risk of experiencing an escalation in food insecurity.
For the indicator Target, which is the outcome all indicators are measured against, four different groupings are presented:
Original IPC phase: Categorical integer between 1 and 5, where a higher number indicates a level level of food insecurity, following the IPC phase format.
IPC phase excluding HA: The IPC phase adjusted for Humanitarian Assistance (HA). When an area received HA, the idea is that this lowered the IPC phase by 1. For example, an area in IPC phase 3, which received HA, will have an IPC phase excluding HA of 4.
Binarized target indicator: The model uses a binary target indicator, where a 1 corresponds to admin 2/date combinations where the IPC phase is above a set threshold (IPC level 3+ or IPC level 4+ depending on the country). A 0 corresponds to all IPC phase clasifications below this cutoff.
Possible escalations: This study focusses on escalations in food insecurity, which means an increase in IPC phase from below the cutoff to above the cutoff. To train the model on these escalations, we define admin 2/date combinations where the previous recorded IPC phase was below the IPC phase cutoff as a possible escalations.</notes>
  <txt>Categorical description for what the value column is showing</txt>
</var>
<var ID="V8" name="value" files="F1">
  <labl>Value</labl>
  <notes>A numeric value which captures the value corresponding to the selected indicator and grouping.</notes>
  <txt>The value corresponding to the indicator/grouping combination</txt>
</var>
<var ID="V9" name="iso3" files="F2">
  <labl>Country code</labl>
  <notes>ISO3C codes, also known as ISO 3166-1 alpha-3 codes, are three-letter country or territory codes that are part of the ISO 3166 international standard. These codes are used to uniquely represent and identify countries and dependent territories in a standardized manner. Each ISO3C code corresponds to a specific country or territory and is often used in various applications, such as international trade, banking, internet domain names, and statistical analysis, to simplify and standardize country and territory references.</notes>
  <txt>Country code in ISO 3166-1 alpha-3 format</txt>
</var>
<var ID="V10" name="ipc phase cutoff" files="F2">
  <labl>IPC phase cutoff</labl>
  <notes>The FEWS NET IPC phases are integers from 1 to 5, where the higher the number, the higher the level  of food insecurity. This cutoff value means that the model was trained on values below the high risk cutoff vs values of the cutoff and above. A value of three thus indicates a model that was trained on IPC3+ risk.</notes>
  <txt>The FEWS NET IPC phase cutoff for high risk</txt>
</var>
<var ID="V11" name="indicator" files="F2">
  <labl>Indicator</labl>
  <notes>Different indicators are measured against historical known escalations in food security. Examples of possible indicators are: Food prices, Fuel prices, Exchange rate, Conflict, Drought rainfall, Drought NDVI and Drought ASI.</notes>
  <txt>The indicator name used in the JMR model</txt>
</var>
<var ID="V12" name="alert level" files="F2">
  <labl>Alert level</labl>
  <notes>For each indicator, two thresholds are set; a heightened and a critical. These thresholds are the outcome of the univariate analysis of each indicator against the binarized target indicator. This modeling aims to minimize a loss function, which is a weighted average between the False Positive Rate and the False Negative Rate. For the heightened risk thresholds a heavier weight is put on minimizing the False Negative Rate and for the critical risk thresholds a heavier weight is put on minimizing the False Positive Rate.</notes>
  <txt>The alert level, eiher heightened or critical</txt>
</var>
<var ID="V13" name="threshold" files="F2">
  <labl>Threshold</labl>
  <notes>A numeric value. In the description field it is made clear that an alert is raised whenever the indicator value goes either above or below the threshold. For instance for the indicator Drought Rainfall, an alert is raised when the indicator value is BELOW the threshold, whereas for most other indicators, alerts are raised when the indicator value goes ABOVE the threshold.</notes>
  <txt>The threshold that, if breached and depending on the selected alert level, raises either a heightened risk alert or a critical risk alert</txt>
</var>
<var ID="V14" name="description" files="F2">
  <labl>Description</labl>
  <notes>Holds information on which method with which time-window was used on the indicators original value in order to transform it to the indicator value. For instance for the indicator Food prices, the method used could be Percentag of moving average over the last 6 months. For the indicator Drought Rainfall, the method used could be the Standard Precipitation Index, which time-window 12 months.</notes>
  <txt>Description of the indicator</txt>
</var>
<var ID="V15" name="loss escalations" files="F2">
  <labl>Loss metric for escalations in training dataset</labl>
  <notes>A value between 0 and 1. The loss function is a weighted average between the False Positive Rate and the False Negative Rate, where a Heightened risk alert puts a heavier weight on minimizing the False Negative Rate and a Critical risk alert puts a heavier weight on minimizing the False Positive Rate.</notes>
  <txt>One of the two metrics the model is optimized over, the lower the value, the better the performance. Looks only at the escalations in the target indicator in the training dataset</txt>
</var>
<var ID="V16" name="fpr escalations" files="F2">
  <labl>False Positive Rate escalations</labl>
  <notes>A value between 0 and 1. A lower rate indicates the model is not raising too many false alerts.</notes>
  <txt>The False Positive Rate of the food insecurity escalations in the training dataset</txt>
</var>
<var ID="V17" name="fnr escalations" files="F2">
  <labl>False Negative Rate escalations</labl>
  <notes>A value between 0 and 1. A lower rate indicates the model is not missing to many actual alerts.</notes>
  <txt>The False Negative Rate of the food insecurity escalations in the training dataset</txt>
</var>
<var ID="V18" name="loss all" files="F2">
  <labl>Loss metric for the whole training dataset</labl>
  <notes>A value between 0 and 1. The loss function is a weighted average between the False Positive Rate and the False Negative Rate, where a Heightened risk alert puts a heavier weight on minimizing the False Negative Rate and a Critical risk alert puts a heavier weight on minimizing the False Positive Rate.</notes>
  <txt>One of the two metrics the model is optimized over, the lower the value, the better the performance. Looks at the whole training dataset</txt>
</var>
<var ID="V19" name="fpr all" files="F2">
  <labl>False Positive Rate all</labl>
  <notes>A value between 0 and 1. A lower rate indicates the model is not raising too many false alerts.</notes>
  <txt>The False Positive Rate of the food insecurity predictions in the training dataset</txt>
</var>
<var ID="V20" name="fnr all" files="F2">
  <labl>False Negative Rate all</labl>
  <notes>A value between 0 and 1. A lower rate indicates the model is not missing to many actual alerts.</notes>
  <txt>The False Negative Rate of the food insecurity predictions in the training dataset</txt>
</var>
<var ID="V21" name="adm0_pcode" files="F3">
  <labl>Admin 0 pcode</labl>
  <notes>P-codes (Place codes) are unique geographic identification codes, usually represented by combinations of letters and numbers to identify a specific place, point, positional location or feature on a map or within a database. There is only one P-code per administrative unit. The COD-AB standard is used (Common Operational Datasets).</notes>
  <txt>Administrative boundary level 0 pcode</txt>
</var>
<var ID="V22" name="adm1_name" files="F3">
  <labl>Admin 1 name</labl>
  <notes>Following OCHA and United Nations best matching area names</notes>
  <txt>Administrative boundary level 1 name</txt>
</var>
<var ID="V23" name="adm1_pcode" files="F3">
  <labl>Admin 1 pcode</labl>
  <notes>P-codes (Place codes) are unique geographic identification codes, usually represented by combinations of letters and numbers to identify a specific place, point, positional location or feature on a map or within a database. There is only one P-code per administrative unit. The COD-AB standard is used (Common Operational Datasets).</notes>
  <txt>Administrative boundary level 1 pcode</txt>
</var>
<var ID="V24" name="adm2_name" files="F3">
  <labl>Admin 2 name</labl>
  <notes>Following OCHA and United Nations best matching area names</notes>
  <txt>Administrative boundary level 2 name</txt>
</var>
<var ID="V25" name="adm2_pcode" files="F3">
  <labl>Admin 2 pcode</labl>
  <notes>P-codes (Place codes) are unique geographic identification codes, usually represented by combinations of letters and numbers to identify a specific place, point, positional location or feature on a map or within a database. There is only one P-code per administrative unit. The COD-AB standard is used (Common Operational Datasets).</notes>
  <txt>Administrative boundary level 2 pcode</txt>
</var>
<var ID="V26" name="country" files="F3">
  <labl>Country</labl>
  <notes>Following OCHA and United Nations best matching country names</notes>
  <txt>Administrative boundary level 0 name</txt>
</var>
<var ID="V27" name="iso3" files="F3">
  <labl>Country code</labl>
  <notes>ISO3C codes, also known as ISO 3166-1 alpha-3 codes, are three-letter country or territory codes that are part of the ISO 3166 international standard. These codes are used to uniquely represent and identify countries and dependent territories in a standardized manner. Each ISO3C code corresponds to a specific country or territory and is often used in various applications, such as international trade, banking, internet domain names, and statistical analysis, to simplify and standardize country and territory references.</notes>
  <txt>Country code in ISO 3166-1 alpha-3 format</txt>
</var>
<var ID="V28" name="iso3" files="F4">
  <labl>Country code</labl>
  <notes>ISO3C codes, also known as ISO 3166-1 alpha-3 codes, are three-letter country or territory codes that are part of the ISO 3166 international standard. These codes are used to uniquely represent and identify countries and dependent territories in a standardized manner. Each ISO3C code corresponds to a specific country or territory and is often used in various applications, such as international trade, banking, internet domain names, and statistical analysis, to simplify and standardize country and territory references.</notes>
  <txt>Country code in ISO 3166-1 alpha-3 format</txt>
</var>
<var ID="V29" name="ipc phase cutoff" files="F4">
  <labl>IPC phase cutoff</labl>
  <notes>The FEWS NET IPC phases are integers from 1 to 5, where the higher the number, the higher the level  of food insecurity. This cutoff value means that the model was trained on values below the high risk cutoff vs values of the cutoff and above. A value of three thus indicates a model that was trained on IPC3+ risk.</notes>
  <txt>The FEWS NET IPC phase cutoff for high risk</txt>
</var>
<var ID="V30" name="year" files="F4">
  <labl>Year</labl>
  <notes>The year variable represents the year associated with each data point, provided in numerical format (e.g., 2023).</notes>
</var>
<var ID="V31" name="month" files="F4">
  <labl>Month</labl>
  <notes>The month variable indicates the month number (1-12) corresponding to each data point, presented in a numerical format.</notes>
  <txt>Administrative boundary level 2 pcode</txt>
</var>
<var ID="V32" name="indicator" files="F4">
  <labl>Indicator</labl>
  <notes>Different indicators are measured against historical known escalations in food security. Examples of possible indicators are: Food prices, Fuel prices, Exchange rate, Conflict, Drought rainfall, Drought NDVI and Drought ASI.</notes>
  <txt>The indicator name used in the JMR model</txt>
</var>
<var ID="V33" name="grouping" files="F4">
  <labl>Grouping</labl>
  <notes>For each indicator, this column groups into:
Original value: The raw value of the indicator, before any modeling has occuered. For instance, for the indicator Drought rainfall, the Original value will show the rainfall in mm
Indicator value: The value of the indicator after the modeling/transformation has occurred. For instance for the indicator Drought rainfall, the Indicator value could be the Standard Precipitation Index of the total rainfall in mm. The methods that were used for each indicators can be found in the model details datafile.
Alert level: The alert level corresponding to the given Indicator value. A 0 corresponds to Typical, a 1 corresponds to Heightened and a 2 corresponds to Critical. The thresholds for each indicator can be found in the model details datafile.
For the indicator GLM, which is the combined model indicator, an additional option for grouping is added; Population living in areas at risk, which is an indication of the people living in that specific admin 2 area at the certain date that are at risk of experiencing an escalation in food insecurity.
For the indicator Target, which is the outcome all indicators are measured against, four different groupings are presented:
Original IPC phase: Categorical integer between 1 and 5, where a higher number indicates a level level of food insecurity, following the IPC phase format.
IPC phase excluding HA: The IPC phase adjusted for Humanitarian Assistance (HA). When an area received HA, the idea is that this lowered the IPC phase by 1. For example, an area in IPC phase 3, which received HA, will have an IPC phase excluding HA of 4.
Binarized target indicator: The model uses a binary target indicator, where a 1 corresponds to admin 2/date combinations where the IPC phase is above a set threshold (IPC level 3+ or IPC level 4+ depending on the country). A 0 corresponds to all IPC phase clasifications below this cutoff.
Possible escalations: This study focusses on escalations in food insecurity, which means an increase in IPC phase from below the cutoff to above the cutoff. To train the model on these escalations, we define admin 2/date combinations where the previous recorded IPC phase was below the IPC phase cutoff as a possible escalations.</notes>
  <txt>Categorical description for what the value column is showing</txt>
</var>
<var ID="V34" name="value" files="F4">
  <labl>Value</labl>
  <notes>A numeric value which captures the value corresponding to the selected indicator and grouping.</notes>
  <txt>The value corresponding to the indicator/grouping combination</txt>
</var>
</dataDscr></codeBook>
