Skip to main content

Band Selection and Indices

Use Bandnames in processing requests to control which outputs are returned.

Common Bandnames Patterns​

  • rgb: quicklook-oriented output.
  • all: all bands available for the selected model/level.
  • B8,B4,B3: explicit spectral band list.
  • [B8_B4]: NDVI-style index expression.
  • B8,B4,[B8_B4]: spectral bands and an index in the same download.

Example: Bands and NDVI in One Request​

{
  "Wkt": "POLYGON ((9.877893206725581 56.47856668238974, 10.196496722350581 56.47856668238974, 10.196496722350581 56.27782087776097, 9.877893206725581 56.27782087776097, 9.877893206725581 56.47856668238974))",
  "Date": "2024-05-03T00:00:00Z",
  "Resolution": 10,
  "EpsgProjection": 32632,
  "Model": "Stratus2",
  "SatelliteConstellations": ["Sentinel1", "Sentinel2", "Landsat89"],
  "Bandnames": "B8,B4,[B8_B4]"
}

Use one geometry mode per request (Wkt or GeoJson, not both).

Recommendation: Prefer Explicit Band Lists in Production​

Use explicit Bandnames values (for example B2,B3,B4,B8) for automated pipelines.

Why:

  • all depends on model/level availability. Available bands differ across models (for example Stratus currently has a 10-band set, while Nimbus levels can expose additional bands).
  • Explicit lists keep downstream schemas stable over time.

Use all mainly for exploration and quick checks.

Scaling and Metadata​

Do not duplicate scaling or metadata assumptions in downstream docs.

Use canonical values from Bands, formats, scaling, and metadata.