Open soxofaan opened 5 months ago
(Same question for the optional "Link" header in synchronous processing response, but I don't think there are implementations of that in the wild yet)
:eyes:
I was also thinking of the Request-Id
header for debugging (successful) requests; looks like an easier version of the Link
header.
and related, here I propose to add a OpenEO-Identifier
header for sync requests to align better with batch job creation:
(Same question for the optional "Link" header in synchronous processing response, but I don't think there are implementations of that in the wild yet)
The Google Earth Engine driver implements it if you want to test it.
The response of synchronous processing (https://api.openeo.org/#tag/Data-Processing/operation/compute-result) has an optional "OpenEO-Costs" header with processing costs.
How could we expose that to user from a simple
cube.download()
call?