Error: Scene B3DA causing error with no /bounds

[jonaraphael]

KeyError: 'bounds' at .get_bounds ( /app/cerulean_cloud/titiler_client.py:43 )`

S1A_S3_GRDH_1SDV_20230807T171941_20230807T172010_049772_05FC2A_B3DA

Seems like this one image is repeatedly tossed on the queue, and keeps breaking the container because it does not have any bounds associated with it.

Looking at it, it seems quite strange:

[vincentsarago]

are you sure about the scene id?

from rio_tiler_pds.sentinel.aws.sentinel1 import S1L1CReader
sceneid="S1A_S3_GRDH_1SDV_20230807T171941_20230807T172010_049772_05FC2A_B3DA"
with S1L1CReader(sceneid) as src:
    print(src.bounds)

InvalidSentinelSceneId: Could not match S1A_S3_GRDH_1SDV_20230807T171941_20230807T172010_049772_05FC2A_B3DA

[jonaraphael]

@vincentsarago ,
Yep! All my scene IDs originally come from an SNS tied to the AWS open data registry as objects are added. You can look it up on scihub, but unfortunately scihub's interface does not provide bespoke URLs for specific objects, so here is a screenshot.
https://scihub.copernicus.eu/dhus/#/home

[vincentsarago]

can you open an issue in rio-tiler-pds 🙏

[jonaraphael]

Can do! Just note that I’m not sure the issue originated from rio-tiler-pds. I’ve not dig into this too deeply, since it doesn’t seem to happen often

[jonaraphael]

see cogeotiff/rio-tiler-pds#78

[jonaraphael]

New example with the same behavior:
S1A_S1_GRDH_1SDV_20230809T020729_20230809T020754_049792_05FCE6_1175

Notes:
• This one does not have that strange feathering on its edges
• This one is not close to the anti-meridian
• This one is an S1A_S1, whereas the first example was an S1A_S3