Skip to main content
Queryable fields let you filter datapoints by custom metadata before Tilebox returns the query result. You can combine custom field expressions with temporal, spatial, and collection filters in the same query.

Find queryable fields

The dataset schema identifies which fields are queryable. Inspect the schema to find fields available for filtering.
The open_data.aws_earth.sentinel2 dataset exposes these queryable fields:

Filter datapoints

This query returns Sentinel-2C Level-2A datapoints with less than one percent cloud cover between July 20 and July 28, 2026.
Tilebox combines custom field expressions with temporal, spatial, and collection filters using AND.

Operators

Custom field filters support comparisons, boolean composition, and null checks.
Use &, |, and ~ instead of and, or, and not, and place each comparison in parentheses.
Fields of type bool support only equality and inequality.

Missing and null values

Filter expressions use three-valued logic: true, false, and null (unknown). A datapoint matches only when the complete expression is true. Comparisons against a missing or explicitly null field return null and do not match. This behavior also applies to inequality. For example, quality != 1 requires quality to be present. Combine the comparison with an explicit null check when missing values should also match.

Query safeguards

A single query can contain filters with at most 64 top-level expressions or operands, 256 expression nodes in total, and eight levels of nesting. These safeguards keep query evaluation bounded.

Next steps

Dataset schemas

Learn how dataset kinds, custom fields, and schema updates work.

Build a spatio-temporal catalog

Create a custom catalog, ingest metadata, and query its custom fields.