Splunk® Enterprise

Dashboards and Visualizations

Download a California counties shapefile

To generate a choropleth map in Splunk Web, you need a geographic feature collection file, also known as a shapefile or Keyhole Markup Language/Keyhole Markup Zipped (KML/KMZ) file, that provides geographic boundaries that match the spatial granularity of your data. This tutorial uses county-level drought data in California, so you need a feature collection that divides California into counties. You can download this file from the CA.gov California Open Data Portal.

Most US, city, and state-level government websites have Geospatial Information Systems (GIS) data portals where you can download geographic reference maps. Other sites with useful geographic reference maps include the US Census Bureau Cartographic Boundary Files site and the USGS The National Map Data Download site.

Prerequisites

Steps

Follow these steps to download the appropriate geographic feature collection. Alternatively, download the ca_counties.kmz.zip file directly.

  1. Navigate to the Datasets page of the California Open Data Portal.
  2. Locate the .kmz file of California county boundaries using one of the two following approaches:
    1. Enter California Counties in the search bar.
    2. Narrow your search using the following selections:
      Field in Dataset Search page Values
      Topics Economy and Demographics
      Format kml
  3. Select the file entitled California Counties and download the .kmz file.
  4. Rename the downloaded file to ca_counties.kmz.

Next step

Create a new geospatial lookup

Last modified on 01 August, 2019
Upload and configure your data   Create a new geospatial lookup

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.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.11, 8.1.13, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.3.0, 9.3.1, 9.3.2, 9.4.0, 8.1.10, 8.1.12, 8.1.14, 8.1.2


Was this topic useful?







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