c-scale-community / c-scale-community/use-case-return
Data requirements
- Dominant language
- Jupyter Notebook
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Dear @backeb
From a SURF perspective the list generated by by WP4 on confluence for this use case is fine with us. Please note that SURF does not have an in-house EO data holding. However, we do have excellent network connections to the outside world.
For part (a) of this use case we have currently setup a workflow based on FORCE that is able to access EO data provided by various public cloud providers. More info on FORCE:
https://github.com/davidfrantz/force
https://force-eo.readthedocs.io/en/latest/
SURF is listed as the initial provider, we are in regular contact with this use case and are making progress.
One important note here is that this use case aims to use LANDSAT (USGS) data. None of the data providers in the C-SCALE currently provides access to this data. However, via FORCE we are able to access this data using the public cloud providers. Other use cases have also mentioned a need for LANDSAT and hence the solution developed by the return may also work for other use cases. I will investigate whether this work can be shared within C-SCALE.
Regarding part (b) of the use case we are still waiting to hear from the use case whether the data provided by EODC is sufficient.
best regards,
Raymond
Contributor guide
No contributing guide indexed for this repository
Research direction
No project files or tests are named. Start by reviewing parts (a) and (b) of this issue and the linked FORCE documentation, then clarify the LANDSAT access approach and whether EODC data is sufficient; completion requires an agreed data plan for both parts.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100