application-package-patterns
Application package patterns based on data stage-in and stage-out behaviors commonly used in EO workflows
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (6.9%) to scientific vocabulary
Repository
Application package patterns based on data stage-in and stage-out behaviors commonly used in EO workflows
Basic Info
- Host: GitHub
- Owner: eoap
- License: apache-2.0
- Language: Common Workflow Language
- Default Branch: main
- Homepage: https://eoap.github.io/application-package-patterns/
- Size: 4.78 MB
Statistics
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
- Releases: 0
Metadata Files
README.md
Application package patterns based on data stage-in and stage-out behaviors commonly used in EO workflows
Application packages expose several patterns in terms of data access and result publishing.
This repository contains CWL descriptions implementing these patterns to verification and validation activities
The patterns are:
1. one input/one output
The CWL includes:
- one input parameter of type Directory
- one output parameter of type Directory
This scenario typically takes one input, applies an algorithm and produces a result
Implementation: delineate water bodies using NDWI and Otsu automatic threshold taking as input a Landsat-9 acquisition
2. two inputs/one output
The CWL includes:
- two input parameters of type Directory
- one output parameter of type Directory
This scenario typically takes as input one pre-event acquisition, one post-even acquisition, applies an algorithm and produces a result
Implementation: delineate water bodies using NDWI and Otsu automatic threshold taking as input Landsat-9 acquisitions
3. scatter on inputs/one output
The CWL includes:
- scatter on an input parameter of type Directory[]
- one output parameter of type Directory
This scenario typically takes as input a stack of acquisitions, applies an aggregation algorithm and produces a result
Implementation: process the NDVI taking as input a stack of Landsat-9 acquisitions producing a STAC Catalog with n STAC Items
json
{
"water_bodies": [
{
"value": "s3://results/pattern-3-9451lj/catalog.json",
"type": "https://raw.githubusercontent.com/eoap/schemas/main/string_format.yaml#URI"
},
{
"value": "s3://results/pattern-3-ezt7al/catalog.json",
"type": "https://raw.githubusercontent.com/eoap/schemas/main/string_format.yaml#URI"
}
]
}
4. one input/two outputs
The CWL includes:
- one input parameter of type Directory
- two output parameters of type Directory
This scenario takes as input an acquisition, applies two algorithms and generates two outputs.
Implementation: process the NDVI and NDWI taking as input a Landsat-9 acquisition. The output include two STAC Catalogs, each with a single STAC Item
5. one input/scatter on outputs
The CWL includes:
- one input parameter of type Directory
- scatter on an output parameter of type Directory[]
This scenario takes as input an acquisition, applies an algorithm and generates several outputs
Implementation: process the NDVI and NDWI taking as input a Landsat-9 acquisition and generating a stack of STAC Catalogs
6. one input, no output
The CWL includes:
- one input parameter of type Directory
- there are no output parameters of type Directory
This corner-case scenario takes as input an acquisition, applies an algorithm and generates an output that is not a STAC Catalog
Implementation: derive the NDVI mean taking as input a Landsat-9 acquisition
Output:
json
{
"mean": 0.07260978
}
7. optional inputs, one output
The CWL includes:
- one optional input parameter of type Directory?
- one output parameter of type Directory
This scenario may take as input an acquisition, an optional input, applies an algorithm and generates an output
Implementation: process the NDVI taking as input Landsat-9 acquisitions
8. one input, optional output
The CWL includes:
- one input parameter of type Directory
- one output parameter of type Directory?
This scenario takes as input an acquisition, applies an algorithm and may or may not generate and output
Implementation: process the NDVI taking as input a Landsat-9 acquisition with a parameter to create or not the output
9. one input, optional outputs
The CWL includes:
- one input parameter of type Directory
- output parameter of type Directory[]?
This scenario takes as input an acquisition, applies an algorithm and may or may not generate outputs
10. multiple inputs, multiple outputs
The CWL includes:
- input parameter of type Directory[]
- output parameter of type Directory[]
This scenario takes as input an array of acquisition, applies an algorithm to each of them.
Owner
- Name: Earth Observation Application Package
- Login: eoap
- Kind: organization
- Location: Italy
- Repositories: 1
- Profile: https://github.com/eoap
Best practices and examples to package Earth Observation applications
CodeMeta (codemeta.json)
{
"version": "0.2.0"
}
GitHub Events
Total
- Release event: 18
- Member event: 1
- Push event: 106
- Pull request event: 7
- Fork event: 1
- Create event: 6
Last Year
- Release event: 18
- Member event: 1
- Push event: 106
- Pull request event: 7
- Fork event: 1
- Create event: 6