Documentation

geo.strictFilter() function

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

geo.strictFilter() filters data by latitude and longitude in a specified region.

This filter is more strict than geo.gridFilter(), but for the best performance, use geo.strictFilter() after geo.gridFilter(). Input rows must have lat and lon columns.

Function type signature
(<-tables: stream[{B with lon: D, lat: C}], region: A) => stream[{B with lon: D, lat: C}] where A: Record

For more information, see Function type signatures.

Parameters

region

(Required) Region containing the desired data points.

Specify record properties for the shape.

tables

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

Examples

Strictly filter data to a specified region

import "experimental/geo"

data
    |> geo.strictFilter(region: {lat: 40.69335938, lon: -73.30078125, radius: 50.0})

View example input and output


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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