We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
download
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?
cube.download()
The text was updated successfully, but these errors were encountered:
(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)
Sorry, something went wrong.
👀
I was also thinking of the Request-Id header for debugging (successful) requests; looks like an easier version of the Link header.
Request-Id
Link
and related, here I propose to add a OpenEO-Identifier header for sync requests to align better with batch job creation:
OpenEO-Identifier
The Google Earth Engine driver implements it if you want to test it.
No branches or pull requests
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?The text was updated successfully, but these errors were encountered: