Documentation

Group geo-temporal data

This page documents an earlier version of InfluxDB. InfluxDB v2.6 is the latest stable version. View this page in the v2.6 documentation.

Use the geo.groupByArea() to group geo-temporal data by area and geo.asTracks() to group data into tracks or routes.

For example results, use the bird migration sample data to populate the sampleGeoData variable in the queries below.

Group data by area

Use the geo.groupByArea() function to group geo-temporal data points by geographic area. Areas are determined by S2 grid cells

  • Specify a new column to store the unique area identifier for each point with the newColumn parameter.
  • Specify the S2 cell level to use when calculating geographic areas with the level parameter.

The following example uses the sample bird migration data to query data points within 200km of Cairo, Egypt and group them by geographic area:

import "experimental/geo"

sampleGeoData
    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
    |> geo.groupByArea(newColumn: "geoArea", level: 5)

Group data by track or route

Use geo.asTracks() function to group data points into tracks or routes and order them by time or other columns. Data must contain a unique identifier for each track. For example: id or tid.

  • Specify columns that uniquely identify each track or route with the groupBy parameter.
  • Specify which columns to sort by with the sortBy parameter. Default is ["_time"].

The following example uses the sample bird migration data to query data points within 200km of Cairo, Egypt and group them into routes unique to each bird:

import "experimental/geo"

sampleGeoData
    |> geo.filterRows(region: {lat: 30.04, lon: 31.23, radius: 200.0})
    |> geo.asTracks(groupBy: ["id"], orderBy: ["_time"])

Was this page helpful?

Thank you for your feedback!


Set your InfluxDB URL

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.