Documentation

geo.shapeData() function

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

geo.shapeData() renames existing latitude and longitude fields to lat and lon and adds an s2_cell_id tag.

Use geo.shapeData() to ensure geotemporal data meets the requirements of the Geo package:

  1. Rename existing latitude and longitude fields to lat and lon.
  2. Pivot fields into columns based on _time.
  3. Generate s2_cell_id tags using lat and lon values and a specified S2 cell level.
Function type signature
(
    <-tables: stream[{C with _field: string}],
    latField: A,
    level: int,
    lonField: B,
) => stream[{D with s2_cell_id: string, lon: float, lat: float}] where A: Equatable, B: Equatable

For more information, see Function type signatures.

Parameters

latField

(Required) Name of the existing field that contains the latitude value in decimal degrees (WGS 84).

Field is renamed to lat.

lonField

(Required) Name of the existing field that contains the longitude value in decimal degrees (WGS 84).

Field is renamed to lon.

level

(Required) S2 cell level to use when generating the S2 cell ID token.

tables

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


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