-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"SENTINEL1_GRD" band metadata is not properly enriched #277
Comments
Actually, the values in STAC should be ordered. I guess this should be fixed in STAC. Opened an issue here: |
Is there anything that should be fixed/adapted at the level of the python client? |
No, apparently it's something that Sinergise should fix (but not quite yet because it will break our S1 collections: Open-EO/openeo-geopyspark-driver#129). |
I think this ticket should be re-opened because it's still an issue: import openeo
con = openeo.connect("openeo.vito.be")
datacube = con.load_collection('SENTINEL1_GRD') triggers warning:
And practically it means that the client potentially will use wrong index when translating |
Metadata issue must be fixed at back-end side. |
Open-EO/openeo-geopyspark-driver#129 was fixed so I adapted layercatalog.json in order to align the band names and get rid of the warning. |
Confirmed, I don't get the UserWarning anymore when loading "SENTINEL1_GRD" on openeo-dev.vito.be |
The band metadata for collection "SENTINEL1_GRD" is not properly enriched by the STAC metadata at https://collections.eurodatacube.com/stac/sentinel-1-grd.json.
This is because the order of the bands in "cube:dimensions"/"bands"/"values" is different from the order of bands in "summaries"/"raster:bands":
as opposed to
The specification says that "values" is "A set of all potential values" so that implies that it is unordered.
The text was updated successfully, but these errors were encountered: