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!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.