openEO

[mhungen]

Hallo there, planetarycomputer team!

Are there any future plans to offer an openEO API?
I think that could be a great addition to the platform and would make it even easier to enter the world of EO data processing.

regards,
Martin

[TomAugspurger]

Hi Martin. I don't have any experience with deploying or maintaining an openEO instance. I'd be curious how far someone could get with an openEO deployment that uses the Planetary Computer APIs and data, without necessarily being part of the Planetary Computer itself.

[m-mohr]

Hey @TomAugspurger, feel free to reach out to the openEO PSC (which I'm part of) if you are interested to discuss: [email protected]

Especially with the background of the security-based deprecation on the Hub, it might be worthwhile to think about a more security-restricted API alternative, if you still consider processing as a service for users. I had similar throughts when reading about the deprecation this morning, see also #347 (reply in thread)

Generally speaking, an openEO API should be able to load from MS PC via the load_stac process, but there will be the data loading bottleneck, so having this as close to the data as possible is surely an advantage over having the openEO implementation hosted externally.

[TomAugspurger]

Thanks Matthias. I do want to explore openEO more when I have a chance.

so having this as close to the data as possible is surely an advantage over having the openEO implementation hosted externally.

Indeed. The nice thing about the Planetary Computer architecture is that anyone is able to get access to the data with resources deployed in their own Azure subscription. They just need to be in the same region as the data (typically West Europe, but the Collection metadata includes information on which region the data is stored in).