Splunk® Enterprise

Dashboards and Visualizations

Download manual as PDF

Download topic as PDF

Tutorial overview

Choropleth maps visualize data aggregated by location.

To create a choropleth map that visualizes a value, you need a geographic feature collection that provides geographic boundaries at the same level of granularity as your data. For example, if you want to map the US population by state, you can use a Splunk search to create a statistics table with a row for the population of each state and use the geo_us_states lookup to render the geometry of states on the map. To map the population by county, you would need to create a more granular table with a row for every US county and a new geospatial lookup that provides boundaries of all US counties. To learn more about geospatial lookups, see Define a geospatial lookup in Splunk Web in the Knowledge Manager Manual.

Goals

In this tutorial, you will learn how to do the following:

  • Locate and upload a public data file from the United States Drought Monitor and a geospatial boundary file at the appropriate level of granularity into your Splunk platform instance.
  • Use the lookup file to create a new geospatial lookup in addition to the geo_us_states and geo_countries lookups that are included with Splunk software.
  • Generate a choropleth map that demonstrates the severity of drought conditions by California county in 2018.

Your finished choropleth map will look like the following image:
Screenshot of finished choropleth map of California drought severity in 2018

Prerequisite

Make sure that you have a running Splunk platform instance. See the following links for information:

Steps

  1. Locate and download USDM data
  2. Upload and configure your data
  3. Download a California counties shapefile
  4. Create a new geospatial lookup
  5. Generate a choropleth map
  6. (Optional) Use Trellis view to visualize multiple aggregate functions
PREVIOUS
Cluster maps
  NEXT
Locate and download USDM data

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 8.0.0, 8.0.1


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters