-
Notifications
You must be signed in to change notification settings - Fork 151
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
i.eodag: add files support #1097
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @HamedElgizery Here are some comments regarding the proposed changes. Since I was not present at the last meeting, @lucadelu and @veroandreo please feel free to dismiss comments you do not agree with...
Co-authored-by: Stefan Blumentrath <stefan.blumentrath@gmx.de>
Co-authored-by: Stefan Blumentrath <stefan.blumentrath@gmx.de>
Co-authored-by: Stefan Blumentrath <stefan.blumentrath@gmx.de>
I can't get the module to see the eodag library that I injected in the jupyter env where I'm testing ( In any case, |
After activating the eodag venv and injecting pandas there, I get:
With default S1 product it works:
|
@veroandreo If you set the DEBUG environment variable to zero, the error should be gone. |
Instead I'm a little bit confused by provider option. I think providers are defined by the user in the EODAG config file, it should be enough. |
It should be enough, agree yes. But, the provider option is to constraint the module, and to tell it where to search exactly... if it didn't find the scene I am looking for with the provider being set, then stop and don't look in other providers... If it was to depend on the config file, it will try to look for the provider with highest priority, if it didn't find any scenes it will search using the next priority provider, and so on. So, I think constraining it and having it working with one and only one provider, makes it more reliable and expected... I think we could make the provider optional as well, and let eodag use the config file for searching when the provider is not set, so we can have both ways for searching, right? |
Yes I think this is the most useful way, keep it as optional. It is true that it is more reliable and expected but if I want to download that images I'm not interested where they come from since they should be identical in each provider |
Now, if we make the provider optional, that I agree, do we need a default product and provider, so when users do |
I think we can make the provider optional without setting a default one, and so if none is provided it will then use the config file to figure out which provider to use (or use multiple providers till it find the scenes)... And for the default product I agree that we can make it S2_MSI_L1C. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works as expected in the tests I did, ready to merge once doc changes are applied
Co-authored-by: Veronica Andreo <veroandreo@gmail.com>
Co-authored-by: Veronica Andreo <veroandreo@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @HamedElgizery , here are some comments on the code. I hope I do not come across too picky. Please feel free to dismiss the more stylistic comments and suggestions. What I think is important to discuss is the usage of sort filter capabilities in EODAG vs. downstream adjustmens / re-implementations... But the latter can be tackled in the next PR or the PR thereafter....
Co-authored-by: Stefan Blumentrath <stefan.blumentrath@gmx.de>
Co-authored-by: Stefan Blumentrath <stefan.blumentrath@gmx.de>
Co-authored-by: Stefan Blumentrath <stefan.blumentrath@gmx.de>
Co-authored-by: Stefan Blumentrath <stefan.blumentrath@gmx.de>
Thanks for the comment, @ninsbl. |
Note when ready to merge, or if it is somewhat possible to fix: the last commit, 6c27785 says that it adds "panadas" as a requirement, but it rather should be "pandas". The actual contents seem fine though. |
This pull request will add: