Replies: 1 comment
-
Dear Thomas, I don't see any issue on my end and could not reproduce the behaviour:
Are you running the job through Docker, or is this a custom installation? You could try using the debug container (dev-debug) and inspect the individual output layers. Best, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hallo David,
I was updating my existing Landsat data archive (L8, L9) for two tiles for the years 2022-2023. One tile gives me correct data (192/027) while there is no updated data for the other tile (except when i force it to 100% cc, then i get an image with nodata values). The log files are all the same with data coverage: 0 and cloud coverage 100%. I first thought it might be the DEM coverage but it is definitely large enough (and it all ran smoothly before). I attach here a log files and the parameter files, I am using FORCE DEV.
Any idea what might be the cause?
Thanks a lot for your support,
best,
Thomas
192027.txt
193027.txt
LC08_L1TP_193027_20230907_20230912_02_T1.txt.log
Update: I did another run without the DEM and I do get also results for the 193027 tile. Yet, I don't understand why this is happening and I would like to use the topographic correction. The DEM is correct and large enough.
The only notable difference between the two tiles is the difference in UTM zone (UTM 33 works, UTM 32 doesn't). The DEM is in geographic coordinates.
Beta Was this translation helpful? Give feedback.
All reactions