Scene B3DA causing error with no /bounds
Closed this issue · 3 comments
Our titiler instance fails when requesting bounds for the following scene:
S1A_S3_GRDH_1SDV_20230807T171941_20230807T172010_049772_05FC2A_B3DA
The object itself is rather strange looking in Scihub. With some weird sort of value-threshold feathering happening beyond the edge of what I would call the bounds of the image.
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
🤔 the issue is because the ID is invalid, because we only accept mode (beam) IW or EW. The beam S1 or S3 is something new to me.
oh, those are stripmap modes, which are slightly different from Interferometric modes: https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/acquisition-modes/stripmap
I thing there is no real blocker from rio-tiler-pds side to allow those datasets!
Amazing! Thank you so much for including these!