Documentation

Group geo-temporal data

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

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"], sortBy: ["_time"])

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