Invalid band name/index 'VV'

[sulova.andrea]

Hey,

Why does the SENTINEL1_GRD collection provide an error regarding bands when “openeo.cloud” is applied?

connection = openeo.connect("openeo.cloud").authenticate_oidc()

datacube = connection.load_collection(
  "SENTINEL1_GRD",
  spatial_extent={"west": 16.06, "south": 48.06, "east": 16.65, "north": 48.35},
  temporal_extent=["2017-03-01", "2017-04-01"],
  bands=["VV", "VH"]
)

ValueError : Invalid band name/index ‘VV’. Valid names: []

[stefaan.lippens]

Thanks for reporting

apparently this is because of an inconsistency in band order across backends:

• VITO uses VV, VH, HV, HH (https://openeo.vito.be/openeo/1.0/collections/SENTINEL1_GRD)
• EODC uses HH, VV, HH+HV, VV+VH (https://openeo.eodc.eu/v1.0/collections/SENTINEL1_GRD)

the aggregator (openeo.cloud) tries to merge this part of the metadata by picking the common prefix of both lists, which is empty in this case

I’ll try to come up with a quick fix

[stefaan.lippens]

fix is in production:
aggregator should now advertise bands VV VH HV HH for SENTINEL1_GRD

[sulova.andrea]

I am trying to test this but I am getting this error (tried to run it multiple times)

ConnectionError: ('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))

[stefaan.lippens]

on what statement does that fail? on openeo.connect("openeo.cloud") or .authenticate_oidc() or something else?

[sulova.andrea]

I was running it again today and it seems to work now !
Thanks for fixing it