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!


Select your region

Linux Package Signing Key Rotation

All signed InfluxData Linux packages have been resigned with an updated key. If using Linux, you may need to update your package configuration to continue to download and verify InfluxData software packages.

For more information, see the Linux Package Signing Key Rotation blog post.

InfluxDB Cloud backed by InfluxDB IOx

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by IOx, this is the correct documentation.

If powered by TSM, see the TSM-based InfluxDB Cloud documentation.

InfluxDB Cloud backed by InfluxDB TSM

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine which enables nearly unlimited series cardinality and SQL query support. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by TSM, this is the correct documentation.

If powered by IOx, see the IOx-based InfluxDB Cloud documentation.

State of the InfluxDB Cloud (IOx) documentation

The new documentation for InfluxDB Cloud backed by InfluxDB IOx is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.