Replies: 1 comment
-
Wouldn't it be a solution to have it defined in a parameter with the pattern? Example: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For the moment, depending on the provider used to download products, you may have different output directory depth. This is due to additional top directories inside archives that are kept after extraction.
Example of output directory:
A parameter in the provider settings,
archive_depth
already exists to help eodag returning the good directory level that is effectively pointing to the data. But it may be something like/path/to/{title}/{title}.SAFE
or/path/to/{title}.SAFE
.See issues where we have talked about it: #251 and #266
In order to try standardizing output folders depth a bit more, would you prefer:
/path/to/{title}/{title}.SAFE
whenarchive_depth=2
(like peps) or/path/to/{title}
whenarchive_depth=1
(like mundi)/path/to/{title}.SAFE
whenarchive_depth=2
: we keep the archive root directory/path/to/{title}
whenarchive_depth=2
: we delete the archive root directory8 votes ·
Beta Was this translation helpful? Give feedback.
All reactions