No CLM band in terrascope SENTINEL2_L2A anymore?

1

I am trying to run a simple extraction process from SENTINEL2_L2A collection on openeo.vito.be, which fails with the following error:

OpenEO batch job failed: ValueError("Invalid band name/index 'CLM'. Valid names: ['B01', 'B02', 'B03', 'B04', 'B05', 'B06', 'B07', 'B08', 'B8A', 'B11', 'B12', 'SCL', 'relativeAzimuthAngles', 'sunZenithAngles', 'viewZenithAngles']")

However, band name CLM should exist in the SENTINEL2_L2A collection (in fact it existed yesterday …). What am I doing wrong ?

Here is the graph:

{
  "process_graph": {
    "filterspatial1": {
      "arguments": {
        "data": {
          "from_node": "loadcollection1"
        },
        "geometries": {
          "crs": {
            "properties": {
              "name": "urn:ogc:def:crs:OGC:1.3:CRS84"
            },
            "type": "name"
          },
          "features": [
            {
              "geometry": {
                "coordinates": [
                  [
                    [
                      1.115540995306387,
                      44.955190001352186
                    ],
                    [
                      1.240991973644394,
                      44.95719178113812
                    ],
                    [
                      1.238263310755816,
                      45.04626870153675
                    ],
                    [
                      1.112617998502606,
                      45.04426072993823
                    ],
                    [
                      1.115540995306387,
                      44.955190001352186
                    ]
                  ]
                ],
                "type": "Polygon"
              },
              "properties": {},
              "type": "Feature"
            }
          ],
          "type": "FeatureCollection"
        }
      },
      "process_id": "filter_spatial"
    },
    "loadcollection1": {
      "arguments": {
        "bands": [
          "B02",
          "B03",
          "B04",
          "B05",
          "B06",
          "B07",
          "B08",
          "B8A",
          "B11",
          "B12",
          "SCL",
          "CLM",
          "sunAzimuthAngles",
          "sunZenithAngles",
          "viewAzimuthMean",
          "viewZenithMean",
          "dataMask"
        ],
        "id": "SENTINEL2_L2A",
        "properties": {
          "eo:cloud_cover": {
            "process_graph": {
              "lte1": {
                "arguments": {
                  "x": {
                    "from_parameter": "value"
                  },
                  "y": 75
                },
                "process_id": "lte",
                "result": true
              }
            }
          },
          "provider:backend": {
            "process_graph": {
              "eq1": {
                "arguments": {
                  "x": {
                    "from_parameter": "value"
                  },
                  "y": "vito"
                },
                "process_id": "eq",
                "result": true
              }
            }
          }
        },
        "spatial_extent": null,
        "temporal_extent": [
          "2022-01-01",
          "2022-12-31"
        ]
      },
      "process_id": "load_collection"
    },
    "saveresult1": {
      "arguments": {
        "data": {
          "from_node": "filterspatial1"
        },
        "format": "netCDF",
        "options": {
          "sample_by_feature": true
        }
      },
      "process_id": "save_result",
      "result": true
    }
  }
}

Regards,

Julien

2

Hi Julien,
that band is provided via Sentinelhub only, but you have set the provider:backend property to vito, which indeed does not have this band.
As workaround, you could consider requesting the CLM band in a separate load_collection, and doing merge_cubes to join it with other bands. This would allow you to use vito for most bands, and then a much smaller input from Sentinelhub.

best regards,
Jeroen

3

Hi, thanks Jeroen,

I am bit confused because in collection explorer, SENTINEL2_L2A indeed has this band …

image
image1824×978 148 KB

Is this a glitch in documentation ?

Regards,

Julien

4

Hi Julien,
I have to correct my proposed workaround:
provider:backend would apparently not yet work to force usage of the Terrascope collection.
So instead, the solution is to use TERRASCOPE_S2_TOC_V2 to load most bands, and SENTINEL2_L2A_SENTINELHUB to load CLM band.

We will log an issue to see how we can more smartly resolve bands that only exist at one data provider.