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.

Sign up for GitHub

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

Jump to bottom

Underscore is not a good delimiter with S3 naming conventions #7

Closed
fwfichtner opened this issue May 6, 2020 · 0 comments
Closed

Underscore is not a good delimiter with S3 naming conventions #7

fwfichtner opened this issue May 6, 2020 · 0 comments
Assignees
@fwfichtner
Labels
bug Something isn't working

Comments

@fwfichtner
Copy link
Contributor

fwfichtner commented May 6, 2020 •
edited
Loading

Describe the bug
In certain cases there's multiple underscores in S3 filenames, see naming conventions.

To Reproduce
Use following example filename S3A_OL_1_EFR____20151102T094537_20151102T094837_20151103T075458_0180_090_022______LN2_D_NT_001.SEN3 with get_ts_from_sentinel_filename().

Expected behavior
Give back 20151102T094537.
@fwfichtner fwfichtner added the bug Something isn't working label May 6, 2020
@fwfichtner fwfichtner self-assigned this May 6, 2020
@fwfichtner fwfichtner mentioned this issue May 6, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fwfichtner fwfichtner

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

position in S3-naming, convention allows multiple '_' dlr-eoc/ukis-pysat
1 participant
@fwfichtner