Skip to content
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

Run EOEPCA externally #332

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 55 additions & 0 deletions proposals/run_eoepca_externally.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
{
"id": "run_eoepca_externally",
"summary": "Run processing externally on EOEPCA",
"description": "Runs processing tasks on an [EOEPCA](https://eoepca.org/) compliant processing platform, which essentially runs a hosted docker container.",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably add information about the API interface. Is this always OGC API - Processes?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It needs to be much more specific than just saying OGC API - Processes.
EOEPCA should have a kind of profile with process signatures that an application package can support to be callable by openEO.

"categories": [
"cubes",
"import",
"export",
"udf"
],
"experimental": true,
"parameters": [
{
"name": "data",
"description": "The data to be passed to the external processing platform.",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This implicitly does a save_result to a file format the image can read.

"schema": {
"type": "object",
"subtype": "raster-cube"
}
},
{
"name": "url",
"description": "Absolute URL to a remote EOEPCA service.",
"schema": {
"type": "string",
"format": "uri",
"subtype": "uri",
"pattern": "^https?://"
}
},
{
"name": "context",
"description": "Additional data such as configuration options to be passed to the container.",
"schema": {
"type": "object"
},
"default": {},
"optional": true
}
],
"returns": {
"description": "The data processed by the external processing platform.",
"schema": {
"type": "object",
"subtype": "raster-cube"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here the application package would implictly need to save a result in a way that openEO can read it. The allowed file formats are available through GET /file_formats, but there might be issues in the details (e.g. how are dimensions named in netCDF, etc.)

}
},
"links": [
{
"rel": "about",
"href": "https://eoepca.org/",
"title": "EOEPCA: Earth Observation Exploitation Platform Common Architecture"
}
]
}