STAC API for batch job results?

[m-mohr]

It could in some use cases (very large results exported as COGs and visualized via a web browser client) be useful to expose an actual STAC API for job results instead of just the "static" STAC Item or Collection.

[jdries]

@LukeWeidenwalker @christophreimer linked to 'user collection' concept?

[m-mohr]

It is actually not really possible in a standards compliant and non-breaking way:

• openEO allows a Collection or Item at GET /jobs/{job_id}/results
• STAC API requires the landing page to be a Catalog

Moving to 2.0.0.

Related: #376
Duplicate: #484

[clausmichele]

@m-mohr is it currently possible to return a STAC Collection, which is also exposed in a STAC API? Maybe the "self" link could point to the Collection exposed at the API (i.e. the json that the API would return for that Collection).

[m-mohr]

That should be possible if the Collection lists all assets in the collection, too.

[clausmichele]

So, the Collection exposed via the API should be a copy of the one returned by openEO (i.e. conform to the openEO API with the assets also at Collection level). Should also all the Items be listed in the links or it's not necessary?