-
Notifications
You must be signed in to change notification settings - Fork 4
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
Sentinel2 L1C: SAA SZA VAA VZA bands not found #177
Sentinel2 L1C: SAA SZA VAA VZA bands not found #177
Comments
…nder API, so it works locally too. #177
…al conflicts when using S3. Allow to use S3 acces for angles layers. #177
also check state of these bands SENTINEL2_L2A |
…ensions#177" This reverts commit cc6f910.
…l raster sources under BandCompositeRasterSource have the same row/col. #177
This works now on CDSE and tests are added as to Also tested with example from Pratichhya: pratichhya_angle_bands.json.txt However, on |
This seem to work for simple graphs using angle bands, but when running this larger example, there is still an extent error: |
Also tested on https://openeo.dev.warsaw.openeo.dataspace.copernicus.eu/ |
Probably here, changing finder.creodias.eu to zipper.creodias.eu could solve the problem.
Also filtering out the prefixes could be nicer.
openeo-geotrellis-extensions/openeo-geotrellis/src/main/scala/org/openeo/geotrellis/layers/FileLayerProvider.scala
Line 884 in 6814321
Example error from kibana:
The error is about the prefix, but even without the good prefix, the url gives a 404: https://finder.creodias.eu/files/Sentinel-2/MSI/L1C/2023/05/30/S2B_MSIL1C_20230530T104629_N0509_R051_T31UFS_20230530T125255.SAFE/GRANULE/L1C_T31UFS_A032538_20230530T104623/MTD_TL.xml
The text was updated successfully, but these errors were encountered: