--- language: "en" --- # Household Economy Analysis (HEA) Baseline Database ## Household Economy Analysis (HEA) Baseline Database Learn more about best practices for Baseline Storage Sheets (BSS) collection, how to upload them to the HEA database, and HEA database administration. [Get Started](https://help.fews.net/hea/about.md) ### Table of Contents #### [About](https://help.fews.net/hea/about.md) #### [System Architecture](https://help.fews.net/hea/system-architecture.md) #### [Baseline Data Collection Guidance](https://help.fews.net/hea/baseline-data-collection-guidance.md) #### [Data Management](https://help.fews.net/hea/data-management.md) #### [Metadata Management](https://help.fews.net/hea/metadata-management.md) * #### [User Management](https://help.fews.net/hea/user-management.md) * #### [API](https://help.fews.net/hea/api.md) --- language: "en" --- # About The Household Economy Analysis (HEA) Livelihoods Explorer Database serves as a pivotal resource in the assessment and understanding of household economies across various regions. Its creation and ongoing management enable a structured approach to data storage and presentation of the Livelihood Strategies and other characteristics of households within and across diverse Livelihood Zones. One of the important opportunities presented by the Livelihoods Explorer (LEX) Database is its ability to standardize the language and classification used across the range of Baseline surveys and the resulting Baseline Storage Sheets (BSS) for each country. This standardization plays a crucial role in enhancing the comparability and coherence of data, which, in turn, is instrumental in: * **Ensuring consistency**: By adopting international standards and a uniform set of terminologies for metadata, the database ensures that data collected from different regions or studies can be compared and analyzed in a consistent manner. This consistency is fundamental for aggregating data at a national or regional level, thereby providing a comprehensive overview of Livelihood Strategies. * **Facilitating cross-regional analysis**: Standardization of language and classification across BSS allows for the direct comparison of data across different countries and regions. This comparative analysis is essential for identifying patterns, trends, and anomalies in household economies. * **Improving data quality and reliability:**Standardized data storage and classification methodologies contribute to the overall quality and reliability of the data stored in the LEX Database. This reliability is critical for stakeholders, researchers, and policymakers who depend on accurate and comparable data to make informed decisions. * **Enhancing accessibility:** A standardized language and classification system make the database more accessible to a broader audience, including international agencies, non-governmental organizations (NGOs), and researchers unfamiliar with local terminologies. This accessibility is pivotal for collaborative efforts and knowledge sharing on a global scale. * **Enabling data integration:** The use of global metadata standards, such as ISO 3166 for countries, ISO 4217 for currencies, and the Central Product Classification (CPC) v2.1 for products, allow current data for items such as market prices and crop year forecasts to be compared to the data for the reference year, easing the use of HEA data in outcome analysis. --- language: "en" --- # API The Livelihoods Explorer (LEX) offers a comprehensive REST API to access data based on user permissions. This API provides more flexibility than the Livelihoods Explorer user interface. The LEX REST API supports extensive functions. [++Interactive API documentation is available++](https://livelihoodsdev.fews.net/api/). ## Authentication A small amount of information in the Livelihoods Explorer is not available publicly. This includes the list of specific community names and links to download the original BSS files. In order to access this information, users must be authenticated by logging in to the Livelihoods Explorer. After logging in, your browser will send a session cookie automatically to authenticate requests to the API. If you do not authenticate or lack permission to access the data: * You may receive the error "no data found" when you query data that has restricted permissions. * Not all expected data may be included in the response. ## API link structure Each URL consists of up to 5 parts: the base URL, the endpoint, output format, filters, and fields. **Example:** [https://livelihoodsdev.fews.net/api/season.html?country=ET\&fields=simple](https://livelihoodsdev.fews.net/api/season.html?country=ET&fields=simple) This URL has all 5 parts. It can be used to view a list of the seasons in the database for Ethiopia. * Base HEA database URL: https://livelihoods.fews.net/api/ * Endpoint: season * Output format: .html * Filters: ?country=ET * Fields: \&fields=simple ### Base URL The base URL for the Livelihoods Explorer API is https://livelihoods.fews.net/api/. ### Endpoints This API includes a number of endpoints. The most useful endpoints for individuals doing data analysis are: | **Name** | **URL** | **Description** | |---------------------------|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | livelihoodactivitysummary | [https://livelihoods.fews.net/api/livelihoodactivitysummary/](https://livelihoodsdev.fews.net/api/livelihoodactivitysummary/) | View aggregated sums of calories and income from specific livelihood activities for Baseline Wealth Groups. Calculate the amount of overall income, expenditure, kcals_consumed and percentage_kcals that are derived from specific products and/or strategy types. [Learn more about this endpoint](https://help.fews.net/hea/livelihoodactivitysummary.md). | | livelihoodzonebaseline | [https://livelihoods.fews.net/api/livelihoodzonebaseline/](https://headev.fews.net/api/livelihoodzonebaseline/) | Access spatial data of available livelihood zones for mapping. | The most useful endpoints for individuals involved in gathering and submitting BSS data are: | **Name** | **URL** | **Description** | |---------------------------|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| | classifiedproduct | [https://livelihoods.fews.net/api/classifiedproduct/](https://headev.fews.net/api/classifiedproduct/) | View a list of products in the database and their aliases. | | season | [https://livelihoods.fews.net/api/season/](https://headev.fews.net/api/season/) | View a list of seasons in the database. | | seasonalactivitytype | [https://livelihoods.fews.net/api/seasonalactivitytype/](https://headev.fews.net/api/seasonalactivitytype/) | View a list of the types of seasonal activities available in the database and their aliases. | | wealthcharacteristic | [https://livelihoods.fews.net/api/wealthcharacteristic/](https://headev.fews.net/api/wealthcharacteristic/) | View a list of wealth characteristics available in the database and their aliases. | | livelihoodcategory | [https://livelihoods.fews.net/api/livelihoodcategory/](https://headev.fews.net/api/livelihoodcategory/) | View a list of livelihood categories (e.g. Livelihood zone types) available in the database and their aliases. | | livelihoodproductcategory | [https://livelihoods.fews.net/api/livelihoodproductcategory/](https://headev.fews.net/api/livelihoodproductcategory/) | \[Note: This endpoint is currently inaccessible.\] | | wealthgroupcategory | [https://livelihoods.fews.net/api/wealthgroupcategory/](https://headev.fews.net/api/wealthgroupcategory/) | View a list of wealth group categories available in the database and their aliases. | | hazardcategory | [https://livelihoods.fews.net/api/hazardcategory/](https://headev.fews.net/api/hazardcategory/) | View a list of hazard categories available in the database and their aliases. | Additional endpoints include: | **Name** | **URL** | |-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | country | [https://livelihoods.fews.net/api/country/](https://headev.fews.net/api/country/) | | currency | [https://livelihoods.fews.net/api/currency/](https://headev.fews.net/api/currency/) | | unitofmeasure | [https://livelihoods.fews.net/api/unitofmeasure/](https://headev.fews.net/api/unitofmeasure/) | | user | [https://livelihoods.fews.net/api/user/](https://headev.fews.net/api/user/) | | userprofile | [https://livelihoods.fews.net/api/userprofile/](https://headev.fews.net/api/userprofile/) | | sourceorganization | [https://](https://headev.fews.net/api/sourceorganization/)[livelihoods](https://livelihoodsdev.fews.net/api/livelihoodactivitysummary/)[.fews.net/api/sourceorganization/](https://headev.fews.net/api/sourceorganization/) | | livelihoodzone | [https://livelihoods.fews.net/api/livelihoodzone/](https://headev.fews.net/api/livelihoodzone/) | | community | [https://livelihoods.fews.net/api/community/](https://headev.fews.net/api/community/) | | wealthgroup | [https://livelihoods.fews.net/api/wealthgroup/](https://headev.fews.net/api/wealthgroup/) | | baselinewealthgroup | [https://livelihoods.fews.net/api/baselinewealthgroup/](https://headev.fews.net/api/baselinewealthgroup/) | | communitywealthgroup | [https://livelihoods.fews.net/api/communitywealthgroup/](https://headev.fews.net/api/communitywealthgroup/) | | wealthgroupcharacteristicvalue | [https://livelihoods.fews.net/api/wealthgroupcharacteristicvalue/](https://headev.fews.net/api/wealthgroupcharacteristicvalue/) | | baselinewealthgroupcharacteristicvalue | [https://livelihoods.fews.net/api/baselinewealthgroupcharacteristicvalue/](https://livelihoodsdev.fews.net/api/baselinewealthgroupcharacteristicvalue/) | | communitywealthgroupcharacteristicvalue | [https://livelihoods.fews.net/api/communitywealthgroupcharacteristicvalue/](https://livelihoodsdev.fews.net/api/communitywealthgroupcharacteristicvalue/) | | livelihoodstrategy | [https://livelihoods.fews.net/api/livelihoodstrategy/](https://headev.fews.net/api/livelihoodstrategy/) | | livelihoodactivity | [https://](https://headev.fews.net/api/livelihoodactivity/)[livelihoods](https://livelihoodsdev.fews.net/api/livelihoodactivitysummary/)[.fews.net/api/livelihoodactivity/](https://headev.fews.net/api/livelihoodactivity/) | | baselinelivelihoodactivity | [https://livelihoods.fews.net/api/baselinelivelihoodactivity/](https://headev.fews.net/api/baselinelivelihoodactivity/) | | responselivelihoodactivity | [https://livelihoods.fews.net/api/responselivelihoodactivity/](https://headev.fews.net/api/responselivelihoodactivity/) | | milkproduction | [https://livelihoods.fews.net/api/milkproduction/](https://headev.fews.net/api/milkproduction/) | | butterproduction | [https://livelihoods.fews.net/api/butterproduction/](https://headev.fews.net/api/butterproduction/) | | meatproduction | [https://livelihoods.fews.net/api/meatproduction/](https://headev.fews.net/api/meatproduction/) | | livestocksale | [https://livelihoods.fews.net/api/livestocksale/](https://headev.fews.net/api/livestocksale/) | | cropproduction | [https://livelihoods.fews.net/api/cropproduction/](https://headev.fews.net/api/cropproduction/) | | foodpurchase | [https://livelihoods.fews.net/api/foodpurchase/](https://headev.fews.net/api/foodpurchase/) | | paymentinkind | [https://livelihoods.fews.net/api/paymentinkind/](https://headev.fews.net/api/paymentinkind/) | | relief | [https://livelihoods.fews.net/api/relief/](https://headev.fews.net/api/relief/) | | fishing | [https://livelihoods.fews.net/api/fishing/](https://headev.fews.net/api/fishing/) | | hunting | [https://livelihoods.fews.net/api/hunting/](https://headev.fews.net/api/hunting/) | | wildfoodgathering | [https://livelihoods.fews.net/api/wildfoodgathering/](https://headev.fews.net/api/wildfoodgathering/) | | othercashincome | [https://livelihoods.fews.net/api/othercashincome/](https://headev.fews.net/api/othercashincome/) | | otherpurchase | [https://livelihoods.fews.net/api/otherpurchase/](https://headev.fews.net/api/otherpurchase/) | | seasonalactivity | [https://livelihoods.fews.net/api/seasonalactivity/](https://headev.fews.net/api/seasonalactivity/) | | seasonalactivityoccurrence | [https://livelihoods.fews.net/api/seasonalactivityoccurrence/](https://headev.fews.net/api/seasonalactivityoccurrence/) | | communitycropproduction | [https://livelihoods.fews.net/api/communitycropproduction/](https://headev.fews.net/api/communitycropproduction/) | | communitylivestock | [https://livelihoods.fews.net/api/communitylivestock/](https://headev.fews.net/api/communitylivestock/) | | marketprice | [https://livelihoods.fews.net/api/marketprice/](https://headev.fews.net/api/marketprice/) | | seasonalproductionperformance | [https://livelihoods.fews.net/api/seasonalproductionperformance/](https://headev.fews.net/api/seasonalproductionperformance/) | | hazard | [https://livelihoods.fews.net/api/hazard/](https://headev.fews.net/api/hazard/) | | event | [https://livelihoods.fews.net/api/event/](https://headev.fews.net/api/event/) | | expandabilityfactor | [https://livelihoods.fews.net/api/expandabilityfactor/](https://headev.fews.net/api/expandabilityfactor/) | | copingstrategy | [https://livelihoods.fews.net/api/copingstrategy/](https://headev.fews.net/api/copingstrategy/) | ### Output format All endpoints support a standard range of extract formats, which can be accessed using an extension on the URL (for example, ) or a query parameter (for example, [https://livelihoods.fews.net/api/livelihoodactivitysummary/\&format=json](https://livelihoods.fews.net/api/livelihoodactivitysummary/&format=json)). The standard values for the format parameter include: * `html` : a plain HTML table * `json` : a JavaScript Object Notation text string * `csv` : a UTF-8 comma-separated values file with a header row and a UTF-8 byte order mark (BOM) to enable Microsoft Excel and other tools to recognize the file correctly * `xml` : an extensible markup language text string. XML is the recommended format for importing data into Microsoft Excel. The `livelihoodzonebaseline` endpoint also supports spatial extracts using the `geojson` extract format. ### Filters and pagination Many of the time series data domains contain a large amount of data, such that attempting to extract all of it in a single request may fail due to browser timeouts. Best practice is to filter the request to include only the data that is required, or to use pagination to limit the size of each response. #### Filters Options for filters are unique to the end point. Some of the most common and/or useful filter options are described below. To view a full list of options for your endpoint, view our comprehensive, interactive API documentation. * Geography * `country_code` : The ISO 3166-1 alpha-2 two letter code for a country. Options can be found using [https://livelihoods.fews.net/api/country/](https://headev.fews.net/api/country/). Example: \&country_code=KE * `country` : Similar to the country_code filter above, but uses the name of the country rather than the ISO code. This is easier to use, but may be slower, especially for large extracts. Example: ?country=Kenya * `livelihood_zone`: A Livelihood Zone code such as ML12. Options can be found using [https://livelihoods.fews.net/api/livelihoodzone/](https://headev.fews.net/api/livelihoodzone/). * Livelihoods and Baselines * `main_livelihood_category`: The dominant pattern of livelihoods for a Livelihood Zone, such as pastoral or urban. Also called livelihood zone system or production system. Options can be found using [https://livelihoods.fews.net/api/livelihoodcategory/](https://headev.fews.net/api/livelihoodcategory/). * `wealth_group_category`: A Wealth Group Category such as Poor (P) or Better off (B/O). Options can be found using [https://livelihoods.fews.net/api/wealthgroupcategory/](https://headev.fews.net/api/wealthgroupcategory/). * `wealth_characteristic`: An attribute of a Wealth Group such as the number of school-age children. Options can be found using [https://livelihoods.fews.net/api/wealthcharacteristic/](https://headev.fews.net/api/wealthcharacteristic/). * `strategy_type`: A type of livelihood strategy, such as crop production. Options include `MilkProduction`, `ButterProduction`, `MeatProduction`, `LivestockSale`, `CropProduction`, `FoodPurchase`, `PaymentInKind`, `ReliefGiftOther`, `Hunting`, `Fishing`, `WildFoodGathering`, `OtherCashIncome`, `OtherPurchase`. * `scenario`: A Livelihood Activity contains the outputs of a Livelihood Strategy employed by one of the following: * A Wealth Group in a Community in the reference year * A Wealth Group representing the Baseline as a whole in the reference year (the `baseline` scenario) * A Wealth Group representing the Baseline as a whole in response to a shock (the `response` scenario) * `as_of_date`: Using `as_of_date` equal to today will filter out Baselines that are no longer valid. Dates should be in the format YYYY-MM-DD. Example: `as_of_date=2026-06-12`. * Products * `cpc` : CPC is the UN's [++Central Product Classification++](https://unstats.un.org/unsd/classifications/Econ/cpchttps://unstats.un.org/unsd/classifications/Econ/cpc). CPC is a hierarchy, so specifying L02122AF will return only those matching records, whereas filtering for L02122 would return prices for both L02122AA and L02122AF. Options can be found using [https://livelihoods.fews.net/api/classifiedproduct/](https://headev.fews.net/api/classifiedproduct/) Example: ?cpc=L02122 * `product` : A given product name or description. This is easier to use, but may be slower and less accurate than filtering using the `cpc` . Example: ?product=maize * Seasonal calendars * `season_type`: The classification of a specific time of year based on weather patterns, temperature, and other factors. Options include `harvest`, `lean`, `wet`, `dry`, `mild`, `spring`, `summer`, `fall`, `winter`, and `monsoon`. * `activity_category`: Types of seasonal activities. Options include `climatology`, `stress_periods`, `crop`, `livestock`, `fishing`, `other_income`, and `other`. * `seasonal_activity_type`: A specific activity type such as weeding, harvesting, or births. Options can be found using [https://livelihoods.fews.net/api/seasonalactivitytype/](https://headev.fews.net/api/seasonalactivitytype/). #### Pagination When using JSON-formatted responses, the data can be paginated by passing *page_size* and offset parameters as part of the request. For example a request for [++https://livelihoods.fews.net/api/country.json?page_size=10\&offset=0++](https://livelihoodsdev.fews.net/api/country.json?page_size=10&offset=0) will return the following response: { "count": 251, "next": "https://livelihoodsdev.fews.net/api/country.json?offset=0&page=2&page_size=10", "previous": null, "results": [ ] } ### Fields By default the API responses will contain a large number of fields. For some domains they may include various additional statistics such as the value one year ago or the five-year average. It is possible to control which fields are returned by the API using the `fields` parameter. A reduced set of the commonly used fields can be selected using `&fields=simple.` Alternatively, specific fields can be specified in a comma-separated list such as `&fields=dataseries,start_date,period_date,value,two_year_average` . ### Ordering Results can be ordered based on select fields. To order by a specific field, use `&ordering=[field]` such as `&ordering=livelihood_zone`. Default is to order ascending. To order descending, add a `-` before the field name such as `&ordering=-livelihood_zone`. ## Additional support If your use case is not covered by our documentation, please contact [++Help Desk Support++](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/-1). --- language: "en" --- # Baseline Data Collection Guidance This page contains recommendations for general BSS setup. The [Livelihood Strategies](https://help.fews.net/hea/livelihood-activities.md) and [Seasonal Calendar](https://help.fews.net/hea/seasonal-calendars.md) pages contain recommendations for data entry in a BSS. These guidelines ensure that data will be easy to load into the HEA Baseline Database. Loading new Baseline Storage Sheets (BSS) into the database requires the import to recognize the data in the various worksheets and allocate the correct standard metadata. Data that differs from these norms cannot be recognized automatically and must be reconciled manually, requiring additional effort and risking additional data entry errors. ## Spatial files Each BSS should be accompanied by a spatial file that contains the boundaries for the associated Livelihood Zone. This file can be Livelihood Zone specific or a contain multiple Livelihood Zone boundaries (e.g., boundaries for an entire country) and can be in any geocoded format (shapefile, GeoJSON, etc.). Spatial files are essential for including the BSS information in the Livelihoods Explorer application. The administrative zones matching the reference year or zone map validation year should be used. ## File formats All new BSS should be maintained using current versions of Excel and saved in the `.xlsx` file format. The `.xls` format is obsolete and is not supported by many modern tools. The database does not support `.csv `files. Files are locked as soon they are received by the Hub. However, All columns and rows should be unhidden and iterative calculations should be turned on. If this is not the case, we may need to make those formatting changes. ## Livelihood Zone Codes The database allows for comparison of a Livelihood Zone across time. In order to ensure accurate comparison, Livelihood Zones that use the same code should be broadly the same geographically. While small changes are acceptable (see Burkina Faso or Mali, for example), a new code should be used when there is a major change in geography. **Example** A country is split into 40 Livelihood Zones when Baselines are done in 2015. When they are redone in 2025, it is only split into 15 Livelihood Zones. The 2025 set of Livelihood Zones should be numbered 41-55 instead of reusing 1-15, since the boundaries have significantly changed. Note that this has not been the practice historically for Livelihood Zones. Where we have Baseline data for a historic Livelihood Zone where the geography has changed significantly, the Livelihood Explorer will have two different mapped outlines for the Livelihood Zone (see Nigeria Baselines, for example). In some cases, organizations collect Baseline data intending to represent areas smaller than a Livelihood Zone, usually the intersection of a Livelihood Zone and one or more administrative units. In such cases, the Baseline will retain the number of the larger zone and will be appended with a 3-letter geographic identifier. For example, the Niger agropastoral zone crosses the entire country from East to West. No organization has yet assessed the entire zone as a unit with a single BSS. Rather, multiple Baselines collected over many years cover parts of the zone representing one or more administrative departments each (i.e., NE04(DTK), NE04(TAN), NE04(NMT), NE04(TAP)). Livelihood Zone Codes should be structured as CC## or as CC##-ABC (where applicable). * CC is the 2 letter country code (e.g. ML, NE) * ## is the 2 digit zone number (e.g. 04, 15) * ABC is the 3-letter geographic identifier for subzones (e.g. DTK, TAN) ## Methods The **Methods** sheet should contain sufficient information for the BSS to be understood with no need to look up key information in other files. Important standard fields: * Dates of fieldwork * Reference year dates and description * Currency We recommend adding entries for: * **code**: The Livelihood Zone Code (e.g. ML14) is normally part of the filename, but the format is not standard and the filename frequently contains dates or other information. Putting the code as a separate field in the Methods tab will make it system-readable. * **alternate_code**: In some countries, there an alternative Livelihood Zone Code that is used locally. For example, MW01 is referred to within Malawi as CKA. * **name_en** : The agreed name of the Livelihood Zone is a critical attribute, and should be available within the BSS. For the BSS to be loaded into the HEA Database the English name (*name_en)* must be specified even if the BSS was authored in another language. Please follow the naming conventions described in the Practitioners' Guide to HEA, Chapter 2. * **name_fr, name_es, etc.**: There should be separate name entries for each language in which the BSS will be used. Available options are as follows: * French: name_fr * Spanish: name_es * Portuguese: name_pt * Arabic: name_ar * **main_livelihood_category_id**: This is often referred to as the livelihood system within the HEA community. The Primary Livelihood System is important for analyses that process data from multiple BSS. This entry should be one of the following. If an additional category is needed that is not listed below, contact us so we can add it to the metadata. * Agricultural * Agropastoral * Pastoral * Irrigation * Peri_Urban * Urban * Fishing * Mining * Tourism * Other * **description_en, description_fr, etc.**: While the Livelihood Zone name must be relatively succinct for display, the description allows for a paragraph that describes the zone. There should be separate description entries for each language in which the BSS will be used. Description language options are the same as Livelihood Zone name languages. ## Community Names The Community Full Name is constructed from the admin unit name (typically labeled *District* ) and the community name (typically labeled *Village*) in rows 4 and 5 of the WB, Data, Data2, and Data3 worksheets in a BSS. The database uses these names to ensure that the data from the different worksheets can be linked to the correct Community entry in the database. Consequently, the spelling of those names in all places where they appear is critical to successfully recognizing the data. In general, names of administrative areas should be capitalized as proper nouns, not in all capital or all lowercase letters. Ideally, either cell validation or conditional formatting should be used to ensure that the names are accurate, for example, by comparing them to the Form 3 interview results in 'WB'!C4:L5. ## Formatting labels In general, labels (items in column A of WB, Data, Summary, and several other sheets) should be formatted as follows: \[product\]\[season if applicable\] - \[additional identifier if applicable\]: \[attribute\] where each piece is defined as: * Product: The name of the product that data is being reported on in the rowset. * Season: A relevant seasonal identifier. This should always start with the word "season" (or "saison", etc.). For example, season A or season deyr. * Additional identifier: Any additional information that is useful for HEA practitioners. This might be something that: * Further identifies a product, for example a list of fruit types when several are reported in one rowset and fruit is used as the product such as `fruits - orange/mandarin`. * Indicates its use, for example `banana - beer`. * Indicates who is providing a service for example `domestic labor - women`. * Attribute: The type of data being reported in that row. --- language: "en" --- # BSS Production Data ## Crop Production Community level Crop Production data for a crop-producing community is captured in Form 3 and stored in the BSS 'Production' worksheet. This data supports the cross checks for the Livelihood Activity data and expandability/coping data that is contained in the Livelihood Impact Analysis Spreadsheet (LIAS). This data is not ingested from the BSS automatically. Community Crop Production contains the following fields: * **Community or village**: The community that corresponds with this entry. * **Crop type**: The CPCv2.1 code and name of the crop that corresponds with this entry. * **Crop purpose**: Indicates if this is a main food crop or a cash crop. * **Season**: Indicates the primary production Season for the crop. * **Yield with inputs**: The yield of crops that require inputs (e.g., seeds and fertilizer) in the reference period. * **Yield without inputs**: Yield in the reference period without inputs. * **Seed requirement**: Required seed amount in kilograms. * **Crop unit of measure**: The unit used to measure the yield of this crop in this community. * **Land unit of measure**: The unit used to measure land area in this community. ## Livestock Production Community Livestock Production represents animals typically raised by households in a Community, with relevant additional attributes. This data is captured in Form 3 and is stored in the BSS 'Production' worksheet. This data supports the cross checks for the Livelihood Activity data and expandability/coping data that is contained in the LIAS. This data is not ingested from the BSS automatically. Community Livestock Production contains the following fields: * **Wealth Group**: The Wealth Group that corresponds with this entry. * **Livestock type**: The CPCv2.1 code and name of the livestock that corresponds with this entry. * **Birth interval**: The typical number of months between births. * **Wet season lactation period**: The number of days of lactation during the wet season. * **Wet season milk production**: The number of liters produced each day during the wet season. * **Dry season lactation period**: The number of days of lactation during the dry season. * **Dry season milk production**: The number of liters produced each day during the dry season. * **Age at sale**: Age in months at which the animal is typically sold or exchanged. * **Additional attributes**: Any additional attributes that are relevant. --- language: "en" --- # BSS Setup The BSS Setup menu contains administrative screens for adding and managing Source Organizations, Livelihood Zones, Livelihood Zone Baselines, Baseline corrections, and Communities. ## Source Organizations Each Baseline Storage Sheet (BSS) uploaded to the database must have an associated Source Organization. The Source Organization is the organization that produced the BSS and is responsible for any corrections or maintenance needed. The Source Organization is an owner of the Baseline but may not be the only owner of the Baseline. Source Organizations have three fields: * **Name (required)**: A short name for display. * **Full name (required)**: The full name of the organization. * **Description**: Any extra information or detail about the organization that may be relevant. **Example** Name: SC Full name: Save the Children ## Livelihood Zones Each BSS uploaded to the database must have an associated Livelihood Zone. Livelihood Zones may be associated with more than one BSS, but each BSS can only have one Livelihood Zone. Livelihood Zones have the following fields: * **Code (required)**: The primary identifier for the Livelihood Zone. This code should be unique. * **Alternate code**: An alternate identifier for the Livelihood Zone, typically a meaningful code based on the name of the Zone. * **Country (required)**: The country of the Livelihood Zone. * **Name (English) (required)**: An English name for the Livelihood Zone. * **Name (French, Spanish, Portuguese, and Arabic)**: Names in additional languages are optional. * **Description (English, French, Spanish, Portuguese, and Arabic)**: Livelihood Zone descriptions can be added in any available language. See the [Baseline Data Collection section](https://help.fews.net/hea/baseline-data-collection-guidance.md#Livelihood-Zone-Codes) for best practices on developing codes for new Livelihood Zones. ## Livelihood Zone Baselines BSS can be added individually and managed from this screen. Baselines contain the following fields: * **Livelihood Zone (required)**: The Livelihood Zone associated with this Baseline. * **Livelihood Zone alternate code**: Inherited from the chosen Livelihood Zone. * **Country**: Inherited from the chosen Livelihood Zone. * **Name (English, French, Spanish, Portuguese, and Arabic)**: Names for the Livelihood Zone Baseline in available languages. * **Primary Livelihood System (required)**: Primary Livelihood Systems include choices such as cropping, agropastoral, and urban. * **Source Organization (required)**: The organization that produced the BSS and is responsible for any corrections or maintenance needed. If the Source Organization does not exist, a new one can be added from this screen. * **BSS Excel file (required)**: The original BSS file in an .xlsx format with all rows and columns unhidden and iterative calculation setting turned on. * **BSS language**: The language in which the BSS is written. * **Profile reports PDF file (English, French, Spanish, Portuguese, and Arabic)**: PDF files of profile reports associated with the BSS can be added. * **Reference year start date (required)**: The first day of the month in which the reference year begins. You can use the calendar date picker or enter the date in the format YYYY-MM-DD. For example, if the reference year begins in April of 2023, enter a date of April 1, 2023 as 2023-04-01. * **Reference year end date (required)**: The last day of the month in which the reference year ends. You can use the calendar date picker or enter the date in the format YYYY-MM-DD. For example, if the reference year ends in March of 2024, enter a date of March 31, 2024 as 2024-03-31. * **Valid from date**: Enter the first day of the month that the Baseline is valid from. You can use the calendar date picker or enter the date in the format YYYY-MM-DD. For example, if the baseline is valid starting in April of 2023, enter a date of April 1, 2023 as 2023-04-01. The database and Explorer use the Valid from date to differentiate multiple Baselines within a zone. * **Valid to date**: This will usually be left blank for new Baselines and only completed when a Baseline becomes invalid or a new Baseline is available for the Livelihood Zone. Enter the last day of the last month in which the Baseline is valid, typically 10 years from the Valid from date. You can use the calendar date picker or enter the date in the format YYYY-MM-DD. For example, if the baseline is valid through May of 2023 but a new Baseline should be used starting in June 2023, enter a date of May 31, 2023 as 2023-05-31. * **Data collection start date**: The date that the data collection for the Baseline began. Use YYYY-MM-DD format. * **Data collection end date**: The date that the data collection for the Baseline ended. Use YYYY-MM-DD format. * **Publication date**: The date the Baseline was published. Use YYYY-MM-DD format. * **Currency (required)**: The default currency for income and expenditures from the Livelihood Activities within this Baseline. * **Description (English, French, Spanish, Portuguese, and Arabic)**: Livelihood Zone Baseline descriptions can be added in any available language. ### Additional There are some additional fields related to the Baseline that you can choose to view or edit. * **Information about the BSS upload**: This includes content hash, upload date and time, and the file size. This information allows for verification of which file version is loaded in the system. * **Population source and estimate**: The estimated population of the Livelihood Zone during the reference year and the data source for that estimate, e.g. National Bureau of Statistics. Although different organizations may choose to use alternate sources of population data when conducting outcome analysis, it is common for the organization that conducts the Baseline survey to provide a population estimate for the Livelihood Zone at the time of the Baseline. * **Read only BSS info**: This includes the main staple, household size, and survival non-food expenditure for the Poor Wealth Group, along with the cost of annual kcals. This information can assist in troubleshooting the loading of Baselines. ### Livelihood Zone Baseline corrections Existing Baselines will list all associated corrections at the end of the page. New corrections can be added from this screen as well. ## Baseline corrections Individual corrections can be added or managed from this screen. Corrections contain the following fields: * **Livelihood Zone Baseline (required)**: The Baseline that the correction should be applied to. * **Worksheet name (required)**: The tab in the Baseline spreadsheet that needs to be corrected. * **Cell range (required)**: The cell or range of cells that must be corrected (e.g., Q5 or BG4:BJ4). * **Previous value before correction**: The original, incorrect value in the Baseline spreadsheet. Be sure to put the value inside double quotation marks (e.g. "0"). For an empty or null value, use "". * **Corrected value**: The new, correct value for the Baseline spreadsheet. Be sure to put the value inside double quotation marks. For an empty or null value, use "". * **Correction author (required)**: Choose your username. * **Correction comments (required)**: Add a brief description of the error and correction. If there is an associated Jira ticket, mention it here. ## Communities Each Baseline will be associated with several communities. These are the villages and neighborhoods where the Community and Wealth Group interviews occur. Communities contain the following fields: * **Name (required)**: The name of the community (e.g., Alahina). * **Full name (required)**: The name of the Community, plus the parent administrative unit (e.g., Alahina, Keniéba). * **Livelihood Zone Baseline (required)**: Choose an existing Baseline. Communities can not be added without a corresponding Baseline. * **Livelihood Zone alternate code**: Inherited from the chosen Livelihood Zone. * **Country**: Inherited from the chosen Livelihood Zone. * **Aliases**: A list of alternate names and spellings for the community. If adding new aliases, they should be separated by commas. If adding aliases, remove the term "null." * **Interview number**: An interview number or interview code assigned to the Community. * **Community interview date**: The date that the Community Interview (Form 3) was conducted. Use YYYY-MM-DD format. * **Wealth Group interview date**: The date that the Wealth Group Interviews (Form 4) were conducted. Use YYYY-MM-DD format. --- language: "en" --- # BSS WB, Data Sheets This section contains information from the WB, Data, Data2, and Data3 sheets in a BSS. ## Wealth Group Data Wealth Groups are a group of households within a Livelihood Zone with similar capacity to exploit the available food and income options. Typically, rural Livelihood Zones have 4 Wealth Groups: Very poor, Poor, Medium, and Better off. Note that although most Wealth Groups are based on income and assets, i.e. wealth, that is not always the case. For example female-headed households, internally-displaced persons, or refugees may be a surveyed Wealth Group. Wealth Groups are implicit in the BSS 'WB' worksheet in Column B and the 'Data' worksheet in Row 3. Wealth Groups include the following fields: * **Livelihood Zone Baseline**: The Baseline associated with the Wealth Group. * **Community**: The Community associated with the Wealth Group. * **Wealth Group Category**: The Wealth Group Category of the Wealth Group, e.g. Poor or Better off. * **Average Household Size**: The average household size within the Wealth Group. * **Percentage of Households**: Percentage of households in the Community or Livelihood Zone that are in this Wealth Group. There is additional read only information available for assistance in troubleshooting BSS loading: * Percentage of population * Population source * Population estimate * Household annual kcals cost * Survival Threshold as percentage of kcals * Survival Threshold as cash * Livelihoods Protection Threshold as percentage of kcals * Livelihoods Protection Threshold as cash You can also view and add associated Wealth Group Characteristic values and Livelihood Activities from this screen. --- language: "en" --- # Common The items in the Common menu are metadata based on common international standards. ## Countries A Country (or dependent territory or special area of geographical interest) included in ISO 3166. Countries contain the following fields: * **ISO 3166-1 Alpha-2**: The 2 letter ISO 3166 code representing the Country. * **Name**: The name of the Country as displayed in the database. This may differ from the ISO name for ease of use. * **ISO 3166-1 Alpha-3**: The 3 letter ISO 3166 code representing the Country. * **ISO 3166-1 Numeric**: The numeric ISO 3166 code representing the Country. * **ISO English ASCII name**: The name of the Country approved by the ISO 3166 Maintenance Agency with accented characters replaced by their ASCII equivalents. * **ISO English ASCII full name**: The full formal name of the Country approved by the ISO 3166 Maintenance Agency with accented characters replaced by their ASCII equivalents. * **ISO English name**: The name of the Country approved by the ISO 3166 Maintenance Agency. * **ISO English full name**: The full formal name of the Country approved by the ISO 3166 Maintenance Agency. * **ISO French name**: The name in French of the Country approved by the ISO 3166 Maintenance Agency. * **ISO French full name**: The full formal name in French of the Country approved by the ISO 3166 Maintenance Agency. * **ISO Spanish name**: The name in Spanish of the Country approved by the ISO 3166 Maintenance Agency. ## Currencies A monetary unit in common use and included in ISO 4217. Currencies contain the following fields: * **ISO 4217 Alpha-3**: The 3 letter ISO 4217 code representing the Currency. * **ISO 4217 Numeric**: The numeric ISO 4217 code representing the Currency. * **Name**: The ISO 4217 English name of the Currency. ## Products Products are commodities and services classified by a [FEWS NET system that is based on UN CPC v2.1 codes](https://help.fews.net/hea/product-and-service-categorization.md). CPC codes are prefixed with R, L, P or S, a letter indicating whether the Product is Raw agricultural output, Live animals, a Processed product, or a Service. Classified Products include the following fields: * **CPC v2.1**: A code from the FEWS NET classification structure of Products based on version 2.1 of the UN's Central Product Classification rules. * **Description**: A description of the Product. * **Common name**: The common name for the Product. * **Scientific name**: The scientific name for the Product. * **Unit of Measure**: A unit of measure commonly used for the Product. * **Kcals per Unit**: The number of kilocalories the Product contains per the chosen unit of measure. * **Aliases**: A list of alternate names for the Product. * **CPC v2**: A code from the FEWS NET classification structure of Products based on version 2 of the UN's Central Product Classification rules. This aids in cross-referencing products against older standards. * **HS2012**: The 6-digit codes for the Product in the Harmonized Commodity Description and Coding System (HS), stored as XXXX.YY. This aids in cross-referencing products against alternative standards. * **Position and Relative to**: These fields position the Product appropriately within the product hierarchy. For example, wheat is marked with a position of "First child of" relative to "R011 Cereals". ## Units of Measure A unit of measure, such as kilogram, liter, or meter. Unit of Measure contain the following fields: * **Abbreviation**: A short name for the Unit to be displayed in the database. * **Unit type**: The type of Unit. Choices include weight, volume, item, area, yield, percentage and length. * **Aliases**: A list of alternate names for the Unit. * **Description**: Any extra information or detail that is relevant to the Unit of Measure. The Unit of Measure screen also contains conversions for the unit of measure into alternative units. This allows the system to convert any unit contained in the BSS to a standard unit. For example, establishing these BSS-specific units of measure allows *cuerdas* to be displayed as hectares and *coros* as kg. --- language: "en" --- # Data Management * [Loading New Baselines](https://help.fews.net/hea/loading-new-baselines.md) * [Deleting Baselines and Livelihood Zones](https://help.fews.net/hea/deleting-baselines-and-livelihood-zones.md) --- language: "en" --- # Deleting Baselines and Livelihood Zones You can't delete a zone if it has an associated baseline. You can delete a baseline and it will delete everything underneath the baseline. If you want to delete all Livelihood Zones, you have to delete all the baselines first. 1. Go to **BSS Setup** \> **Livelihood Zone Baselines**. 2. Select all baselines and select **Delete** from the Action menu. 3. Confirm you want to delete the baselines. 4. Go to **BSS Setup** \> **Livelihood Zones**. 5. Select all zones and select **Delete** from the Action menu. --- language: "en" --- # Expandability and Coping The Expandability and Coping admin screens contain information about how Wealth Groups respond to hazards and events through coping strategies and expandability. Expandability is the percentage of the quantity sold, income, or expenditure in the reference year of a Livelihood Strategy in a response scenario. It is stored on the BSS 'Exp factors' worksheet. Coping is the capacity of households to diversify and expand access to various sources of food and income, and thus to cope with a specified hazard. It is captured in the 'Coping' Sheet of the BSS whenever available. Notably the Coping sheet is not found in most BSSs. In addition, at times in the literature, Coping seems used synonymously to Expandability. However, it seems suitable to model the data in 'Coping' sheet; see Practitioners' guide page 137. Coping and Expandability are better analyzed during the outcome analysis stage, by taking into account the exact Hazard/Shock. These items are not currently ingested from the BSSs but are a part of the model. --- language: "en" --- # Hazards and Events The Hazards and Events admin screens contain data about annual and seasonal production and how hazards and events can affect that production. This information is stored on the BSS 'Timeline' worksheet based on responses to Form 3. It is not yet being ingested into the Livelihoods Explorer but is a part of the model. ## Annual/Seasonal Production Performances This screen contains relative Production Performance experienced in a specific year or season. Most BSSs contain the performance for the year as a whole and will use a 'Main' or 'Annual' season. However, in Livelihood Zones with bimodal rainfall we can capture performance for each season individually. Fields include: * **Community or village**: The community or village this Production Performance is associated with. * **Performance year start date**: The first day of the month of the start month in the performance year. * **Performance year end date**: The last day of the month of the end month in the performance year. * **Seasonal performance**: Rating of the Seasonal Production Performance from Very poor (1) to Very good (5). ## Hazards A shock such as drought, flood, conflict or market disruption which is likely to have an impact on people's livelihoods. Hazards can be chronic (every year) or periodic (not every year). Fields include: * **Community or village**: The community or village this Hazard is associated with. * **Chronic or periodic**: Indicates if this Hazard is chronic or periodic. * **Ranking**: Indicates how important the Hazard is. * **Hazard category**: The type of Hazard, for example pests, flooding, or livestock disease. * **Description of Event(s) and/or Response(s)**: Additional context or notes on the Hazard can be included here. ## Events A shock such as drought, flood, conflict or market disruption which happened in a recent year prior to the reference year. Fields include: * **Community or village**: The community or village this Event is associated with. * **Event year start date**: The first day of the month of the start month in the Event year. * **Event year end date**: The last day of the month of the end month in the Event year. * **Description of Event(s) and/or Response(s)**: Additional context or notes on the Event can be included here. --- language: "en" --- # Key Concepts The Livelihoods Explorer Database uses HEA terminology in specific ways. In particular, the following terms are used in ways that may not be immediately obvious to an HEA practitioner. [See the Metadata Standards page for more.](https://help.fews.net/hea/metadata-standards.md) ## Primary Livelihood Systems The dominant patterns of livelihoods identified in the development of a Livelihood Zone map, for example pastoralism, fisheries, or irrigated cropping, are called **Primary** **Livelihood Systems.**These are often called production systems by HEA practitioners. ## Wealth Groups **Wealth Group Categories** allow for the comparison of the local definitions of Wealth Groups across all BSS. These are standardized from the BSS 'WB' worksheet in Column B and the 'Data' worksheet in Row 3. Wealth Categories include options such as very poor, poor, medium, and better off. A **Wealth Group** is a group of households belonging to a specific Wealth Group Category in a specific community or attributed to a Baseline summary. **Wealth Group Characteristics** are potential productive characteristics of a Wealth Group, such as number of children at school, type of housing, or owning a computer. A **Wealth Group Characteristic Value** is the value assigned to a Wealth Characteristics for a specific Wealth Group in a BSS. These values may be numbers or words/short phrases. **Example** **Wealth Group Category**: Poor **Wealth Group**: The Poor households in a specific community in BF01. This can also refer to all poor households in BF01. **Wealth Group Characteristic**: Land area cultivated **Wealth Group Characteristic Value**: 5.5 hectares cultivated by the average poor household in a specific community of, or all of, BF01. ## Livelihood Strategies and Activities **Livelihood Strategy Types** include things like milk production, crop production, food purchase, relief aid, and wild food gathering. [++See a full list++](https://help.fews.net/lex/livelihoods-explorer-glossary.md#LST). They are used to categorize Livelihood Strategies for ease of comparison. A **Livelihood Strategy** is one of a set of options used by households in a Livelihood Zone to obtain food and cash income and acquire the items needed to live. When a Livelihood Strategy is used by a specific Wealth Group, it is called a **Livelihood Activity**. **Example** **Livelihood Strategy Type**: Food Purchase **Livelihood Strategy**: The purchase of husked rice in Livelihood Zone HT02 (2014) **Livelihood Activity**: The amount of husked rice purchased by the very poor Wealth Group in Livelihood Zone HT02 (2014) ## Seasons A Country must have a set of Season definitions set up in the database before the pipeline will be able to read data for the Country. Any Seasons referenced within the BSS must have an accompanying definition. Each definition should identify: * **Geography, if applicable**: Some countries have different seasonal patterns in different parts of the country or for different primary livelihood systems. In this case, the season definition must also be associated with the relevant livelihood zones or other geographic boundaries. * **Purpose**: For each Country (or Country + Geography if there are multiple seasonal patterns) there must be three sets of Seasons differentiated by purpose: Milk Production, Butter Production, and null. Livelihood Strategy Types other than Milk Production or Butter Production will use the null purpose set of Seasons. Each Purpose must contain a set of entries that includes all months of the year without repeating or overlapping months. * **Type of season**: Harvest, post-harvest, lean, etc. * **Typical start and end**: The start and end of the Season in months or number of days from the start of the year. * **Milking cohorts, if applicable**: For milk production, identify whether the Seasons are for multiple cohorts of animals or early and late milking Seasons for a single cohort. * **Aliases:** A Season may be referenced in different ways within a Baseline or within a Country (i.e., Season 1 or Season A). These must be specified as aliases for the relevant Season Purposes for the pipeline to read those Seasons. ### Example Democratic Republic of the Congo has the following seasons: | **Geography** | **Purpose** | **Type** | **Start and end** | |----------------------------------------------------------------|-------------------|-------------------------|--------------------| | Democratic Republic of the Congo, Eastern highlands | | Lean | October-November | | Democratic Republic of the Congo, Eastern highlands | | Harvest (Season A) | December-March | | Democratic Republic of the Congo, Eastern highlands | | Post harvest (Season A) | April-May | | Democratic Republic of the Congo, Eastern highlands | | Harvest (Season B) | June-September | | Democratic Republic of the Congo, Eastern highlands | Milk Production | Peak | September-April | | Democratic Republic of the Congo, Eastern highlands | Milk Production | Dry | May-August | | Democratic Republic of the Congo, Eastern highlands | Butter Production | Peak | September-April | | Democratic Republic of the Congo, Eastern highlands Butter Dry | Butter Production | Dry | May-August | | Democratic Republic of the Congo, Southern Unimodal | | Lean | March-April | | Democratic Republic of the Congo, Southern Unimodal | | Harvest | May-June | | Democratic Republic of the Congo, Southern Unimodal | | Post harvest | July-February | | Democratic Republic of the Congo, Southern Unimodal | Milk Production | Peak | October-April | | Democratic Republic of the Congo, Southern Unimodal | Milk Production | Dry | May-September | | Democratic Republic of the Congo, Southern Unimodal | Butter Production | Peak | October-April | | Democratic Republic of the Congo, Southern Unimodal | Butter Production | Dry | May-September | | Democratic Republic of the Congo, Central | | Harvest A | June-August | | Democratic Republic of the Congo, Central | | Post harvest A | September | | Democratic Republic of the Congo, Central | | Lean | October-November | | Democratic Republic of the Congo, Central | | Harvest B | December-February | | Democratic Republic of the Congo, Central | | Post harvest B | March-May | | Democratic Republic of the Congo, Central | Milk Production | Peak | September-December | | Democratic Republic of the Congo, Central | Milk Production | Dry | January-August | | Democratic Republic of the Congo, Central | Butter Production | Peak | September-December | | Democratic Republic of the Congo, Central | Butter Production | Dry | January-August | --- language: "en" --- # Labels Labels are used to match information from the Baseline Storage Sheets to metadata in the database. ## Wealth Characteristic Labels Wealth Characteristic Labels are used by the WealthCharacteristicValue ingestion pipeline to determine the attributes for a given row of Column A of the 'WB' worksheet in a BSS. Wealth Characteristic Labels contain the following fields: * **Wealth Characteristic Label**: This field contains the label from Column A of the WB worksheet in a BSS. * **Status**: There are three status options: * Complete: The label has been associated with a Wealth Characteristic and can be ingested. * Under discussion: Discussion or investigation is needed to determine if this can be ingested or if it needs a correction. It may need a new Wealth Characteristic or it may be unclear what the associated Wealth Characteristic should be. * Correct the BSS: Discussion or investigation has led to the conclusion that a correction is needed. * **Wealth Characteristic**: The Wealth Characteristic that corresponds with this Label, if applicable. * **Product**: The product associated with this Wealth Characteristic Label, if applicable. * **Unit of Measure**: The unit of measure associated with this Wealth Characteristic Label, if applicable. * **Notes**: Any notes explaining the status or choice of associated Wealth Characteristic should be entered here. **Example 1** **Wealth Characteristic Label**: autre: camelin **Status** : Complete *This status was chosen because there is an easily identifiable corresponding Wealth Characteristic.* **Wealth Characteristic**: number owned **Product**: L02121 Camels **Unit of measure**: - **Notes**: - **Example 2** **Wealth Characteristic Label**: donkeys/horses (no. owned) **Status** : Under discussion *This status was chosen because there is not a corresponding Wealth Characteristic but there should be.* **Wealth Characteristic**: number owned **Product**: - **Unit of measure**: - **Notes**: Need to add horses/donkeys ## Activity Labels Activity Labels are pulled from Column A of the 'Data', 'Data2' or 'Data3' worksheets in a BSS. They are used for the LivelihoodStrategy and LivelihoodActivity data ingestion pipelines to determine the attributes for the LivelihoodStrategy and/or LivelihoodActivity for a given row in a BSS. Activity Label fields include: * **Activity Label:**This field contains an item from Column A of the 'Data', 'Data2' or 'Data3' worksheets in a BSS. * **Activity Type:** The tab or sheet in the BSS of the Livelihood Activity that corresponds to this label. This could be a general Livelihood Activity in the 'Data' worksheet, an *Other Cash Income* activity from the 'Data2' worksheet, or a *Wild Foods* , *Fishing* , or *Hunting* activity from the 'Data3' worksheet. * **Status:**There are five status options: * Processed by regular expression: The Label has been associated with a Wealth Characteristic via a regular expression and can be ingested. * Override automatically recognized metadata: The Label has been associated with a Wealth Characteristic via an override and can be ingested. * Under discussion: Discussion or investigation is needed to determine if this can be ingested or if it needs a correction. It may need a new Wealth Characteristic or it may be unclear what the associated Wealth Characteristic should be. * Correct the BSS: Discussion or investigation has led to the conclusion that a correction is needed. * Ignore this label and associated data in the row: The information in this row should not be ingested. * **Is Start?:** Select the checkbox to indicate if this Activity Label marks the start of a new Livelihood Strategy rowset in the BSS. For example, *Sorghum Deyr: kg produced* indicates the start of a new Livelihood Strategy. * **Strategy Type:**The type of Livelihood Strategy, such as crop production or wild food gathering. * **Product:**The Product associated with this Activity Label, if applicable. All Livelihood Activity IsStart labels must have either a product or additional identifier and an attribute. * **Unit of Measure:**The unit of measure associated with this Activity Label, if applicable. * **Currency:**The currency associated with this Activity Label, if applicable. * **Season:**The Season associated with this Activity Label, if applicable. * **Additional Identifier** **:**Additional text identifying the Activity Label, if applicable. * **Attribute** **:** Additional attributes from the BSS for the associated Livelihood Activity, if applicable. This describes the type of information being stored and will correspond to the attribute column in the ActivityLabel tab in the Reference Data workbook. For example, *Sorghum Deyr: kg produced* maps to the `quantity_produced` attribute. Possible attributes include: * milking_animals * lactation_days * daily_production * quantity_produced * quantity_sold * price * income * type_of_milk_sold_or_other_uses * quantity_other_uses * percentage_kcals * animals_slaughtered * carcass_weight * purchase_price * sales_price * product__kcals_per_unit * times_per_month * months_per_year * expenditure * times_per_year * unit_multiple * people_per_household * payment_per_time * percentage_sold_slaughtered * reference_year_percentage_sold * percentage_milk_sold * quantity_produced_or_purchased * quantity_purchased * number_of_local_measures * name_of_local_measure * product__name * percentage_monthly_kcals * number_of_children * activity_notes * no_of_weeks * **Notes:**Any notes explaining the status or choice of associated Activity or Strategy type should be entered here. --- language: "en" --- # Livelihood Activities The following recommendations for data entry pertain to the WB and Data sheets in a BSS. ## Adding and removing rows and columns One of the benefits of using a database for data collection and analysis is that you do not have to worry about adding rows and columns to your spreadsheet as they can not break anything. Therefore, we recommend adding rows and columns where needed in order to keep data tidy in the spreadsheet. For example, if a section only has space for 3 items but you have 5 items to record, you do not need to make the data fit into 3 sets of rows. In fact, forcing the data to fit will make ingestion harder. Instead, add two additional sets of rows to accommodate all of your data. This also means that you can have rows for both individual and summary data. **Example** Each village in a BSS produces a different vegetable: squash, tomatoes, chilies, etc. Traditionally, they might all fall under one set of rows with the label `mixed vegetable production`. However, now the best approach is to list each product in a different set of rows. If a summary of mixed vegetable production is still desired, it can be included in its own set of rows containing only the summary data and no community-level data. Duplicate rows should be removed. The pipeline will read only 1 product per Livelihood Activity per BSS. **Example** In this example, rows 632-3 are repeated in rows 634-5. An entry for labor migration will be created for rows 632 and 633. Since the pipeline cannot create a second entry for the same Livelihood Activity, the kcals, payment per time, and income in rows 636 - 638 are orphaned and cannot be stored. Ideally, rows 634-5 are deleted to prevent this issue. ![image-20260423-192630.png](https://help.fews.net/__attachments/a_a8fa3fe16b40516d89c218c6d1956896c12b1d472df5943a9ada289bed93ffb3/image-20260423-192630.png?cb=be0f002d2f934d5d83c0ad1eece68df4) ## IDPs While it is rare for one BSS to contain data for both IDPs and the local community, it does happen on occasion. In this instance, use a single WB sheet, add rows/columns as needed and rename the wealth categories in column B. Likewise, use a single data sheet, add rows/columns as needed, and rename the wealth categories at the top, usually in row 3. The labels should make it clear which wealth groups are IDPs. For example, a French BSS would use TP for the very poor in the community and TP-IDP for the very poor in the displaced population. ## Column A The labels in column A are used to tell the data ingestion pipeline what kind of information is stored in that row of the spreadsheet. Therefore, it is important to understand the patterns that the pipeline is looking for. ### Rowsets In general, the start of a new rowset (i.e. a full set of rows with data about a single Livelihood Activity) should have a label in column A structured as *Product: Attribute* where *Product* is a the name of the product that data is being reported on in the rowset and *Attribute* is the type of data being reported in that row. **Example** These are two examples from the same BSS. Each image shows one rowset where the first row is correctly labeled with the *Product: Attribute* format. ![Rows 287 - 293 of a BSS. The first row is in bold and has a green background to signify it is the start of a new rowset. It is labeled Sunflower kg produced.](https://help.fews.net/__attachments/a_0e489eb73e65d7ab2e9b1f64eb5004790a1edb35dd47abe4c6c2a17a0b2c328d/2026-05-26_13-13-53.668.png?cb=26e187b35167697b394c17e8c7ca47c5) This rowset pertains to the product Sunflowers. The first row should contain numerical data about the quantity of kg produced. ![Rows 304 - 313 of a BSS. The first row is in bold and has a green background to signify it is the start of a new rowset. It is labeled Sweet potatoes no local meas.](https://help.fews.net/__attachments/a_dc0aa94d80ccb663ae4c4a807ebeee87469059a481900d22fa75baeceaf96772/2026-05-26_13-14-06.358.png?cb=37c51141ee882f763a8c352715e993b8) This rowset pertains to the product Sweet potatoes. The first row should contain numerical data about the number of local measures (produced). #### Use standardized product/crop names The labels used in column A of the WB and Data sheets should use standardized and specific names and/or product codes where possible. The Livelihoods database uses a [set of product codes](https://livelihoodsdev.fews.net/api/classifiedproduct.html) based on [CPC v2.1](https://unstats.un.org/unsd/classifications/unsdclassifications/cpcv21.pdf). Using a name and/or code from this list ensures that the correct item is associated with that data in the database. **Example**: Cocoyam Cocoyam can refer to a number of items including taro and yautia. Instead of using `cocoyam` in column A, use a more specific identifier such as `01550 Taro` or `01591 Yautia`. #### Distinguish between raw products and processed products where needed Some products require distinctions between raw product and product that is consumed. Each code begins with a one-character alpha-code prefix that FEWS NET uses to split its product and service codes into 4 distinct sub-groups. 1. R: raw, un-processed agricultural product 2. L: animal/livestock product 3. P: manufactured or processed product 4. S: service product **Example**: Coffee and Rice * Coffee: Coffee for crop production (e.g., coffee cherry, green coffee bean) uses R01610 and differs from coffee for expenditure/purchase (e.g., roasted whole or ground bean) which uses P23911 - P23914. * Rice: Paddy rice (referring to what is produced) uses an R code and differs from husked rice (referring to what is purchased), which uses a P code. #### Links to other cells should not be used in lieu of a name Links are not a good substitute for specific names as they are not readable by the database and can cause errors. **Example**: Main cereal In the BSS pictured below, column A is labeled as `Main cereal - Belg: kg produced` and is linked to another cell in the spreadsheet. This should instead use a specific product name/code and attribute, such as `Maize:kg produced`. ![Selection from a BSS of Main cereal - Belg label.](https://help.fews.net/__attachments/a_76b1936497ce41b987c647fa1e983b2bb6610c36d4baf49283ca00ee937489ef/image-20250926-205043.png?cb=1bd155a56a43b210beed2bebe56ef231) ### Column A should explicitly state the expected data values for the row If data is expected in the row, then the label in column A should explicitly state what data is expected. **Example**: Bambara nuts If the expected data is the number of local units purchased, use *bambara nuts: no. local meas.* If the expected data is the amount produced, use *bambara nuts: kg produced.* This avoids the ambiguity inherent in labels such as *Other Crop Type: bambara nuts*, where it is unclear whether the values represent the amount in kg, the number of local measures, or just a label where no additional data is expected. ### Metadata should only be in column A Don't put information describing the livelihood strategy (metadata) in the per-community columns (column B onwards). Within each rowset, the numbers for each community must refer to the same Livelihood Strategy. If the strategy refers to a particular type of food, then it should be the label in Column A, not in that row in Column B. For example, the following data: | **WEALTH GROUP** | V.Poor | V.Poor | V.Poor | |------------------------------------|----------|--------|----------| | **WILD FOODS** | termites | | termites | | **Wild food type 1 - kg gathered** | 2 | | 10 | Should properly be entered as: | **WEALTH GROUP** | V.Poor | V.Poor | V.Poor | |----------------------------|--------|--------|--------| | **WILD FOODS** | | | | | **Termites - kg gathered** | 2 | | 10 | Notice that "termites" has been moved from the community cells (columns B and D) to the label in column A. If the communities in the BSS gathered several different types of wild food, a row would be added for each food. ### Data should not be stored in label rows Do not put data values, including 0, in columns B onward on rows where the value in column A is a heading or other label not associated with expected data (e.g. the Wild Foods row in the example above). The BSS ingestion will refuse to load a BSS containing data in unexpected locations to ensure that no important data is lost. This sometimes happens when the previous Livelihood Activity contained a 0 entry for many rows and they have been copied down one row too far, into the heading for the next section of the BSS. ## Use zero purposefully Only use zero when there is an opportunity for earning money, kcal, etc. If there is no opportunity, leave the cell blank. For example, labor should be left blank for kcal unless the field contains kcals from payment in kind. There is one exception to this recommendation. In general, if the only values entered from any community for an activity are zero, it is better to leave all of the community values blank for that activity so that the system does not create a product for which the only data is zero. **Example** If all of the communities in a BSS would report 0 for *Other crops - kg produced* , it would be preferable to leave those entries null (blank) rather than create the baseline entry for *Other crops - kg produced* with only entries of 0 kg. ## Green consumption Green consumption should be reported in months, not weeks. Note that there are 4.3 weeks in a month, according to the HEA field guide, so 1 week = 1/4.3 months or .23 months. Add rows to the green consumption section if necessary to capture green consumption of each crop individually. In keeping with the spirit of the CPC 2.1, crops consumed green will use a different product code than the main crop. For example, regular maize is R01122, but green maize is R01290HA. ## Payment in kind When documenting payment in kind, there are two types of products involved: * The labor that is performed is the `product`. * The item that was provided in exchange for the labor is the `payment_product.` The `kcals per unit` for the `payment_product` are used to calculate/validate the kcals provided by the Livelihood Activity. The first row of the Livelihood Activity in the BSS should contain the `product`. The `payment_per_time` label should specify the exact food item that was provided. Example labels for column A are as follows: | **English Label** | **French Label** | **Notes** | |----------------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Pre-Harvest Labor: weeding | Travail Pre-Récolte: sarclage | The product should be in the label in column A, not in the per Community / Wealth Group responses in columns B onwards. The label should contain only one separator (typically a colon) with the first part being the product, such as Pre-Harvest Labor, and the second part being an attribute, such as weeding or number of people per household. | | no. people per HH | nbr personnes par ménage | | | no. times per month | nbr fois par mois | | | no. months | nbr mois | | | payment in kg per time (sorghum) | paiement en kg par fois (sorgho) | Use the common name for a specific product, such as *sorghum* or *maize* , rather than a generic term such as *grain*. | | kcals (%) | kcals (%) | | --- language: "en" --- # Loading a Single Baseline via the Admin Screen To load a single file, use the Livelihood Explorer admin screens instead of the Dagster pipelines. 1. On a desktop copy of the BSS, enable editing and set calculations to automatic. 2. Open the admin screen: 3. Ensure Source Organization and Livelihood Zone exist. 1. Source Organization should already exist. If not, use the guidance on the [BSS Setup](https://help.fews.net/hea/bss-setup.md) page. 2. Livelihood Zone: Be sure to enter a code, country, and name. Enter a description of the Livelihood Zone if available. Save. 4. Add seasons 1. Learn more about adding [Season definitions](https://help.fews.net/hea/metadata.md#Seasons). 5. Add Livelihood Zone Baseline 1. Choose the Livelihood Zone code. 2. Add name. 3. Choose the Primary Livelihood System. 4. Choose Source organization. 5. Choose file \> select your BSS file. 6. Choose BSS language. 7. Upload profile report if available. This can be added later. 8. Choose the start and end date for the reference year. 9. Add a valid from date. Leave the valid to date blank. 10. Choose the Data Collection start and end dates. 11. Add a publication date if available. 12. Choose the currency. 13. Add descriptions in any languages available. 14. Click save. 6. Tell the Hub it has been uploaded so we can run the pipelines manually. It may take up to 10 minutes for the partition to appear in the pipeline. In Dagster, the Hub will complete the following steps: 1. Materialize missing partitions. 2. Run imported_communities for relevant partition. 3. imported_baseline - run upstream all that haven't been run (depth of 4) for relevant partition - make sure activity groups are included, back to corrected files 4. Review unrecognized_labels to see if there are any missing. 5. At each step, check for errors and needed corrections and create tickets as needed. --- language: "en" --- # Loading New Baselines New Baseline Storage Sheets (BSS) can be loaded in to the Livelihoods Explorer individually using database administration screens or in bulk using the Dagster pipelines. This section includes information on: * [Loading a Single Baseline via the Admin Screen](https://help.fews.net/hea/loading-a-single-baseline-via-the-admin-screen.md) * [Quality Assurance for BSS Loading](https://help.fews.net/hea/quality-assurance-for-bss-loading.md) --- language: "en" --- # Market Prices ## Markets A Market represents a geographic point where Market Prices are collected. Markets contain the following fields: * **Code** : This field should include a unique identifier for the Market, such as the [FNID](https://help.fews.net/fdw/fews-net-ids-fnids.md). * **Name**: The name of the Market in all available languages. * **Aliases**: A list of alternate names or spellings for the Market. * **Country**: The country in which the Market resides. * **Description**: Any extra information or detail that is relevant about the Market, in all available languages. ## Market Prices This includes Prices gathered in Form 3 and stored on the BSS Prices worksheet. These Prices are not automatically ingested from the BSS. Market Prices contain the following fields: * **Community or village**: The community or village where this Market Price was collected. * **Product**: The product associated with the Price. * **Currency**: The currency of the reported Price. * **Market**: The market where the Price was observed. * **Description**: Any extra information or relevant detail about the product or Price. * **Low price**: The lowest recorded Price. * **Low price start day**: The numeric day of the year when the lowest Price starts. The system will automatically convert the first day of the start month in the BSS to a day of the year. * **Low price end day**: The numeric day of the year when the lowest Price ends. The system will automatically convert the last day of the end month in the BSS to a day of the year. * **High price**: The highest recorded Price. * **High price start day**: The numeric day of the year when the highest Price usually starts. * **High price end day**: The numeric day of the year when the highest Price usually ends. * **Unit of measure**: The unit of measure the product is reported in for Price reasons. For example, if a product is $3 per liter, this field would contain liter. Note that Price start and end dates are stored in days, even though the BSS records this information in months. The system automatically converts months into a numeric day of the year by using the first day in a start month and the last day in an end month. This is a measure taken to allow for more granular data collection in the future iterations of collection tools. --- language: "en" --- # Metadata Management To effectively manage metadata within the HEA Database, the following practices are implemented: * **Data Entry and Validation:** All metadata entries are subject to validation against the respective standards before inclusion in the database. This ensures accuracy and consistency of the data. * **Data Ownership**: Each metadata item has an Owner and designated Editors. The Owner is ultimately responsible for data quality for that metadata item. This approach ensures that someone has a full picture of the individual metadata items and can avoid duplicates, etc. * **Regular Updates**: Metadata standards, especially wealth characteristics, are periodically reviewed and updated to reflect changes in economic practices and data classification standards. * **Training and Documentation:** Personnel involved in metadata management are provided with training and detailed documentation on [metadata standards](https://help.fews.net/hea/metadata-standards.md). * **Quality Assurance:** Regular audits of the metadata are conducted to ensure adherence to standards and to identify and correct any inconsistencies. --- language: "en" --- # Metadata Standards To maintain consistency, accuracy, and global interoperability, the HEA Database adheres to international standards for metadata coding, where possible. Below are the specific metadata types and the standards applied to each type of reference data: ## Country **Standard**: ISO 3166 **Description**: Countries are identified using the ISO 3166 standard, which provides codes for the names of countries, dependent territories, and special areas of geographical interest. The database uses the ISO standard names for countries, and uses the iso3166a2 code as the short identifier. The current list of countries is accurate, and changes to the list are rare. The FEWS NET Hub will keep the list up to date from the ISO-published master list. ## Currency **Standard**: ISO 4217 **Description**: Currencies are classified according to the ISO 4217 standard, which assigns three-letter codes to each currency. The current list of currencies is accurate, and changes to the list are rare. The FEWS NET Hub will keep the list up to date from the ISO-published master list. ## Livelihood Activity **Standard**: Custom taxonomy developed specifically for the HEA Database, informed by local knowledge and existing classifications where possible. **Description**: Livelihood Activity records mostly contain pointers to other metadata (season, product, unit of measure, etc.). Livelihood Activities typically use the classified product that is used for equivalent Market Price data in the FEWS NET Data Warehouse: * **Livestock Sale** activities use the classified product for the animal, e.g. *L02123: Goats.* If the BSS includes a designation of local or export quality animals, more specific classified products will be used rather than an additional identifier. For example, *Pig sales - local: no. sold* uses the classified product *L02140HA: Swine / pigs, local quality* and *Vente de moutons - locale: nb venduss* uses the classified product *L02122AP: Sheep, local quality*. * **Meat Production** activities use the classified products for the meat product, e.g. *P21116: Meat of goat, fresh or chilled.* * **Milk Production** activities use the classified products for the raw milk, e.g. *P02292: Raw milk of goats*. * **Butter Production** activities use the classified products for the specific butter, e.g. *P22249HC: Butter and other fats and oils derived from milk of goats*. * **Crop Production** activities use the classified products for the non-seed crop, e.g. *R01122: Maize (corn), other* . Green consumption is also a Crop Production activity, using specific classified products for the green crop, e.g. *R01290HA: Green corn (maize)*. ## Livelihood Strategy Type **Standard**: Custom taxonomy developed specifically for the HEA Database, informed by local knowledge and existing classifications where possible. **Description**: Livelihood Strategies are one of a set of options used by households in a Livelihood Zone to obtain food and cash income and acquire the items needed to live. Livelihood Strategy records mostly contain pointers to other metadata (Season, Product, Unit Of Measure, etc.). Livelihood Strategies are categorized by type to allow for easy aggregation and comparison of Livelihood Strategies and Activities. They include things like milk production, crop production, food purchase, relief aid, and wild food gathering. [++See a full list++](https://help.fews.net/lex/livelihoods-explorer-glossary.md#LST). Strategy Types are defined based on categories used in the BSS, with additions where necessary. Livelihood Strategies use a similar Classified Product list to that used for equivalent Market Price data in the FEWS NET Data Warehouse: * **Livestock Sale** strategies use the Classified Product for the animal, e.g. *L02123: Goats.* If the BSS includes a designation of local or export quality animals, more specific Classified Products will be used rather than an Additional Identifier. For example, *Pig sales - local: no. sold* uses the Classified Product *L02140HA: Swine / pigs, local quality* and *Vente de moutons - locale: nb venduss* uses the Classified Product *L02122AP: Sheep, local quality*. * **Meat Production** strategies use the Classified Product for the meat product, e.g. *P21116: Meat of goat, fresh or chilled.* * **Milk Production** strategies use the Classified Product for the raw milk, e.g. *P02292: Raw milk of goats*. * **Butter Production** strategies use the Classified Product for the specific butter, e.g. *P22249HC: Butter and other fats and oils derived from milk of goats*. * **Crop Production** strategies use the Classified Product for the non-seed crop, e.g. *R01122: Maize (corn), other* . Green consumption is also a Crop Production activity, using specific Classified Products for the green crop, e.g. *R01290HA: Green corn (maize)*. ## Primary Livelihood System **Standard**: Custom taxonomy developed specifically for the HEA Database, informed by local knowledge and existing classifications where possible. **Description**: This metadata type categorizes the primary Livelihood Zone System types, such as Pastoral, Rainfed, Agropastoral, etc. It includes but is not limited to pastoral and agricultural categories. Primary Livelihood Systems are defined based on regional economic activities and ecological characteristics. ## Product **Standard**: Central Product Classification (CPC) Version 2.1 **Description**: Products are categorized using the CPC Version 2.1, facilitating uniform classification of goods and services. The leaf node of the main CPC hierarchy is used where that is appropriately specific. Where the main CPC hierarchy is not sufficiently specific then a leaf node from the FEWS NET Data Warehouse (FDW) is used instead, if one exists. These nodes contain a 2-letter suffix to the main CPC code, typically starting with A, e.g. *P21393AA: Cassava Chips* . If FDW does not contain a suitable product, then a new leaf node with a suffix beginning with H is created in the HEA database, e.g. *R01219HA: Other leafy or stem vegetables, dark green*. The HEA database uses version 2.1 of the CPC hierarchy, as recommended by FSIN. Note that currently FDW is using version 2.0, so there are some discrepancies. The HEA database stores the \`cpcv2\` as a multi-valued correspondence code that matches the value in FDW. The primary key in the HEA database is just called \`cpc\`. The FEWS NET Hub will create new Products on request. ## Season **Standard**: Custom taxonomy developed specifically for the HEA Database, based on similar information stored in FDW. **Description**: A division of the year, marked by changes in weather, ecology, and associated Livelihood Zone Activities for income generation. The Seasons for a Country are organized such that the set of Seasons covers a 12 month period with each month assigned to one Season and no Seasons sharing a month. Aliases are used to find a Season that corresponds information in the Baseline Storage Sheets (BSS). Any Seasons referenced within the BSS should have an accompanying definition. * Each definition should identify: * **Purpose**: Milk Production, Butter Production, null, etc. Each Purpose must contain a set of entries that includes all months of the year. * **Type of season**: Harvest, post-harvest, lean, etc. * **Typical start and end**: The start and end of the season in months or number of days from the start of the year * **Milking cohorts, if applicable**: For milk production, identify whether the Seasons are for multiple cohorts of animals or early and late milking Seasons for a single cohort. * **Geography, if applicable**: Some countries have multiple different Seasons in different parts of the country or for different types of livelihood. In this case, the Season definition must also be associated with the relevant Livelihood Zones or other geographic boundaries. * Examples: * Season 1: Cropping, main harvest season; October-December * Season 2: Milking, second cohort; April-June ## Source Organization **Standard**: Centrally maintained list **Description**: There are currently only two approved Source Organizations: FEWS NET and Save the Children. The FEWS NET Hub controls this metadata item because changes to it typically have implications for user accounts and permissions management. ## Wealth Group Category **Standard**: Custom taxonomy developed specifically for the HEA Database, informed by local knowledge and existing classifications where possible. **Description**: Local definitions of Wealth Groups, common to all Baseline Studies in a Livelihood Zone (LHZ), such as Very poor, Poor, Medium, Better off. These categories help in understanding the economic stratification within communities. Although this is a custom taxonomy, it contains only a small number of items, and changes to the list are rare. Therefore it is appropriate for the FEWS NET Hub to control changes to the list, particularly because they may have impacts on the application code. ## Wealth Group Characteristic **Standard**: Custom taxonomy developed specifically for the HEA Database, informed by local knowledge and existing classifications where possible. **Description**: Characteristics of a Wealth Group, such as "Number of children at school", livestock ownership, land size, etc. These characteristics provide detailed insights into the assets and vulnerabilities of different wealth groups. Livestock Wealth Group Characteristics use classified products to enable easy matching against other data such as market prices. Trees do not use classified products and are separate Wealth Characteristics. This is because the existing hierarchy does not include trees as an obvious branch, the Baseline Surveys are not always specific about the types of tree owned (e.g. *trees* , or *fruit trees*), and trees are closer to assets like oxcarts or motorcycles than they are to products and services. Fruit from trees, e.g. Avocados or Mangoes have corresponding classified products which are used in the Crop Production Livelihood Activities to capture income from the sale of fruit and calories from consumption of it. The fruit can be cross-referenced with other CPC-coded data, most importantly current price data. The Hub will create new items on this list as required to enable the BSS to be fully recognized. The Hub will conduct periodic reviews to ensure that the metadata standards are being followed. The Hub will provide recommendations on new items on request. Many of the BSSs use wealth characteristic labels on the 'WB' worksheet like "Other (Fishing Gear)" or "Other (Fruit Trees)". They also contain a mixture of singular (television, motorcycle, kiosk) and plural (hoes, avocado trees, oxcarts). The Wealth Group Characteristic metadata will be standardized to use the singular version, without the "Other". I.e. if the BSS has the label "Other (Fruit Trees)", the corresponding Wealth Characteristic will be "Fruit Tree". The list of aliases for the Wealth Characteristic will contain all of the variations found in BSSs that contain that Characteristic, e.g. `name = 'Fruit Tree'` `aliases = [` ` 'fruit trees',` ` 'other fruit trees - type',` ` 'tree for fruits (mangoes, orange, jack, avocado etc)'` `]` --- language: "en" --- # Product and Service Categorization This page documents the principles used as a basis for categorization and any decisions made about coding products and services that are not straightforward. * **Purpose of Product Description:** The product description should enable practitioners to understand the impact of shocks on livelihoods. This requires descriptions that are specific enough to separate out different things if a shock affects them differently. * **Migration Coding:** Use an HEA code for migration that crosses all labor categories rather than being a separate category, expressing that it could be any type of work. * **Domestic Services Coding:** Due to the confusing language in the CPC 2.1, it was decided to make "domestic services" an HEA code (98HA) to aggregate various individual domestic services. * **Money Lending/Credit Coding:** For financial transactions like money lending and credit, it was decided to use separate HEA codes (HA, HB, HC) to differentiate between money lending as a livelihood activity, credit received (cash management), and loan repayment as an expenditure. Generally, products and services are handled in LEX the same way they are [handled in the FDW](https://help.fews.net/fdw/fews-net-product-and-service-code-structure.md). The exception is that new products that the two-character alpha code appended to products that are specific to HEA work will always being with an H. --- language: "en" --- # Quality Assurance for BSS Loading When reviewing a loaded BSS, you are looking to answer the questions: * Did the pipeline recognize all of the communities and labels? * Are the Data Points assigned to the correct wealth characteristic, product, attribute, or season? * Are there any logical errors in the BSS that need to be corrected? Because the Livelihoods Explorer (LEX) reads from the database, if the BSS and LEX match, then you can assume the database matches as well. If the BSS and LEX do not match, check the database. If the BSS and database match, there is likely a processing error between the database and LEX. ## Quality assurance checks ### Map * [ ] The geographic area represented by the data is in the correct location and showing the correct Primary Livelihood System. ### Quick view * [ ] The Baseline reflects the correct reference year. * [ ] All wealth groups are showing. * [ ] The survival and livelihood protection thresholds match the BSS. ### Detail view * [ ] Appropriate wealth characteristics are listed in the Characteristics tab. * [ ] All seasons are present and accurately represented in the Calendar tab. * [ ] Appropriate key parameters are listed in the Key Parameters tab. ### Compare view * [ ] The poor-household size matches the BSS WB sheet. * [ ] Units are listed correctly, including currency abbreviations and land units. * [ ] Wealth characteristic values match the BSS WB sheet. *(Note: Wealth characteristics without an order assigned in the Reference Data sheet should not appear in LEX.)* * [ ] Livelihood activity values match the BSS Data Summary section, below the livelihood activity entries, including Other Income and Wild Foods. *(Notes: Strategy-type assignments may differ between the BSS, database, and LEX, but totals should not. Income minus expenditure has not yet been added as a non-essential expenditure entry and may explain some discrepancies.)* ### Database * [ ] The following values match: * * In the database: Go to **Livelihood Zone Baselines** \> **Poor survival non-food expenditure.** * In the BSS: Go to *Exp factors* sheet \> *Analysis of Basket Composition and Costs - Details* table \> *Expenditure in baskets* \> *PET* column. Take the sum of all values in this column that have a corresponding code `3` (survival non-food expenditure) in the *basket* column. --- language: "en" --- # Seasonal Calendar ## Seasonal calendar format * **Use numbers to represent months** . The month cells must be integers representing the month number. That means for the month of January use a `1`, for February use a `2`, etc. The pipeline cannot recognize month names or abbreviations in this row. * **Ensure the same start month across the entire calendar** . The start month for each village and for the results section must be the same, regardless of what month the village believes begins their consumption year. The Results columns will automatically calculate their values from the corresponding cell position within each community. That means the first cell in the Results range for a row will read the first cell from each of the villages. If half of the villages start from August (`8`) and the other half starts in September (`9`), and the results section starts with `9` for September, then the Results column labeled `9` (the start month) will represent the values for August for some villages and September for other villages, leading to incorrect results. * **Use only 1s and blanks in the village columns** . If data was collected in the villages, use the village fields to show this data. Use `1` and not a character such as an `x`. * **Only add collected data in the village columns**. If the Seasonal Calendar was developed during the analysis and reconciliation workshop (i.e., no village seasonal calendar data was collected), do not fill in the village fields. Only fill in the results fields. ## Rowset format For crops and animals the pipeline is designed to read a product (crop or animal) as the start of a rowset and attributes (land preparation, sowing, weeding, harvesting, heat, conceptions, births, milk production, peak sales, etc.) in subsequent rows below the product. **Example** In this seasonal calendar, peak sales (*pic ventes* ) for cattle (*bovins* ) and goats/sheep (*caprins/ovins*) are recorded in rows 61-62. However, peak sales should be an attribute recorded under each product rowset. This means that data from lines 61 and 62 should be recorded under the Bovins and Caprins/Ovins rowsets. Edits might look as follows: * Remove row 60. The seasonal calendar pipeline cannot parse an attribute as a heading with products in rows below it. * Relabel row 61 to "pic ventes." Without row 60, the pipeline will read data currently in row 61 if relabeled with the attribute "pic ventes" as the peak sales attribute for the rowset with the product label "Caprins/Ovins." * Data from line 62 should be recorded in line 54. Row 62 should be removed. The *Caprins*label for row 56 should also be removed as it is a product that will assign all subsequent attributes to goats instead of goats and sheep as intended by the primary label. ![image-20260520-165211.png](https://help.fews.net/__attachments/a_3a358878d20dec5305175a29f9fb210f52476bdeceedd907437f1e99561e971b/image-20260520-165211.png?cb=1b84474caf29d12d40b8ee66986506f6) ## Marking key activities To ensure that the seasonal calendar in the Livelihoods Explorer shows all key activities, those activities should be differentiated within the spreadsheet. The easiest way to do this is to add a column at the end of the spreadsheet (after the results column set) labeled Key activity. Use a "1" to mark rows that should appear in the seasonal calendar visualization. --- language: "en" --- # Seasonal Calendars ## Seasonal activities A seasonal activity is a seasonal activity type associated with a specific Baseline, season, and product and / or additional identifier. The pipeline reads seasonal activities from the BSS 'Seas Cal' worksheet in Column A, if present. Seasonal activities contain the following fields: * **Livelihood Zone Baseline**: The Livelihood Zone Baseline connected to this seasonal activity. * **Seasonal Activity Type**: The type of activity this is. * **Season**: The season or seasons in which this activity occurs. * **Product**: The CPC code and name of a product related to this seasonal activity, if applicable. * **Additional** **identifier**: Any additional text that helps identify the seasonal activity. * **Key Seasonal Activity?**Is this seasonal activity essential to the livelihood zone baseline such that it should appear in the Livelihood Explorer? For example, perhaps for livestock vaccinations not enough villages reported this activity as relevant or perhaps there was not a clear season for the activity to merit designating this as a key seasonal activity. ## Activity occurrences Activity occurrences are the specific times when a Seasonal Activity is undertaken in a Community or in the Livelihood Zone as a whole. These are documented in the BSS 'Seas Cal' worksheet, if present. Seasonal activity occurrences include the following fields: * **Seasonal activity**: The seasonal activity (not seasonal activity type) related to this occurrence. The menu options here will display seasonal activities as a combination of Livelihood Zone Baseline, seasonal activity type, and product. * **Livelihood Zone Baseline**: The Livelihood Zone Baseline connected to this seasonal activity. * **Community or village**: The community where this activity occurred. * **Start day**: The numeric day of the year when the activity starts. The system will automatically convert the first day of the start month in the BSS to a day of the year. * **End day**: The numeric day of the year when the activity ends. The system will automatically convert the last day of the end month in the BSS to a day of the year. Note that if a Community is specified then the Seasonal Activity Occurrence contains the period that the Activity occurred, as reported by that Community. If the Community is null, it is because the pipeline read the values from the "Results" section, meaning the Seasonal Activity Occurrence represents the consolidated and reconciled (summary) period for that Baseline's Seasonal Activity. --- language: "en" --- # System Architecture [View the database model](https://lucid.app/lucidchart/8086b325-bf3e-49d7-a766-206a90efe14d/edit?page=4VTH_3yX3sJ3#) for details on the relationships between entities in the HEA database. The Livelihoods Explorer administrative screen includes the following sections: * [BSS Setup](https://help.fews.net/hea/bss-setup.md) * [BSS WB, Data Sheets](https://help.fews.net/hea/bss-wb-data-sheets.md) * [Wealth, Activity, and Strategy Insights](https://help.fews.net/hea/wealth-activity-and-strategy-insights.md) * [Labels](https://help.fews.net/hea/labels.md) * [BSS Production Data](https://help.fews.net/hea/bss-production-data.md) * [Market Prices](https://help.fews.net/hea/market-prices.md) * [Seasonal Calendars](https://help.fews.net/hea/seasonal-calendars.md) * [Hazards and Events](https://help.fews.net/hea/hazards-and-events.md) * [Expandability and Coping](https://help.fews.net/hea/expandability-and-coping.md) * [Common](https://help.fews.net/hea/common.md) --- language: "en" --- # User Management Because the Livelihoods Explorer data is public and the application does not require a login, user management for this application is minimal. However, the following standards are used to manage users and permissions for the administrative side of the database. * **Creating user accounts**: Accounts should be created for users who will add or maintain code, data, and/or metadata. * **Removing user accounts**: Accounts should not be deleted once a user is no longer actively adding or maintaining code, data, and/or metadata. Instead, the box marking the user as Active should be unchecked. * **Assigning permissions**: In general users of this system should not need to be assigned individual permissions. Instead, users should be given Staff status to allow them to log in and fall into one of two categories: * **Superuser status**: This status designates that a user has all permissions without explicitly assigning them. * **Group member**: Groups are used to manage specific roles within the database, such as Baseline Administrator. Permissions should be assigned to a group, rather than to individuals. --- language: "en" --- # Wealth, Activity, and Strategy Insights The Wealth, Activity, and Strategy Insights menu contains administrative screens for adding and managing Wealth Group Characteristic Values, Livelihood Activities, and Livelihood Strategies. ## Wealth Group Characteristic Values Wealth Groups are groups within a specific community categorized by a wealth category such as Very poor, Poor, and Better off. Wealth Group Characteristics are potential attributes of a Wealth Group. These are the items in column A of the "WB" tab of a BSS. This includes: * Assets like bicycles, mobile phones, fishing gear, and cashew trees. * Counts of assets like number died, number born, land area owned and cultivated. * Other community or household descriptors like number of children in school, main source of cash income, school levels commonly attained, and household size. Wealth Group Characteristic Values are the values assigned to each of the Wealth Characteristics for a Wealth Group in a BSS. These values may be numerical or words/short phrases. Wealth Group Characteristic Values have eight fields: * **Wealth Group**: Each value must be associated with a specific Wealth Group within a Baseline. The Wealth Group can be assigned for an entire Baseline or a specific community within a Baseline. * **Wealth Characteristic:**Pick an item from the menu of Wealth Group Characteristics or create a new Wealth Group Characteristic from this page. * **Reference Type**: This indicates where the value comes from - Community Interviews (Form 3), Wealth Group Interviews (Form 4), or the Baseline Summary. * **Product**: If applicable, an associated product can be selected. * **Unit of Measure**: If applicable, a unit of measure can be selected. * **Value**: This is the value associated with the Wealth Group Characteristic. For example, "55," "true," "yes," or "primary." This should not include a unit of measure. * **Min_value** : The minimum value of the possible range for this value, found in the summary columns of the WB worksheet. The minimum value is the value in the `from` column. * **Max_value** : The maximum value of the possible range for this value, found in the summary columns of the WB worksheet. The maximum value is the value in the `to` column. If there is a min/max range and the summary value does not fall within that range, it will cause an error in the pipeline. ## Livelihood Strategy A Livelihood Strategy is one of a set of options used by households in a Livelihood Zone to obtain food and cash income and acquire the items needed to live. They are categorized by type for ease of comparison. Livelihood Strategy Types include things like milk production, crop production, food purchase, relief aid, and wild food gathering. [++See a full list++](https://help.fews.net/lex/livelihoods-explorer-glossary.md#LST). Each Livelihood Zone has a set of possible Livelihood Strategies. When one of those Strategies is used by a specific Wealth Group in the Livelihood Zone, it is a Livelihood Activity. **Example** **Livelihood Strategy Type**: Food Purchase **Livelihood Strategy**: The purchase of husked rice in Livelihood Zone HT02 (2014) **Livelihood Activity**: The amount of husked rice purchased by the very poor Wealth Group in Livelihood Zone HT02 (2014) A Livelihood Strategy is not necessarily used by all Wealth Groups within a Livelihood Zone. Livelihood Strategies have the following fields: * **Livelihood Zone Baseline:** The associated Baseline. * **Strategy** **Type**: The type of Livelihood Strategy, such as crop production or wild food gathering. * **Season**: The Season in which the Livelihood Strategy occurs. * **Product**: The product associated with the Livelihood Strategy. For example, if the Strategy type is meat production, the associated product might be cattle. * **Unit of Measure**: The unit used to measure production from this Livelihood Strategy. * **Currency**: The currency of income or expenditure from this Livelihood Strategy. * **Additional** **Identifier**: Additional text identifying the Livelihood Strategy. Note that the name of the Livelihood Strategy is a combination of the Livelihood Zone Baseline, Strategy type, Season, and Product or additional identifier. These pieces of information are essential for identifying a strategy. ## Livelihood Activity A Livelihood Activity contains the outputs of a Livelihood Strategy employed by one of the following: * A Wealth Group in a Community in the reference year. * A Wealth Group representing the Baseline as a whole in the reference year (the Baseline scenario). * A Wealth Group representing the Baseline as a whole in response to a shock (the Response scenario). Livelihood Activities contain 14 fields divided into 4 sections: * **General information** * **Wealth Group**: The specific Wealth Group undertaking this Livelihood Activity. * **Livelihood Strategy**: All Livelihood Activities are associated with at least one Livelihood Strategy (e.g., milk production, crop production). * **Scenario**: The scenario in which the outputs of this Livelihood Activity apply (e.g. baseline or response). * **Extra attributes**: Any additional attributes from the BSS for this Livelihood Activity. This includes the name of local measures and the number of kcals per unit for the associated product. * **Quantity**: Indicates the number that was produced, purchased, consumed, sold, and/or used in another way. Note that if the associated Livelihood Strategy contains a product and unit of measure, then those items should not be included here. * **Kcals**: * **Total Kcals Consumed**: Total kcals consumed by a household in the reference year from this Livelihood Activity. * **Percentage**: Percentage of annual household kcal requirement provided by this Livelihood Activity. * **Economy** * **Price**: Price per unit. Note that if the associated Livelihood Strategy contains a product and unit of measure then those items should not be included here. * **Income**: Total annual household income derived from this Livelihood Activity. * **Expenditure**: Total annual household expenditures on this Livelihood Activity. * **Activity done by**: The group mainly responsible for carrying out this Livelihood Activity (e.g., men, women, boy, girls, children, or all) The following Strategy Types have additional sections: * **Milk production** * Number of milking animals * Average number of days of lactation: Number of days of lactation for the season indicated in the associated Livelihood Strategy. * Average daily milk production per animal * Skim or whole milk consumed: Indicates if milk consumed by those who are milking the cows is whole or skim milk. * Skim or whole milk sold or used for other purposes: Indicates if milk sold or used for other purposes is skim or whole milk. * **Meat production** * Number of animals slaughtered * Carcass weight per animal * **Food purchase** , **Other purchase** , and**Relief** * Relief/Purchase size: Multiple of the unit of measure received each time * Purchases per month/Number of times per month the item is received * Months per year: Number of months in a year that the item is received * Times per year: Number of times in a year that the item is received * **Payment in Kind** and**Other cash income** * Payment product (included only for Payment in Kind): Product provided as payment, typically a staple food item in exchange for labor. This will differ from the product associated with the Livelihood Strategy, which is the product produced by the labor. * Payment per time: Amount of item received each time the labor is performed * People per household: Number of household members who perform the labor * Labor per month: Number of times the labor is performed per month. * Months per year: Number of months in a year that the labor is performed * Times per year: Number of times in a year that the labor is performed ## Livelihood Product Category The Livelihood Product Category describes how a Product is used in the Livelihood Zone, such as staple food or livelihood protection. Each Product associated with a Livelihood Activity in a BSS is assigned to one of the following baskets for each Wealth Group: * Main staple crop * Other survival food purchases (e.g., Cooking Oil, Flour, Salt) * Survival non-food purchases (e.g., Soap, Cooking Fuel, Lighting, Tea) * Livelihoods protection purchases (e.g., Seeds, Fertilizer, Animal Drugs) The total usage of a livelihood product may not be 100% in a single basket. For example, `OtherPurchase` of kerosene may be allocated as 75% in the survival non-food purchases basket. Because LEX only stores one category per product, the remaining 25% would implicitly be part of an "other" basket of discretionary spending. Allocation can vary by Wealth Group. For example, cooking needs may require 75% of the total for very poor households, but only 50% for medium and better off households. These baskets are used to calculate the Survival and Livelihood Protection Thresholds. * The Survival Threshold is calculated using the Main Staple, Other Survival Food and Survival Non-Food Items for the Poor Wealth Group. * The Livelihood Protection Threshold is calculated per Wealth Group and adds the Livelihoods Protection items to the Survival Basket. Livelihood Product Categories contain the following fields: * **Baseline Livelihood Activity**: The livelihood Activity being assigned to a basket. * **Product basket**: The basket this Livelihood Activity belongs to - main staple, other survival food purchases, survival non-food purchases, or livelihoods protection purchases. * **Percentage allocation to basket**: A number between 0 and 1 representing the percent of the Product that should be allocated to the indicated basket. Any remainder will implicitly be added to an "other" basket of discretionary spending. ## Key Parameter By default a Key Parameter is a Livelihood Strategy that contributes more than 5% of food + cash for two or more Wealth Groups, or more than 10% for a single Wealth Group. If the Strategy meets this threshold for the Baseline then it is a Production Key Parameter, and the quantity produced or available should be monitored. It the Strategy meets this threshold for the Response scenario then it is a Price Key Parameter and the price per unit should be monitored. If the Strategy meets the threshold in both the Baseline and Response scenarios then both quantity and price should be monitored. Note that the numerical threshold is only a default and it is possible to have Key Parameters that don't meet the threshold. For example, a Strategy that provides the majority of income for VP or P households during the lean season may not reach 10% of annual income, but still be considered a Key Parameter. The Key Parameter admin screen is used to indicate if price and/or quantity should be monitored. Key Parameters contain only three fields: * **Livelihood Strategy**: A Livelihood Strategy that has been marked as a Key Parameter. * **Monitor Quality**: This box is checked if the quantity produced or available should be monitored. * **Monitor Price**: This box is checked if the price per unit should be monitored. --- language: "en" --- # FEWS NET Brand ## FEWS NET Brand Standards for creating usable, appealing, and consistent materials that represent FEWS NET. [Get Started](https://help.fews.net/brand/about-the-brand.md) ### Table of Contents * #### [About the Brand](https://help.fews.net/brand/about-the-brand.md) #### [Colors](https://help.fews.net/brand/colors.md) * #### [Wordmark and Partner Logos](https://help.fews.net/brand/logos.md) * #### [Photography](https://help.fews.net/brand/photography.md) #### [Text Formatting](https://help.fews.net/brand/text-formatting.md) #### [Written Products](https://help.fews.net/brand/written-products.md) #### [Visualizations](https://help.fews.net/brand/visualizations.md) --- language: "en" --- # About the Brand ![Favicon for the FEWS NET Brand Knowledge Base.](https://help.fews.net/__attachments/a_86ea74111c2290c26b4244b268bfbf9cf1c3fe335d3ed73b245375ced5ea5d9b/Favicon_Brand.png?cb=d7720909712d78d2617d11e1ef79c3d0) The FEWS NET Brand is an integrated set of visual and content standards for FEWS NET partners and stakeholders to apply when creating FEWS NET materials. The Brand includes standards for: * Visual style * Text formatting and style * User interface and user experience These standards make it simple to create accessible, appealing and consistent products that represent FEWS NET. Just like FEWS NET's other products, the FEWS NET Brand is a platform that grows and evolves to meet its users' needs. If you have an application question or recommendation for an addition to the standards, [contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43). --- language: "en" --- # Base Color Palette FEWS NET's base color palette is the source of truth for colors used in the FEWS NET brand and our products. This palette is for reference only. Do not use color values directly from this palette. Instead, refer to [Brand Colors](https://help.fews.net/brand/colors.md) and [Data Visualization Colors](https://help.fews.net/brand/data-visualization-colors.md) to see the values from this palette that are recommended for use. ## Color values | **Color style name** | **Hex value** | **RGB value** | **Token name** | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|--------------------| | ![Sample of Red 800.](https://help.fews.net/__attachments/a_e22eb786f078527f49e0d7e89c854a2ae6b9477fef56fb472a685adecf23880b/red-800.png?cb=bb4493a4e38d9808056139d626ea6779) Red 800 | #451914 | 69, 25, 20 | base-red-800 | | ![Sample of Red 700.](https://help.fews.net/__attachments/a_29bf8386f44c5cc25a6f6432550eba8fdd3e349ae9106536c6aa063a56dd1615/red-700.png?cb=3c94dec7a62db305aff9d9aae0f7d6db) Red 700 | #541E18 | 84, 30, 24 | base-red-700 | | ![Sample of Red 600.](https://help.fews.net/__attachments/a_055625c31eb3a980e3d5b4c6a25f38982b47a0e137da5515accf37445d74c082/red-600.png?cb=8a55b89d48208f5196afa8bd4d877658) Red 600 | #6D4140 | 109, 65, 64 | base-red-600 | | ![Sample of Red 500.](https://help.fews.net/__attachments/a_5a2a2d230b89748c96d1bbc114a8e297e975cecf254503c8932e0fc83d7aaa20/red-500.png?cb=2f25fface5bd6219171c2e316a817cfb) Red 500 | #7A5A5A | 122, 90, 90 | base-red-500 | | ![Sample of Red 400.](https://help.fews.net/__attachments/a_ae47f2576780e21b341ccf05a016f023b35f2532d432c70112033714fd757a52/red-400.png?cb=0a0fb2837f7cd341cd13de7a2cfe459a) Red 400 | #A88A8A | 168, 138, 138 | base-red-400 | | ![Sample of Brick 700](https://help.fews.net/__attachments/a_ecdba881afc34b8df130a53c9c6e9c97d0a76534f4fc49941b1128e5865154b1/brick-700.png?cb=1bffca523fd3f4cc8e8bc0452b430706) Brick 700 | #7E201F | 126, 32, 31 | base-brick-700 | | ![Sample of Brick 600](https://help.fews.net/__attachments/a_f7afdd9c665ae4845520355a89258d4152b89af2a3acd63a596591eeb15fda72/brick-600.png?cb=5a4fa44b4cc1602a96744de5c452ad85) Brick 600 | #AC1C1E | 172, 28, 30 | base-brick-600 | | ![Sample of Brick 500](https://help.fews.net/__attachments/a_b670935de3adcf8e85686a3f0c0ec8040d428baadfcb0722ceb91f76d165d091/brick-500.png?cb=43864210d5ee6fc924ebeeab032dea5e) Brick 500 | #C15153 | 193, 81, 83 | base-brick-500 | | ![Sample of Brick 400](https://help.fews.net/__attachments/a_bbed6667da274206d94aa042bae8d046fd68dffef8595a23d34a24f2a6e5a8eb/brick-400.png?cb=4d9ddb1b6ef887628ae07de2f3274db6) Brick 400 | #D58687 | 213, 134, 135 | base-brick-400 | | ![Sample of Brick 300](https://help.fews.net/__attachments/a_ac5c22705b074ad45055c062d51f392af4d70b3f4b92d89387f8fabdd90a2563/brick-300.png?cb=61c849fce6a1359f0bf4a587389b8e05) Brick 300 | #F0CDCC | 240, 205, 204 | base-brick-300 | | ![brick-200.png](https://help.fews.net/__attachments/a_d6abb902421dfcc64ea749f7d85fd9d0e96202a1714b0b8edf7d03b8252d2ed3/brick-200.png?cb=0beb9f9a7d0bfe4fb2b82d1aa7475d88) Brick 200 | #F7E6E5 | 247, 230, 229 | base-brick-200 | | ![brick-150.png](https://help.fews.net/__attachments/a_daa9041f537d9a8aff6f3b1e0cfc3c556782dbc31267ea2e3810e14757e4dbb4/brick-150.png?cb=363f39c137b09b2071e27ac2bbee10c2) Brick 150 | #FEF0EF | 254, 240, 239 | base-brick-150 | | ![Sample of Orange 700.](https://help.fews.net/__attachments/a_8bb459d239c03a4d5a3a6172d624e75e2d81b3b477c2896c26b5b9d5766eaf8d/orange-700.png?cb=9dac7cbca8f40c28b3bf276e51d52dd1) Orange 700 | #AB4B1E | 171, 75, 30 | base-orange-700 | | ![Sample of Orange 600.](https://help.fews.net/__attachments/a_230d148852b713d57fcf6331a632d322b1f9af20148dbefce551e4e1a8de9171/orange-600.png?cb=84ea437972b2a3a6bd8dc0cf67f3818f) Orange 600 | #B95A38 | 185, 90, 56 | base-orange-600 | | ![Sample of Orange 500.](https://help.fews.net/__attachments/a_5e3355e8809db4bd5478cd383f2a667dedab7822bfc7c7763f09662e077a14c2/orange-500.png?cb=a9ab00e4eaa73bffa5eb64389cdf2422) Orange 500 | #BA6B55 | 186, 107, 85 | base-orange-500 | | ![Sample of Orange 400.](https://help.fews.net/__attachments/a_e752589148da0a40f0a81146e6c31e517cdcc16f88596fb78616acb0de3e6091/orange-400.png?cb=1fa462d977cd8b8579b3168b18fc9a76) Orange 400 | #D6A79A | 214, 167, 154 | base-orange-400 | | ![Sample of rust 700](https://help.fews.net/__attachments/a_d08d314b7d03f4266142e57f888d9a4a96f498aadf9a895b05bfe2334c9d77f1/rust-700.png?cb=cc8695585a5c385a7436a82818dbf361) Rust 700 | #A95B24 | 169, 91, 36 | base-rust-700 | | ![Sample of tangerine 600](https://help.fews.net/__attachments/a_e263ef70b82faa2813863d24e5c2efc391a4d123a06baac27c228923277123e3/tangerine-600.png?cb=47be091d884ff190958a5dc92f23f0b2) Tangerine 600 | #E8792A | 232, 121, 42 | base-tangerine-600 | | ![Sample of gold 700](https://help.fews.net/__attachments/a_dbe629e380960bb2fa844c4000ecb0a7350ed9641f8454d92da09d1321015a99/gold-700.png?cb=2b113a14b230cdf4ac9beb91a7fcecb9) Gold 700 | #E39602 | 227, 150, 2 | base-gold-700 | | ![Sample of gold 600](https://help.fews.net/__attachments/a_4e54ad5b1c40965274956939144e66e4341f344bc77c38468e185b89d35290d7/gold-600.png?cb=c34a5ee70e0323908b02369acca6d5da) Gold 600 | #FDB833 | 253, 184, 51 | base-gold-600 | | ![Sample of gold 200](https://help.fews.net/__attachments/a_43e5c9dff0189e59d50a3be640a350180784b6d41fd1a8d284cce6065d69f170/gold-200.png?cb=2e996b0f233279fcfb019dddef34bff7) Gold 200 | #FFF6CC | 255, 246, 204 | base-gold-200 | | ![Sample of Yellow 600.](https://help.fews.net/__attachments/a_b6adea5eca58ca2e18a658eb306adda09ae7f83b559ec6c3d4ab1f7b38fb712f/yellow-600.png?cb=a52534b6ab2507d2169caab783fe0c86) Yellow 600 | #FDD835 | 253, 216, 53 | base-yellow-600 | | ![Sample of Yellow 500.](https://help.fews.net/__attachments/a_fbe26f56db81d74ac42843281ae468164366b43fe208d675257789f35bcb877b/yellow-500.png?cb=fd8e5b66a1e34cb846e46260e21ceb59) Yellow 500 | #FFEE58 | 255, 238, 88 | base-yellow-500 | | ![Sample of Yellow 400.](https://help.fews.net/__attachments/a_3691b7b5c0f9531a6bbb8f8695d18031e5600229b7913d788dfaa27b84773eb5/yellow-400.png?cb=45fccf5bfe5fa77932794414d203c14b) Yellow 400 | #FFF59D | 255, 245, 157 | base-yellow-400 | | ![Sample of Yellow 200.](https://help.fews.net/__attachments/a_9c3add5b76bfbf4265c4c1e99dbf59dd075175369fa1221c87bb97be72bedf66/yellow-200.png?cb=0a468c6cab7893272b5658fa25ebedee) Yellow 200 | #FFF9C4 | 255, 249, 196 | base-yellow-200 | | ![Sample of Olive 700.](https://help.fews.net/__attachments/a_d91814cb70dd62accf54df62148525f9a82f0f5df9b5b4e1b245b22fe9876381/olive-700.png?cb=359aa036b88ea1646a6e4f8317c49af3) Olive 700 | #484817 | 72, 72, 23 | base-olive-700 | | ![Sample of Olive 600.](https://help.fews.net/__attachments/a_a7059222f0d23c91daa2f6b899b1f89667aaeba1e833df34f79b2636dbc6b6ec/olive-600.png?cb=9894255eb0fc7c97e1487f4f85f5410e) Olive 600 | #60613A | 96, 97, 58 | base-olive-600 | | ![Sample of Olive 500.](https://help.fews.net/__attachments/a_04fe417c0887926d211c0f9a4ff7a7ec261bea0e7838fcf4a3118507657c4675/olive-500.png?cb=a055c183d07a6ab589ed2bbcf9e1c22e) Olive 500 | #707257 | 112, 114, 87 | base-olive-500 | | ![Sample of Olive 400.](https://help.fews.net/__attachments/a_e0a742c33f16a1ae4754c9d0efc8c7a4d9da5304b699e32a7255bd94ad364bc9/olive-400.png?cb=69fcda725d5642c008fc45a4ba621028) Olive 400 | #9B9D80 | 155, 157, 128 | base-olive-400 | | ![lime-600.png](https://help.fews.net/__attachments/a_1da1f5f6dee7e47a73194a9fb7f95a2d448e1ec36cef698e620225abe16a0f09/lime-600.png?cb=8fb18512e3b6573445d3fb35cb337771) Lime 600 | #689F38 | 104, 159, 56 | base-lime-600 | | ![Sample of Lime 500.](https://help.fews.net/__attachments/a_5c96c054e5bab4cba7e1d708c1a03f717a10fdb7c91b780154dfa3f131073333/lime-500.png?cb=27aeba81f89e0ae882ed7854f6d99a4e) Lime 500 | #8BC34A | 139, 195, 74 | base-lime-500 | | ![Sample of Lime 400.](https://help.fews.net/__attachments/a_7b70b26123a11f394277afd81b645e3f86779bd4489d0259c7df4ea54470e644/lime-400.png?cb=b4bd4766c4920c2b959fb46a88df030c) Lime 400 | #AED581 | 174, 213, 129 | base-lime-400 | | ![Sample of Lime 200.](https://help.fews.net/__attachments/a_1403ae3f0d295c7d1e273fa1133c9d4977006e8be5600a0a6f591010ffa0e7ac/lime-200.png?cb=bee7be9d312776d4449961e68e0dc7b0) Lime 200 | #DCEDC8 | 220, 237, 200 | base-lime-200 | | ![lime-150.png](https://help.fews.net/__attachments/a_d36d980427b59ebf700375d7210ee55c7f2063fedd62fb1c397e98356f4a586a/lime-150.png?cb=24d6213884d837f17c31a9966b206207) Lime 150 | #EDF6E3 | 237, 246, 227 | base-lime-150 | | ![Sample of mint 500](https://help.fews.net/__attachments/a_a5ee94610fe70c550295593b15cc1ec61b2a09427472024aa55a2d277a588bfe/mint-500.png?cb=f5e719f4628120a0c78a35b291c3d32b) Mint 500 | #52B788 | 82, 183, 136 | base-mint-500 | | ![Sample of mint 200](https://help.fews.net/__attachments/a_ee8b5d5cce5055b78d4150b6f414023415b8e746a4c8b8e3e8deae96064c6f8b/mint-200.png?cb=9ec8c2b5d30ad6450f4abdc97c53185e) Mint 200 | #D8F3DC | 216, 243, 220 | base-mint-200 | | ![Sample of green 800](https://help.fews.net/__attachments/a_c410ee301a13fc1c855fe882c774f9bd37faa5376ecd770852612435d6314d3a/green-800.png?cb=1f9657be915f8659340c6f421bdef96e) Green 800 | #074B2F | 7, 75, 47 | base-green-800 | | ![Sample of green 700](https://help.fews.net/__attachments/a_108623ea36f37f56172ab8fe66629b93cf637940b1e832a25240b4ee031c0eb1/green-700.png?cb=71d50daf42c8cdf5b01eea40d1965f83) Green 700 | #096640 | 9, 102, 64 | base-green-700 | | ![Sample of Green 600](https://help.fews.net/__attachments/a_9f91438a208e84698d35c34f50217f878763d68e1d48851441e401daf4a6c024/green-600.png?cb=555ccdd33e2dcbfbafa94e2c25d828b8) Green 600 | #0B8351 | 11, 131, 81 | base-green-600 | | ![green-500.png](https://help.fews.net/__attachments/a_bed89878bbe7e4ab394167095017f5406826ba7cdb05ec2f2a38391894f57144/green-500.png?cb=db62db30d8f74a49d3d19e4fd9ac2357) Green 500 | #19B877 | 25, 184, 119 | base-green-500 | | ![pine-800.png](https://help.fews.net/__attachments/a_49546bd756be30b6128c59328c73b5b2221f3df5c971db29f9a67d8bf8e55730/pine-800.png?cb=d4086fd93a836f954b179601be82d2d2) Pine 800 | #0C5D40 | 12, 93, 64 | base-pine-800 | | ![Sample of Pine 700.](https://help.fews.net/__attachments/a_04f0eaa6c6ca6c9c11160b0532e2eb9d5fc290536001bec609bf36d441bebdc9/pine-700.png?cb=7ce24751cd75b4f38698105e1e203caa) Pine 700 | #107157 | 16, 113, 87 | base-pine-700 | | ![Sample of Pine 600.](https://help.fews.net/__attachments/a_e778bae4485533dada53118321f93a794a64aad079aa163f5b9eee1f5768d5a2/pine-600.png?cb=3eccd67333f2335ed0ac0560f8b04906) Pine 600 | #2C8C79 | 44, 140, 121 | base-pine-600 | | ![Sample of Pine 500.](https://help.fews.net/__attachments/a_a5a0108f805b604031d1454db8787de1a60bf52fb65aa9439c1ed29f5c5b2a95/pine-500.png?cb=5f8b715a048f8a18c3323b5dd8395cdb) Pine 500 | #319B86 | 49, 155, 134 | base-pine-500 | | ![Sample of forest 800](https://help.fews.net/__attachments/a_cf71ec0efbac0f1d61ad8acead6783c52fd19b212d295d58a78bf0884d6b3e0e/forest-800.png?cb=b0370fb257fad9c806bf1a12e03de67e) Forest 800 | #00573F | 0, 87, 63 | base-forest-800 | | ![Sample of sky 800](https://help.fews.net/__attachments/a_03d72b1266031feefdf65fac702259be4e35537106ceaa82f077ba530bc315d9/sky-800.png?cb=472765d70c08b914be5005210b438ca1) Sky 800 | #144D4B | 20, 77, 75 | base-sky-800 | | ![Sample of sky 700](https://help.fews.net/__attachments/a_d1d647ac321517610a3956dee653869ec92be8c1a9db2cd48c1b35477691c8fc/sky-700.png?cb=d9d45f8c929dea3f39185202fd4f0d74) Sky 700 | #3C716E | 60, 113, 110 | base-sky-700 | | ![Sample of sky 600](https://help.fews.net/__attachments/a_7f4534fb9c24e0b6dd162e2fbd9079fcca1d8f842ab56ec2083f6bcdda25822b/sky-600.png?cb=d9b6b2eaedfdf91405c943a9a7cd720e) Sky 600 | #88BFB6 | 136, 191, 182 | base-sky-600 | | ![Sample of sky 400](https://help.fews.net/__attachments/a_c355d1d9de6227eed78200bfab0da8c9cf537e522da7bc48a27a2da448376489/sky-400.png?cb=dc2fc496c27d67c9dd22c3441a28e5fd) Sky 400 | #BDDBD6 | 189, 219, 214 | base-sky-400 | | ![Sample of sky 200](https://help.fews.net/__attachments/a_65e94cca60122cf4b7d84a721fc9fb7b6de9895de3934385f87cf7abe98aac02/sky-200.png?cb=4bf904d9ecf2c4b3387d73a0ca608c94) Sky 200 | #E4F1EF | 228, 241, 239 | base-sky-200 | | ![Sample of sky 150](https://help.fews.net/__attachments/a_288a7c49035c180e2b5db5e69da2c8d4a79179613cccd06c7986991168c01f7b/sky-150.png?cb=6ad59fcbeae09df9cf63504656e2728b) Sky 150 | #FAFCFC | 250, 252, 252 | base-sky-150 | | ![Sample of Ocean 400.](https://help.fews.net/__attachments/a_01c8b6fdb2c71120d07b2ca51ae77b8ee1ca567f51bd54e4b7fb138e5a960edb/ocean-400.png?cb=12e3d24b51ca9de80cf0fb639e4b2d64) Ocean 400 | #BCDAE9 | 188, 218, 233 | base-ocean-400 | | ![Sample of Blue 700.](https://help.fews.net/__attachments/a_b0e506a2cb493e88c58f3b105c6c82005f90347c6271b0448fba89d2de40e4a1/blue-700.png?cb=6b0aae8308a335b999b25bcc473b8ad4) Blue 700 | #305088 | 48, 80, 136 | base-blue-700 | | ![Sample of Blue 600.](https://help.fews.net/__attachments/a_1f539b384bb1ebcdd9a86da21c7e09545bca9bb7da8c54c482295bea019e9f09/blue-600.png?cb=31b7d6b4f7bb2261559294636767dcec) Blue 600 | #426FBC | 66, 111, 188 | base-blue-600 | | ![Sample of Blue 500.](https://help.fews.net/__attachments/a_fd7127f5c2eeb25d1505f59278a3aba5db0e4f431ae94e2c391d9a8e99c6d420/blue-500.png?cb=4ef25eb001622c65f567e19d1b3a10f5) Blue 500 | #688CCA | 104, 140, 202 | base-blue-500 | | ![Sample of Blue 400.](https://help.fews.net/__attachments/a_88d59b5ad23f4900335a68e0fb2a5be4de1fdd52ba7ea2489a039cb09f438ee1/blue-400.png?cb=e91d293ed18b1b4761faf7f1caae12a4) Blue 400 | #A6BFE2 | 166, 191, 226 | base-blue-400 | | ![Sample of cobalt 600](https://help.fews.net/__attachments/a_71fcaae58519b9e9257d180fe9d902fc5b04a6b7d4895c9a9e049e20f801f7c6/cobalt-600.png?cb=8cf9a70953ed2349a5efe16cfc199448) Cobalt 600 | #2B6CB0 | 43, 108, 176 | base-cobalt-600 | | ![Sample of cobalt 200](https://help.fews.net/__attachments/a_f712c05a08b21b9fd584bf800522d11dd11c8a9bc4619779fdf9851a9de5c0c9/cobalt-200.png?cb=f01e74a030ea55833fcbb54e7454ea2c) Cobalt 200 | #EBF8FF | 235, 248, 255 | base-cobalt-200 | | ![Sample of Purple 700.](https://help.fews.net/__attachments/a_b8d0a2cc494dcdbdef8e1eaa51caacd7f2e44a35da67d1c468f3ff06ad64d736/purple-700.png?cb=1f95e4d2bbabdce19c0d792d29a39b89) Purple 700 | #492674 | 73, 38, 116 | base-purple-700 | | ![Sample of Purple 600.](https://help.fews.net/__attachments/a_2fa0f87a9d72c71d0dbc04ab7c9ffcf8fc6c2ef65b43caf97c61f8ca49f63ab7/purple-600.png?cb=0bc5d21ea131281745234a7cf8d53455) Purple 600 | #784595 | 120, 69, 149 | base-purple-600 | | ![Sample of Purple 500.](https://help.fews.net/__attachments/a_1e7a33a2e854d338480139657fa41d4dd299aaa8f134bb2a7de40839c239ecc9/purple-500.png?cb=340dc6a76f0ed3f5acb3804261dc02c2) Purple 500 | #A173B3 | 161, 115, 179 | base-purple-500 | | ![Sample of Purple 400.](https://help.fews.net/__attachments/a_08f34b2c95ae139228198eeb95493e43294feb59ee9fe9b9fe576f3e8eff3b12/purple-400.png?cb=22bc2e66b392bc707965a899be9285de) Purple 400 | #DBBEE0 | 219, 190, 224 | base-purple-400 | | ![Sample of Steel 700.](https://help.fews.net/__attachments/a_a370bbf2abe44250d1117279b5a51a6db040e0e29ae5ed657f66230080ca95e0/steel-700.png?cb=41fa7445d6232a96e0bcfe0ac263ed1b) Steel 700 | #416371 | 65, 99, 113 | base-steel-700 | | ![Sample of Steel 600.](https://help.fews.net/__attachments/a_f9040e8d855e4cafe868f12bbc60b355fc91b053c7d41334ba0b7e6de4058083/steel-600.png?cb=ed9cb4f78a742d8349259b084a546ed6) Steel 600 | #55747E | 85, 116, 126 | base-steel-600 | | ![Sample of Steel 500.](https://help.fews.net/__attachments/a_aa58aa1ef3e9a7b21758340fb4a3f06c536f0e303d19d0b385e254b2ac676f20/steel-500.png?cb=5ce27b6af8387b5904562b9b759a37d6) Steel 500 | #6A8188 | 106, 129, 136 | base-steel-500 | | ![Sample of Steel 400.](https://help.fews.net/__attachments/a_c712d052ef2427b611cf7911fae27dfee2c6123a6f191270426babd88a7d1316/steel-400.png?cb=c46f01d32ecbcc2c5d284ac1dd9da155) Steel 400 | #98A9AE | 152, 169, 174 | base-steel-400 | | ![Sample of Charcoal 700.](https://help.fews.net/__attachments/a_26880c28789e9f85787b57a17c3b24dbece7e2fb7e74529dcaca9ec29f5d4091/charcoal-700.png?cb=fa88c0f346b90132d94babcdc2e60cd1) Charcoal 700 | #0C1D28 | 12, 29, 40 | base-charcoal-700 | | ![Sample of Charcoal 600.](https://help.fews.net/__attachments/a_410537e5ed56b7e6f3013b2df9ab80a3afd3c8081ff4a337561b3218c0883060/charcoal-600.png?cb=9299d15bb8e137bcf8a95d61c4f9e801) Charcoal 600 | #3A454C | 58, 69, 76 | base-charcoal-600 | | ![Sample of Charcoal 500.](https://help.fews.net/__attachments/a_17e997c264890be67441e53e4c1f04d57c465937821eaaf25ca83c4f4fb99e64/charcoal-500.png?cb=b7d99ca7fad2d67dd05c3f5f0e8c44db) Charcoal 500 | #555E62 | 85, 94, 98 | base-charcoal-500 | | ![Sample of Charcoal 400.](https://help.fews.net/__attachments/a_cea5736e37b5131aaea766bd22746678ec02b25293a06dcb844850937caf8837/charcoal-400.png?cb=eb0c410631739e05078eb5189be8d52f) Charcoal 400 | #7C888D | 124, 136, 141 | base-charcoal-400 | | ![Sample of the darkest gray, gray 800.](https://help.fews.net/__attachments/a_d7e7b19273bd8381b5dadb92895061f91c913cb1095ba510216d094af553fdac/gray-800.png?cb=13e7f46ee1ebc598221aaf7ff22be4c5) Gray 800 | #424242 | 66, 66, 66 | base-gray-800 | | ![Sample of gray 700.](https://help.fews.net/__attachments/a_9fb8a6aff6d2c079011816efdfe742ecfbc52d03671d463e457625925132fc61/gray-700.png?cb=ab7a1cce506537a88b52eef5426c7331) Gray 700 | #585858 | 88, 88, 88 | base-gray-700 | | ![Sample of gray 600.](https://help.fews.net/__attachments/a_d9e96f7b179e8c0e268bc8a1633ff923a42d26763e14df9dc14631bb0d24a2cb/gray-600.png?cb=1e297143769a78da2ab752a8296ff6c5) Gray 600 | #808080 | 128, 128, 128 | base-gray-600 | | ![Sample of gray 500.](https://help.fews.net/__attachments/a_89c01a8eeffc3808621cc194cd1e351c0b42f507c1cca87b27cf3f9d20243a85/gray-500.png?cb=c44173c127aa11718ff2a2cd423b60ea) Gray 500 | #ADADAD | 173, 173, 173 | base-gray-500 | | ![Sample of gray 400.](https://help.fews.net/__attachments/a_db37da55473787bac5f699a34fe1159f1f141275917b3b7da8fa596d5f8d49d9/gray-400.png?cb=96cb4d82ce42e4cc0c1b1847d668d110) Gray 400 | #D1D3D4 | 209, 211, 212 | base-gray-400 | | ![Sample of gray 300](https://help.fews.net/__attachments/a_8f83529dbd894bd5c5ae8edc20e4131e826b4d396803c0c9d72613a6bb40be80/gray-300.png?cb=840b36a9a554adc33468acc5339528fd) Gray 300 | #E6E7E8 | 230, 231, 232 | base-gray-300 | | ![Sample of gray 200.](https://help.fews.net/__attachments/a_cc167799ef4615732c0460ef77a1b422a6fec724b3628f9701d3d09732ef7ba1/gray-200.png?cb=d16f975028ee4da3556f3b6d96977320) Gray 200 | #F4F5F5 | 244, 245, 245 | base-gray-200 | | ![Sample of the lightest gray, gray 150.](https://help.fews.net/__attachments/a_daeab0d48ed626db39f61fa6d9b07bd0b5ffe3c26e27a48e065ccc63d1f3bf7e/gray-150.png?cb=021ab889f6435536ae299f141a80759b) Gray 150 | #FAFAFA | 250, 250, 250 | base-gray-150 | | ![Sample of black 800](https://help.fews.net/__attachments/a_e4db37ca25f6259485607bbc467a945162f9f0ff80e54ed540925b8aed09eda5/black-800.png?cb=97f50883ac1b8ae339b692f4e8c3ec4b) Black 800 | #212721 | 33, 39, 33 | base-black-800 | | ![Sample of black 900](https://help.fews.net/__attachments/a_cc149a4502b3c5131201409110af8b439ce22254b3d1ee99dda36824cd2470ba/black-900.png?cb=ff0ddbc634d1c9376946d5b4233d6fc5) Black 900 | #090B09 | 9, 11, 9 | base-black-900 | ## Palette diagram ![Diagram displaying brand color values](https://help.fews.net/__attachments/a_e96dfc94bd9ee5cadfe5f2ba2ddd8858650d34c7a9b2d2e34e4a86147bd5302e/FEWS%20NET%20Base%20Color%20Values.png?cb=5d4f8d57199381eb0fb5e79215c4be6e) *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Brand Colors ## Using brand colors Brand colors are the only colors that should appear on FEWS NET products except where these standards specify otherwise. Brand Primary and Brand Black are the two core brand colors and should appear on all FEWS NET branded materials. Brand Secondary may also be used in support of these two colors. Brand Accent may be used sparingly for graphic elements that highlight or emphasize, while Brand Alert may be used sparingly to convey warnings or disallowed actions. Brand White is the general-use background for text and pages. See [Color Safety and Recommended Combinations](https://help.fews.net/brand/color-safety-and-recommended-combinations.md) for more usage guidance. ![Sample of brand primary green.](https://help.fews.net/__attachments/a_4013d1b14f49fd8f524fd1001e2027ec9b993f6cdbfd0027e72d607c32cc5641/brand-primary.png?cb=3ce7d6dfbc6d64ebf9c1256c324c3895) **Brand Primary** #096640 R 9 G 102 B 64 ![Sample of brand black.](https://help.fews.net/__attachments/a_b507e84fd38ace8556ef39c87ed4d3ad3a7af15af1e21f9b97f266c1172948ed/brand-black.png?cb=01a2cae19820128db64f1173310433ab) **Brand Black** #212721 R 33 G 39 B 33 ![Sample of the brand sky blue.](https://help.fews.net/__attachments/a_c9e23f525eeeddd8a3dad4ea1bde4b7e515832a877b7c1fcfffd9f542d6ba62d/brand-secondary.png?cb=3d0912774acf3631db50cd483ff162ce) **Brand Secondary** #BDDBD6 R 189 G 219 B 214 ![Sample of brand accent orange.](https://help.fews.net/__attachments/a_f0f26a7935849ef4eb10d1447be9743da4ef4c37151af654479476d13a574276/brand-accent.png?cb=8a8815539dec5aa45c3cf66e0f9da623) **Brand Accent** #A95B24 R 169 G 91 B 36 ![Sample of brand alert red.](https://help.fews.net/__attachments/a_01d3c25037d00555720ecc9883b8c06b8b0aae426d416df98cdd35259e098848/brand-alert.png?cb=1454bb08979021206c99da8d431d25ee) **Brand Alert** #AC1C1E R 172 G 28 B 30 ![Sample of brand white.](https://help.fews.net/__attachments/a_551ffd4dd9eac46707f336e701802654d7e9f99ce4982ff3f1f095fc979bddd3/brand-white.png?cb=40a3c5fe1be365cfad89468ef1c8f268) **Brand White** #FFFFFF R 255 G 255 B 255 Darker and lighter shades of some brand colors are available. Always use the standard shade unless a different shade works better for a particular use case. Note that Brand Accent Light is sometimes used in existing brand assets but is not otherwise recommended for use. ![Chart of primary brand colors showing lighter and darker shades of each.](https://help.fews.net/__attachments/a_6b3b29f2ab4d5d3a546f9825b6ce71ec6849a3a9db5761093f4a63dfeea423a5/Brand%20Colors%20Primary%20-%20Shades.png?cb=0d6f93c5332f1c4235d4590c5248ba74) Finally, grays from FEWS NET's base color palette are also included in the brand colors for use as lines, borders, background fills, and graphic elements. ![Chart of brand grays.](https://help.fews.net/__attachments/a_e1f057c3ab0b743adf22c950a8cb0539ef6d77d3fdb0502e6189f37cb6df490a/Brand%20Colors%20-%20Supporting%20Grays.png?cb=6e06598b24c3a70dfe09a12ee88fb4a2) ## Color values | **Color style name** | **Hex value** | **RGB value** | **Token name** | **Base token** | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|-----------------------|--------------------| | ![Sample of brand primary green.](https://help.fews.net/__attachments/a_4aa0851a2c2fa4fc5af698b9d4f336c56a2aaeff650dadfa1caeefda4bcb5e57/green-700.png?cb=71d50daf42c8cdf5b01eea40d1965f83) Brand Primary | #096640 | 9, 102, 64 | brand-primary | base-green-700 | | ![Sample of brand primary green light.](https://help.fews.net/__attachments/a_34c8ba33596603c85c16198a5a8fa5666b85a15db4c0be3e44e651832b00bab6/green-600.png?cb=555ccdd33e2dcbfbafa94e2c25d828b8) Brand Primary Light | #0B8351 | 11, 131, 81 | brand-primary-light | base-green-600 | | ![Sample of brand primary green dark.](https://help.fews.net/__attachments/a_12a590496f10d8d428bf6bab017679f7439e5b9ea15646993591679892cb297f/green-800.png?cb=1f9657be915f8659340c6f421bdef96e) Brand Primary Dark | #074B2F | 7, 75, 47 | brand-primary-dark | base-green-800 | | ![Sample of brand black.](https://help.fews.net/__attachments/a_ee2e82c1c976dbce5cd24b1eaa7eb1b928053b1077feff32f5b13a64967d1bd4/black-800.png?cb=97f50883ac1b8ae339b692f4e8c3ec4b) Brand Black | #212721 | 33, 39, 33 | brand-black | base-black-800 | | ![Sample of brand black dark.](https://help.fews.net/__attachments/a_aef4bf5b88c440435260d5a086620569a99d97f2d5e9ee2d1add51b1fa7144a3/black-900.png?cb=ff0ddbc634d1c9376946d5b4233d6fc5) Brand Black Dark | #090B09 | 9, 11, 9 | brand-black-dark | base-black-900 | | ![Sample of brand secondary sky blue.](https://help.fews.net/__attachments/a_3cc367bda8c1e14bf33cf0e4d8c1be83d3c2a0827a4053404faec5230336e80c/sky-400.png?cb=dc2fc496c27d67c9dd22c3441a28e5fd) Brand Secondary | #BDDBD6 | 189, 219, 214 | brand-secondary | base-sky-400 | | ![Sample of brand secondary sky blue light.](https://help.fews.net/__attachments/a_084a7de78cf34b3297d03ad2db874e01e067b2e50dfdef76a0dd798605b31ea6/sky-200.png?cb=4bf904d9ecf2c4b3387d73a0ca608c94) Brand Secondary Light | #E4F1EF | 228, 241, 239 | brand-secondary-light | base-sky-200 | | ![Sample of brand secondary sky blue dark.](https://help.fews.net/__attachments/a_6dfe2e6ace20ac9611e1a94ce629c3873e339b09e3c56e1ce04ffaab170a946e/sky-600.png?cb=d9b6b2eaedfdf91405c943a9a7cd720e) Brand Secondary Dark | #88BFB6 | 136, 191, 182 | brand-secondary-dark | base-sky-600 | | ![Sample of brand accent orange.](https://help.fews.net/__attachments/a_a5af6639cf7378cba10d8ffd8e8e0d1208cb0c86f29f3dda8a81a4bfa5c1bf2c/rust-700.png?cb=cc8695585a5c385a7436a82818dbf361) Brand Accent | #A95B24 | 169, 91, 36 | brand-accent | base-rust-700 | | ![Sample of brand accent orange light.](https://help.fews.net/__attachments/a_6a9ad4417b2b1c8280901873e262b05776c5a0bdd41b84afa63f2dd15fcff225/tangerine-600.png?cb=47be091d884ff190958a5dc92f23f0b2) Brand Accent Light | #E8792A | 232, 121, 42 | brand-accent-light | base-tangerine-600 | | ![Sample of brand alert red.](https://help.fews.net/__attachments/a_8fcf256001f3b1e0e63b4138c50b685a8ea9e92389a9defd34a45e84dbcb6258/brick-600.png?cb=5a4fa44b4cc1602a96744de5c452ad85) Brand Alert | #AC1C1E | 172, 28, 30 | brand-alert | base-brick-500 | | ![Sample of brand alert red light.](https://help.fews.net/__attachments/a_093698d2aa80a2c2b6a192f99eae1638a7824270f83ab59e501ba2f5b23657fd/brick-500.png?cb=43864210d5ee6fc924ebeeab032dea5e) Brand Alert Light | #C15153 | 193, 81, 83 | brand-alert-light | base-brick-600 | | ![Sample of brand alert red dark.](https://help.fews.net/__attachments/a_476286bde196d836b16542090e5f899936bf579bf022badf547c04726c289b92/brick-700.png?cb=1bffca523fd3f4cc8e8bc0452b430706) Brand Alert Dark | #7E201F | 126, 32, 31 | brand-alert-dark | base-brick-700 | | ![Sample of brand white.](https://help.fews.net/__attachments/a_7a4f0d293c21de1d2d1f691ce39484fe603e0f89bdb84bb0c3e6e6deca241a58/gray-100.png?cb=236a48d7a590218ab600e9a65ebe36f4) Brand White | #FFFFFF | 255, 255, 255 | brand-white | base-gray-100 | | ![Sample of the darkest gray, gray 800.](https://help.fews.net/__attachments/a_b20775116669a7865fd9306908944cf63d65d046b1b36699cffb4b82b816c6c8/gray-800.png?cb=13e7f46ee1ebc598221aaf7ff22be4c5) Gray 800 | #424242 | 66, 66, 66 | - | base-gray-800 | | ![Sample of gray 700.](https://help.fews.net/__attachments/a_e0b8f4ae2bd90984b9cdacf9cbe56129e624f4a351997516b1218e03fe403a67/gray-700.png?cb=ab7a1cce506537a88b52eef5426c7331) Gray 700 | #585858 | 88, 88, 88 | - | base-gray-700 | | ![Sample of gray 600.](https://help.fews.net/__attachments/a_aa2c7e9b2a6e6edbde5318cd11a6ef428cbd052c54d2a35685d639ce2fc10a43/gray-600.png?cb=1e297143769a78da2ab752a8296ff6c5) Gray 600 | #808080 | 128, 128, 128 | - | base-gray-600 | | ![Sample of gray 500.](https://help.fews.net/__attachments/a_d4ec2881dee7808c2d2e194e8335f75d1fd657025cb3ed335b1052a39273520c/gray-500.png?cb=c44173c127aa11718ff2a2cd423b60ea) Gray 500 | #ADADAD | 173, 173, 173 | - | base-gray-500 | | ![Sample of gray 400.](https://help.fews.net/__attachments/a_062a8550b13fed393d64ee25c95a53c23ac5f51e1b2d7b989b731d5b31b16c0b/gray-400.png?cb=96cb4d82ce42e4cc0c1b1847d668d110) Gray 400 | #D1D3D4 | 209, 211, 212 | - | base-gray-400 | | ![Sample of gray 300](https://help.fews.net/__attachments/a_4f8cac010727a70434a9efd6d75997171e26d5d6b01afe601e8697cae0b2cd5b/gray-300.png?cb=840b36a9a554adc33468acc5339528fd) Gray 300 | #E6E7E8 | 230, 231, 232 | - | base-gray-300 | | ![Sample of gray 200.](https://help.fews.net/__attachments/a_df9fc1a1e4e6f3c395f3a257c82928d2cfb27b3f76264cd8aaf9da69ddc443ed/gray-200.png?cb=d16f975028ee4da3556f3b6d96977320) Gray 200 | #F4F5F5 | 244, 245, 245 | - | base-gray-200 | | ![Sample of the lightest gray, gray 150.](https://help.fews.net/__attachments/a_10ffdc232159b7182bf4aec7aff802f1d7111af1e05cbc895ab859118af221f9/gray-150.png?cb=021ab889f6435536ae299f141a80759b) Gray 150 | #FAFAFA | 250, 250, 250 | - | base-gray-150 | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Capitalization FEWS NET uses sentence case for most writing. Sentence case only capitalizes the first word of each string of text and any proper nouns. Using sentence case makes it easy to scan FEWS NET writing for important proper nouns like countries or organization names. Use title case for titles and subtitles that have 6 or fewer words on web pages and documents only. Title case capitalizes all words except for non-initial articles like "a, the, and", etc. When counting the number of words, "FEWS NET" counts as 1 word, and non-initial articles do not count. Use sentence case for all text in slide decks, including individual slide titles. ## Do * Use sentence case for page and document titles that are longer than 6 words. Example: "Historic high needs anticipated across Southern Africa through early 2025" * Use title case for web page and document titles that are shorter than 6 words. Example: "Acute Food Insecurity Data" as a web page title * Use sentence case for slide titles. Example: "Upcoming action items" * Use sentence case for visualization titles. Example: "Kilograms of maize that a goat can purchase in Gode, Somalia" * Use sentence case for text describing actions in a user interface. Example: "Submit form" on a button used to submit a form entry ## Don't * Capitalize words for emphasis. * Capitalize words that are not the first word in a text string or a proper noun. * Use title case for section headings. Use sentence case for all headings other than short titles or subtitles at the beginning of web pages or documents. ## Rules for technical writing Technical writing for FEWS NET documentation and FEWS NET product user interfaces should follow additional rules for the types of terms included in the table below. Don't use these rules for communication or reporting products. Above all, use your judgment. These rules should not be used so stringently that it looks like we have made a mistake. | **Term** | **Capitalization rules** | **Notes and examples** | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Actions in UI** | Cap first word of an action if referring to a specific button/action in the UI. | Do: * Click **Submit.** * Learn to submit data. * Click **Save selection**. Don't: Learn to Submit data. | | **Dashboard** | Capitalized when referring to a specific dashboard by name. Regular sentence case otherwise. | Do: * **Data Freshness Dashboard** * This dashboard... Don't: * Data Freshness dashboard * Data freshness dashboard * This Dashboard | | **Dashboard names** (e.g., Crop Assessment, Data Freshness) | Title case and use Dashboard at the end. | Do: * **Data Freshness Dashboard** * This dashboard... Don't: * Data Freshness dashboard * Data freshness dashboard * This Dashboard | | **Data fields** | Sentence case in UI. Always cap and bold when referring to an item in the UI. Regular sentence case if not referring to a UI item. | * Add **Total kcals consumed** * Total kcals consumed by a household in the reference year from this livelihood strategy | | **Data point types** * (Livelihood/Community/Seasonal/Baseline) Activity * Annual Production Performance * Coping Strategy * Crop/Livestock Production (note, these may also be metadata options such as in the LEX UI legends) * Event/s * Expandability Factor * Fact/s * Hazard/s * Livelihood Strategy * Market Prices * Occurrences * Phases * Threshold * Value/s * Wealth Group | Title case when used as a technical term. | Do: * Import Acute Food Insecurity Phases * To refresh the Data Point Facts... * The value of... Don't: * The Value of... | | **Topics/Domains** (including Semi-Structured) | Title case when referring to the domain or used as a technical term. | | | **Metadata** **categories** **(common)** * Classified products * Common * Community * Country/ies * Country groups * Currency/ies * Market * Metadata * Product * Relationship * Unit of measure | Sentence case in UI. Always cap and bold when referring to an item in the UI. Regular sentence case if not referring to a UI item or using as a technical term. | Do: * Narrative metadata (in UI) * Click **Narrative metadata**. | | **Metadata** **categories (technical)** * Admin Unit * (Livelihood Zone) Baseline * Characteristics Group * Data Usage Policy * Geographic Unit * Hazard Category * Indicator * Livelihood Category * Livelihood Zone * Scenario * Season * Seasonal Activity Type * (Data) Source Document * (Data) Source Organization * Wealth Category * Wealth Group Characteristic | Title case | | | **Metadata options** This also includes hard coded options such as Livelihood Strategy Types. | Sentence case in UI. Always cap and bold when referring to an item in the UI. Regular sentence case if not referring to a UI item. | Do: * Current situation (in UI) * Click **Current situation**. * The current situation in the country... | | **Style names** (e.g., Brand Black, Text XL Bold) | Title case | | | **System objects** * Collection Period * Correction * Data Collection * Data Point/s * Data Series * Dataset * Domain * Group * Label * Permission * Shapefiles * User * Visualization | Title case | Do: User should always refer to a specific object in the interface and therefore be capitalized. Don't: Use "user" as a generic term (e.g., the user will) in documentation. | | **Platforms** FDE, FDW, KB, EWX, FEWS Tools, LEX etc. | Title case, spell out acronyms before using (except for FEWS NET) | Do: * FEWS NET Data Explorer * Knowledge Base | | **Tags** | Tags should be all lower case unless they are using an acronym which should be all caps. | | | **Visualization titles and subtitles** | Visualization titles and subtitles should be in sentence case. | | | **Visualization types**(e.g., Acute Food Insecurity Map, Exchange Rate Chart) | Treat the same as dashboards. When referring to a specific visualization type, use title case, including the type of visualization at the end (e.g., chart, map). | Do: * **Exchange Rate Chart** * The map shown here... Don't: * Acute Food Insecurity map * Exchange rate chart * The Map shown here... | | **Other** * Administration * As-is * Analysis * Assumptions * Data * Email * Entry * Filter * Home page * Management * News articles * Offline * Outlooks * Processing * Report/s * Report items * Supporting documents * Supporting evidence * Uploads | Sentence case | These are additional words that were specifically considered and were determined to fall within the normal capitalization rules stated at the top of the page. | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Chart Body ![Example of a line chart using brand colors.](https://help.fews.net/__attachments/a_9a90ac7dd9eb8ff6b9343329d53c7519eea8ea3b1649861e18843a0ffadc5165/BrandDocs_Shape_15.png?cb=46e973e9aaefa6c12bcbc13bfac46ffc) *** ** * ** *** ## Usage ### General **Use alternating bands in tables to improve readability.** See [specifications](https://help.fews.net/brand/chart-body.md#Chart-content-background). **Avoid featuring missing data.**To the extent possible, try to use charts that include data for all the locations included in the scope of the chart. **Choose a meaningful timeframe that isn't arbitrary.** To the extent possible, when selecting a timeframe for a chart, choose one that best illustrates the key message or trend you want to highlight. **Use brand styles.**In general, use Segoe UI or Open Sans for all text throughout the chart. Pay attention to font weight (for example, use Semibold for titles) and colors. **Do not include descriptive text or text boxes.** The footer may be used to include footnotes with clarifications or additional explanation that need to accompany the visualization. If the visualization appears in context of narrative text, consider including a note in the surrounding text instead of in the visualization itself. ### Axes **Ensure legibility.** Choose a readable font size and color contrast for axis labels and numbers. Ensure that even those with visual impairments can clearly read the chart. **Keep it simple.** Keep the axis design simple and avoid unnecessary design elements that don't add to the interpretation of the data. **Use descriptive labels.** Always label both the x-axis (horizontal) and y-axis (vertical) with clear, concise descriptions of what the data represents. If the x-axis includes a time scale, no axis label is needed. **Different time scales.** When showing data from different time scales, it should be easily distinguishable. **Include units.** Specify the unit of measurement in the axis label (e.g., percentage, currency, time) to avoid ambiguity. **Know when to use linear vs. logarithmic scales.** Use a linear scale when values increase at a steady rate, and a logarithmic scale for values that grow exponentially. Make sure the scale fits the nature of your data. **Start at zero.**As much as possible, it is strongly recommended to begin the x-axis and y-axis at zero to avoid distorting the data. **Rotate labels if needed.** For long or densely packed labels, consider rotating them (especially on the x-axis) to 40° angles to prevent overlap. Consider reducing tick marks or shortening labels rather than packing labels. **Use subtle gridlines.** Use light, subtle gridlines to help align data points to the axes without distracting from the main chart. Keep them muted (e.g., light grey) so they don't overpower the data. **Place labels appropriately.** Ensure that axis labels are placed close to their respective axes for easy reference without interfering with the data. **Follow brand guidance for dates.** If space permits, use the format Month YYYY. Otherwise, abbreviate to MMM YYYY (ex. Mar 2025 or Sept 2021). For a time series spanning multiple years, you might label the x-axis like: Jan 2023 \| Jul 2023 \| Jan 2024 \| Jul 2024 \| Jan 2025. See [Dates](https://help.fews.net/brand/dates.md). **Use consistent number formatting.** If you're using decimal points, ensure consistency throughout the axis. Avoid mixing formats like "0.5" and "5,000" without explanation. If using currency, format consistently as "$1M, $2M, $3M" instead of mixing "$1,000,000" and "$2M." **Format large numbers succinctly.** Use abbreviations for large numbers (e.g., "K" for thousands, "M" for millions) to avoid overcrowded labels. Use "10K" instead of "10,000." **Don't crowd ticks and labels.** Too many tick marks or labels can clutter the chart. Use fewer ticks or round numbers to make the axis easy to read. **Don't use arbitrary time intervals.** For time series data, use regular intervals (e.g., every month, year, or quarter) to maintain clarity. **Don't disproportionately scale the chart.** The aspect ratio of the chart should not distort the data. Stretching or compressing the axes can exaggerate trends. Use a consistent ratio to reflect the true relationship between variables. ### Colors **Confirm 508 compliance.** Ensure that colors have sufficient color contrast to meet 508 compliance standards. Section 508 a federal law that requires federal agencies to make their communication accessible to people with disabilities. Meeting the **color contrast** requirement ensures the visual presentation of text and images of text has a contrast ratio of at least 4.5:1. Tools such as [++webaim.org++](https://webaim.org/) are helpful for checking color contrast. See [++Color safety and recommended combinations++](https://help.fews.net/brand/colors.md#Color-safety-and-recommended-combinations). **Use shapes and patterns.** Instead of just colors, consider using shapes or patterns to differentiate items, especially for colorblind accessibility. **Don't use similar shades of color.** Avoid using shades of the same color that are too difficult to distinguish **Avoid using more than 6 data colors per chart.** Consider using symbols, dashed lines, and other techniques rather than using more colors than needed. *** ** * ** *** ## Components * Chart content frame * Lines * Bars * Axis titles * Y-axis labels * Text * Tick * X-axis labels * Text * [Pop-overs](https://help.fews.net/brand/interactive-components.md#Popover) and [tooltips](https://help.fews.net/brand/interactive-components.md#Tooltip), for **live charts** *** ** * ** *** ## Padding and spacing * Chart body fills full width of the visualization frame * Chart body height is fixed to the minimum height necessary to clearly convey the relevant data * **0px** top * **8px** bottom * **16px** when x-axis title is present * **52px** right side * **16px** when y-axis title is present * **16px** left side * **16px** horizontal between y-axis title(s) and y-axis labels * **2px** horizontal between y-axis label and tick * **13px** horizontal padding between left- and right-most x-axis labels and y-axes * **8px** vertical between x-axis and x-axis labels * **24px** between x-axis labels and x-axis title, when present * **60px** minimum vertical space between y-axis labels *** ** * ** *** ## Layout and responsiveness * Chart content frame width and height fills full space available * Y-axis titles are vertically centered to y-axis * X-axis title is horizontally centered to x-axis, when present * Equal vertical space between each y-axis label * Equal horizontal space to the left and right of each x-axis label * Left-side y-axis label text hugs right, right side text hugs left * Y-axis label text is vertically centered to y-axis tick, including bottom "0" label and top label * Chart content frame scales down horizontally as width decreases until 609px width is reached, after which width and height scale down proportionally. * Note axis titles and labels remain the same size *** ** * ** *** ## Fills ### Chart content background Every chart should have rows of alternating colors to delineate divisions of y-axis values. Colors should alternate between **Brand** **White** (#FFFFFF) and **Gray 150** (#FAFAFA). ### Data When representing data series using lines or bars, use colors in the following order. These colors were chosen to ensure the best possible contrast for 6 lines against each other and a White/Gray 150 fill. Charts should not contain more than 6 line/bar colors. 10 additional colors are included in the sequence for rare cases where more than 6 colors are needed. There are [additional specifications](https://docs.google.com/document/d/1cC7yI3fjmrQGZJxnSaZEkX-Cb2MEyaZotK9Dlde8URU/edit?usp=drive_link) for charts in livelihoods products (staff only). | **Order** | **Color style name** | **Hex value** | **RGB value** | |-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------| | 1 | ![Sample of Blue 600.](https://help.fews.net/__attachments/a_c62547c25c0c569b2d11942431e82660983b47d51d7e22807d12f2654ec2100b/blue-600.png?cb=31b7d6b4f7bb2261559294636767dcec) Blue 600 | #426FBC | 66, 111, 188 | | 2 | ![Sample of Pine 500](https://help.fews.net/__attachments/a_d6a1fcbf4e5b6628c62e0da49a66125cae7fef88060fd22770f3d324c1c287fe/pine-500.png?cb=5f8b715a048f8a18c3323b5dd8395cdb) Pine 500 | #319B86 | 49, 155, 134 | | 3 | ![Sample of Charcoal 600](https://help.fews.net/__attachments/a_fd488efa28b36b7d5f31e0586880e128c181e6abc4013b231b86277e30948550/charcoal-600.png?cb=9299d15bb8e137bcf8a95d61c4f9e801) Charcoal 600 | #3A454C | 58, 69, 76 | | 4 | ![Sample of orange 500](https://help.fews.net/__attachments/a_a111cd4f7183f40b1c1dd72c4fca38f9825afd6bc290c32a1e30292710954dec/orange-500.png?cb=a9ab00e4eaa73bffa5eb64389cdf2422) Orange 500 | #BA6B55 | 186, 107, 85 | | 5 | ![Sample of red 500](https://help.fews.net/__attachments/a_db8ee5bee74ce5500c5c5982603a8ee88458be4577d204c01a55d606efa6d802/red-500.png?cb=2f25fface5bd6219171c2e316a817cfb) Red 500 | #7A5A5A | 122, 90, 90 | | 6 | ![Sample of steel 600](https://help.fews.net/__attachments/a_1f0fe1b4c8ab2ab30fe3e8ab694c6dc49006e5197806f3e4db1588b784edd55a/steel-600.png?cb=ed9cb4f78a742d8349259b084a546ed6) Steel 600 | #55747E | 85, 116, 126 | | 7 | ![Sample of olive 500.](https://help.fews.net/__attachments/a_1f12f5692ef27b51b745e8f8246de2f1401e2b2f5d21666ebd70e60090377a51/olive-500.png?cb=a055c183d07a6ab589ed2bbcf9e1c22e) Olive 500 | #707257 | 112, 114, 87 | | 8 | ![Sample of purple 500.](https://help.fews.net/__attachments/a_7b9018b12577acdefac960614e76999bdfa97f909aafdd319385e76e894a39ed/purple-500.png?cb=340dc6a76f0ed3f5acb3804261dc02c2) Purple 500 | #A173B3 | 161, 115, 179 | | 9 | ![Sample of blue 700.](https://help.fews.net/__attachments/a_1e55cd3b8a701d3ce78b8c5db222681c4db8cab06ac366d87255345849cf8317/blue-700.png?cb=6b0aae8308a335b999b25bcc473b8ad4) Blue 700 | #305088 | 48, 80, 136 | | 10 | ![Sample of pine 700.](https://help.fews.net/__attachments/a_3d6f9f6d64726fe83a2b5b1f1190c256d9df9b562afb23154f4a5cc7f2454901/pine-700.png?cb=7ce24751cd75b4f38698105e1e203caa) Pine 700 | #107157 | 16, 113, 87 | | 11 | ![Sample of charcoal 500.](https://help.fews.net/__attachments/a_bd72995d41c62ea2223e22214b9b806cc9d37420724d0786c156950b255f64c5/charcoal-500.png?cb=b7d99ca7fad2d67dd05c3f5f0e8c44db) Charcoal 500 | #555E62 | 85, 94, 98 | | 12 | ![Sample of orange 600.](https://help.fews.net/__attachments/a_852012a146569fa52dd336a7bb52e76daa012396b2bb052a22a6cdc3b7f27701/orange-600.png?cb=84ea437972b2a3a6bd8dc0cf67f3818f) Orange 600 | #B95A38 | 185, 90, 56 | | 13 | ![Sample of red 600.](https://help.fews.net/__attachments/a_c617a726d109afae276114f5324db0a7065ef59859346d63c7de6421bd244bfb/red-600.png?cb=8a55b89d48208f5196afa8bd4d877658) Red 600 | #6D4140 | 109, 65, 64 | | 14 | ![Sample of steel 500.](https://help.fews.net/__attachments/a_76ec803fe6a8aa961ce749181ab43d4acde66c1a3b1c6426797a525dfeb68954/steel-500.png?cb=5ce27b6af8387b5904562b9b759a37d6) Steel 500 | #6A8188 | 106, 129, 136 | | 15 | ![Sample of olive 600.](https://help.fews.net/__attachments/a_45e175b58a6a6edc243b6ef05adf0115c188e9ebc0dd55dab54e45b0641a3a72/olive-600.png?cb=9894255eb0fc7c97e1487f4f85f5410e) Olive 600 | #60613A | 96, 97, 58 | | 16 | ![Sample of purple 600.](https://help.fews.net/__attachments/a_b705c1bcbd9d99aa71adc03971f9900296e7340f173a4d4582a1f40536be1b1c/purple-600.png?cb=0bc5d21ea131281745234a7cf8d53455) Purple 600 | #784595 | 120, 69, 149 | *** ** * ** *** ## Lines | **Type** | **Thickness** | **Color** | **Additional Specifications** | |-----------------------------|---------------|--------------------|----------------------------------------------------------| | Axis | 1px (1pt) | Gray 500 (#ADADAD) | * Borders left, right, and bottom of chart content frame | | Y-axis tick (left of axis) | 1px (1pt) | Gray 500 (#ADADAD) | * 8px length | | Y-axis tick (right of axis) | 1px (1pt) | Gray 400 (#D1D3D4) | * Fills width of chart content frame | | Line (Data) | 4px (3pt) | See Fills \> Data | | *** ** * ** *** ## Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Font** | **Line height** | **Color** | **Additional specifications** | |----------------|----------------------|-----------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Axis title | 16px (12pt) Semibold | 120% | Brand Black Dark (#090B09) | * X-axis title should be horizontal * X-axis title may be omitted if the unit is clear from the chart title * Y-axis title should be vertical | | Axis label | 14px (10.5pt) Bold | 120% | Brand Black Dark (#090B09) | * X-axis labels should be at a 40 degree angle * Y-axis labels should be horizontal * Dates should use one of the following formats: * YYYY (e.g., 2016) * Mon-YY (e.g., Feb-17) * DD Mon (e.g., 1 Aug or 22 Aug) | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Color Safety and Recommended Combinations Only specific combinations of brand colors have high enough color contrast to be recommended for use in text or graphics. See the [color contrast quick reference sheet](https://drive.google.com/file/d/1pTd2AhJXkfDe8zmH5F0uU5LVoM4t-b1D/view?usp=sharing) for a table of all recommended brand color combinations and uses. For text, aim to choose a text color that has a minimum 7:1 contrast ratio with its background color. Meaningful graphics like icons, shapes, and user interface elements should aim to achieve a minimum 4.5:1 contrast ratio with their background color. [Online tools](https://webaim.org/resources/contrastchecker/) are available to check the contrast ratio between two colors. These recommendations are meant to comfortably exceed the minimum color contrast requirements set by the Web Content Accessibility Guidelines (WCAG). Always aim for the highest possible contrast ratio between colors. ## Recommended color combinations for text and graphics ![Recommended Color Contrast options for text and graphics.](https://help.fews.net/__attachments/a_a541fbcda28377ebebf3b37ea89318945c51264a90c127ba7938e5c352aff745/Color%20Contrast%20Recommended.png?cb=b42ba00a0014a53e55f15fad8010e72b) ### Values | **Background color** | **Hex value** | **Foreground color** | **Hex value** | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| | ![Sample of Brand primary.](https://help.fews.net/__attachments/a_28c9429d5a1503407d60adcfd37a3233ff4a5f6ede496a71d85c5c7655699fd0/green-700.png?cb=71d50daf42c8cdf5b01eea40d1965f83) Brand Primary | #096640 | ![Sample of brand white.](https://help.fews.net/__attachments/a_196d33124dd72627f0ad634921e70dc259abe194975fe0e1730e85da23a1252d/gray-100.png?cb=236a48d7a590218ab600e9a65ebe36f4) Brand White | #FFFFFF | | ![Sample of brand black.](https://help.fews.net/__attachments/a_ab2b1185a9495e8003d91cf49c8c220280694d1c00664c62d1cf1ecaa577327e/black-800.png?cb=97f50883ac1b8ae339b692f4e8c3ec4b) Brand Black | #212721 | ![Sample of brand white.](https://help.fews.net/__attachments/a_196d33124dd72627f0ad634921e70dc259abe194975fe0e1730e85da23a1252d/gray-100.png?cb=236a48d7a590218ab600e9a65ebe36f4) Brand White | #FFFFFF | | ![Sample of brand secondary.](https://help.fews.net/__attachments/a_8927d8f986ba1c3f14cfab7b9e5806cf10f7a03aea0989fe5aff27d8cef94182/sky-400.png?cb=dc2fc496c27d67c9dd22c3441a28e5fd) Brand Secondary | #BDDBD6 | ![Sample of brand black.](https://help.fews.net/__attachments/a_ab2b1185a9495e8003d91cf49c8c220280694d1c00664c62d1cf1ecaa577327e/black-800.png?cb=97f50883ac1b8ae339b692f4e8c3ec4b) Brand Black | #212721 | | ![Sample of brand secondary light](https://help.fews.net/__attachments/a_e9565c37b234e694702f1ce31511ae6dc54c4f5d01ef9c2bf417e2a8d24134e9/sky-200.png?cb=4bf904d9ecf2c4b3387d73a0ca608c94) Brand Secondary Light | #E4F1EF | ![Sample of brand black.](https://help.fews.net/__attachments/a_ab2b1185a9495e8003d91cf49c8c220280694d1c00664c62d1cf1ecaa577327e/black-800.png?cb=97f50883ac1b8ae339b692f4e8c3ec4b) Brand Black | #212721 | | ![Sample of brand white.](https://help.fews.net/__attachments/a_196d33124dd72627f0ad634921e70dc259abe194975fe0e1730e85da23a1252d/gray-100.png?cb=236a48d7a590218ab600e9a65ebe36f4) Brand White | #88BFB6 | ![Sample of brand black.](https://help.fews.net/__attachments/a_ab2b1185a9495e8003d91cf49c8c220280694d1c00664c62d1cf1ecaa577327e/black-800.png?cb=97f50883ac1b8ae339b692f4e8c3ec4b) Brand Black | #212721 | | ![Sample of brand white.](https://help.fews.net/__attachments/a_196d33124dd72627f0ad634921e70dc259abe194975fe0e1730e85da23a1252d/gray-100.png?cb=236a48d7a590218ab600e9a65ebe36f4) Brand White | #FFFFFF | ![Sample of brand primary.](https://help.fews.net/__attachments/a_28c9429d5a1503407d60adcfd37a3233ff4a5f6ede496a71d85c5c7655699fd0/green-700.png?cb=71d50daf42c8cdf5b01eea40d1965f83) Brand Primary | #096640 | | ![Sample of gray 400](https://help.fews.net/__attachments/a_3e696f83d9c00525e574d7f7a10d75a454f427d40d9eff93a9f2a38795b62770/gray-400.png?cb=96cb4d82ce42e4cc0c1b1847d668d110) Gray 400 | #D1D3D4 | ![Sample of brand black.](https://help.fews.net/__attachments/a_ab2b1185a9495e8003d91cf49c8c220280694d1c00664c62d1cf1ecaa577327e/black-800.png?cb=97f50883ac1b8ae339b692f4e8c3ec4b) Brand Black | #212721 | | ![Sample of Gray 300](https://help.fews.net/__attachments/a_2897dc82c2363b7e23a8e4ac31417b30eca16314c700a631d416d2aadd921c1e/gray-300.png?cb=840b36a9a554adc33468acc5339528fd) Gray 300 | #E6E7E8 | ![Sample of brand black.](https://help.fews.net/__attachments/a_ab2b1185a9495e8003d91cf49c8c220280694d1c00664c62d1cf1ecaa577327e/black-800.png?cb=97f50883ac1b8ae339b692f4e8c3ec4b) Brand Black | #212721 | ## Recommended color combinations for graphics only Brand color combinations with contrast ratios that are 4.5:1 or greater but less than 7:1 are recommended for graphics only. Any color combinations listed as "Graphics only" on the [color contrast quick reference sheet](https://drive.google.com/file/d/1pTd2AhJXkfDe8zmH5F0uU5LVoM4t-b1D/view?usp=sharing) fall into this category. For example, Brand Primary and Brand Secondary may be used against each other for graphics. Brand Accent may be used against white, and Brand Primary may be used against lighter shades of gray such as Gray 400. ![Color Contrast options for use in Graphics Only](https://help.fews.net/__attachments/a_b8e1f0a9f69446e1e82026f9781c4b55524c142721e35050d931e585fbd9193a/Color%20Contrast%20Graphics%20Only.png?cb=137afbdbb0bb0429c3b0dbb6ef350e6e) ## Minimum requirements and prohibited color combinations The WCAG 2.0 level AA accessibility standard requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. WCAG 2.1 requires a contrast ratio of at least 3:1 for meaningful graphics and user interface elements. These are the minimum color contrast requirements for combinations of FEWS NET brand colors, and any color combinations that fall below these standards are prohibited. Some examples of foreground / background color combinations that are prohibited for both text and graphics include: Brand Black / Brand Primary; Brand Secondary / Brand White; Gray 500 / Brand White; Brand Black / Gray 500. ![Color Contrast options that are prohibited.](https://help.fews.net/__attachments/a_9d8c228d1ef8ee1d3419b30086747c8ff7551254d5a6fd2b8b06e9bec93b95d4/Color%20Contrast%20Prohibited.png?cb=2ddc574f08e3c0d28588742dc8060575) *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Colors ![FEWS NET's primary brand colors.](https://help.fews.net/__attachments/a_b5c605810d9a56b8721bd989465d15ccc4f2d0e00f23f0c2b382972a4a724ed0/Brand%20Colors%20Primary.png?cb=a01bd84bc49a96e828043b0b2f98b835) FEWS NET's color palette is designed to represent our global expertise in a modern, engaging and approachable way. Use FEWS NET brand colors consistently and accurately to maintain a safe brand that is accessible to all. See Color Safety and Recommended Combinations for guidance on using brand colors together. * [Brand Colors](https://help.fews.net/brand/brand-colors.md) * [Data Visualization Colors](https://help.fews.net/brand/data-visualization-colors.md) * [Livelihoods Products](https://docs.google.com/document/d/1cC7yI3fjmrQGZJxnSaZEkX-Cb2MEyaZotK9Dlde8URU/edit?usp=drive_link) (staff only) * [Color Safety and Recommended Combinations](https://help.fews.net/brand/color-safety-and-recommended-combinations.md) * [Base Color Palette](https://help.fews.net/brand/base-color-palette.md) *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Data Visualization Colors ## Using data visualization colors Use data visualization colors to represent data via charts, maps, and other visualizations that require many colors for clear understanding. These colors were selected for accessibility, readability, and contrast against the IPC data colors. Refer to [Visualizations](https://help.fews.net/brand/visualizations.md) for detail about when and how to use these colors. While these colors are intended to help maximize accessibility, not all combinations of these colors will be color safe, and you are responsible for verifying the usability and accessibility of any data visualizations you create using these colors. ![Table of visualization colors.](https://help.fews.net/__attachments/a_b8ccf4f6825cf33e903307745cda03489939b90cddb7c968734c41858ed4cee0/Visualization%20Colors.png?cb=aefdde5173cab39886bde65057a8e650) ## Color values | **Color style name** | **Hex value** | **RGB value** | **Token name** | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|-------------------| | ![Sample of Red 800.](https://help.fews.net/__attachments/a_df3bd39456e8a127c9b5b41e8c99dbe29cd129d0c2a51e3b5df2de8181de1c6c/red-800.png?cb=bb4493a4e38d9808056139d626ea6779) Red 800 | #451914 | 69, 25, 20 | base-red-800 | | ![Sample of Red 700.](https://help.fews.net/__attachments/a_9d5a10301e7a0f3fd8cc4a8eae1d8925d48ac49a585bb2a29ea26f5db1d32497/red-700.png?cb=3c94dec7a62db305aff9d9aae0f7d6db) Red 700 | #541E18 | 84, 30, 24 | base-red-700 | | ![Sample of Red 600.](https://help.fews.net/__attachments/a_8b677aa83c350df0fc6865b4dbf9f613c38d4e3a79adda8c59838079ce47d179/red-600.png?cb=8a55b89d48208f5196afa8bd4d877658) Red 600 | #6D4140 | 109, 65, 64 | base-red-600 | | ![Sample of Red 500.](https://help.fews.net/__attachments/a_552efa85535f59e40590f049ee907132b531cdaa1338bb53cf631b62f3ad0423/red-500.png?cb=2f25fface5bd6219171c2e316a817cfb) Red 500 | #7A5A5A | 122, 90, 90 | base-red-500 | | ![Sample of Red 400.](https://help.fews.net/__attachments/a_b5af00e4e73427a2a199b4f174d7299da4e81284f9d70146309eb45374718e57/red-400.png?cb=0a0fb2837f7cd341cd13de7a2cfe459a) Red 400 | #A88A8A | 168, 138, 138 | base-red-400 | | ![Sample of Orange 700.](https://help.fews.net/__attachments/a_1cf356202eefcbcea6ebb31d2a3182e5e99e0643f2ac86002b74cd0ac0da9975/orange-700.png?cb=9dac7cbca8f40c28b3bf276e51d52dd1) Orange 700 | #AB4B1E | 171, 75, 30 | base-orange-700 | | ![Sample of Orange 600.](https://help.fews.net/__attachments/a_c62cc6165cffec8dba3596479916528bcc183866916783805e3833b6746e65a0/orange-600.png?cb=84ea437972b2a3a6bd8dc0cf67f3818f) Orange 600 | #B95A38 | 185, 90, 56 | base-orange-600 | | ![Sample of Orange 500.](https://help.fews.net/__attachments/a_586a834ec725476be4a8793f500e94054dc170c9ad9e0278bf19ad75403014f4/orange-500.png?cb=a9ab00e4eaa73bffa5eb64389cdf2422) Orange 500 | #BA6B55 | 186, 107, 85 | base-orange-500 | | ![Sample of Orange 400.](https://help.fews.net/__attachments/a_194190d51ad998eeeadf1f6fbb286a48c2f076c2cefce833323435afa542daa0/orange-400.png?cb=1fa462d977cd8b8579b3168b18fc9a76) Orange 400 | #D6A79A | 214, 167, 154 | base-orange-400 | | ![Sample of Yellow 600.](https://help.fews.net/__attachments/a_85a2ce5c56498ae935cc53cc104de883822f1890b52cc7ce6b58fb1917891722/yellow-600.png?cb=a52534b6ab2507d2169caab783fe0c86) Yellow 600 | #FDD835 | 253, 216, 53 | base-yellow-600 | | ![Sample of Yellow 500.](https://help.fews.net/__attachments/a_d05dd066234c7c230b841ea5df56c8af7a447e5cad2f24d7b8dc53013fdfd8b9/yellow-500.png?cb=fd8e5b66a1e34cb846e46260e21ceb59) Yellow 500 | #FFEE58 | 255, 238, 88 | base-yellow-500 | | ![Sample of Yellow 400.](https://help.fews.net/__attachments/a_1f23f7ebe7d2a17ac1e35307a67deaf72a15f4c299dd1a215b6c48223e035f85/yellow-400.png?cb=45fccf5bfe5fa77932794414d203c14b) Yellow 400 | #FFF59D | 255, 245, 157 | base-yellow-400 | | ![Sample of Yellow 200.](https://help.fews.net/__attachments/a_19764def338053d18a8435e28886e18a2c9b901503671f3e050008af35fdfa58/yellow-200.png?cb=0a468c6cab7893272b5658fa25ebedee) Yellow 200 | #FFF9C4 | 255, 249, 196 | base-yellow-200 | | ![Sample of Olive 700.](https://help.fews.net/__attachments/a_688d5cf39f860c07c2f79524bb38a4f388df36bfe2bc8ae05167e0b39e733025/olive-700.png?cb=359aa036b88ea1646a6e4f8317c49af3) Olive 700 | #484817 | 72, 72, 23 | base-olive-700 | | ![Sample of Olive 600.](https://help.fews.net/__attachments/a_31a68d7cd7dd0212e8bd37ed6db0da075b7ab24a086b99e6fb79164372b867c3/olive-600.png?cb=9894255eb0fc7c97e1487f4f85f5410e) Olive 600 | #60613A | 96, 97, 58 | base-olive-600 | | ![Sample of Olive 500.](https://help.fews.net/__attachments/a_dd42920f05a0c32b2082bc29a82ccb2deac06cd7d830a99a43606d6def148dfb/olive-500.png?cb=a055c183d07a6ab589ed2bbcf9e1c22e) Olive 500 | #707257 | 112, 114, 87 | base-olive-500 | | ![Sample of Olive 400.](https://help.fews.net/__attachments/a_88c4abbe0f0487498abcebe36de5b372ceaf13605f16f581415c5b8e29c4a2e7/olive-400.png?cb=69fcda725d5642c008fc45a4ba621028) Olive 400 | #9B9D80 | 155, 157, 128 | base-olive-400 | | ![lime-600.png](https://help.fews.net/__attachments/a_60a29b102db65d55f99d987b567b06b27640f624d24d07e0f75a8f345526d8b9/lime-600.png?cb=8fb18512e3b6573445d3fb35cb337771) Lime 600 | #689F38 | 104, 159, 56 | base-lime-600 | | ![Sample of Lime 500.](https://help.fews.net/__attachments/a_0bb305fcf7c9046a16ceb3f9f3c1187ecbde40f66ed773e37ef075a90fc46b1c/lime-500.png?cb=27aeba81f89e0ae882ed7854f6d99a4e) Lime 500 | #8BC34A | 139, 195, 74 | base-lime-500 | | ![Sample of Lime 400.](https://help.fews.net/__attachments/a_22eef28317cea98c527e8ab4c09d67abe634d32d4bc82a0b76f4281edbb3d092/lime-400.png?cb=b4bd4766c4920c2b959fb46a88df030c) Lime 400 | #AED581 | 174, 213, 129 | base-lime-400 | | ![Sample of Lime 200.](https://help.fews.net/__attachments/a_235781af88a14f5eb96c4e97259ff8d78ab1720451567b7469d821cfcafc7bbc/lime-200.png?cb=bee7be9d312776d4449961e68e0dc7b0) Lime 200 | #DCEDC8 | 220, 237, 200 | base-lime-200 | | ![Sample of Pine 800.](https://help.fews.net/__attachments/a_46a6006e30004bccee72db4c9e2219f5e5b204bbe9566c03d84e26681a58c349/pine-800.png?cb=ea8f400aabc4c807cdb5113546d15ed0) Pine 800 | #0C5D40 | 12, 93, 64 | base-pine-800 | | ![Sample of Pine 700.](https://help.fews.net/__attachments/a_30530733f1ffa227b84364c670db5104b3b44fc83bf810d4fec176e853c39720/pine-700.png?cb=7ce24751cd75b4f38698105e1e203caa) Pine 700 | #107157 | 16, 113, 87 | base-pine-700 | | ![Sample of Pine 600.](https://help.fews.net/__attachments/a_a49042cd6024add9a20d0cf3ed7cd2df50ab4cdce3ebf81b762cb043d847a15a/pine-600.png?cb=3eccd67333f2335ed0ac0560f8b04906) Pine 600 | #2C8C79 | 44, 140, 121 | base-pine-600 | | ![Sample of Pine 500.](https://help.fews.net/__attachments/a_23e613d207cd096496312964e4cf001ea4bbd99442f24fb19be0493d288caa03/pine-500.png?cb=5f8b715a048f8a18c3323b5dd8395cdb) Pine 500 | #319B86 | 49, 155, 134 | base-pine-500 | | ![Sample of Ocean 400.](https://help.fews.net/__attachments/a_e5660eb611a765b6da25070bc1d19bd56f5ef85f015794ef341c1efb303644fe/ocean-400.png?cb=12e3d24b51ca9de80cf0fb639e4b2d64) Ocean 400 | #BCDAE9 | 188, 218, 233 | base-ocean-400 | | ![Sample of Blue 700.](https://help.fews.net/__attachments/a_607f57c0d8b3671f2c703fa742a0e0c74fca03daad029b33ae53013373a964bb/blue-700.png?cb=6b0aae8308a335b999b25bcc473b8ad4) Blue 700 | #305088 | 48, 80, 136 | base-blue-700 | | ![Sample of Blue 600.](https://help.fews.net/__attachments/a_108ef9cbdf66481c119469b4859f6120a0f8e6a1cb055af74ebbf746a2696f7f/blue-600.png?cb=31b7d6b4f7bb2261559294636767dcec) Blue 600 | #426FBC | 66, 111, 188 | base-blue-600 | | ![Sample of Blue 500.](https://help.fews.net/__attachments/a_75080cf5f41cfc758565af5f30d3947e0a556d51f4ed4d34a57436234e38a8f6/blue-500.png?cb=4ef25eb001622c65f567e19d1b3a10f5) Blue 500 | #688CCA | 104, 140, 202 | base-blue-500 | | ![Sample of Blue 400.](https://help.fews.net/__attachments/a_edddbd7beaca69c8f8ae6ef414b9fb32fe61176ac11688b33281827de4266c62/blue-400.png?cb=e91d293ed18b1b4761faf7f1caae12a4) Blue 400 | #A6BFE2 | 166, 191, 226 | base-blue-400 | | ![Sample of Purple 700.](https://help.fews.net/__attachments/a_bcccae4b01a65c7cf3db4dc4dfa5130619e1d7ed91129f1f8fb21cecba3b25e7/purple-700.png?cb=1f95e4d2bbabdce19c0d792d29a39b89) Purple 700 | #492674 | 73, 38, 116 | base-purple-700 | | ![Sample of Purple 600.](https://help.fews.net/__attachments/a_581f66f6b91a72ca19fa5e178f9229f8de4210d005de450ed606be53ac0f2a7d/purple-600.png?cb=0bc5d21ea131281745234a7cf8d53455) Purple 600 | #784595 | 120, 69, 149 | base-purple-600 | | ![Sample of Purple 500.](https://help.fews.net/__attachments/a_e8bb1d3253f977527bd209aeca8d0252b061e6d08db8ecc20716106711a06070/purple-500.png?cb=340dc6a76f0ed3f5acb3804261dc02c2) Purple 500 | #A173B3 | 161, 115, 179 | base-purple-500 | | ![Sample of Purple 400.](https://help.fews.net/__attachments/a_bcd158059366f215aecd8f3addffc08f10ddaf8cad61c352c311c939525723bd/purple-400.png?cb=22bc2e66b392bc707965a899be9285de) Purple 400 | #DBBEE0 | 219, 190, 224 | base-purple-400 | | ![Sample of Steel 700.](https://help.fews.net/__attachments/a_82f5174e1dde4b92ab41081a1ecc80a0e815f378165bcca973e00f4e16767064/steel-700.png?cb=41fa7445d6232a96e0bcfe0ac263ed1b) Steel 700 | #416371 | 65, 99, 113 | base-steel-700 | | ![Sample of Steel 600.](https://help.fews.net/__attachments/a_e51ba496d853b4a85f371912b580150f183a82f3004b49455576f1ad666ed731/steel-600.png?cb=ed9cb4f78a742d8349259b084a546ed6) Steel 600 | #55747E | 85, 116, 126 | base-steel-600 | | ![Sample of Steel 500.](https://help.fews.net/__attachments/a_1dc5f9f8c32fb733f86db44ee604ff45ecd4b9c6487b6a7953d2e4460c0bf7df/steel-500.png?cb=5ce27b6af8387b5904562b9b759a37d6) Steel 500 | #6A8188 | 106, 129, 136 | base-steel-500 | | ![Sample of Steel 400.](https://help.fews.net/__attachments/a_a11862cee437d4d09b6b025c1bcc3713964d34a39c574d216aed0e1da22c367d/steel-400.png?cb=c46f01d32ecbcc2c5d284ac1dd9da155) Steel 400 | #98A9AE | 152, 169, 174 | base-steel-400 | | ![Sample of Charcoal 700.](https://help.fews.net/__attachments/a_c18b8af0b50be552748c5ec3af247f13c67ecc4136a786d05868455a4b0b0177/charcoal-700.png?cb=fa88c0f346b90132d94babcdc2e60cd1) Charcoal 700 | #0C1D28 | 12, 29, 40 | base-charcoal-700 | | ![Sample of Charcoal 600.](https://help.fews.net/__attachments/a_5e627cc9c327888406942f024aca4a313d6d12eacb8161e0c1cd60be948e64e0/charcoal-600.png?cb=9299d15bb8e137bcf8a95d61c4f9e801) Charcoal 600 | #3A454C | 58, 69, 76 | base-charcoal-600 | | ![Sample of Charcoal 500.](https://help.fews.net/__attachments/a_612df9d32e79484bd3eb4f00e254a8249f7ffa3ad6c615196a2cd4dcb29efef3/charcoal-500.png?cb=b7d99ca7fad2d67dd05c3f5f0e8c44db) Charcoal 500 | #555E62 | 85, 94, 98 | base-charcoal-500 | | ![Sample of Charcoal 400.](https://help.fews.net/__attachments/a_fc6e04d1951639e9bab87315ea299aa91e1a63f9aa556b0620bb26bb9bf88428/charcoal-400.png?cb=eb0c410631739e05078eb5189be8d52f) Charcoal 400 | #7C888D | 124, 136, 141 | base-charcoal-400 | ## IPC data colors FEWS NET uses the Integrated Food Security Phase Classification (IPC) colors on maps that display IPC-compatible analysis. See [Map Body](https://help.fews.net/brand/map-body) for color values and usage details. | **Type** | **Phase** | **Fill color** | **Additional specifications** | |----------------------------------------------|----------------------|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| | Acute Food Insecurity and Acute Malnutrition | None / Minimal | #CDFACD; RGB: 205, 250, 205 | | | Acute Food Insecurity and Acute Malnutrition | Stressed | #FAE61E; RGB: 250, 230, 030 | | | Acute Food Insecurity and Acute Malnutrition | Crisis | #E67800, RGB: 230, 120, 000 | | | Acute Food Insecurity and Acute Malnutrition | Emergency | #C80000, RGB: 200, 0, 0 | | | Acute Food Insecurity and Acute Malnutrition | Catastrophe / Famine | #640000, RGB: 100, 0, 0 | | | Acute Food Insecurity and Acute Malnutrition | Famine Likely | #640000, RGB: 100, 0, 0 | * Overlay [++diagonal white stripes++](https://drive.google.com/file/d/1vKqEk9Vke2_1C4KJWaC8Clb-2XeEP_VD/view?usp=sharing) from bottom left to top right | | Chronic Food Insecurity | None / Minimal | #CDFACD; RGB: 205, 250, 205 | | | Chronic Food Insecurity | Mild | #CBC9E2; RGB: 203, 201, 226 | | | Chronic Food Insecurity | Moderate | #9E9AC8; RGB: 158, 154, 200 | | | Chronic Food Insecurity | Severe | #6A51A3; RGB: 106, 81, 163 | | | All types | Areas not analyzed | #BDBDBD; RGB: 189, 189, 189 | | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Dates FEWS NET uses the Month DD, YYYY format for dates in writing, and the YYYY-MM-DD format in places where dates are represented numerically as data, such as in spreadsheets, databases, or UI fields. These standards align with accepted date reference standards and aim to make FEWS NET's date references intuitive to the widest range of international users. ## Written date specifications ### General The day in a written date may include one or two digits. Always write out the full name of the month. Month names may be abbreviated to the first three letters when many months are written next to each other, such as in a table or on chart axis labels. If you abbreviate month names, do so consistently. Include a comma after the year when you write a full date in a sentence. No comma is necessary after writing a partial date or range of partial dates. ### Partial dates Use Month YYYY when the specific day is unknown or not relevant. When referring to dates inside a time range where the year has already been established, Month DD or "the DD of Month" with the appropriate suffix on the day may be used. Months or years may be referenced on their own in appropriate context. Days should always appear in conjunction with a month unless you are referring to a repeated action or step in a process that occurs on a specific day each month. ### Date ranges Use an en dash and no spaces to connect two dates that are part of a range, such as Month DD--Month DD, YYYY, or Month DD--DD, YYYY. In sentences, "from the DD to the DD of Month" and similar parallel constructions are also acceptable. Type an en dash on Windows computers using the keyboard shortcut **ctrl** +**minus sign (-)** . On Mac computers, hold down the **option** key while pressing **hyphen (-)**. In a date range between two years, the second year may be abbreviated to the last two digits if it is in the same century as the first year. **Example** Correct: 2023--24 Correct: 2023--2024 Correct: 1998--2005 Incorrect: 1998--05 ## Do * Use the Month DD, YYYY format for dates in written contexts. Example: "The parties reached an agreement on January 15, 2025, but incursions continued on the outskirts." * Use the YYYY-MM-DD format for dates in spreadsheets, databases, or UI fields. Note that hyphens, not en dashes, separate each section. Example: "2014-04-08" * Use partial dates when appropriate. Example: There have been multiple developments in January 2025. Heavy rains occurred from the 3rd to the 7th of January." * Use en dashes without spaces to connect date ranges. Example: "the 2023--24 rainy season" * Consistently abbreviate month names to the first three letters if it helps save space in visualization axis labels or a user interface. ## Don't * Connect date ranges with anything other than an en dash. Examples: "2023/24 rainy season," "June 2023 - June 2024" * Use numerical date formats in sentences. Example: "The conference took place on 12/24/2025" * Write the day before the month. Example: "10 April, 2025" * Abbreviate years that are not part of a range. Example: "The '23 rainy season" * Abbreviate month names in written contexts. Example: "See the Feb--Sep 2024 report" * Include a placeholder digit for a single digit day in non-numerical dates. Example: "The diplomatic party arrived on June 03, 2024" * Include a suffix on the day unless the day appears separately from the month. Example: "The market opened on January 25th, 2025" * Omit placeholder digits for numerical dates. Example: "2024-2-4" *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Documents ## Using templates * Links to templates may be found on the [FEWS NET Exchange Intranet](https://sites.google.com/fews.net/exchange2/work-essentials/templates?authuser=0) (staff only). * Always use FEWS NET document templates and do not modify the styles in any way. Upholding consistent document standards helps advance FEWS NET's global credibility and maintains compliance with branding and marking requirements. ## Formatting The following formatting standards apply to all FEWS NET internal and external written documents. Text formatting standards listed elsewhere in FEWS NET's brand documentation also apply to documents. Some format and style specifications vary between document types. Using the appropriate template is the easiest way to guarantee correct document styling. ### Text styles The following table contains text styles for generic, formal FEWS NET documents. Internal documents, US government documents, and analysis reports use different heading systems that are accessible via their respective templates. | **Typeface** | **Style** | **Size (pt.)** | **Font format** | **Color** | **Spacing (pt.)** | |--------------|-----------------|----------------|-----------------|-------------------------|--------------------------| | Georgia | Title | 24 | - | Brand Black (#212721) | 1.15, 4 before, 4 after | | Open Sans | Pre-title | 10 | Semibold | Brand Primary (#096640) | 1.15, 8 before, 4 after | | Open Sans | Subtitle | 14 | - | Brand Black (#212721) | 1.15, 4 before, 14 after | | Open Sans | Normal text | 10 | - | Brand Black (#212721) | 1.15, 10 after | | Open Sans | H1: Heading | 14 | Bold | Brand Black (#212721) | 1.15, 20 before, 8 after | | Open Sans | H2: Heading | 12 | Bold | Brand Primary (#096640) | 1.15, 18 before, 4 after | | Open Sans | H3: Heading | 11 | Semibold | Brand Accent (#A95B24) | 1.15, 16 before, 4 after | | Open Sans | H4: Sub-heading | 10 | Bold | Brand Black (#212721) | 1.15, 12 before, 6 after | | Open Sans | H5: Sub-heading | 10 | Semibold | Brand Primary (#096640) | 1.15, 8 before, 4 after | | Open Sans | Figure label | 10 | Semibold | Brand Black (#212721) | 1 | | Open Sans | Figure title | 10 | Semibold | Brand Black (#212721) | 1, | | Open Sans | Figure subtitle | 10 | - | Brand Black (#212721) | 1 | | Open Sans | Figure caption | 10 | Italic | Brand Black (#212721) | 1.15, 14 after | | Open Sans | Figure Source | 9 | - | Brand Black (#212721) | 1.15 | | Open Sans | Footer | 9 | Italic | Brand Black (#212721) | 1.15 | ### Page setup FEWS NET uses one-inch margins for documents. Margins may be slightly decreased to allow tables or figures to fit on one page. See Paragraph layout. ### Text and graphics alignment Left justify all text. Do not indent paragraphs. Left or right justify images and graphics. Do not center any elements on the page. ### Titles Titles should be brief, clear and descriptive. Titles should ideally fit on the first line and should be no more than two lines long. Use a subtitle if you need to convey additional detail. * Always write out the name of the organization in the document pre-title. * See [Capitalization](https://help.fews.net/brand/capitalization.md) for capitalization standards. ### Headings Always use built-in heading styles to separate sections. Review your document to make sure you applied headings in a consistent and intuitive way. * If headings require additional punctuation beyond a comma, periods should be used (e.g., "Annex 1. Definitions"). Exceptions include the title and subtitle of a document, which may use semicolons. * Headings are not numbered within text. * Headings are not the place to define acronyms. Acronyms should only be defined within the body of the text. * Use the word "and" rather than the symbol "\&" in all headings. * See [Capitalization](https://help.fews.net/brand/capitalization.md) for capitalization standards. ### Paragraph spacing and layout Do not use hard returns to add space between text. Using the built in styles will automatically create appropriate spacing, regardless of header or text type. If built in styles can not be used, refer to the text styles table and use the specified line and paragraph spacing instead of hard returns. In general, no page breaks should be used to separate headings. Exceptions may apply when considering the overall "look and feel" of the spacing of text, figures, and tables: * If a Heading 1 occurs in the bottom ¾ of the page, then a page break can be inserted. * If a table begins on the bottom ¾ of the page, and adding a page break will allow the table to remain whole, on a single page. Avoid 'widows and orphans': * Do not end a page with a single line that begins a new paragraph. * Do not begin a page with the final line of a continuing paragraph from the preceding page. * Two or more lines of text must appear beneath a heading. * Do not allow a heading to appear at the bottom of a page while all of its text appears at the top of the following page." ### Word spacing Use one space after periods and other punctuation. Leave one space after periods and colons and before Zip Codes: * See Jane run. See Dick fall. * Items will include: (1) x; (2) y. Arlington, VA 22201 Leave one space between the abbreviations "FY", "CY" or "MY" and the year: * FY 2009; CY 2009 Leave one space after a period when it follows a number or letter that indicates enumeration (agenda items, numbered paragraphs, etc.): * I. Agenda Item 1 * A. Funding Source ### Lists #### In-paragraph lists Lists within the body of the text should only be used for a maximum of four listed items; otherwise, break the text into a numbered or bulleted list separated by lines. * For lists with less than four items, number each item using lowercase Roman numerals surrounded by parenthesis, with each item separated by a semi-colon, and with the word "and" preceding the final item. * Note that the first word following the Roman numeral should be in lowercase (e.g., "(i) list" rather than "(i) List"). For example, a list should look like: (i) list item one; (ii) list item two; (iii) list item three." #### Numbered and bulleted lists Ordered lists should use Google Docs default numbered bullets. Unordered lists should use Google Docs default bullets. The format and spacing of bulleted or numbered lists should be consistent within the document. There should be no added space between items in a bulleted list. Spacing can be removed by selecting items within your list, then clicking **Format** \> **Line \& paragraph spacing** \> **Remove space after paragraph**. If possible, no list should exceed one page or continue from one page to another with a page break in between. Use parallel structure in bulleted or numbered lists, so that each item in the list starts with either a noun or a verb. The style should be the same vertically, so that nouns and verbs are not mixed. If verbs are used, make sure that the same tense is used consistently. List items may be given short headings using a short phrase in bold, normal text, with a period after the phrase. * **Example.** This is an example of how to format a list item header. **Pro tip.** If you use an item header for one item, remain consistent and use it for every item in the list. ### Figures #### Title and number All figures should be titled with a figure number, followed by a period, then a title (e.g., "**Figure 1. The Role of the Hub**"). * Each figure is numbered sequentially. Tables and figures maintain their own numbering and are not mixed (for example, in a document with both tables and figures intermixed, items may be numbered as Table 1, Figure 1, Figure 2, Table 2). * Titles are preferably no longer than a few words. Explanatory text can be added in a subtitle, the document narrative, or under a table as a caption. #### Caption and source Captions go below a figure and add additional information that can not be found in the narrative, title or subtitle. If a source is being provided, the source should come under the caption and be formatted as "Source: \[insert source name\]." #### Alt text Include alternative text for images, drawings, and other graphics. Otherwise, screen reader users just hear "image." Some images automatically include alt text, so it's a good idea to verify that this automatic alt text is what you want. To add or edit alt text, right click on an image, drawing, or graphic and select Alt text. #### Border While borders around images are not required, they are recommended if placed within the body of the text or if there is substantial white page space in the text. If a border is applied, it should be 1px gray-400 (#D1D3D4). #### Reference in text Figures should be referenced in the body of the text (e.g., "See Figure 1." or "See Figure 1 below."). Figures should be cross-referenced and linked elsewhere in the document if mentioned more than once. ### Cover pages Most FEWS NET branded documents will not need a cover page. When needed, the cover page includes a FEWS NET wordmark in the upper left hand corner and a report title, subtitle, and a month or submission date. *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Fonts ![Image displaying the names of the typefaces FEWS NET uses set in the respective typefaces. Georgia and Segoe UI are large on the first line with Tinos and Open Sans smaller on a second line underneath.](https://help.fews.net/__attachments/a_39ecd550a9c5e4a7b6c9a36c91cbb4b707e1705ee0c157b292a59e908999e066/Typefaces.png?cb=d00e73a04fc80835546b66578acb33c0) FEWS NET uses the Segoe UI and Open Sans typefaces for most text. Segoe UI is preferred when available, while Open Sans is used in Google Suite products and elsewhere as a fallback for Segoe UI. FEWS NET uses the Georgia typeface for official headlines only. Tinos may be used as a fallback for Georgia. ## Segoe UI and Open Sans FEWS NET uses Segoe UI (or Open Sans as a fallback) for most text, including normal body text, titles of internal documents, page headings and subheadings, technical user interface elements, and graphics and social media products. Bold (700 weight) and Semibold (600 weight) may be used for titles, headings and subheadings, and other cases where text emphasis is appropriate. See [Text Emphasis](https://help.fews.net/brand/text-emphasis.md) for details. Regular (400) may be used for text in all other cases. Regular Italic may be used where appropriate (see [Italics](https://help.fews.net/brand/italics.md) for details). ### Size #### Minimums The minimum allowable size for print body text (such as for a written report) is 10/9 pt for Segoe UI / Open Sans. No print text should be smaller than 8/7 pt for Segoe UI / Open Sans. #### Size conversion between fonts Open Sans is visually larger than Segoe UI by a factor of approximately 1.09x. Precise visual size conversions from Segoe UI to Open Sans adjust the point size by this factor. For example, a conversion from Segoe UI to Open Sans should divide the Segoe UI point size by 1.09 and round to the nearest tenth (or whole point in Google Suite) to achieve analogous visual size for Open Sans. ### Don't * Use font classes other than Bold, Semibold, Regular, or Regular Italic * Use Segoe UI for headlines of official web pages, report documents, or presentation slides * Make text smaller than the specified minimums to fit more content on a page ## Georgia FEWS NET only uses the Georgia Regular (400 weight) font for headlines of official web pages, report documents, and presentation slides. Preserving use of Georgia for these cases provides FEWS NET audiences with a reliable visual signal of formal materials that are backed by FEWS NET's expertise. ### Size Text that uses Georgia should be the most visually prominent text in any context where it is used, and should therefore have the largest point size. Size specifications are available for [documents](https://help.fews.net/brand/documents.md) and [presentations](https://help.fews.net/brand/presentations.md). ### Don't * Use Georgia Bold, Georgia Italic, or Georgia Bold Italic * Use Georgia in any color other than Brand Black or Brand White * Use Georgia for headings or subheadings below the page, document, or slide title * Use Georgia in social media or promotional graphics * Use Georgia in documentation or technical user interfaces These standards apply equally to Tinos when Georgia is not available. Because headlines in Georgia are a key visual aspect of the FEWS NET brand, avoid use of Tinos to the extent possible. *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Footer FEWS NET visualizations use footers to display any disclaimer text and sources for the information included in the visualization. ![Disclaimer example for interactive visualization.](https://help.fews.net/__attachments/a_e5ed911212bd3cef52fe5a9ded6a9e330147f23e45a5d7b9705056bbd9796ff0/BrandDocs_Shape_10.png?cb=4890d0abec8577196592928760efe47d) ## Usage The primary purpose of the footer is to include source and disclaimer information. ### Sources and Disclaimers **Always include a citation of the visualization source data**, even if the source is FEWS NET. **Include sources with links.** If appropriate, link to either the homepage of the entity that provided the data, or a direct link to the data used (if publicly available). **Visually separate sources.**Include a space between sources when listing more than one. **Keep it focused.** The footer may be used to include footnotes with clarifications or additional explanation,but don't include verbose language or describe redundant details in the chart that are already apparent in the title, subtitle, or elsewhere. If the visualization appears in context of narrative text, consider including a note in the surrounding text instead of in the visualization itself. ## Components The footer contains: * Disclaimer, if present * Source ## Padding and spacing * **8px** on all sides * Measured perpendicularly from straight edges of the visualization frame, disregarding rounded corners * **8px** between disclaimer, if present, and source ## Layout and responsiveness * Footer always sits adjoining the bottom edge of the visualization frame * Footer width fills the visualization frame * Footer height hugs the enclosed components * Disclaimer, if present, sits directly above source * Disclaimer and source hug left * Disclaimer and source text wrap to additional lines based on available space ## Background The footer background uses **Brand White** (#FFFFFF). ## Typography | **Style name** | **Font** | **Line height** | **Color** | |----------------|-----------------------|-----------------|-----------------------| | Disclaimer | 12px (9pt) Italic | 140% | Brand Black (#212721) | | Source | 14px (10.5pt) Regular | 140% | Brand Black (#212721) | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Global Layout and Frame Styles This page includes layout principles and frame styles used by all FEWS NET visualizations. For details about responsive behavior of live visualizations based on the width of the visualization frame, see [Frame Responsiveness](https://help.fews.net/brand/responsive-specifications.md). ![Examples of map layouts for a laptop, tablet, and phone.](https://help.fews.net/__attachments/a_be4aec052381126dc6f3b4bb01ad221cbc925ff11efe87a49e6b48a7a46040a0/BrandDocs_Shape_1.png?cb=3d1a1f75cf7b354568286f0db74b6fa6) ## Components and Layout Visualizations are made up of components organized inside a visualization frame.**Static visualizations** and **live charts** include components in the following order, from top to bottom: * Header * Body * Legend * Footer These components all fill the width of the visualization frame. The layout ofa**live map**changes depending on the map's width. Each map has a user-interactive zone containing components in the following order, from top to bottom: * Header * Map Body ![Example of a map body.](https://help.fews.net/__attachments/a_554618d2cceefbd3fc6e992b16c12e637a7994efb4afe58215dbfac15c74cfd9/BrandDocs_Shape_4.png?cb=7376ab94433b9db4195aefcaa2525a3c) Map with its user-interactive zone outlined for emphasis On wide maps, the legend forms a column to the right of the user-interactive zone that fills the same vertical space. On narrow maps, the legend wraps beneath the user-interactive zone and both components fill the width of the visualization frame. The footer is always present at the bottom of the visualization and fills the width of the visualization frame. ## Padding and Spacing Visualizations use minimum padding and spacing in order to provide maximum area for visualization content. * **No padding** is used between the edge of the visualization frame and enclosed components. For example, the left edge of a live map contained inside the user interactive zone should touch the left edge of the visualization frame. * **No spacing** is used between the components contained inside the visualization frame. Visual space is provided by padding inside individual components. For example, on a wide live map, the left edge of the legend component should touch the right edge of the user-interactive zone. ![Example of a map with all required components.](https://help.fews.net/__attachments/a_4f9288f8e788b67fee5251f54f19e7df042e83303009c216c2a158117c99f80c/BrandDocs_Shape_3.png?cb=babdf27524206746a86f542a69969a70) Map with component volumes outlined for emphasis ## Borders Visualizations use minimal borders to outline key volumes. * All visualizations use a **1px wide, Gray 400** (#D1D3D4) border around the visualization frame * **Live maps** use a **1px wide, Gray 300** (#E6E7E8) border around the user-interactive zone ## Corners Visualizations use rounded corners for interface components. This conveys an attitude of approachability that invites user interaction and provides subtle contrast with the rectangular volumes of text paragraphs and presentation slides where visualizations typically appear. | **Component** | **Style** | **Additional specifications** | |-----------------------|---------------------------------------------|-------------------------------| | Visualization frame | 16px radius, all corners | * Use for all visualizations | | User-interactive zone | 15px radius, all corners except bottom left | * Use for live maps | | Legend section | 4px radius, all corners | * Use for all maps | | Popover | 16px radius, all corners | * Use for live visualizations | | Tooltip | 8px radius, all corners | * Use for live visualizations | ## Shadows Where possible, visualizations cast a shadow to create visual interest and highlight interactivity. For non-web contexts, it is acceptable to omit shadows so long as the no-shadow treatment is applied consistently to all visualizations. | **Style name** | **Color** | **Blur** | **X offset** | **Y offset** | **Spread** | **Additional specifications** | |----------------------|----------------------|----------|--------------|--------------|------------|------------------------------------------------------------------| | Global Shadow | #000000, 10% opacity | 4px | 0px | 2px | 0px | * Use for all visualizations except the global homepage live map | | Viz Highlight Shadow | #000000, 25% opacity | 20px | 0px | 6px | 0px | * Use for global homepage live map | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Header FEWS NET visualizations use different header styles depending on the visualization type and context. *** ** * ** *** ## Usage The primary purpose of the header is to contain the title of a visualization. ### Titles and Subtitles **Be clear and descriptive.** The title should convey the key message or insight the chart is meant to highlight. Avoid vague or overly technical language. **Keep it concise.** A title should be short but informative. Ideally, it should be no longer 15 words, which would limit it to about one or two lines. **Use active voice.** Where possible, frame the title to emphasize the takeaway or trend being shown. **Align with the data.** The title should reflect the main point of the data, summarizing what the viewer will understand after seeing the chart. **Describe the intent of the chosen timeframe.** Use subtitles and other time-related text to make it clear why a timeframe was chosen, such as the time period for a projected outcome, the collection date for mapped data, or detail about the nature of a time comparison. **Use consistent formatting.** Ensure the font size, style, and placement of subtitles are consistent with FEWS NET visualization technical specifications. **Use the right tone.** The tone of your titles and subtitles should be neutral and objective, especially when dealing with sensitive data. **Don't be verbose.** Don't use titles that are unnecessarily lengthy or repeat details in the chart **Don't use titles in title case.** Don't use inconsistent capitalization, and don't capitalize everything. Instead, sentence case is preferred for titles. **Avoid overloading information.** While subtitles can be more detailed, avoid cramming too much information that could distract or confuse the viewer. *** ** * ** *** ## Global Use the global header for **all** **charts** and **static maps**. ![Example of a chart header.](https://help.fews.net/__attachments/a_4a55733d41b630ea69e71e645f7edc81326bb758dfb4d18eda14c43f56c73b3b/BrandDocs_Header_1.png?cb=53a76afecfa30611defc36a25510e780) Example application of the global header ### Components The header contains: * Title * Subtitle, if needed * Download button, for **live charts** ### Padding and spacing * **16px** on top and sides * **24px** vertical between the last line of text and the bottom * **8px** vertical between the title and subtitle, when a subtitle is present * **40px**minimum horizontal space between the longest text line and the download button, when the button is present * **8px** vertical between the title and download button, when the button is wrapped below the title ### Layout and responsiveness * Header width fills the visualization frame * Header height hugs the enclosed components * Title hugs the left margin and the top, subtitle when present falls directly below the title and behaves identically * On **live charts**: * download button hugs the right margin and is vertically centered to the text * download button wraps below text and hugs the left margin after reaching the minimum space between the text and button * text lines wrap to additional lines when the visualization frame width is shorter than the text line length ### Background The header background uses **Brand White** (#FFFFFF). ### Buttons For **live charts** , the download button is a 40px square with transparent background enclosing a centered 24px square download icon that uses **Brand Black Dark** (#090B09). For the hover state, the icon fill changes to **Brand Primary** (#096640). ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Font** | **Line height** | **Color** | **Additional specifications** | |----------------|----------------------|-----------------|----------------------------|--------------------------------------------------------------------------------------------| | Title | 20px (15pt) Semibold | 120% | Brand Black Dark (#090B09) | * See [Capitalization](https://fdw.fews.net/en/dashboard/standard_visualization_styles.js) | | Subtitle | 16px (12pt) Regular | 120% | Brand Black Dark (#090B09) | | *** ** * ** *** ## Interactive - Primary Use the primary interactive header at the top of **live** **maps** and **live combined charts.**For live combined charts, the primary interactive header is placed above the global header. ![3 examples of map and chart headers.](https://help.fews.net/__attachments/a_9a9f7d8069121f26813ff617d3ca83ed6de64ca9d97b41c9efa336b831e65132/BrandDocs_Header_2.png?cb=6b48a657c748703fb01f960b379bdec3) Example applications of the primary interactive header ### Components The header contains: * Title * [++Input++](https://help.fews.net/brand/interactive-components.md#Input), for **live maps** with multiple views and **combined charts** ### Padding and Spacing * **12px** on top, or **8px** when input is present * **14px** on bottom, or **10px** when input is present * **12px** on left margin * **16px** on right margin, or **8px**when input is present * **40px** minimum horizontal space between the title and input, when input is present * **16px** vertical between the title and input, when input is wrapped below the title ### Layout and Responsiveness * For **live maps** , header width fills the user-interactive zone. For **live combined charts**, header width fills the visualization frame. * Header height hugs the enclosed components * Title hugs the left margin and is vertically centered * Input hugs the right margin and is vertically centered * Input wraps below text and hugs the left margin after the minimum space between the title and input is reached * Title wraps to additional lines when the visualization frame width is shorter than the title line length ### Background The header background uses **Gray 200** (#F4F5F5). ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Font** | **Line height** | **Color** | **Additional specifications** | |----------------|----------------------|-----------------|----------------------------|--------------------------------------------------| | Title | 20px (15pt) Semibold | 120% | Brand Black Dark (#090B09) | * See [Capitalization](https://help.fews.net/brand/capitalization.md) | *** ** * ** *** ## Interactive - Secondary Use the secondary interactive header for **live maps**that have layers with time-relevant information or interactivity. The secondary interactive header is always placed directly below the primary interactive header. ![3 examples of secondary headers for maps.](https://help.fews.net/__attachments/a_15a0e1eb95eb9476fb1998031020f10b9b9e643411ba5920477c36c91a048205/BrandDocs_Shape_5.png?cb=8e5ab7ec83951637f5ef58db77d6ec8b) Example applications of the secondary interactive header ### Components The header contains: * Subtitle * Reported date, if applicable * [++Time slider++](https://help.fews.net/brand/interactive-components.md#Time-slider), if applicable ### Padding and spacing * **8px** on top * **12px** on sides * **14px** on bottom, or **0px** when time slider is present * **40px**minimum horizontal space between subtitle and reported date, when reported date is present * **4px** horizontal between reported date icon and text * **8px** additional horizontal padding between the reported date and the right edge of the header * **14px** vertical between the last line of text and the time slider, when time slider is present * **8px** vertical between the subtitle and reported date, when the reported date is wrapped below the title ### Layout and responsiveness * Header width fills the user-interactive zone * Header height hugs the enclosed components * Title hugs the left margin and is vertically centered * Reported date hugs the right margin and is vertically centered to align with title * Time slider falls directly below text row, when present * Reported date wraps below subtitle and hugs the left margin after the minimum space between the title and reported date is reached ### Background The header background uses **Brand White** (#FFFFFF). ### Border The header uses a 1px border, **Gray 500** (#ADADAD), on the bottom edge ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Font** | **Line height** | **Color** | **Additional specifications** | |----------------|-----------------------|-----------------|----------------------------|--------------------------------------------------| | Subtitle | 16px (12pt) Regular | 120% | Brand Black Dark (#090B09) | * See [Capitalization](https://help.fews.net/brand/capitalization.md) | | Reported date | 14px (10.5pt) Regular | 120% | Brand Black (#212721) | * Use "Reported \[Month\] \[YYYY\]" | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Interactive UI Components *** ** * ** *** ## Popover Use popovers to expose additional context when a user clicks on part of a **live visualization**. When popovers use inlay charts, visit [Chart Body](https://help.fews.net/brand/chart-body.md) to see chart specifications and best practices not addressed here. Developers: [++Figma component++](https://www.figma.com/design/FwWNRdLia5W11iBP8HL9Ej/FEWS-NET-Pattern-Library?node-id=5329%3A29786&t=p1vwNrIkRHhTcN9I-1) ![Examples of popovers.](https://help.fews.net/__attachments/a_eb7b613bdc2ada34b27566071676fd174ce2530f0665103bb8dd4e865487884a/BrandDocs_Shape_11.png?cb=68186ee1ec1a5a183ef208982b2fa5be) ### Components The popover contains: * Title * Sections, if needed: * Section title * Section content * Reported date, if needed * Horizontal divider, if inlay chart is present * Inlay chart, if needed: * Title * Chart body ### Padding and spacing * **12px** on top * **16px**on sides * Excluding horizontal divider, when present * **8px** on bottom * **4px** extra vertical padding between bottom and reported date, when present * **8px** horizontal between title text and flag, if present * **16px** vertical between title and sections, if present * **2px** vertical between section title and section content * **8px** vertical between sections * **16px** vertical between title (or last text, if present) and reported date * **4px** horizontal space between reported date icon and text * If inlay chart is present: * **8px** vertical between title (or last section, if present) and horizontal divider * **4px** extra vertical padding between horizontal divider and reported date, when present * **8px** vertical between horizontal divider and inlay chart title * **24px** vertical between inlay chart title and chart body * **4px** horizontal space between Y axis labels and chart body * Chart body fills available width * **170px** max chart body height, shorter if appropriate to chart content * **8px** vertical space between chart body bottom and X axis labels * **12px** vertical space between chart X axis labels and inlay chart bottom ### Layout and responsiveness * Popover width is fixed at 280px wide * Components hug left and stack vertically * Excluding "X" close icon, which hugs top right * Popover height hugs the enclosed components * Title text is vertically centered to flag, when present * Popovers should appear **above and to the right** of the user click or hover position * Popovers respect the edges of map body / chart body and adjust position to fall within the body if a user makes a selection near the edge. Next preferences after above right are above left, followed by below right and below left ### Background The popover background uses **Brand White** (#FFFFFF). Inlay chart Y axis segments do not use alternating background fills, unlike chart body in other contexts. ### Border The horizontal divider, if present, is **1px** , **Gray 400** (#D1D3D4). ### Corners Popovers use a rounded corner with **16px**radius. ### Shadows Popovers cast a shadow on the body of the visualization. | **Style name** | **Color** | **Blur** | **X offset** | **Y offset** | **Spread** | |-------------------|----------------------|----------|--------------|--------------|------------| | Viz On-Map Shadow | #000000, 25% opacity | 10px | 0px | 1.87px | 0px | ### Icons * Flags are 40px wide and 22px high, with 1px outside border, Gray 400 (#D1D3D4). * The "X" close icon is 16px square enclosing an X, Brand Black (#212721). ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Font** | **Line height** | **Color** | **Additional specifications** | |--------------------------------|----------------------------------------|-----------------|----------------------------|-------------------------------------------------| | Popover Title | 14px (10.5pt) Bold | 140% | Brand Black Dark (#090B09) | | | Popover Title (Link) | 14px (10.5pt) Bold Underlined | 140% | Brand Primary (#096640) | * Use when popover title links to another page | | Popover Section Title | 14px (10.5pt) Regular | 140% | Brand Black Dark (#090B09) | * Use for popover inlay chart title, if present | | Popover Text | 14px (10.5pt) Bold | 140% | Brand Black Dark (#090B09) | | | Popover Reported Date | 12px (9pt) Bold **Should be Regular?** | 120% | Brand Black (#212721) | | | Popover Inlay Chart Axis Label | 14px (10.5pt) Regular | 140% | Brand Black Dark (#090B09) | | *** ** * ** *** ## Tooltip Use tooltips to add additional layers of context when a user hovers over part of a **live visualization**. Tooltips may appear to expose a global layer, such as to show regional groupings, or to provide more detail when a user hovers over a specific chart or geography, including on an inlay chart inside a popover. Developers: [++Figma component++](https://www.figma.com/design/FwWNRdLia5W11iBP8HL9Ej/FEWS-NET-Pattern-Library?node-id=1512%3A10778&t=p1vwNrIkRHhTcN9I-1) ![Examples of popovers.](https://help.fews.net/__attachments/a_5a6fd329766c1cfa73316cbc6cc2925cf565d2ae7dba845522404a9a48240193/BrandDocs_Shape_12.png?cb=3002484918665d26bd56b9d4c62e2773) ### Components The tooltip contains: * Clickable title, if needed * Section, if needed: * Section title * Section content ### Padding and spacing * **8px** on all sides * **4px** extra bottom spacing if clickable title is the lowest component * **4px** horizontal between clickable title icon and text, when present * **2px** vertical between section title and section content ### Layout and responsiveness * Components hug left and stack vertically * Popover width and height hugs the enclosed components * Clickable text is vertically centered to flag, when present * Tooltips that appear globally should appear for the entire time a users' cursor is present on the visualization body content * Tooltips that appear at specific points should appear **directly above and horizontally centered** on thecursor hover position so the bottom triangular caret appears to be emanating out of the cursor * Tooltips respect the edges of map body / chart body and adjust position to fall within the body if a user hovers near the edge. Next preference after directly above the hover point is directly below. This doesn't apply to tooltips appearing inside popover inlay charts. ### Background The tooltip background uses **Brand White** (#FFFFFF). ### Corners Tooltips use a rounded corner with **8px**radius. ### Shadows Tooltips cast a shadow on the body of the visualization or popover from which they emanate. | **Style name** | **Color** | **Blur** | **X offset** | **Y offset** | **Spread** | |-------------------|----------------------|----------|--------------|--------------|------------| | Viz On-Map Shadow | #000000, 25% opacity | 10px | 0px | 1.87px | 0px | ### Icons * Clickable title icons are 12px square and match the color of clickable title text. ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Font** | **Line height** | **Color** | **Additional specifications** | |-----------------------|-----------------------|-----------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Clickable Title | 16px (12pt) Bold | 140% | Brand Primary (#096640) | * Use when a user's click on the hovered area will cause an action such as zooming into a section or opening a popover. * Use a representative icon in the title to signal what the action will be. | | Tooltip Section Title | 14px (10.5pt) Regular | 140% | Brand Black Dark (#090B09) | | | Tooltip Text | 14px (10.5pt) Bold | 140% | Brand Black Dark (#090B09) | | *** ** * ** *** ## Time slider Use the time slider to allow users to navigate time series data on a **live map**. Developers: [++Figma component++](https://www.figma.com/design/FwWNRdLia5W11iBP8HL9Ej/FEWS-NET-Pattern-Library?node-id=4350%3A37643&t=orHW95Co1QudkKUs-1) ![Example of a time slider element.](https://help.fews.net/__attachments/a_bff4c81384dd26c8ddb706aea240bb3d351fc5ab9c4eb6f54e7e946ee0c7a457/BrandDocs_Shape_13.png?cb=d95447454df896cf8742e35a3404a99a) ### Components The tooltip contains: * Back button * Timeline * Line * Items * Tick mark * Item text * Active pin * Forward button ### Padding and Spacing * **2px** on top * **12px** on sides * **6px** on bottom * **10px** horizontal between buttons and timeline * **140px** minimum item width * **4px** vertical between item tick mark and item text ### Layout and Responsiveness * Time slider width fills available horizontal space in the user-interactive zone * Time slider height hugs enclosed components * Components lie horizontally from left to right * Components hug the top * Timeline item tick marks and text fall vertically below the timeline line * Active pin indicates the selected item and falls directly above the intersection of the selected item tick and the timeline line * Timeline item text is horizontally centered to timeline item tick * Timeline items fill evenly across available horizontal space * When timeline items run out of available space, *older* items overlap off of the left edge of the timeline component, leaving the future or most recent items visible ### Background The time slider background uses **Brand White** (#FFFFFF). ### Lines Timeline line and item tick marks are**2px** ,**Gray 500** (#ADADAD) ### Borders The time slider has a**1px** ,**Gray 500** (#ADADAD) border on bottom. ### Icons Active pin is a 12px diameter circle using **Brand Primary Light** (#0B8351) background fill with an outer border **1px** , **Brand Primary** (#096640) ### Buttons * The left and right buttons are circles of 40px diameter enclosing 16px square icons. * Buttons use **Brand White** (#FFFFFF) background fill and icons use **Brand Primary** (#096640). Buttons have an inner border **1px** , **Gray 500** (#ADADAD) * For hover state, background fill uses **Brand Secondary Light** (#E4F1EF) and icons use **Brand Black Dark** (#096640). ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Font** | **Line height** | **Color** | **Additional specifications** | |---------------------------|------------------------|-----------------|----------------------------|--------------------------------------------------------------| | Timeline item text | 14px (10.5pt) Regular | 120% | Brand Black Dark (#090B09) | | | Timeline item text active | 14px (10.5pt) Semibold | 120% | Brand Black Dark (#090B09) | * Use for a single time slider item that is currently active | *** ** * ** *** ## Input Use the input to allow users to select a view on a **live map** with multiple views or to select a chart on a **multi-layer chart**. Developers: [++Figma component++](https://www.figma.com/design/FwWNRdLia5W11iBP8HL9Ej/FEWS-NET-Pattern-Library?node-id=5247%3A24178&t=orHW95Co1QudkKUs-1) ![Select map view menu.](https://help.fews.net/__attachments/a_abbd14f3830a49f6b4c9ac79a552a3dd2cca29fefa1245abaed3739ffbef4421/BrandDocs_Shape_14.png?cb=28ed1e2440a1660d8fd6ee752b0b73be) ### Components The input contains: * Input title * Input field * Selected item text * Dropdown icon * Dropdown * Dropdown section titles, if needed * Dropdown items * Dropdown items ### Padding and spacing * **0px**on sides * **8px** horizontal between input title and input field * **8px** vertical, when wrapped * Input field: * **6px** on top and bottom * **16px**on left side * **12px** on right side * Dropdown: * **0px** vertical between items * Dropdown item: * **8px** on top and bottom * **6px** on sides ### Layout and responsiveness * Input height hugs components * Components hug left, including text inside input field and dropdown items * Components sit horizontally until visualization width is 607px or narrower, after which input field wraps below input title * Input title: * Input title size varies depending on visualization width (see Typography) * Input field: * Fixed width of 434px, unless wrapped, in which case fills available horizontal space * Dropdown: * Appears below and directly adjoins input field so dropdown item text is vertically aligned with field text * Fills horizontal space to appear visually centered to input field width ### Background * The input field background uses **Brand White** (#FFFFFF). * The dropdown item uses **Brand White** (#FFFFFF) background fill. * Hover state uses **Brand Secondary Light** (#E4F1EF) and selected state uses **Brand Secondary** (#BDDBD6). ### Borders * The input field has a**.5px** ,**Brand Primary Dark** (#074B2F) outer border. * The dropdown field has a **1px** , **Gray 500** (#ADADAD) outer border. ### Icons Dropdown icon is 16px square and uses **Brand Black Dark** (#096640). ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Font** | **Line height** | **Color** | **Additional specifications** | |------------------------|------------------------|-----------------|----------------------------|-----------------------------------------------------------| | Input title XL | 16px (12pt) Semibold | 140% | Brand Black Dark (#090B09) | * Use when visualization is at 1452px width or wider | | Input title LG-MD | 14px (10.5pt) Semibold | 140% | Brand Black Dark (#090B09) | * Use when visualization is between 1452px and 607px wide | | Input title SM-XS | 14px (10.5pt) Regular | 140% | Brand Black Dark (#090B09) | * Use when visualization is 607px wide or narrower | | Input field text | 14px (10.5pt) Regular | 140% | Brand Black Dark (#090B09) | | | Dropdown section title | 14px (10.5pt) Semibold | 140% | Brand Black Dark (#090B09) | | | Dropdown item | 14px (10.5pt) Regular | 140% | Brand Black Dark (#090B09) | | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Italics The primary use of italics in FEWS NET writing is for non-English words or phrases that are not commonly used in English. Explain the terms on first use if necessary. If a word from another language becomes familiar through repeated use throughout a work, italicize it only the first time it appears. If the word appears rarely, however, italicize it every time. ## Do * Italicize non-English words or phrases, and explain the term on its first appearance. Examples: * "*Manjekwits* (food vendors) are popular in Haiti." * "The team in Nigeria used an *okada* (motorcycle taxi) to access hard-to-reach areas." * Italicize disclaimers in footers of formal FEWS NET documents. ## Don't * Italicize words for emphasis. Example: "*This is a critical food security update.*" * *See* [Text Emphasis](https://help.fews.net/brand/text-emphasis.md). * Italicize words in lieu of using a correct brand style for [headings](https://help.fews.net/brand/documents#Documents-Textstyles). * Italicize non-English words or phrases that are commonly used in English (e.g. ad hoc, de facto). * Italicize the formal names of organizations, institutions, or places, even if they are in a non-English language (e.g. Action Jeunesse pour le Développement). ## Uses in technical writing There are additional uses of italics in writing for FEWS NET documentation and FEWS NET product user interfaces: * Data that appears within the UI, such as names of Data Source Documents or Data Series, may be italicized (e.g., *Famine Early Warning Systems Network (FEWS NET), Nigeria, Livestock Price (weekly)*). * Italicize words that are used as words (e.g. Don't use \& (ampersand) as a conjunction. Use the word *and*instead.) * Documentation may italicize Parameter names (e.g., Select *Price Bulletin Report* from the **Narrative Metadata Type** list.) * Documentation may italicize words sparingly for emphasis - primarily for notes or when introducing and defining a term. *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Legend Legends help users navigate a visualization by describing the relevant visual properties, such as fills, patterns, and symbols. For live visualizations, legends also explain any available interactivity that isn't obvious in the visualization interface. FEWS NET visualizations always use legends, but the legend format varies depending on the type of visualization. ![Sample of a map legend.](https://help.fews.net/__attachments/a_9d4035ad1d4795c4f333b4745031751f74b7221b29a74db73774d7d8bc15a51d/BrandDocs_Shape_7.png?cb=31ec8e51a419e207ddebf5db0c02fb80) *** ** * ** *** ## Usage **Use strategic placement.** Place the legend in a location that doesn't obstruct important data, typically to the right or below the chart. **Give the legend a title.** Title the legend, "Legend" for clarity **Group related items together.** If applicable, categorize using a bar or gray boxes for separation to help viewers understand the data more intuitively. See following specifications for more details. **Ensure clear separation.** Make sure the legend does not overlap with the data being represented; this helps prevent confusion. Avoid describing redundant details in the chart that are already apparent in the title, subtitle, or elsewhere **Don't include instructions.** Don't instruct the user where to click or look for details in the chart. Details should be apparent through labeling, titles, and callouts alone. **Keep it focused.**Don't include verbose language or describe redundant details in the chart that are already apparent in the title, subtitle, or elsewhere *** ** * ** *** ## Chart Use the chart legend for **all charts**. ![Sample of a chart legend.](https://help.fews.net/__attachments/a_dc14e77048ab6354ee7f28f9e9d5b404fe0fbe62d06e31c0ae77dd1a29fe9965/BrandDocs_Shape_8.png?cb=26a506324e74a3e3b6157c46327f7077) ### Components The legend contains: * Title, for **live maps** * Instructions, for **live maps** if needed * Sections, if needed: * Section titles * Items * Items ### Padding and spacing * **16px** on all sides * **8px** horizontal between title and instructions * **4px** horizontal between instructions icon and text * **18px** vertical between bottom line of title text (or instruction text, if present and wrapped) and items (or first section title, if present) (margin) * **8px** vertical between section title and items in section * **16px** vertical between sections, if present * **8px** horizontal between item symbol and text * **24px** horizontal between items * **24px** vertical between items when wrapped * **40px**minimum space between the longest text line and the download button, when the button is present * **8px** between the title and download button, when the button is wrapped below the title ### Layout and responsiveness * Legend width fills the visualization frame * Legend height hugs the enclosed components * Item symbols sit left of item text and are vertically centered to text * Item text wraps below to additional lines if needed * Items hug left and wrap to additional lines if needed * For **live charts**: * Title hugs left, instructions sit to the right of the title and hug left * Instruction icon and title are vertically centered to instruction text * Instruction text wraps below to additional lines if needed ### Background The legend background uses **Brand White** (#FFFFFF). ### Symbols * The item symbol for items describing data represented as a **bar** is a 20px square with background fill matching the bar color and .45px border line, Brand Black (#212721). * The item symbol for items describing data represented as a **line**is a 50px wide horizontal line with 6px stroke weight, round cap, with fill matching the line color. Dotted or dashed lines should use the same pattern in the symbol. Dotted or dashed symbols may be modified to better represent the line pattern. (Will likely be too long for png images, symbol width is defined by line width. Might consider a separate set of values for pngs.) ### Icons * The instructions icon is 16px square enclosing a circle with a lowercase "i" inside centered, Cobalt 600 (#2B6CB0). ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Application notes** | **Font** | **Line height** | **Color** | |-------------------------|-------------------------------------------------|------------------------|-----------------|----------------------------| | Legend title | | 14px (10.5pt) Regular | 120% | USAID Black Dark (#090B09) | | Legend section subtitle | * Live charts use this style for section titles | 14px (10.5pt) Semibold | 120% | USAID Black Dark (#090B09) | | Legend text | * Use for item text | 14px (10.5pt) Regular | 120% | USAID Black Dark (#090B09) | | Legend instructions | | 14px (10.5pt) Regular | 120% | Info Blue (#2B6CB0) | *** ** * ** *** ## Map Use the map legend for **all maps**. ![Two map legends. One is on the right of a map, the other is below a map.](https://help.fews.net/__attachments/a_6974682c1f7d9c22c6614bd310a0a8e4b4983eccfb420b9bb6e7afac6f755307/BrandDocs_Shape_9.png?cb=6e5bb92dd06bceaa348df3c8fd5302d2) ### Components The legend contains: * Title, for **live maps** * Instructions, for **live maps** if needed * Section boxes: * Section title * Descriptive text * Subsections, if needed: * Section subtitle * Items * Items ### Padding and spacing * **16px** on top and sides * **8px** on bottom * **8px** horizontal between title and instructions * **8px** vertical between title and instructions, when wrapped * **4px** horizontal between instructions icon and text * **8px** vertical between bottom line of title text (or instruction text, if present and wrapped) and first section box * Inside section boxes: * **8px** on top * **16px** on sides and bottom * **12px**vertical between bottom line of section title text and items, or first subsection title if present * For subsections: * **8px** vertical between subsection title and items * **12px** vertical between subsections * **8px** vertical between section boxes * **120px** minimum width for each item * **8px** horizontal between item symbol and text * **8px** minimum horizontal space between items * **8px**vertical between items when stacked in single column * **4px** vertical between items when stacked in multiple columns ### Layout and responsiveness * For **static maps**: * Legend falls below the map body * Legend width fills the visualization frame * Legend height hugs the enclosed components * For **live maps**: * Title hugs top left, instructions sit to the right of the title and hug left * Instruction icon and title are vertically centered to instruction text * Instruction text wraps below to additional lines if needed * For **live maps** 1200px wide or wider: * Legend sits to the right of the user-interactive zone * Legend width and components fill available space * Legend becomes narrower, to minimum width of 252px, before wrapping * Legend height fills available space * For **live maps** 1199px wide or narrower: * Legend falls below the user-interactive zone * Legend width and components fill the visualization frame * Legend height hugs the enclosed components * Section boxes stack vertically, below title and instruction text if present * Item symbols sit left of item text and are vertically centered to text * Item text wraps below to additional lines if needed * Items sit in a single horizontal line hugging left * If available horizontal space is narrower than can fit all items on one line with minimum horizontal spacing, items wrap into two equal width columns that fill the available horizontal space. Items stack vertically and hug left within these columns. If minimum space between any two vertically aligned items in these columns is not available, items wrap into a single column. ### Background * Legend background uses **Brand White** (#FFFFFF) * Section box background uses **Gray 200** (#F4F5F5), except Remote Sensing maps, which use **Brand White**(#FFFFFF) ### Border * Section boxes of Remote Sensing maps use a **1px** , **Gray 400** (#D1D3D4) border ### Corners * Section boxes use a rounded corner with **4px**radius ### Symbols * The item symbol for items describing data represented as a **fill** is a 20px wide, 14px high rectangle with background fill matching the fill color and texture and .45px border line, Brand Black (#212721). * The item symbol for items describing data represented as a **bubble**is a \[\] ### Icons * The instructions icon for **live maps** is 16px square enclosing a circle with a lowercase "i" inside centered, Cobalt 600 (#2B6CB0). ### Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. | **Style name** | **Application notes** | **Font** | **Line height** | **Color** | |-------------------------|-----------------------|------------------------|-----------------|----------------------------| | Legend title | | 14px (10.5pt) Regular | 120% | Brand Black Dark (#090B09) | | Legend section title | | 14px (10.5pt) Bold | 120% | Brand Black Dark (#090B09) | | Legend section subtitle | | 14px (10.5pt) Semibold | 120% | Brand Black Dark (#090B09) | | Legend text | * Use for item text | 14px (10.5pt) Regular | 120% | Brand Black Dark (#090B09) | | Legend instructions | | 14px (10.5pt) Regular | 120% | Cobalt 600 (#2B6CB0) | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Links FEWS NET uses links in text across its platforms and documents to connect users to relevant pages and resources. ## Functionality Links should typically open in the current tab. Users should always be able to right- or control-click a link to expose the option to open it in a new tab. Links that provide context to a form should open in a new tab and include a visible indication that this will happen, such as a text label in parentheses. Do not use the external link icon to provide this indication. ### Accessibility Make sure links are accessible to users who are using a keyboard or screen reader to navigate the page. Label links with descriptive tags in code when appropriate. ### Don't * Set links to automatically open a new tab or window * Create links that can't be right- or control-clicked * Use the external link icon to indicate links that open in a new tab ## Style Links in text should use the following styles whenever possible: * Default: Brand Primary (green) colored, underlined and/or bold * Hover or focus: Brand Primary Light (light green) colored, no underline ### Don't rely on color alone Note that changing the text color is not enough to show a link in text. Make sure text links are always visually different from surrounding text in an additional way to color. Changing the text color is also not enough to show a hover or focus state. Make sure another visual change occurs on hover or focus, such as a change in font weight or underline. #### Confirm accessible color contrast Make sure the link default color has minimum contrast of 7:1 with the background color and the link hover color has minimum contrast of 4.5:1 with the background color. In general, place text with links on Brand White or very light brand colors to maintain accessible contrast. #### Insert links contextually Make links in text accessible by inserting them contextually within a sentence. (e.g. Follow the [++Microsoft instructions to change the default app for opening CSV and XML to Excel++](https://support.microsoft.com/en-us/windows/change-default-programs-in-windows-10-e5d82cad-17d1-c53b-3505-f10a32e1894d).) This format should not be applied to citations in FEWS NET reports. ### External links Links to external websites, defined as websites that are not hosted at a .fews.net address, should always have a visible indication that the link will lead the user to an external website. Ideally, include an external link icon to the right of a link in text or a button label. It is sufficient but less preferred to write "(external link)" instead of including a external link icon if it is not feasible to add an icon next to your external link. *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Wordmark and Partner Logos ![Workmark options](https://help.fews.net/__attachments/a_f11d8943863fd787552621cebacc31fc2bb9865a1085cca977b06c953091d7f1/Logos.png?cb=e2bc313ecd3f9dc5712c84ec4083b79e) FEWS NET uses its name in wordmark format and the U.S. Department of State logo on all formal FEWS NET branded materials. Partner logos are also used on a case-by-case basis depending on partner involvement. ## Quick links * [All FEWS NET wordmark files](https://drive.google.com/drive/folders/1P9AC3AlLHHHzu47GPPEGtxwaSYSVZWOX?usp=drive_link) (staff only) * [++U.S. Department of State logo++](https://brand.america.gov/d/WrAFnKrhEEfk/domestic-assets/show/eyJpZCI6MTExNDQ4OTAsInNjb3BlIjoiYXNzZXQ6dmlldyIsInRpbWVzdGFtcCI6IjE3NTUwMDkwMTMifQ:frontify:80cvevhKD5C4tm1kvjKPfotnelOl9ohwCQA9NyVeGd8) * [++U.S. Department of State branding guidelines++](https://brand.america.gov/d/WrAFnKrhEEfk/domestic-branding#/-/domestic-branding-guidelines) ## FEWS NET Wordmark The FEWS NET wordmark is used on all FEWS NET formal branded materials. These links open the most-used default wordmark files. ### [Standard wordmark](https://drive.google.com/file/d/1IfgDhDHBTGuXy_f2KfciIPAOtGLt58OM/view) This is the correct variant to use in most cases. ![Standard wordmark.](https://help.fews.net/__attachments/a_b05b9bbe97895af008c3c103fd18d867407a19dc5f48044ad89a65022826191c/FEWS_NET_Logo.png?cb=26ca009f590324b6a66738d01b6ed454) #### [Full name wordmark](https://drive.google.com/file/d/10yn_lr3ccNHnbe8Xq1Luq-3F_eCJ0r3U/view) * Use this variant for partner reporting. * Use this variant when the wordmark will be a "headline" introducing FEWS NET and will be large enough for the name to be legible. * Do not use this variant on a FEWS NET branded document as a substitute for writing out the name of the organization in text. ![Full name wordmark](https://help.fews.net/__attachments/a_9eef0839d8e8e7e9360fcbf35bd78a9ffbd8fa86a6688635b97788c1dba0ac06/FEWS_NET_Logo_Full.png?cb=b9a7bf8574887f12ebe6b958e3ca8eb8) #### [Square wordmark](https://drive.google.com/file/d/1ONdk7468FxSpKQamJeL5KRyN_8-k0SPi/view?usp=sharing) * Use this variant to represent FEWS NET in circle- or square-only formats like a social media profile picture. * This variant is only available in standard black with a white background. ![Square wordmark](https://help.fews.net/__attachments/a_552b725f1ca4318e1516c5c877270c680e1959b210f799773f70aaa3b1fbca60/FEWS_NET_Logo_Square.png?cb=be873314c93d0e5e2c5bd13d241d9c75) ### Usage It is critical that all instances of the wordmark are consistent. Using the wordmark correctly upholds the integrity of FEWS NET products. #### Acceptable variants The FEWS NET wordmark may be rendered in black (default), white, or grayscale. The square variant may only be rendered in black with a white background. #### Minimum size Set the wordmark to a minimum of 72 pixels or 3/4 inches in height. ![Standard wordmark with the minimum height of 72 pixels or 3 quarters of an inch marked.](https://help.fews.net/__attachments/a_a82fdfd6141c5d5f7fa8d9b91f06468018eca03d5a0fcac191b951c83905ceda/Wordmark_Height_Visual.png?cb=a6a7422901109272e4f178ccf7df0b30) #### Minimum clearance Give the wordmark breathing room and define a minimum clear space. The minimum clear space is measured by the x-height of the name in the horizontal version of the wordmark. Other graphic, image or typographic elements should not appear in that space. ![Standard workdmark with minimum clearance marked.](https://help.fews.net/__attachments/a_0e16ac46a7b38f3e987215c5c7570b0d8cc20c5e399a4535eb6c564df05748b1/Wordmark_Space_Visual.png?cb=dd838b9ad8d7162c993c134cf45d1027) #### Background contrast Place the wordmark on backgrounds that provide excellent, accessible contrast. Here is an example of the type of background where the wordmark should be placed. ![White wordmark on a background picture.](https://help.fews.net/__attachments/a_085922b612165786cf5418d221c705cb6d7e7e41f96b13d8bb2087f649d2da41/Wordmark_Contrast_Visual.png?cb=b1925c7d012b116887811efbac9752b9) #### Don't Change the font or rearrange the wordmark. ![Wordmark with the words out of place and a line through it.](https://help.fews.net/__attachments/a_4e40f7f1c296802a6ec56162120532dd48b614fca2f834ff4e472484f6a802db/Wordmark_Rearrange_Visual.png?cb=642201cdf247e037d7d19bc41dacefd4) Recolor, make transparent, or use a low-contrast background. Only use white or grayscale wordmark variants in cases where the wordmark appears on a colorful background that would make the black default wordmark hard to distinguish, or where the wordmark is included alongside partner logos that use one of these color profiles. ![Wordmark in green with a line through it.](https://help.fews.net/__attachments/a_63a2b46f9185ab524c3329985d202dd540dd8d40463c3b6a07488e119f43a348/Wordmark_Recolor_Visual.png?cb=5b35c158af3cd02a5823b6d408ba6a8a) Stretch or squash the wordmark. Always use the original aspect ratio of the source file. ![Wordmark stretched with a line through it.](https://help.fews.net/__attachments/a_cd24d4c17b50ee9122a1218a3d67101ab55ea658e1473868e7d3d97ae969b065/Wordmark_Stretch_Visual.png?cb=99f6130f1fb999c19e56645f4eb39c30) Add additional text or decoration to the wordmark. ![Wordmark with an icon and additional words. A line is through the image.](https://help.fews.net/__attachments/a_e67ba39097b644fb0d5ff734018db79746b9a370c40e804a6b7229c4140fd7bd/Wordmark_Additions_Visual.png?cb=1285b1a348a04ff9e8dbc4f3cbab0e24) ### Co-branding The FEWS NET wordmark is frequently presented alongside one or more partner logos. Leave a minimum of 1/2 inch or 48px of clear visual space between the wordmark and each logo and use unaltered versions of each. #### Visual balance In general, the FEWS NET wordmark should be displayed at visually equal size and prominence as each of the other partner's logos. When using partner logos it is important to ensure the wordmark and all logos are of visually equal weight. In general, this means that the wordmark and all logos are about the same height. However, if a logo is particularly small in width, or light in color, the logo may need to be made slightly taller than other logos. Likewise, if a logo is particularly large in width, or dark in color, the logo may need to be made slightly shorter than other logos. A good rule of thumb to follow is that your eye should be drawn to the wordmark and all logos equally and not one in particular when you look at the page. Make sure to follow all preceding specifications for FEWS NET wordmark usage when making adjustments to the wordmark for co-branding. ## U.S. Department of State logo FEWS NET uses the U.S. Department of State [flag and seal logo](https://brand.america.gov/d/WrAFnKrhEEfk/domestic-assets/show/eyJpZCI6MTExNDQ4OTAsInNjb3BlIjoiYXNzZXQ6dmlldyIsInRpbWVzdGFtcCI6IjE3NTUwMDkwMTMifQ:frontify:80cvevhKD5C4tm1kvjKPfotnelOl9ohwCQA9NyVeGd8) on its formal materials in accordance with the Department's [branding guidelines](https://brand.america.gov/d/WrAFnKrhEEfk/domestic-branding#/-/domestic-branding-guidelines). In particular, the logo is always represented without any modifications and with visual spacing on all sides equal to or greater than the height of 3 stripes of the American flag used in the logo. The U.S. Department of State logo and the FEWS NET wordmark should be visually balanced wherever they appear on the same materials. Ensure that the FEWS NET wordmark does not supersede the U.S. Department of State logo in visual weight and impact. None of the wordmark and logo guidelines presented here are intended to supersede U.S. Department of State guidelines. Always check the latest Department guidelines, linked above, and follow those guidelines in any case where FEWS NET guidelines are unclear or appear to conflict. ## Partner logos ### Quick links The current list of FEWS NET partners changes frequently. The following logo files are presented for quick reference and are not intended to constitute a formal listing of all FEWS NET partners. Partner logos may also become out of date, so refer to each partner's brand resources to confirm brand compliance. [**All partner logos**](https://drive.google.com/drive/folders/1eks-GnGx3C_iiC3ykEmTMOFwoLyGkOax) * [Chemonics](https://drive.google.com/open?id=1TcyOvMBxzJwArVJyOWOKiNF_J_mkq2Fw&usp=drive_copy) * [Climate Hazards Center](https://drive.google.com/open?id=1iPQCBDBAM3yZFu0wFZmYdfp_emXooaCb&usp=drive_copy) * [NASA](https://drive.google.com/open?id=15yYHeZwsrvHYa29HfsoGpZW9KsmhPfDi&usp=drive_copy) * [NOAA](https://drive.google.com/open?id=1vYjzksJAIqmY_64qpMu5xNDZQhzcZUmv&usp=drive_copy) * [USDA](https://drive.google.com/open?id=1Iy95ahjoPgWLTHs-Yhv1qLEW0zWpDXyv&usp=drive_copy) * [USGS](https://drive.google.com/open?id=12sQyAeaPJ2xhwIepJxfiR9jPIH0VW3yc&usp=drive_copy) ### Usage When they are used, partner logos should always appear directly adjacent to the FEWS NET wordmark. Partner logos should follow their own organization's co-branding standards without superseding [FEWS NET's standards](https://help.fews.net/brand/logos#Logos-Co-branding). There are not set brand criteria for when partner logos are used on branded materials. Partner co-branding should be determined by USG on a case-by-case basis. *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Map Body ![Example of a map body in a visualization.](https://help.fews.net/__attachments/a_8e04ae5a015e2ed49203b14cd9732b2da3e94a8f5b61b9a5d0854b5e16cde1f3/BrandDocs_Shape_6.png?cb=665b7b35b74a6ba5fb794498aa48603f) *** ** * ** *** ## Usage ### General **Avoid featuring missing data.**To the extent possible, try to use maps that include data for all the locations included in the scope of the map. **Choose a meaningful timeframe that isn't arbitrary.** To the extent possible, when selecting a timeframe for a chart, choose one that best illustrates the key message or trend you want to highlight. **Use brand styles.**In general, use Sego UI or Open Sans for all text throughout the chart. Pay attention to font weight (for example, use Semibold for subtitles). Specifications are available below. **Use branded symbols.**For symbol maps, use symbols outlined in the following specifications. In general, choose symbols with adequate differentiation. **Provide geographic context.**Always provide sufficient padding around the main areas of concern on the map to give context and help viewers understand the region within its broader geographic setting. **Do not include descriptive text or text boxes.** The footer may be used to include footnotes with clarifications or additional explanation that need to accompany the visualization. If the visualization appears in context of narrative text, consider including a note in the surrounding text instead of in the visualization itself. ### Colors **Confirm 508 compliance.** Ensure that colors have sufficient color contrast to meet 508 compliance standards. Section 508 a federal law that requires federal agencies to make their communication accessible to people with disabilities. Meeting the **color contrast** requirement ensures the visual presentation of text and images of text has a contrast ratio of at least 4.5:1. Tools such as [webaim.org](https://webaim.org/) are helpful for checking color contrast. See [Color safety and recommended combinations](https://help.fews.net/brand/colors.md#Color-safety-and-recommended-combinations). **Use shapes and patterns.** Instead of just colors, consider using shapes or patterns to differentiate items, especially for colorblind accessibility. **Don't use similar shades of color.** Avoid using shades of the same color that are too difficult to distinguish **Avoid using more than 5--7 data colors per map.** Consider using symbols, dashed lines, and other techniques rather than using more colors than needed. *** ** * ** *** ## Components * Map content * Fills * Lines * Labels * Symbols * Scale * North arrow * Map inset for focus area, for **static maps**, if needed * Buttons, for **live maps** * [Pop-overs](https://help.fews.net/brand/interactive-components.md#Popover) and [tooltips](https://help.fews.net/brand/interactive-components.md#Tooltip), for **live maps** *** ** * ** *** ## Padding and spacing * Map content reaches the edges of the frame * For enclosed components: * 12px top and bottom padding * 16px side padding, except buttons when present * For buttons, when present: * 12px side padding * 12px between buttons *** ** * ** *** ## Layout and responsiveness * Scale hugs bottom left * North arrow hugs bottom right * For **live maps**: * Map content crops with center focus as width decreases until 609px width is reached, after which map content width and height scale down proportionally * Buttons hug top right * Buttons stack vertically *** ** * ** *** ## Fills ### Basic colors | **Type** | **Fill color** | **Additional specifications** | |--------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Geographic default | Gray 300 (#E6E7E8) | * Use for non-focused and non-filled countries or other geographic units | | Geographic default with part focused | Gray 400 (#D1D3D4) | * Use for non-focused and non-filled areas of countries or other geographic units on maps where at least one country has a partial area that is able to be focused or that is the subject of a static map (e.g. area of concern, trade flow maps) **Needs clarification** | | Geographic focused | Brand White (#FFFFFF) | * Use for non-filled countries or other geographic units on live maps that are able to be focused and have user focus, or that are the subject of a static map | | Water | Ocean 400 (#BCDAE9) | * Use for mapped bodies of water including oceans, lakes, rivers | ### IPC colors Use for maps that display IPC-compatible analysis. For Remote Monitoring countries, use the appropriate fill color as a thick inner border that hugs the country boundary. The un-filled center area of the country should use **Brand White** (#FFFFFF) as a background fill. | **Type** | **Phase** | **Fill color** | **Additional specifications** | |----------------------------------------------|----------------------|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| | Acute Food Insecurity and Acute Malnutrition | None / Minimal | #CDFACD; RGB: 205, 250, 205 | | | Acute Food Insecurity and Acute Malnutrition | Stressed | #FAE61E; RGB: 250, 230, 030 | | | Acute Food Insecurity and Acute Malnutrition | Crisis | #E67800, RGB: 230, 120, 000 | | | Acute Food Insecurity and Acute Malnutrition | Emergency | #C80000, RGB: 200, 0, 0 | | | Acute Food Insecurity and Acute Malnutrition | Catastrophe / Famine | #640000, RGB: 100, 0, 0 | | | Acute Food Insecurity and Acute Malnutrition | Famine Likely | #640000, RGB: 100, 0, 0 | * Overlay [++diagonal white stripes++](https://drive.google.com/file/d/1vKqEk9Vke2_1C4KJWaC8Clb-2XeEP_VD/view?usp=sharing) from bottom left to top right | | Chronic Food Insecurity | None / Minimal | #CDFACD; RGB: 205, 250, 205 | | | Chronic Food Insecurity | Mild | #CBC9E2; RGB: 203, 201, 226 | | | Chronic Food Insecurity | Moderate | #9E9AC8; RGB: 158, 154, 200 | | | Chronic Food Insecurity | Severe | #6A51A3; RGB: 106, 81, 163 | | | All types | Areas not analyzed | #BDBDBD; RGB: 189, 189, 189 | | ### Diverging colors Use these colors for non-IPC maps with a 3 to 7 point diverging scale used as a country fill for a variable (e.g. self sufficiency status). These colors ensure good differentiation for color blindness and grayscale printing. | **Color** | **7 point scale** | **6 point scale #1** | **6 point scale #2** | **5 point scale** | **4 point scale #1** | **4 point scale #2** | **3 point scale** | |-----------------------------------------|-------------------|----------------------|----------------------|-------------------|----------------------|----------------------|-------------------| | Lime 600: #689F38, RGB: 104, 159, 56 | x | x | x | x | x | x | x | | Lime 500: #8BC34A, RGB: 139, 195, 74 | x | x | x | x | x | | | | Lime 400: #AED581; RGB: 174, 213, 129 | x | | x | | | | | | Yellow 400: #FFF59D; RGB: 255, 245, 157 | x | x | x | x | x | x | x | | Orange 500: #BA6B55; RGB: 186, 107, 85 | x | x | | | | | | | Orange 600: #B95A38; RGB: 185, 90, 56 | | | x | x | | x | | | Orange 700: #AB4B1E; RGB: 171, 75, 30 | x | x | | | | | | | Red 600: #6D4140; RGB: 109, 65, 64 | x | x | x | x | x | x | x | | Gray 400: #D1D3D4; RGB: 209, 211, 212 | No data ||||||| ### Sequential colors This sequence of colors is a neutral option for sequential scales and can be used either as a fill or as symbols. These colors were selected to ensure good differentiation for color blindness and grayscale printing. Other brand colors may be used for sequential scales as long as they achieve good differentiation for color blindness and greyscale display. | Color | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ![Sample of Blue 400, the lightest blue.](https://help.fews.net/__attachments/a_f6c16eb95e2977ab6a60a18795bb8f1c90317e83abb01b52dba125bdf77f20e6/blue-400.png?cb=e91d293ed18b1b4761faf7f1caae12a4) Blue 400: #A6BFE2; RGB: 166, 191, 226 | | ![Sample of blue 500.](https://help.fews.net/__attachments/a_eec404b8bb3200d46a64357ff7039a77b15fab24b237b3203f314f6a3aaee6f5/blue-500.png?cb=4ef25eb001622c65f567e19d1b3a10f5) Blue 500: #688CCA; RGB: 104, 140, 202 | | ![Sample of blue 600.](https://help.fews.net/__attachments/a_ea4569d5388cc5be595787dbd15a1230988bb8bbdc779f7d996206fd55974907/blue-600.png?cb=31b7d6b4f7bb2261559294636767dcec) Blue 600: #426FBC; RGB: 66, 111, 188 | | ![Sample of blue 700, the darkest blue.](https://help.fews.net/__attachments/a_e425881fee21779a2fdb95f04aea1fa260506a0d88f9c09add981faf116e1ab2/blue-700.png?cb=6b0aae8308a335b999b25bcc473b8ad4) Blue 700: #305088; RGB: 48, 80, 136 | | ![Sample of purple 700.](https://help.fews.net/__attachments/a_e9e5f70181e43fc272aae091376d1f74cd7c81e91c8ba991dcce42a62124d724/purple-700.png?cb=1f95e4d2bbabdce19c0d792d29a39b89) Purple 700: #492674; RGB: 73, 38, 116 | | ![Sample of charcoal 700.](https://help.fews.net/__attachments/a_2933665eb8b35f0af064df67b32abfbb41e55bfc5ba30a1239db4b340cfefb9b/charcoal-700.png?cb=fa88c0f346b90132d94babcdc2e60cd1) Charcoal 700: #0C1D28; RGB: 12, 29, 40 | ### Patterns #### Data texture There are 15 data texture patterns available to overlay on color fills to provide additional distinction between fills. Download the .svg files in the [++data texture patterns++](https://drive.google.com/drive/folders/1kYo8eqJxlgsynJZ-0Ln4TMgJ_jRSUTl3?usp=sharing) folder. #### IPC IPC fill patterns may be found in the [++data visualizations \> IPC folder++](https://drive.google.com/drive/folders/1aCLhj2npt60OYYXG0qmdnldTaQdeOgsX?usp=sharing), including: * Humanitarian assistance layer (exclamation points) * Insufficient evidence layer (hexagons) * Famine likely (diagonal white stripes) ### Additional options Refer to the full [++data visualization colors++](https://help.fews.net/brand/colors.md#Data-visualization-colors) to find fill options for non-scale maps (e.g. livelihoods attributes and zones). The 400 shades and lighter have greatest contrast with boundary lines, roads, and other map labels and markings. Using a mix of colors across columns will ensure best contrast for color blindness and grayscale printing. For **livelihood zone maps**, use the following colors for livelihood zone types: * Cropping: Greens * Agro-pastoral: Olive greens * Pastoral: Oranges * Riverine/coastal: Purples *** ** * ** *** ## Lines Styles in this section are for lines that map directly onto geography. For styles associated with symbols and arrows, see those categories. | **Type** | **Thickness** | **Color** | **Additional Specifications** | |-------------------------------------------------------------------------------------|---------------|------------------------|--------------------------------------------------------------------------------------------| | Administrative Unit 0 boundary (static) | 2px (2pt) | Brand Black (#212721) | * Use for static maps | | Administrative Unit 0 boundary (live, Administrative Unit 1 boundaries showing) | 2px (2pt) | Brand Black (#212721) | * Use for live maps where the zoom level is such that Admin 1 boundaries are displayed | | Administrative Unit 0 boundary (Live, Administrative Unit 1 boundaries not showing) | 1px (1pt) | Charcoal 600 (#3A454C) | * Use for live maps where the zoom level is such that Admin 1 boundaries are not displayed | | Administrative Unit 1 boundary | 1px (1pt) | Charcoal 600 (#3A454C) | | | Administrative Unit 2 or below boundary | 1px (1pt) | Charcoal 400 (#7C888D) | | | Major road | 2px (2pt) | Charcoal 600 (#3A454C) | * Use for primary and trunk roads * Always use a solid, non-dashed line | | Minor road | 1px (1pt) | Charcoal 500 (#555E62) | * Use for secondary roads * Always use a solid, non-dashed line | *** ** * ** *** ## Symbols ### Interface | Marker Name | Icon | Specifications | |-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| | North arrow | ![North arrow component.](https://help.fews.net/__attachments/a_ebb66c5bd151af03552f915213ca5186738a21e8cd5017547af57f15c0d44a77/TZXjYVZrvNTMjNTvZKe63wiWXhtCQ9lWdULtawLKZCwPDSqHISyTRoTCOvLgiJFJpzav2WoYKiUcSd6GfnO4b7oi_9R_qDrkYubh6KzRuFaHMdWOQK_NNz3hhcTPvmXJSuZfxhw2d5jgmPT9hVy2ImE?cb=697d7e1242f326aa39135419b5a56ca9) | * See: * Padding and Spacing * Layout and Responsiveness | ### Content #### Geographic markers Files for the symbols for capitals, a north arrow, national parks, and IPC maps can be found in the [++data visualizations++](https://drive.google.com/drive/folders/1RQKq9KIAr39elKFFdQ1boZuJoOVsAa8M?usp=sharing) folder. | Marker Name | Icon | Specifications | |-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| | Capital city (country and regional map) | ![Circle with a star in the middle.](https://help.fews.net/__attachments/a_ffcb6cfbda43027b0d39dc5ffcf29f054adca75c24a4e72a0a6973f50d239882/CUzAt1agS6rhYC_K4jhbmdKILFkOkJFCeu2fAMxf2wNsiE8W-LcvSPgNQYG4lHJR1lzDccCxrPKvYUAESB2OecfjL6cTt1ZV7bOpGx0V5N1uvxuSxTRXNWDjpLnFC50Suwd79vMcFq_eYbndJmFE1_I?cb=25d6be8bc9901dd4e0e916aa18e4e030) | | | Capital city (global map) | ★ | | | City | * | Dot, Brand Black (#212721) | | Market | ![Black square.](https://help.fews.net/__attachments/a_e3fdb39fa228f960fb11ff8fd10b3772b57f6f7353a09d99362615d681e25df8/Screenshot%202024-05-09%20at%203.40.18%E2%80%AFPM.png?cb=26da7632b0d69d931620722d31fc28b3) | Square, Brand Black (#212721) | | IDP Camp | | * Square shape with color matching the IPC classification for the camp * Use 1 px (1pt) outer border in Brand Black (#212721) | | National park | | See [++data visualizations++](https://drive.google.com/drive/folders/1RQKq9KIAr39elKFFdQ1boZuJoOVsAa8M?usp=sharing) folder for pattern | | Humanitarian Food Assistance ( ≥25% of households met 25-50% of their kcal needs through HFA) | ![Light gray wheat bag.](https://help.fews.net/__attachments/a_a3c735ad9b8b00b50ee54a25f6a9fe3b537c7249f6c221580caa47d1ce74ea7b/90dA8lN6-ZdxTaUUQNLNDU6Gz2oE8Du5QpQgGKJiELy-mm5ZOpIgbNokI688MmIoAgk11NLBSsen8CGRvVNcgkOqbosFcyt51ct0lunPU0Rhqt4MLK2uCW5X_HHMLMM0rXppAzrJMgk_x3mTzj6qJy4?cb=4ec1b49af768e00553079963fd7bc573) | * Use for IPC maps | | Humanitarian Food Assistance ( ≥25% of households met \>50% of their kcal needs through HFA) | ![Dark colored wheat bag.](https://help.fews.net/__attachments/a_4c1ef6c107d2dccbb510d341bab74b66d9d01f27caa0e8b7d264af1ebc93cea4/pw7JiXEKUk1_Xj7uJugk2ihUmIQGAVAZrzICTjPo9ltN8MYCBpkWbD-scaYLWoN1MLd5KsxJwgbG0WkVVx3tBpGX7ePMGbOtCWhbWd41t7ubYvaW93OpJNZa5Q1LOD9OxXi_iqbkxW1yEIagqOvrNbw?cb=fdfa919aac161c8d865d6b600170b11b) | * Use for IPC maps | #### Diverging scale markers Use these symbol and color combinations for non-IPC maps with a 3 to 7 point diverging scale (e.g. commodity price maps and price change maps). All symbols use the fill colors listed in the Right hand column and are outlined in a 1 pt/1 px line using Brand Black (#212721). The up and down direction of the triangles can be switched if that makes sense for the data. Since the symbols aid in differentiation, these colors are as visually different as possible in both color and grayscale within each shape group on a small scale. | Color | 7 point scale | 5 point scale | 4 point scale #1 | 4 point scale #2 | 3 point scale | |-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Pine 800: #0C5D40; RGB: 12, 93, 64 | ![Triangle filled with Pine 800.](https://help.fews.net/__attachments/a_49e2c734be2b23d60958e019e4d09b1ef600744aa5570c3ea2ba59b74f7a81a0/haM2T6o71-6qNyuCSmbuPygE44Wm197i_54pTp-f6PHQ_4AyoY50FbTTFYFKhVh_vPQo4mPIb5AH7NImsdQpXkMo37L9G3hUnLHQpo0AFGEGciPmy7NmtptInW76uT_Zvxy_ytSKoH9neb2W-HX-Fj4?cb=c249e3206ca5dcdb53a84e16d4899cd8) | | | | | | Lime 600: #689F38, RGB: 104, 159, 56 | ![Triangle filled with Lime 600.](https://help.fews.net/__attachments/a_ca785855355228fa992f4fa89ddfb83ccac9e205c390ce3f946e82776ef1f901/zdRdz7ZdoybM_BRMNrvYaZbNyrG62fKXlHWGHKViGRrcBp5A90hGFIBBMUNQNZ-Y8rijynFaBqfoHPfZDKM_Q2hW-FyckC0i_v4yaSJQNOq9UQnB7HAOkvGvn1srzhPZiwaM6NQFJouEjjvcwPJrIZ4?cb=000dca25527a52e6cf03cffecd5ce7d9) | ![Triangle filled with Lime 600.](https://help.fews.net/__attachments/a_ca785855355228fa992f4fa89ddfb83ccac9e205c390ce3f946e82776ef1f901/zdRdz7ZdoybM_BRMNrvYaZbNyrG62fKXlHWGHKViGRrcBp5A90hGFIBBMUNQNZ-Y8rijynFaBqfoHPfZDKM_Q2hW-FyckC0i_v4yaSJQNOq9UQnB7HAOkvGvn1srzhPZiwaM6NQFJouEjjvcwPJrIZ4?cb=000dca25527a52e6cf03cffecd5ce7d9) | ![Triangle filled with Lime 600.](https://help.fews.net/__attachments/a_ca785855355228fa992f4fa89ddfb83ccac9e205c390ce3f946e82776ef1f901/zdRdz7ZdoybM_BRMNrvYaZbNyrG62fKXlHWGHKViGRrcBp5A90hGFIBBMUNQNZ-Y8rijynFaBqfoHPfZDKM_Q2hW-FyckC0i_v4yaSJQNOq9UQnB7HAOkvGvn1srzhPZiwaM6NQFJouEjjvcwPJrIZ4?cb=000dca25527a52e6cf03cffecd5ce7d9) | ![Triangle filled with Lime 600.](https://help.fews.net/__attachments/a_ca785855355228fa992f4fa89ddfb83ccac9e205c390ce3f946e82776ef1f901/zdRdz7ZdoybM_BRMNrvYaZbNyrG62fKXlHWGHKViGRrcBp5A90hGFIBBMUNQNZ-Y8rijynFaBqfoHPfZDKM_Q2hW-FyckC0i_v4yaSJQNOq9UQnB7HAOkvGvn1srzhPZiwaM6NQFJouEjjvcwPJrIZ4?cb=000dca25527a52e6cf03cffecd5ce7d9) | ![Triangle filled with Lime 600.](https://help.fews.net/__attachments/a_ca785855355228fa992f4fa89ddfb83ccac9e205c390ce3f946e82776ef1f901/zdRdz7ZdoybM_BRMNrvYaZbNyrG62fKXlHWGHKViGRrcBp5A90hGFIBBMUNQNZ-Y8rijynFaBqfoHPfZDKM_Q2hW-FyckC0i_v4yaSJQNOq9UQnB7HAOkvGvn1srzhPZiwaM6NQFJouEjjvcwPJrIZ4?cb=000dca25527a52e6cf03cffecd5ce7d9) | | Lime 400: #AED581; RGB: 174, 213, 129 | ![Triangle filled with Lime 400.](https://help.fews.net/__attachments/a_c51e82192e9ee922cbcec52463bf96cc28a363a7829e64287cb764ea8a5b39b4/WE3sqTU27l6aIVERAhAM1WHIxuM_mJnWlWsvWwtzMN1kHK_F0caofMcPn9VfnSaW-h6uUsg541bKYv3HM_QCh6y2grR6VgOw_whqrLWYlqebzcpztoOlhpyyyytoSDJLibAhOWPSgB13DuCryvqUE6o?cb=7f81ccfaea3a511774b34483470ab043) | ![Triangle filled with Lime 400.](https://help.fews.net/__attachments/a_c51e82192e9ee922cbcec52463bf96cc28a363a7829e64287cb764ea8a5b39b4/WE3sqTU27l6aIVERAhAM1WHIxuM_mJnWlWsvWwtzMN1kHK_F0caofMcPn9VfnSaW-h6uUsg541bKYv3HM_QCh6y2grR6VgOw_whqrLWYlqebzcpztoOlhpyyyytoSDJLibAhOWPSgB13DuCryvqUE6o?cb=7f81ccfaea3a511774b34483470ab043) | ![Triangle filled with Lime 400.](https://help.fews.net/__attachments/a_c51e82192e9ee922cbcec52463bf96cc28a363a7829e64287cb764ea8a5b39b4/WE3sqTU27l6aIVERAhAM1WHIxuM_mJnWlWsvWwtzMN1kHK_F0caofMcPn9VfnSaW-h6uUsg541bKYv3HM_QCh6y2grR6VgOw_whqrLWYlqebzcpztoOlhpyyyytoSDJLibAhOWPSgB13DuCryvqUE6o?cb=7f81ccfaea3a511774b34483470ab043) | | | | Yellow 400: #FFF59D; RGB: 255, 245, 157 | ![Circle filled with Yellow 400.](https://help.fews.net/__attachments/a_3c907a528c812ad2afccb98c55233c6c18d87038403c7fe88848bea0bb9a3851/wC-CYZx3ZbRM1qWIlXvN-1PMwa_rJ_j527XKB-gRu1nqZg4QQD_IHrRbqHJ31nhuNvohJXShi76tXqsw1-tEP77MkZE9-CQWbjuWY_irm3jMe5OBhbW43nFojJ38xpRoQTE8NjQBJC3q53VAgSzxvDA?cb=2e01aefb9c130960550eaeb2b4bc2790) | ![Circle filled with Yellow 400.](https://help.fews.net/__attachments/a_3c907a528c812ad2afccb98c55233c6c18d87038403c7fe88848bea0bb9a3851/wC-CYZx3ZbRM1qWIlXvN-1PMwa_rJ_j527XKB-gRu1nqZg4QQD_IHrRbqHJ31nhuNvohJXShi76tXqsw1-tEP77MkZE9-CQWbjuWY_irm3jMe5OBhbW43nFojJ38xpRoQTE8NjQBJC3q53VAgSzxvDA?cb=2e01aefb9c130960550eaeb2b4bc2790) | ![Circle filled with Yellow 400.](https://help.fews.net/__attachments/a_3c907a528c812ad2afccb98c55233c6c18d87038403c7fe88848bea0bb9a3851/wC-CYZx3ZbRM1qWIlXvN-1PMwa_rJ_j527XKB-gRu1nqZg4QQD_IHrRbqHJ31nhuNvohJXShi76tXqsw1-tEP77MkZE9-CQWbjuWY_irm3jMe5OBhbW43nFojJ38xpRoQTE8NjQBJC3q53VAgSzxvDA?cb=2e01aefb9c130960550eaeb2b4bc2790) | ![Circle filled with Yellow 400.](https://help.fews.net/__attachments/a_3c907a528c812ad2afccb98c55233c6c18d87038403c7fe88848bea0bb9a3851/wC-CYZx3ZbRM1qWIlXvN-1PMwa_rJ_j527XKB-gRu1nqZg4QQD_IHrRbqHJ31nhuNvohJXShi76tXqsw1-tEP77MkZE9-CQWbjuWY_irm3jMe5OBhbW43nFojJ38xpRoQTE8NjQBJC3q53VAgSzxvDA?cb=2e01aefb9c130960550eaeb2b4bc2790) | ![Circle filled with Yellow 400.](https://help.fews.net/__attachments/a_3c907a528c812ad2afccb98c55233c6c18d87038403c7fe88848bea0bb9a3851/wC-CYZx3ZbRM1qWIlXvN-1PMwa_rJ_j527XKB-gRu1nqZg4QQD_IHrRbqHJ31nhuNvohJXShi76tXqsw1-tEP77MkZE9-CQWbjuWY_irm3jMe5OBhbW43nFojJ38xpRoQTE8NjQBJC3q53VAgSzxvDA?cb=2e01aefb9c130960550eaeb2b4bc2790) | | Orange 400: #D6A79A; RGB: 214, 167, 154 | ![Triangle filled with Orange 400.](https://help.fews.net/__attachments/a_43a5b31f90bdbc8ad39ff334206e12261b58ee904d4b4fb2201467881d641cdd/cUsOtItn27Gl5cks7ucQfk6VbbKBvUezTjzjbH9ylaWuek_wOOEAkWbkmbhp3dmufc77vn-S1i_D-TinmVXdIfc5_ENXdv7C9X_z7Z3hD-Crt7_03yEGLm8jhC1hakmiiw7IWPXwU-5O5nOAltm1krw?cb=32e4e68034470ae3e0a0d81b483c422c) | ![Triangle filled with Orange 400.](https://help.fews.net/__attachments/a_43a5b31f90bdbc8ad39ff334206e12261b58ee904d4b4fb2201467881d641cdd/cUsOtItn27Gl5cks7ucQfk6VbbKBvUezTjzjbH9ylaWuek_wOOEAkWbkmbhp3dmufc77vn-S1i_D-TinmVXdIfc5_ENXdv7C9X_z7Z3hD-Crt7_03yEGLm8jhC1hakmiiw7IWPXwU-5O5nOAltm1krw?cb=32e4e68034470ae3e0a0d81b483c422c) | | ![Triangle filled with Orange 400.](https://help.fews.net/__attachments/a_43a5b31f90bdbc8ad39ff334206e12261b58ee904d4b4fb2201467881d641cdd/cUsOtItn27Gl5cks7ucQfk6VbbKBvUezTjzjbH9ylaWuek_wOOEAkWbkmbhp3dmufc77vn-S1i_D-TinmVXdIfc5_ENXdv7C9X_z7Z3hD-Crt7_03yEGLm8jhC1hakmiiw7IWPXwU-5O5nOAltm1krw?cb=32e4e68034470ae3e0a0d81b483c422c) | | | Orange 600: #B95A38; RGB: 185, 90, 56 | ![Triangle filled with Orange 600.](https://help.fews.net/__attachments/a_4a783258b03ec05ae78cc87ff820024ee45d0d12aaed38aaefd17746d9adc820/XCIVstg9wXoGPh3uguck6bHJNupCFVj9sOSYoVMW55D7ZulakhmnKKB_I-NdysmAmhYOHVgySAtQpBL7HI1snrTEN7yqa6DM-Gl6F5isjRIYa6a6A-uPjsoyQ6OK90S35NCYb71QZhLEqr3pazfRdmk?cb=3a4ed0b803a2afac5c4a4bb3a47a37b8) | ![Triangle filled with Orange 600.](https://help.fews.net/__attachments/a_4a783258b03ec05ae78cc87ff820024ee45d0d12aaed38aaefd17746d9adc820/XCIVstg9wXoGPh3uguck6bHJNupCFVj9sOSYoVMW55D7ZulakhmnKKB_I-NdysmAmhYOHVgySAtQpBL7HI1snrTEN7yqa6DM-Gl6F5isjRIYa6a6A-uPjsoyQ6OK90S35NCYb71QZhLEqr3pazfRdmk?cb=3a4ed0b803a2afac5c4a4bb3a47a37b8) | ![Triangle filled with Orange 600.](https://help.fews.net/__attachments/a_4a783258b03ec05ae78cc87ff820024ee45d0d12aaed38aaefd17746d9adc820/XCIVstg9wXoGPh3uguck6bHJNupCFVj9sOSYoVMW55D7ZulakhmnKKB_I-NdysmAmhYOHVgySAtQpBL7HI1snrTEN7yqa6DM-Gl6F5isjRIYa6a6A-uPjsoyQ6OK90S35NCYb71QZhLEqr3pazfRdmk?cb=3a4ed0b803a2afac5c4a4bb3a47a37b8) | ![Triangle filled with Orange 600.](https://help.fews.net/__attachments/a_4a783258b03ec05ae78cc87ff820024ee45d0d12aaed38aaefd17746d9adc820/XCIVstg9wXoGPh3uguck6bHJNupCFVj9sOSYoVMW55D7ZulakhmnKKB_I-NdysmAmhYOHVgySAtQpBL7HI1snrTEN7yqa6DM-Gl6F5isjRIYa6a6A-uPjsoyQ6OK90S35NCYb71QZhLEqr3pazfRdmk?cb=3a4ed0b803a2afac5c4a4bb3a47a37b8) | ![Triangle filled with Orange 600.](https://help.fews.net/__attachments/a_4a783258b03ec05ae78cc87ff820024ee45d0d12aaed38aaefd17746d9adc820/XCIVstg9wXoGPh3uguck6bHJNupCFVj9sOSYoVMW55D7ZulakhmnKKB_I-NdysmAmhYOHVgySAtQpBL7HI1snrTEN7yqa6DM-Gl6F5isjRIYa6a6A-uPjsoyQ6OK90S35NCYb71QZhLEqr3pazfRdmk?cb=3a4ed0b803a2afac5c4a4bb3a47a37b8) | | Red 600: #6D4140; RGB: 109, 65, 64 | ![Triangle filled with Red 600.](https://help.fews.net/__attachments/a_8aacb88ee8abbd11c3aa4dc0ee8ca2108f6ab75507486311defac4376e621a3c/OqeCxKpQX7I_bVpXHwY8yeXlnuCjbH4zpbqBrjpdgy8rWjHtdztK0wo_PghhIxsPLDLyKugVXubBK8c2lDZuOsu46dvz39no2trAaqV12KHMM29XjSotMgNWb4IcK9FUR9p4wErO3rcJPp4VbrAGdKs?cb=3f96c76c139990817dee83801d7bbe10) | | | | | #### Arrows Use arrows to represent flows. All arrows should be rendered in **Brand Black** (#212721). | Type | Specifications | |-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Large flow | * Line: Width: 4 pt.; Caps: butt; Joins: miter * Marker: Right flow triangle; Size: 14 pt.; Angle: 0 * At extremities: Extremity: Just end, position: 1.5 pt. * Angle to line: check | | Medium flow | * Line: Width: 2.5 pt.; Caps: butt; Joins: miter * Marker: Right flow triangle; Size: 10 pt.; Angle: 0 * At extremities: Extremity: just end; position: 1.5 * Angle to line: Check | | Small flow | * Line: Width: 1pt; Caps: butt; Joins: miter * Marker: Right flow triangle; Size: 7pt; Angle: 0 * At extremities: Extremity: Just end, position: 1.5 * Angle to line: check | #### Bubbles Use bubble layers to represent a variable numerical quantity associated with specific locations (e.g., number of conflicts). Use the following formatting for bubbles: * Shape: circle * Size: Use a size-graduated range with diameters between 4pt minimum and 18pt maximum * Fill: See full [++data visualization colors++](https://help.fews.net/brand/colors.md#Data-visualization-colors) for options. Use any color from the 500 column. * Border: 1pt outer border using the color from the 600 column that corresponds with the fill color. *** ** * ** *** ## Buttons The on-map zoom buttons are combined into a single visual unit of two vertically adjoined buttons of 36px height each and 40px width. Buttons have 80px corner rounding on the non-adjoined corners. The on-map expand and download buttons are circles of 40px diameter. All buttons use **Brand White** (#FFFFFF) background fill and icons use **Brand Black Dark** (#090B09). For hover state, icons change to **Brand Primary**(#096640). Buttons cast the on-map shadow: | **Style name** | **Color** | **Blur** | **X offset** | **Y offset** | **Spread** | |-------------------|----------------------|----------|--------------|--------------|------------| | Viz On-Map Shadow | #000000, 25% opacity | 10px | 0px | 1.87px | 0px | *** ** * ** *** ## Wordmark and Logos * **FEWS NET maps that are not presented inside a FEWS NET web property or official report** should always include the FEWS NET wordmark on the left (horizontal, 0.5 inch, PNG) and the U.S. Department of State logo on the right (horizontal, RGB, 294, PNG). Both should be equal size on the map. Both should also have a transparent background. If a map is embedded in a report that is branded with both the FEWS NET wordmark and U.S. Department of State logo, these maps should not include any wordmarks or logos. Wordmark and logo guidance and links to files can be found on [Wordmark and Partner Logos](https://help.fews.net/brand/logos.md). *** ** * ** *** ## Map inset for focus area Use inside the map body on **static maps**when there is a focus area that includes an entire country or countries. * Country fill: Steel 400 (#98A9AE) * Highlight box border: 1px (1pt), **Orange 700** (#AB4B1E) * Inset map border: 1px (1pt), **Brand Black** (#212721) *** ** * ** *** ## Typography FEWS NET visualizations use the **Segoe UI** typeface unless specified otherwise. Use Open Sans if Segoe UI is not available. All text for maps uses **Brand Black** (#212721) with a 1px (1pt) outer stroke in **Brand White**(#FFFFFF). | **Style name** | **Font** | |-----------------------|----------------------| | City / Market | 9px (7pt) Regular | | Capital city | 14px (10pt) Regular | | Administrative Unit 0 | 16px (12pt) Bold | | Administrative Unit 1 | 14px (10pt) Semibold | | Administrative Unit 2 | 12px (9pt) Semibold | | Administrative Unit 3 | 10px (8pt) Semibold | *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Photography FEWS NET photography should be bright, easily understood, and demonstrate realistic, neutral perspectives on the subjects. Do not show individuals decontextualized from their surroundings or an exoticized version of a culture or population. Photography should not appear as philanthropic. Three types of photographs make up the photography system: * **Arial:** Populations, agriculture, and urban environments. * **Close ups:** Crops and topical sectors with shallow depth of field. Do not use close ups of people that blur or decontextualize their surroundings. * **In the field:** FEWS NET in action depicting actual field work and partners. Use only FEWS NET custom photography for this category. ![An enumerator filling out a farm at a market.](https://help.fews.net/__attachments/a_58cf504381bddfbfec1cfba0ca7ddeb7faf08e6cba1ad23bfb79455a93d3f761/FEWS_NET_Field%20Photo_8.jpg?cb=66fb3fcff03a1f8485756cf481f46114) ![A field full of rows of green crops.](https://help.fews.net/__attachments/a_cd0b23844bea98c6f34fb6043d6428c468c1a52c7138a3bd310e7f1c9204405e/FEWS_NET_Field%20Photo_5.jpg?cb=3faf19a518922ac2fcce950410afd111) ## Finding photos Use photos from FEWS NET, including the [++FEWS NET Flickr account++](https://www.flickr.com/photos/148917357@N03/), when possible. When custom photography is not available, select and license existing photography that features relevant FEWS NET subject matter. Curation is critical to choosing photos that are authentic and reflective of the FEWS NET brand. Audiences should not be able to tell the difference between stock and custom photos. ### Sources for stock photography * [++Pexels++](https://www.pexels.com/): Free stock photos \& videos you can use everywhere. * [++Unsplash++](https://unsplash.com/): Beautiful, free images and photos that you can download and use for any project. * [++iStock++](https://www.istockphoto.com/): Stand out with affordable royalty-free stock photos (paid option). ### Guidance for choosing stock photography * Follow the photography standards included here. Use bright, easily understood, realistic photography with aerial or close up perspectives. * Use keywords to narrow your search. Search using terms like "aerial" "crops" "urban" and actual FEWS NET operating areas like "Mozambique". * Aim for authenticity first. Obvious stock photography lacks authenticity and degrades the brand. Make sure selected photos feel real in terms of both the subject matter and setting. * Avoid overly stylized editing. If it doesn't have a similar aesthetic quality as brand standards, it is not a fit. *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. --- language: "en" --- # Presentations The primary brand guidance for presentations is included directly on the FEWS NET slide deck template. This page provides information about accessing and using the template, plus some basic best practices. ## Using the template * A link to the FEWS NET presentation template may be found on the [FEWS NET Exchange Intranet](https://sites.google.com/fews.net/exchange2/work-essentials/templates?authuser=0#h.tf766noifcaz) (staff only). * Always use the FEWS NET presentation template and do not modify the styles in any way. Upholding consistent presentation standards helps advance FEWS NET's global credibility and maintains compliance with branding and marking requirements. If you have already started to create a slide deck and need to apply the FEWS NET theme, open your slide deck and click **Theme** \> **Import Theme \> YYYYMMDD FEWS NET Slide deck template.**The correct source template will have the "Belongs to a shared drive" indicator next to its name. ![Google slides interface with the theme buttons highlighted.](https://help.fews.net/__attachments/a_fde85bf7db6d07c991ba578ba2296fe2dcd4c84ad1ee89c801f243036dfa881a/Apply_Theme_Instructions_1.png?cb=f4f5bd64d5b292324848b91bea6b50b6) ![Import theme dialogue box with the FEWS NET slide deck template circled.](https://help.fews.net/__attachments/a_27f88a4d9f304e07742e42428e1bfd094127e3977948d875453ff6f42d1e1d62/Screenshot%202026-08-13%20at%201.17.12%E2%80%AFPM.png?cb=48fcb3b5c1df6555bb6a39d1453a309d) ### Slide layouts The FEWS NET slide deck theme has pre-formatted slide layouts. Layouts are always applied to an existing slide, so add a new slide using the plus sign on the left of the toolbar if you want to create a new slide with a particular layout. To use the layouts, select **Layout**from the toolbar, and then select a layout to apply to the current slide. The layout can be changed at any time using the Layout button. To ensure consistency: * Do not move the built-in text boxes or other elements. If you need to build a custom layout to convey specific information, use the Title only, Caption, or Blank slide formats. * Note that there are "standard" and "dense" slide layout options (e.g., "Title only standard" vs. "Title only dense"). The standard option provides a cleaner look with more white space and the dense options allows more room for content. Choose one of these options consistently for all of your slides. ![Google slides interface with the add slide button highlighted.](https://help.fews.net/__attachments/a_7edea1aa893f1822672b7c3bbac57362763a7f1108ad3853ca7f8f48c35bdb9e/Apply_Layout_Instructions_1.png?cb=4aab62927cafcf83bf64d86d834650a2) ![Google Slides interface with the slide layout options highlighted.](https://help.fews.net/__attachments/a_c881f0135635c4986b7f8632cde9bc60d8302d0685ced48022eee82bfd55d38d/Screenshot%202026-08-13%20at%201.23.14%E2%80%AFPM.png?cb=16e8e0677c2794cc45da0e89240fbc59) ### Design resources The FEWS NET slide deck template contains slides with copy and paste design resources (starting on slide 9). These resources can be used to create brand compliant tables, captions, graphic organizers, and other visuals. Note that importing the theme, rather than starting a new slide deck from the template, will not give you access to these design resources. ![Slide from the template with design resources.](https://help.fews.net/__attachments/a_dbe8f5867efaedb3464d8a855ed433dad8e1a46d73fe6d657ad65c6df41339ee/Screenshot%202026-08-13%20at%201.35.54%E2%80%AFPM.png?cb=3120a35a6c2dd61681b34e36fd9267f2) ## Best practices ### Keep it simple. * Slides should contain 1-2 images or limited (clear and specific) text. * Images should be high quality; don't use clip art. * Use the presenter notes to help you remember your key points. * Use animations and transitions sparingly. ### Ensure accessibility. * Include alt-text for all images to ensure your presentation slides are ADA accessible if they are to be disseminated in a PDF format. To access alt-text, hit Ctrl+Alt+Y or right click on your image and choose Alt text. * Use the text boxes included in the layout rather than adding new text boxes. New text boxes should only be added for graphic organizers or other similar visual elements that are not already included in the layout formats. * When you present (Slideshow) with Google Slides, you can turn on automatic captions to display the speaker's words in real time at the bottom of the screen. Learn how to [++present slides with captions++](https://support.google.com/docs/answer/9109474). ### QA your presentation. * Run a spell check by going to **Tools** \> **Spelling** in Google or **Review \> Spelling** in PPT. * Preview your presentation in slideshow mode to make sure everything looks correct and is working as intended. * Practice giving your presentation, preferably to a colleague, to ensure the content flows and you have not missed any crucial information. Set a timer to ensure you won't be rushed or end earlier than intended. *** ** * ** *** [Contact us](https://fewsnet.atlassian.net/servicedesk/customer/portal/2/group/15/create/43) if you have an application question or recommended addition to these standards. [Next Page](https://help.fews.net/llms-full.txt/1)