Documentation

geo.getGrid() function

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

geo.getGrid() calculates a grid or set of cell ID tokens for a specified region.

Note: S2 grid cells may not perfectly align with the defined region, so results include S2 grid cells fully and partially covered by the region.

Function type signature
(
    region: A,
    units: {distance: string},
    ?level: int,
    ?maxLevel: int,
    ?maxSize: int,
    ?minSize: int,
) => {set: [string], level: int} where A: Record

For more information, see Function type signatures.

Parameters

region

(Required) Region used to return S2 cell ID tokens. Specify record properties for the region shape.

minSize

Minimum number of cells that cover the specified region.

maxSize

Minimum number of cells that cover the specified region.

level

S2 cell level of grid cells.

maxLevel

Maximumn S2 cell level of grid cells.

units

(Required) Record that defines the unit of measurement for distance.


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