Maps
Use a map to visualize geospatial data on a map area of your choice. Geospatial data combines your data sets with coordinates on Earth to visually represent quantities and spread across locations.
Generate a map
- Select the Add chart button (
) in the editing toolbar and browse through the available charts. Choose the map.
- Select the map on your dashboard to highlight it with the blue editing outline.
- Set up a new data source by selecting + Create search and adding a search to the SPL query window. Or, you can select an existing data source under the Search, Saved search, or Chain search sections.
- Maps with marker clusters use the SPL
tablecommand. - Maps with bubble clusters use the SPL
geostatscommand. - For example, the following are two different searches. The first is a search for marker layers and the second is a search for bubble layers.
| inputlookup geomaps_data.csv | iplocation device_ip | table bytes device_ip lat lon| inputlookup geomaps_data.csv | iplocation device_ip | geostats latfield=lat longfield=lon count by method - Maps with marker clusters use the SPL
- (Optional) You can also write a new ID that describes the search better than the default by changing the ID in Data source name.
- Select Apply and close.
Set a tile for the base map
Change your map's background by setting a tile for your base map with the options baseLayerTileServer and baseLayerTileServerType. Valid types for baseLayerTileServerType include "vector" and "raster". Types depend on whether the URL set for baseLayerTileServer is a vector or raster map tile.
For more details about options for maps, see Source options for maps.
The following map visualization uses a raster tile for a base map.
Expand the window to see the source code example for setting a tile for a base map. Notice how baseLayerTileServer uses a raster map tile from a URL.
{
"visualizations": {
"viz_lsqZJ7UN": {
"type": "splunk.map",
"options": {
"layers": [
{
"type": "marker",
"latitude": "> primary | seriesByName('lat')",
"longitude": "> primary | seriesByName('lon')"
}
],
"center": [
15.121212505317928,
-54.48385692078051
],
"zoom": 1.482683999151066,
"baseLayerTileServer": "https://api.maptiler.com/maps/outdoor/{z}/{x}/{y}.png?key=NmOL38t5MnH6pNq8if7p",
"baseLayerTileServerType": "raster"
},
"dataSources": {
"primary": "ds_lfaIoBgK"
},
"context": {},
"showProgressBar": false,
"showLastUpdated": false
}
},
"dataSources": {
"ds_lfaIoBgK": {
"type": "ds.search",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| table bytes device_ip lat lon"
},
"name": "Search_1"
}
},
"defaults": {
"dataSources": {
"ds.search": {
"options": {
"queryParameters": {
"latest": "$global_time.latest$",
"earliest": "$global_time.earliest$"
}
}
}
}
},
"inputs": {
"input_global_trp": {
"type": "input.timerange",
"options": {
"token": "global_time",
"defaultValue": "-24h@h,now"
},
"title": "Global Time Range"
}
},
"description": "",
"title": "Example of a tile server for maps",
"layout": {
"tabs": {
"items": [
{
"layoutId": "layout_1",
"label": "New tab"
}
]
},
"layoutDefinitions": {
"layout_1": {
"type": "absolute",
"options": {
"width": 1440,
"height": 960,
"display": "auto"
},
"structure": [
{
"item": "viz_lsqZJ7UN",
"type": "block",
"position": {
"x": 0,
"y": 0,
"w": 800,
"h": 600
}
}
]
}
},
"globalInputs": [
"input_global_trp"
]
}
}
Source code
Configuration panel options
You can use the Configuration panel to configure the following map components.
Title
Give your visualization a name. The title name is also helpful when searching for individual visualizations in the dashboard definitions and is not the same as the automatically assigned unique ID.
Description
Give your visualization a description to explain what the user is viewing.
Data sources
Choose an existing search or create a new one.
Visibility
Optionally hide the visualization when data is unavailable.
Position and size
You can use your mouse or the Position and size section of the Configuration panel to change the size or location of the visualization for pixel-perfect sizing and placement.
Data configurations
Select the map's layer type.
- The Marker layer type uses map pins to visualize data and clusters.
- Select the Latitude list to pick the data source for the visualization's latitude.
- Select the Longitude list to pick the data source for the visualization's longitude.
- The Bubble layer type uses differently sized circles or pie charts to visualize data and clusters.
- Select the Latitude list to pick the data source for the visualization's latitude.
- Select the Longitude list to pick the data source for the visualization's longitude.
- Select the Size list to pick the visualization's bubble size data source.
- The Choropleth layer type uses differently colored map areas to visualize distinct data concentrations.
- Select the Region Area IDs list to pick the field from your data source for the type of geographical area you want visualized with data.
- Select the Values list to pick the data source for measuring results.
Data display
Optionally configure the latitude and longitude of the initial map location, and turn on or off the zoom controls. You can configure these by inputting the desired values in the fields, or by zooming in on the desired initial map location. You can also configure scale settings.
As a dashboard editor, you can click the Fit to data button on the left side of the map below the zoom controls to clear the initial map location settings. For dashboard viewers, the Fit to data button clears zoom settings to display the whole map.
Color and style
-
Title color: configure a font color for the visualization title.
-
Description color: configure a font color for the visualization description.
Select colors for the map, toggle the base layer on or off, and modify the corner radius of the visualization.
Interactions
Use interactions to create interactivity with different map layers. For example, users can select a bubble to set a token that you can use to open a secondary search using the selected values. See Setting tokens on a visualization click.
Select your visualization or its search to view and edit the source code in real-time. You can also change the Visualization ID to a more readable ID to help identify this visualization in the source code.
Marker map example
This marker map example uses differently colored marker clusters to demonstrate a range of HTTP requests across geographical regions. The colors indicate varying numbers of requests based on the following ranges:
- 3001 or more requests are red
- 2001-3000 requests are orange
- 1001-2000 requests are yellow
- 1000 or fewer requests are green
For its initial location, this map has the following configured:
Latitude: 39.22038071325781
Longitude: -28.29206819849543
Zoom: 1.75
The map is also configured to include the bytes field as an additional tooltip field, and renders a maximum of 25 data points using the resultLimit option.
The following is the source code for the marker map example.
{
"title": "Marker Cluster Map example",
"description": "",
"inputs": {
"input_global_trp": {
"options": {
"defaultValue": "-24h@h,now",
"token": "global_time"
},
"title": "Global Time Range",
"type": "input.timerange"
}
},
"defaults": {
"dataSources": {
"ds.search": {
"options": {
"queryParameters": {
"earliest": "$global_time.earliest$",
"latest": "$global_time.latest$"
}
}
}
}
},
"visualizations": {
"viz_marker_cluster": {
"context": {
"config": [
{
"from": 3001,
"value": "#de1d20"
},
{
"from": 2001,
"to": 3000,
"value": "#54afda"
},
{
"from": 1001,
"to": 2000,
"value": "#ded41d"
},
{
"to": 1000,
"value": "#4ade1d"
}
],
"dataColorsEditorConfig": [
{
"to": 1001,
"value": "#118832"
},
{
"from": 1001,
"to": 2001,
"value": "#9D9F0D"
},
{
"from": 2001,
"to": 3001,
"value": "#D97A0D"
},
{
"from": 3001,
"value": "#D41F1F"
}
]
},
"dataSources": {
"primary": "ds_x7YkfW2Y"
},
"options": {
"center": [
39.22038071325781,
-28.29206819849543
],
"layers": [
{
"additionalTooltipFields": [
"bytes"
],
"dataColors": "> dataValues | rangeValue(dataColorsEditorConfig)",
"latitude": "> primary | seriesByName(\"lat\")",
"longitude": "> primary | seriesByName(\"lon\")",
"resultLimit": 25,
"type": "marker"
}
],
"zoom": 1.75
},
"type": "splunk.map"
}
},
"dataSources": {
"ds_4QzeZfAB": {
"name": "Search_3",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| geostats latfield=lat longfield=lon count"
},
"type": "ds.search"
},
"ds_DHERK2tc": {
"name": "Search_4",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| geostats latfield=lat longfield=lon count by method"
},
"type": "ds.search"
},
"ds_TMfPIhsl": {
"name": "Search_2",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| table bytes device_ip lat lon"
},
"type": "ds.search"
},
"ds_x7YkfW2Y": {
"name": "Search_1",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| table bytes device_ip lat lon"
},
"type": "ds.search"
}
},
"layout": {
"globalInputs": [
"input_global_trp"
],
"layoutDefinitions": {
"layout_1": {
"options": {
"display": "auto-scale"
},
"structure": [
{
"item": "viz_marker_cluster",
"position": {
"h": 420,
"w": 1010,
"x": 30,
"y": 30
},
"type": "block"
}
],
"type": "absolute"
}
},
"tabs": {
"items": [
{
"label": "New tab",
"layoutId": "layout_1"
}
]
}
}
}Bubble map example
The following bubble map example uses bubble clusters to demonstrate the type and number of HTTP requests in different geographic regions. The purple portions of the charts represent GET requests and blue portions of the charts represent POST requests.
For its initial location, this map has the following configured:
Latitude: 44.68687682438767
Longitude: 61.75857714613721
Zoom: 2
The map is also configured to include the geobin information as the tooltip header using the tooltipHeaderField option.
The following is the source code for this bubble map example:
{
"title": "Bubble Map example - static coloring",
"description": "",
"inputs": {
"input_global_trp": {
"options": {
"defaultValue": "-24h@h,now",
"token": "global_time"
},
"title": "Global Time Range",
"type": "input.timerange"
}
},
"defaults": {
"dataSources": {
"ds.search": {
"options": {
"queryParameters": {
"earliest": "$global_time.earliest$",
"latest": "$global_time.latest$"
}
}
}
}
},
"visualizations": {
"viz_marker_cluster": {
"containerOptions": {},
"context": {
"config": [
{
"from": 3001,
"value": "#de1d20"
},
{
"from": 2001,
"to": 3000,
"value": "#54afda"
},
{
"from": 1001,
"to": 2000,
"value": "#ded41d"
},
{
"to": 1000,
"value": "#4ade1d"
}
],
"dataColorsEditorConfig": [
{
"to": 1001,
"value": "#118832"
},
{
"from": 1001,
"to": 2001,
"value": "#9D9F0D"
},
{
"from": 2001,
"to": 3001,
"value": "#D97A0D"
},
{
"from": 3001,
"value": "#D41F1F"
}
]
},
"dataSources": {
"primary": "ds_x7YkfW2Y"
},
"options": {
"center": [
44.68687682438767,
61.75857714613721
],
"layers": [
{
"bubbleSize": "> primary | frameWithoutSeriesNames('geobin', 'latitude', 'longitude') | frameBySeriesTypes('number')",
"tooltipHeaderField": "> primary | seriesByName('geobin')",
"type": "bubble"
}
],
"zoom": 2
},
"showLastUpdated": false,
"showProgressBar": false,
"type": "splunk.map"
}
},
"dataSources": {
"ds_4QzeZfAB": {
"name": "Search_3",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| geostats latfield=lat longfield=lon count"
},
"type": "ds.search"
},
"ds_DHERK2tc": {
"name": "Search_4",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| geostats latfield=lat longfield=lon count by method"
},
"type": "ds.search"
},
"ds_TMfPIhsl": {
"name": "Search_2",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| table bytes device_ip lat lon"
},
"type": "ds.search"
},
"ds_x7YkfW2Y": {
"name": "Search_1",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| geostats latfield=lat longfield=lon count by method"
},
"type": "ds.search"
}
},
"layout": {
"globalInputs": [
"input_global_trp"
],
"layoutDefinitions": {
"layout_1": {
"options": {
"display": "auto-scale"
},
"structure": [
{
"item": "viz_marker_cluster",
"position": {
"h": 420,
"w": 1150,
"x": 30,
"y": 30
},
"type": "block"
}
],
"type": "absolute"
}
},
"tabs": {
"items": [
{
"label": "New tab",
"layoutId": "layout_1"
}
]
}
}
}The following bubble map example uses bubble clusters to demonstrate the number of GET requests in different geographic regions. The colors indicate varying numbers of requests based on the following ranges:
- 20 or more requests is green
- 10-20 requests is yellow
- 5-10 requests is orange
- 5 or fewer requests is red
For its initial location, this map has the following configured:
Latitude: 28.513364639699574
Longitude: -8.999089823812596
Zoom: 1.450326329750756
The map displays its scale in imperial units.
The following is the source code for this bubble map example:
{
"title": "Bubble Map example - dynamic coloring",
"description": "",
"inputs": {
"input_global_trp": {
"options": {
"defaultValue": "-24h@h,now",
"token": "global_time"
},
"title": "Global Time Range",
"type": "input.timerange"
}
},
"defaults": {
"dataSources": {
"ds.search": {
"options": {
"queryParameters": {
"earliest": "$global_time.earliest$",
"latest": "$global_time.latest$"
}
}
}
}
},
"visualizations": {
"viz_marker_cluster": {
"containerOptions": {},
"context": {
"config": [
{
"from": 3001,
"value": "#de1d20"
},
{
"from": 2001,
"to": 3000,
"value": "#54afda"
},
{
"from": 1001,
"to": 2000,
"value": "#ded41d"
},
{
"to": 1000,
"value": "#4ade1d"
}
],
"dataColorConfig": [
{
"to": 20,
"value": "#D41F1F"
},
{
"from": 20,
"to": 40,
"value": "#D94E17"
},
{
"from": 40,
"to": 60,
"value": "#CBA700"
},
{
"from": 60,
"to": 80,
"value": "#669922"
},
{
"from": 80,
"value": "#118832"
}
],
"dataColorsEditorConfig": [
{
"to": 5,
"value": "#D41F1F"
},
{
"from": 5,
"to": 10,
"value": "#D97A0D"
},
{
"from": 10,
"to": 20,
"value": "#9D9F0D"
},
{
"from": 20,
"value": "#118832"
}
]
},
"dataSources": {
"primary": "ds_x7YkfW2Y"
},
"options": {
"center": [
28.513364639699574,
-8.999089823812596
],
"layers": [
{
"dataColors": "> dataValues | rangeValue(dataColorsEditorConfig)"
}
],
"scaleUnit": "imperial",
"zoom": 1.450326329750756
},
"showLastUpdated": false,
"showProgressBar": false,
"type": "splunk.map"
}
},
"dataSources": {
"ds_4QzeZfAB": {
"name": "Search_3",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| geostats latfield=lat longfield=lon count"
},
"type": "ds.search"
},
"ds_DHERK2tc": {
"name": "Search_4",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| geostats latfield=lat longfield=lon count by method"
},
"type": "ds.search"
},
"ds_TMfPIhsl": {
"name": "Search_2",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| table bytes device_ip lat lon"
},
"type": "ds.search"
},
"ds_x7YkfW2Y": {
"name": "Search_1",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| where method=\"GET\"\n| geostats latfield=lat longfield=lon count by method\n"
},
"type": "ds.search"
}
},
"layout": {
"globalInputs": [
"input_global_trp"
],
"layoutDefinitions": {
"layout_1": {
"options": {
"display": "auto-scale"
},
"structure": [
{
"item": "viz_marker_cluster",
"position": {
"h": 420,
"w": 1150,
"x": 30,
"y": 30
},
"type": "block"
}
],
"type": "absolute"
}
},
"tabs": {
"items": [
{
"label": "New tab",
"layoutId": "layout_1"
}
]
}
}
}
Bubble map pre-defined tokens
Bubble maps support the following pre-defined tokens in addition to the pre-defined tokens that all visualizations support, like row.<fieldname>.value. The following pre-defined tokens are only available for bubble maps:
| Pre-defined token | Value returned |
|---|---|
| row._geo_bounds_east.value | Longitude value for eastern boundary of selected bubble |
| row._geo_bounds_north.value | Latitude value for northern boundary of selected bubble |
| row._geo_bounds_south.value | Latitude value for southern boundary of selected bubble |
| row._geo_bounds_west.value | Longitude value for western boundary of selected bubble |
| row._geo_lat_field.value | Name of field used to define latitude for the map |
| row._geo_long_field.value | Name of field used to define longitude for the map |
For information on setting pre-defined tokens for visualizations, see Setting tokens on a visualization click.
Choropleth map example
The following map uses IP address location to demonstrate the geographical areas with the highest concentration of unique IP addresses.
The following is the source code for this choropleth map example:
{
"visualizations": {
"viz_epnyq5z8": {
"type": "splunk.map",
"options": {
"center": [
5.684341886080802e-14,
-122.41949999999997
],
"zoom": 0.22881867003789005,
"layers": [
{
"type": "choropleth",
"areaIds": "> primary | seriesByName('country')",
"areaValues": "> primary | seriesByName('count')"
}
]
},
"dataSources": {
"primary": "ds_YyFf4bor"
}
}
},
"dataSources": {
"ds_YyFf4bor": {
"type": "ds.search",
"options": {
"query": "| inputlookup geomaps_data.csv\n| iplocation device_ip\n| lookup geo_countries latitude AS lat longitude AS lon OUTPUT featureId AS country\n| stats distinct_count(device_ip) by country\n| geom geo_countries featureIdField=country"
},
"name": "Search_1"
}
},
"defaults": {
"dataSources": {
"ds.search": {
"options": {
"queryParameters": {
"latest": "$global_time.latest$",
"earliest": "$global_time.earliest$"
}
}
}
}
},
"inputs": {
"input_global_trp": {
"type": "input.timerange",
"options": {
"token": "global_time",
"defaultValue": "-24h@h,now"
},
"title": "Global Time Range"
}
},
"layout": {
"tabs": {
"items": [
{
"layoutId": "layout_1",
"label": "New tab"
}
]
},
"layoutDefinitions": {
"layout_1": {
"type": "absolute",
"options": {
"width": 1440,
"height": 960,
"display": "auto"
},
"structure": [
{
"item": "viz_epnyq5z8",
"type": "block",
"position": {
"x": 0,
"y": 0,
"w": 800,
"h": 600
}
}
]
}
},
"globalInputs": [
"input_global_trp"
]
},
"description": "",
"title": "Choropleth layer example"
}
The following shows a dashboard with 2 maps with choropleth layers. The maps share the same data source and show the different options that you can configure for choropleth layers. The map on the left has gray configured as the empty area color, a stroke around the choropleth layers, the base layer enabled, and the choropleth layers display at 50% opacity. The map on the right has a blue background color, a custom choropleth gradient color, and the choropleth layers display at 80% opacity.
The following provides the source code for this example. Copy and paste the dashboard definition for this example into your own dashboard:
{
"title": "Choropleth layer example",
"description": "",
"inputs": {
"input_global_trp": {
"options": {
"defaultValue": "-24h@h,now",
"token": "global_time"
},
"title": "Global Time Range",
"type": "input.timerange"
}
},
"defaults": {
"dataSources": {
"ds.search": {
"options": {
"queryParameters": {
"earliest": "$global_time.earliest$",
"latest": "$global_time.latest$"
}
}
}
}
},
"visualizations": {
"viz_C1tjN0tJ": {
"context": {
"dataColorsGradientConfig": {
"colors": [
"#ffffff",
"#db5800"
]
}
},
"dataSources": {
"primary": "ds_YyFf4bor"
},
"description": "No empty area color, no stroke, base layer disabled. Background color enabled, custom choropleth gradient. 80% opacity",
"options": {
"backgroundColor": "#c2daf4",
"center": [
29.45443,
10.35
],
"layers": [
{
"additionalTooltipFields": [],
"dataColors": "> areaValues | gradient(dataColorsGradientConfig)",
"type": "choropleth"
}
],
"showBaseLayer": false,
"zoom": 0.5
},
"showProgressBar": true,
"title": "Map 2",
"type": "splunk.map"
},
"viz_epnyq5z8": {
"dataSources": {
"primary": "ds_YyFf4bor"
},
"description": "Empty area color, stroke, and base layer enabled. 50% opacity",
"options": {
"center": [
29.45443,
10.35
],
"layers": [
{
"additionalTooltipFields": [
"n"
],
"choroplethEmptyAreaColor": "#708794",
"choroplethOpacity": 0.5,
"choroplethStrokeColor": "#000000",
"source": "geo://default/world",
"tooltipHeaderField": "> primary | seriesByName('country')",
"type": "choropleth"
}
],
"showScale": false,
"zoom": 0.5
},
"title": "Map 1",
"type": "splunk.map"
}
},
"dataSources": {
"ds_YyFf4bor": {
"name": "Search_1",
"options": {
"query": "| inputlookup geo_attr_countries\n| eval n=random() % 100\n| geom geo_countries featureIdField=country \n| fields country, n, geom"
},
"type": "ds.search"
}
},
"layout": {
"globalInputs": [
"input_global_trp"
],
"layoutDefinitions": {
"layout_1": {
"options": {
"display": "auto",
"height": 960,
"width": 1440
},
"structure": [
{
"item": "viz_epnyq5z8",
"position": {
"h": 600,
"w": 750,
"x": 0,
"y": 0
},
"type": "block"
},
{
"item": "viz_C1tjN0tJ",
"position": {
"h": 600,
"w": 690,
"x": 750,
"y": 0
},
"type": "block"
}
],
"type": "absolute"
}
},
"tabs": {
"items": [
{
"label": "New tab",
"layoutId": "layout_1"
}
]
}
}
}Source options for maps
The following options are available for editing maps in the source editor.
| Property | Type | Default | Description |
|---|---|---|---|
| backgroundColor | string | > themes.defaultBackgroundColor | Specify the color for the background. You can use a data source or hexadecimal code to apply the color. |
| baseLayerTileServer | string | n/a | Specify the tile set URL for the base map. For example, you might use street tiles for a neighborhood map or terrain tiles for a mountain range map. |
| baseLayerTileServerType | ("vector" | "raster") | n/a | Specify the type of tile set for the base map. Valid types include "vector" and "raster". |
| center | number | n/a | Specify the map's center using latitude and longitude. The center might automatically set or result in [0,0] coordinates depending on available data. |
| icon | string | Specify the URL for an image in SVG format of an icon to display inside the bubble layers for a map. This applies to layers where the type is "bubble". | |
| layers | object[] | [object Object],[object Object] | Specify the data visualization layers on top of the base map. The layer can also be empty and only show the base map. |
| scaleUnit | ("metric" | "imperial") | metric | Specify which scale unit to use. |
| showBaseLayer | boolean | true | Specify whether to show the base map. |
| showCoordinates | boolean | true | Specify whether to display coordinates (latitude and longitude) in the tooltip. |
| showScale | boolean | TRUE | Specify whether to show the scale on the bottom left. |
| showZoomControls | boolean | true | Specify whether to display the zoom control panel in the top left. |
| zoom | number | n/a | Specify the zoom level of the map. |
layers (object type)
| Property | Type | Default | Description |
|---|---|---|---|
| additionalTooltipFields | string[ ] | [ ] | Specify the fields to add to the default set of tooltips. Tooltips appear when you hover over data points. These fields and their corresponding values display in addition to those displayed by default. |
| areaIds | string[] | > primary | seriesByType("string") | Specify a dataSource series to identify each area in the choropleth map layer. This applies to layers where type: "choropleth". |
| areaValues | number[] | > primary | seriesByType("number") | Specify a dataSource series that indicates the values for the choropleth map areas. This applies to layers where type: "choropleth". |
| bubbleSize | (string | array) | frameBySeriesTypes("number") | Specify the data column to encode bubble size. This applies to layers where the type is "bubble". |
| choroplethEmptyAreaColor | ("transparent" | "rgb\(\s*(\d{1,3}),\s*(\d{1,3}),\s*(\d{1,3})\)" | "rgba\(\s*(\d{1,3}%?),\s*(\d{1,3}%?),\s*(\d{1,3}%?),\s*(\d*(?:\.\d+)?)\)|\(\w+:)?([^|:]+?)(\|[|\w]+)?\") | > themes.defaultChoroplethEmptyAreaColor | Specify the color used for empty choropleth areas when "type": "choropleth", and will only work when "source" option is correctly configured. |
| choroplethOpacity | number | 0.8 | Specify the opacity of choropleth areas. Choose a number in the range of 0 - 1 (inclusive). You can also express the value as a percentage. For example, "0.8" in code or "80%" in UI. |
| choroplethStrokeColor | ("transparent" | "rgb\(\s*(\d{1,3}),\s*(\d{1,3}),\s*(\d{1,3})\)" | "rgba\(\s*(\d{1,3}%?),\s*(\d{1,3}%?),\s*(\d{1,3}%?),\s*(\d*(?:\.\d+)?)\)|\(\w+:)?([^|:]+?)(\|[|\w]+)?\") | transparent | Specify the stroke color for choropleth area outlines. The hex value format should be "#FFFFFF". |
| dataColors | (string | array) | n/a | Specify the colors used for data points. If specified, this option overrides the seriesColors option. You can use a data source or an array of colors to apply the coloring. For example, " > primary | seriesByName("status") | matchValue(colorMatchConfig)". |
| dataValues | (string | array) | > primary | seriesByType("number") | Specify the data series used to encode colors for dynamic coloring in layers of type "marker" or "bubble". |
| latitude | (string | array) | > primary | seriesByName("latitude") | Specify a data source to apply latitude coordinates for data points displayed on the map. |
| longitude | (string | array) | > primary | seriesByName("longitude") | Specify a data source to apply longitude coordinates for data points displayed on the map. |
| resultLimit | number | 1000 | Specify the maximum number of data points to render on the map. |
| seriesColors | string[] | ["#7B56DB", "#009CEB", "#00CDAF", "#DD9900", "#FF677B", "#CB2196", "#813193", "#0051B5", "#008C80", "#99B100", "#FFA476", "#FF6ACE", "#AE8CFF", "#00689D", "#00490A", "#465D00", "#9D6300", "#F6540B", "#FF969E", "#E47BFE"] | Specify the colors used for data points. If the dataColors option is specified, the seriesColors option is ignored. |
| source | ("geo://default/us" | "geo://default/world") | Source for the geodata for choropleth layer: "us" or "world", and will override data specified in the SPL geom command. | |
| tooltipHeaderField | string | Specify the field to use as the tooltip header. The corresponding value displays as the tooltip header for each data point. | |
| type | ("marker" | "bubble"|"choropleth") | bubble | Specify the type of data layer method to display points on the map. |