Maps
Anatomy of a map
Formatting quick reference
General typography
Use Segoe UI (or Open Sans) for all text
Specifications are listed by by element under Technical Specifications
Titles and subtitles
Use titles to describe the topic and geographic context
Use subtitles to describe time-relevant information
Use sentence case (see Capitalization)
Colors
Legends
Sources and disclaimers
Always include any necessary disclaimers and sources for data used in the chart.
Map types
Choosing the correct map type to visualize data for a famine early warning system is critical for conveying timely and actionable insights to decision-makers. The right map enables users to clearly interpret complex geographic patterns, assess areas of vulnerability, and make informed decisions about resource allocation and intervention. Different map types can highlight various aspects of the data, such as population density, crop conditions, or weather patterns, ensuring that key details aren’t overlooked. A well-chosen map type ensures that data is not only accessible but also effectively communicates urgency, helping stakeholders respond promptly to prevent or mitigate a famine crisis.
Use a choropleth map when:
Visualizing variations in data values across geographic regions (ex., countries, regions, livelihood zones) using color gradients or patterns.
You need to compare data across predefined geographic boundaries or regions and the data is continuous and quantitative (e.g., population density, income, unemployment rates)
Use a heat map when:
Showing the density or intensity of data points across a geographic area, using color to indicate areas of high and low concentration.
When data is concentrated or clustered in specific areas (ex., population clusters, disease outbreaks, temperature extremes).
Use a dot/point map when:
Representing individual occurrences or specific data points in geographic locations.
When you need to show discrete events or phenomena (ex., locations of aid centers, natural disaster occurrences, hospitals, or population counts).
Use a symbol map when:
Visualizing quantitative data by using symbols that vary in size according to the magnitude of the data at each location.
When comparing data magnitude at specific points (ex., crop production by location, population of cities, levels of water availability).
Use a density map when:
Showing the concentration of data points in an area, summarizing how densely data points are distributed across space.
When you want to emphasize data concentration rather than individual occurrences (ex. displaying the density of famine-related issues, such as concentrations of vulnerable populations or areas with high levels of food insecurity.)
When featuring trade routes & migration routes:
Layer travel patterns in the form of lines, shapes or arrows onto the appropriate map type.
Allow for enough contrast to be able to differentiate the layers.
Use line patterns in the map technical specifications.
Principles and best practices
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). Typography standards are available in the technical specifications for more details.
Use branded symbols. For symbol maps, use symbols outlined in Map Body. 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.
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.
Demonstrate intent with the timeframe chosen. Use subtitles and other time-related text that make it clear why a timeframe was chosen.
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.
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 are helpful for checking color contrast. See 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.
Legends
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 legend technical 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
Sources and Disclaimers
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. Don’t include verbose language or describe redundant details in the chart that are already apparent in the title, subtitle, or elsewhere.
Contact us if you have an application question or recommended addition to these standards.