c-scale-community / c-scale-community/use-case-return
Progress updates
- Dominant language
- Jupyter Notebook
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
**yyyy-mm-dd**
**2022-02-06**
@backeb , here is small update on the return project:
1) In 2021 WdK together with NLeSC finished work on the makedatacube project. The makedatacube software is aimed at automatically running and scaling L1 data processing to L2 (imaging) data (Landsat). It is based on the FORCE (https://github.com/davidfrantz/force) software and was enhanced with a.o., script wrappers, configuration files and containerised software. The software was implemented and tested for Landsat data (using Google Cloud as a data data source). For data retrieval, we found by experimentation that upon working with several download stream that it was possible to obtain total download speeds up to around 400 MB/s. A workshop on makedatacube is planned on 2022-02-07. Note that most of the software development work was done outside of C-SCALE and that to date it was not yet used at scale.
2) With WdK and NLeSC leaving the project we are now looking for opportunities to continue the work with makedatacube, use it for sizeable areas and perhaps enhance it to also use Sentinel 2 data. There are possible paths, but these are very uncertain at the moment.
3) With MM we have been exploring Sentinel 1 radar data. Several tests have been done, including succesfully deploying ESA SNAP on the C-SCALE infrastructure at SURF. Atm MM is aiming to get S1 ARD data from EODC to SURF and analyse this here. MM has about 5 months left to work on this project which is expected to be focused on the ARD analysis.
4) At end of Q1 we need to investigate whether there is sufficient interest and effort to continue this use-case within C-SCALE.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue contains only a dated progress update about makedatacube, Landsat and Sentinel data, Google Cloud, and ESA SNAP. It names no file, test, or entry point; clarify the intended follow-up and acceptance criteria before treating it as a contribution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud
- Domain
- cloud, data, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100