Documentation

Map visualization

The Map visualization displays geo-temporal data on a geographic map.

Map data visualization

Set up the Map visualization

To view geo-temporal data on a geographic map, set up a Map visualization.

Set up the Map visualization

  1. Do one of the following:

    • Click Data Explorer in the navigation bar.

    • Click Dashboards in the navigation bar:

      Click the name of the dashboard to update and then do one of the following:

      • To edit an existing cell, click the icon on the cell and then Configure.
      • To create a new cell, click Add Cell.
  2. Use the Query Builder or the Script Editor to enter your query. To determine the location of points on a geographic map, query results must include the following fields:

    • lat: latitude in decimal degrees (WGS 84)
    • lon: longitude in decimal degrees (WGS 84)

    Or the s2_cell_id tag (S2 Cell ID as a token)

    If query results include lat and lon fields and an s2_cell_id tag, the map uses the lat and lon fields to determine point locations. If results only include the s2_cell_id, the map uses the center of the S2 cell as the point location.

    See Example queries.

Example queries

View a bird’s migration path

The following query uses the Bird migration sample data to display the migration path of a specific bird.

from(bucket: "migration")
    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
    |> filter(fn: (r) => r._measurement == "migration")
    |> filter(fn: (r) => r._field == "lat" or r._field == "lon")
    |> filter(fn: (r) => r.id == "91864A")  
    |> aggregateWindow(every: v.windowPeriod, fn: last)

View earthquakes reported by USGS

The following query uses the United States Geological Survey (USGS) earthquake data to display the locations of earthquakes.

from(bucket: "usgs")
    |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
    |> filter(fn: (r) => r._measurement == "earthquakes")
    |> filter(fn: (r) => r._field == "lat" or r._field == "lon")

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2

InfluxDB Cloud powered by TSM