Documentation

geo.toRows() function

geo.toRows() is experimental and subject to change at any time.

geo.toRows() pivots fields into columns based on time.

Latitude and longitude should be stored as fields in InfluxDB. Because most geo package transformation functions require rows to have lat and lon columns, lat and lot fields must be pivoted into columns.

Function type signature
(<-tables: stream[A]) => stream[B] where A: Record, B: Record

For more information, see Function type signatures.

Parameters

tables

Input data. Default is piped-forward data (<-).

Examples

Pivot lat and lon fields into columns

import "experimental/geo"

data
    |> geo.toRows()

View example input and output


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, 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