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

Allow to have a file as input for ids to download #6

Closed
ninsbl opened this issue May 31, 2024 · 4 comments
Closed

Allow to have a file as input for ids to download #6

ninsbl opened this issue May 31, 2024 · 4 comments
Assignees

Comments

@ninsbl
Copy link

ninsbl commented May 31, 2024

It is possible, that users may want to download a lager number of files by ID.
Therefore, we should consider also the possibility of "file" input to the id option.

@HamedElgizery
Copy link
Owner

Do you mean by that we can have a TXT file with a list of IDs (separated by commas maybe), and then we could pass that file to the id option, and then download them?

Also, I think it is relevant to mention this here... there is this serialization/deserialization methods provided by eodag, to save the search results as a GeoJSON file. I will add support for that as well.
https://eodag.readthedocs.io/en/stable/notebooks/api_user_guide/5_serialize_deserialize.html

Would it be reasonable to consider other file types... like CSV? Is it typically used in GRASS?

@HamedElgizery HamedElgizery self-assigned this Jun 1, 2024
@ninsbl
Copy link
Author

ninsbl commented Jun 1, 2024

A text file with one ID per line would be good.

The EODAG produced GeoJSON makes sense too, but plain text seems more simple, esp. if users identify IDs by other means...

@HamedElgizery
Copy link
Owner

Added the text file with IDs option here #8

@HamedElgizery
Copy link
Owner

Merged to trunk. OSGeo#1097

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

No branches or pull requests

2 participants