Skip to content
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

Scene B3DA causing error with no /bounds #78

Closed
jonaraphael opened this issue Aug 9, 2023 · 3 comments · Fixed by #79
Closed

Scene B3DA causing error with no /bounds #78

jonaraphael opened this issue Aug 9, 2023 · 3 comments · Fixed by #79

Comments

@jonaraphael
Copy link

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.
image

@jonaraphael jonaraphael changed the title Scene B3DA causing error with no .bounds Scene B3DA causing error with no /bounds Aug 9, 2023
@jonaraphael
Copy link
Author

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

@vincentsarago
Copy link
Member

🤔 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!

@jonaraphael
Copy link
Author

Amazing! Thank you so much for including these!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants