Error reading Landsat 9 files #101
Replies: 7 comments 16 replies
-
Thanks for reporting this. It seems that the USGS server returned a bad result, and our data pipeline didn't handle it properly. The actual contents of that file are HTML Simplifying things a bit: import planetary_computer
import requests
from IPython.display import HTML
url = "https://landsateuwest.blob.core.windows.net/landsat-c2/level-2/standard/oli-tirs/2022/174/072/LC09_L2SP_174072_20220705_20220803_02_T1/LC09_L2SP_174072_20220705_20220803_02_T1_SR_B7.TIF"
url = planetary_computer.sign(url)
HTML(requests.get(url).text) We'll look into it (along with searching for other places this might have happened) |
Beta Was this translation helpful? Give feedback.
-
Any movement on reprocessing these files? |
Beta Was this translation helpful? Give feedback.
-
It's probably on your list but here is another file with this issue: https://landsateuwest.blob.core.windows.net/landsat-c2/level-2/standard/oli-tirs/2022/101/055/LC08_L2SP_101055_20220612_20220617_02_T2/LC08_L2SP_101055_20220612_20220617_02_T2_SR_B3.TIF Trying to get stackstac or ods.stac to ignore files like this has proven difficult (using e.g. 'errors_as_nodata' for stacstack.stack doesn't seem to working in this case). Short of trying to open every asset and catching errors before calling stack, I've resorted to maintaining a list of bad item ids to filter the itemcollection by prior to reading. Anyone have alternative ideas? |
Beta Was this translation helpful? Give feedback.
-
Just in case it's not on the list, wanted to flag https://landsateuwest.blob.core.windows.net/landsat-c2/level-2/standard/oli-tirs/2022/014/031/LC08_L2SP_014031_20220626_20220706_02_T1/LC08_L2SP_014031_20220626_20220706_02_T1_SR_B3.TIF as the same issue 😄 Looking forward to an update when this is fixed! |
Beta Was this translation helpful? Give feedback.
-
We've updated the STAC items for all of the scenes reported in this discussion. Note that for some of the scenes, the actual URLs in blob storage have changed because USGS reprocessed that scene since we originally pulled it and USGS embeds the processing date in the file paths. For example, the STAC item https://planetarycomputer.microsoft.com/api/stac/v1/collections/landsat-c2-l2/items/LC09_L2SP_174072_20220705_02_T1 previously linked to assets under the prefix
Now, it links to assets under the prefix
(note the We'll eventually delete the original assets, with the problematic files. I don't have an ETA yet, but we'll be auditing our landsat archive to find all the scenes with at least one buggy asset, and will re-download each of those scenes. |
Beta Was this translation helpful? Give feedback.
-
Hello! I've been running into this issue lately. So far I've been listing the offending files and ignoring them. Is it useful for me to post them here, or should I just stay put? Did you get around to auditing the landsat archive? Anything we can do to help? |
Beta Was this translation helpful? Give feedback.
-
I am running through a loop which pulls the least cloudy Landsat image from the collection in a given time range. Some of these time ranges return Landsat 9 imagery. I am running code in this notebook. Here is the error I get for the least cloudy image of July 2022 which covers
array([ 24.784878, -16.664232])
:Error
Any idea what is causing this? This is the second time it has come up and both times it was for Landsat 9 imagery
Beta Was this translation helpful? Give feedback.
All reactions