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

Add openeo.cloud variant with support for 2.0.0 processes #149

Open
JeroenVerstraelen opened this issue Aug 20, 2024 · 3 comments
Open

Add openeo.cloud variant with support for 2.0.0 processes #149

JeroenVerstraelen opened this issue Aug 20, 2024 · 3 comments
Assignees

Comments

@JeroenVerstraelen
Copy link
Contributor

No description provided.

@soxofaan soxofaan changed the title implement support for v2.0.0 process changes (especially datacube subtype) Add openeo.cloud variant with support for 2.0.0 processes Aug 20, 2024
@soxofaan
Copy link
Member

current openeo.cloud config uses these upstream backends:

aggregator_backends={
"vito": "https://openeo.vito.be/openeo/1.1/",
"eodc": "https://openeo.eodc.eu/openeo/1.1.0/",
# Sentinel Hub OpenEO by Sinergise
"sentinelhub": "https://openeo.sentinel-hub.com/production/",

which use v1 version of processes as far as I know.

We should add a variant that supports v2 processes (e.g. like https://openeo.vito.be/openeo/1.2/)

@soxofaan
Copy link
Member

Paths to investigate:

  • implement multi-version support in aggregator itself? Would require "adding a dimension" to the config system in some way, same for the metadata caching. Overall possibly quite a lot of places that have to be adapted
  • just deploy a new instance with other configs. Is probably less work, but adds operational overhead: more systems to monitor, less efficient resource usage, more configs to manage

@soxofaan
Copy link
Member

soxofaan commented Nov 7, 2024

relevant openeo-api/openeo-processes discussion:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants