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.

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!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud powered by TSM