GRASS GSoC 2024 EODAG Support
Accepted Google Summer of Code 2024 project.
| Student Name: | Hamed Ashraf Elgizery, AASTMT, Smart-Village, Giza, Egypt |
| Organization: | OSGeo - Open Source Geospatial Foundation |
| Mentor Name: | Luca Delucchi, Veronica Andreo, Stefan Blumentrath |
| GitHub Fork: | View Fork |
| GSoC Proposal | View Proposal |
Abstract
The project focuses on writing a Python library for GRASS GIS that utilizes EODAG API. Currently, GRASS uses different APIs for each satellite data provider. As a result, a lot of maintenance has to be done to keep up with the changes happening to all the different APIs. Thus, adding EODAG support to GRASS GIS will provide a lot of flexibility in the future development of GRASS, by decreasing the amount of maintenance needed to keep up with all the different APIs updated, and instead, sufficiently, maintain the support for EODAG library. Deliverables for this proposal are supporting Sentinel, Landsat, and MODIS datasets with EODAG, and reimplementation of both i.sentinel.download and i.landsat.download modules with the new GRASS EODAG library.
Timeline
| Period | Timeline | Tasks | Status |
|---|---|---|---|
| Bonding Period | May 1 - May 26 |
|
OK |
| Official Coding Period | Week 1 (May 27 - June 1) |
|
OK |
| Week 2 (June 2 - June 8) |
|
OK OK OK | |
| Week 3 (June 9 - June 15) |
|
OK OK | |
| Week 4 (June 16 - June 22) |
|
||
| Week 5 (June 23 - June 29) |
|
||
| Week 6 (June 30 - July 6) |
|
||
| Week 7 (July 7 - July 13) |
|
||
| Week 8 (July 14 - July 20) |
|
||
| Week 9 (July 21 - July 27) |
|
||
| Week 10 (July 28 - August 3) |
|
||
| Week 11 (August 4 - August 10) |
|
||
| Week 12 (August 11 - August 17) |
|
||
| Evaluation Period | August 26 - September 2 | Submit code and final evaluation |
Log of Pull Requests
| Pull Request | Description | Date | Status |
|---|---|---|---|
| #1090 | i.eodag: add i.eodag module | May 27th, 2024 | Merged |
| #1097 | i.eodag: add files support | June 9th, 2024 | Merged |
| #1104 | i.eodag: add files support | June 16th, 2024 | Draft |
| #11 | i.eodag: add testsuite | June 16th, 2024 | Draft |
Reports
Community Bonding Period
What did I get done this week?
- Finished Wiki setup.
- Throughly read EODAG documentation, and got familiar with its capabilities.
- Got familiar with the contribution guidelines.
- Created an initial add-on, with some basic features of EODAG, and went through the compilation process.
- Setup development environment.
What do I plan on doing next week?
- I plan on designing and building the initial structure for the i.eodag module.
Am I blocked on anything?
- I will be having my final exams for the next two weeks. I have started working on the module and done extra research so that I can extend my work during the exams period. I won’t stop working during that period, but I might not have as much time, so I will get some extra work done before and after the exams to catch up, and so no work will be compromised.
Meetings attended during the community bonding period:
- May 16th 2024: Introductory meeting about EODAG, and what are the expected results, and how will the add-on be used.
- May 23rd 2024: Discussing module structure and features.
Week 1
Following is the report for Week 1.
What did I get done this week?
- Built the initial version of i.eodag, found in #1090.
- Added feature for searching & downloading by product (aka. dataset) type.
- Added the following parameter for searching:
- Start time and end time. Users can specify any time that complies with ISO 8601, including adding the timezone.
- AOI. As for now, it uses the current computational region, and supporting GeoJSON will be added next week.
- Provider. Currently specifying a provider is required by the user, and search won’t be done without it. It is planned to add a way to search broadly without specifying a provider.
- Added feature for downloading products by their IDs.
- Added option for the user to specify their custom EODAG config file.
What do I plan on doing next week?
- Add cloud coverage parameter for searching.
- Add printing for relevant metadata information, regarding the products found by searching, and relevant configurations set by the user.
- Add saving results as a GeoJSON, allowing users to save the search results locally and then load them later, to perform downloading or further filtering.
- Add an option to download products from a list of IDs saved in a text file.
- Add handling of AOI as GeoJSON.
Am I blocked on anything?
- Nothing, except the previously mentioned exams, but everything is going well.
Week 2
Following is the report for Week 2 report.
What did I get done this week?
- Added search filtering for datasets with cloud coverage.
- Added a method to download datasets, using a text file with a list of IDs.
- Added printing metadata about the datasets found after searching.
- All the mentioned above are addressed in #1097.
What do I plan on doing next week?
- Continue working on adding AOI with Vector maps, and possibly GeoJSON.
- Add an initial test suite, for the i.eodag module.
Am I blocked on anything?
- No, and I will be done with my final exams by Wednesday this week.
Week 3
Here is my weekly report for Week 3.
What did I get done this week?
- Added support for setting the AOI based on a Vector Map, included in #1097.
- Added support for two ways of searching:
- General Search: searches through all the available providers for results.
- Restricted Search: only searches through a predetermined – set by the user – provider.
- Started working on a testsuite, for the i.eodag module.
- i.eodag manual can be found here.
What do I plan on doing next week?
- Wrap up the initial testsuite.
- Add filtering & sorting for search results.
- Attend – online – and give a brief presentation about the i.eodag module, for the GRASS Community Meeting Prague 2024.
Am I blocked on anything?
- I am not currently blocked on anything.