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!


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