90. Query: Get SatelliteImagery Data by Geometry

Fetch vegetation-index statistics for any ad-hoc geometry - no registered field boundary required. This endpoint computes summary stats for pixels inside your geometry while ignoring cloudy pixels. Currently supported on Sentinel2 (S2) , Landsat (L4/L5/L7/L8/L9) and Planet (PS) providers.

triangle-exclamation

What you can do

  • Query vegetation indices for Point, MultiPoint, Polygon, and MultiPolygon geometries.

  • Choose imagery providers: S2, L4, L5, L7, L8, L9, PS.

  • Get date-stamped results per acquisition with:

    • cloudfree - fraction of your geometry that’s cloud-free, range of values from 0 to 1, where 1 means fully cloud-free.

    • value - statistics for the selected index computed only on cloud-free pixels, includes min, max, avg, mdn, var, std.

  • Optionally provide ranges array of index value ranges for calculating coverage statistics. When provided, the response will include a ranges field showing what percentage of the area falls within each specified range.

    • Area occupied by each color/range - based on index value (low => high)

    • Coverage percentage - 0..1 value per range representing surface percentage

Supported indices

EVI2, NDVI, RVI, LAI, OSAVI, SAVI, GNDVI, IPVI, GCI, WDRVI, RCI, SBI, MCARI1. Index definitions follow GeoPard’s vegetation index catalogarrow-up-right used throughout the API.

Input parameters

Field
Type
Required
Notes

index

Enum (see above)

Vegetation index to compute.

providers

[Provider!]!

Any of S2, L4, L5, L7, L8, L9, PS.

startDate

String (ISO8601)

Inclusive start, e.g. "2025-05-10T00:00:00.000Z".

endDate

String (ISO8601)

Exclusive end or inclusive end depending on schema; match your other GeoPard queries.

geojson

String

A stringified GeoJSON of type Point / MultiPoint / Polygon / MultiPolygon (WGS84 [lon, lat]). Remember to escape the quotes inside the string.

ranges

[[Float!]!]

Array of [min, max] pairs of index value ranges for calculating coverage statistics

Performance guidance

  • For Polygon/MultiPolygon geometries, keep date ranges tight (~10–15 days) due to processing time.

  • Timeout: 30 s. Use fewer days and/or fewer providers if you hit the limit.

  • For Point/MultiPoint, larger ranges are usually fine (points are lightweight).

Response shape

Example 1: MultiPolygon with MCARI1 on S2/L8/L9 within a 5-day window

Request

Response

Example 2: MultiPoint with NDVI on S2/L8/L9 over a 5-day window

Request

Response

Example 3: MultiPolygon with NDVI on S2/L8/L9 with ranges within a 5-day window

Request

Response

Last updated

Was this helpful?