openEO API v1.2.0
Documentation: https://api.openeo.org/1.2.0/
[1.2.0] - 2021-05-25
Added
- New extensions:
GET /: New Relation types: #404create-formto link to the registration pagerecovery-formto link to the credentials recovery page.
GET /file_formats: Addpointcloudto thegis_data_types. #475GET /me: New Relation typesalternateandrelatedfor user-specific external pages. #404GET /credentials/oidc: Allowauthorization_codeandurn:ietf:params:oauth:grant-type:device_code(both without PKCE) as grants fordefault_clients. #410GET /jobsandGET /jobs/{job_id}: Added a links property that can for example link to results and logs. #453GET /jobs/{job_id}/results:- Recommendation to add a link with relation type
canonicalwhich points to a signed URL with the same content as the response. #397 - Added metadata field
openeo:statusto indicate the job status (and whether the result is complete or not). - Added parameter
partialto allow retrieving incomplete results, which must also add the new propertyopeneo:statusto the metadata. #430
- Recommendation to add a link with relation type
GET /jobs/{job_id}/logs,GET /services/{service_id}/logs: Addedlevelparameter to requests to set the minimum log level returned by the response. #485- Added property
log_levelto secondary web service, batch job and synchronous processing endpoints to indicate the minimum severity level that should be stored for logs. #329 GET /jobs/{job_id}/logs,GET /services/{service_id}/logsandPOST /result: Addedlevelproperty in responses to reflect the minimum log level that may appear in the response. #329- Recommendation to add media types and titles to links for a better user experience.
- Allow the relation type
canonicalto be used generally for (shared) resources (e.g. UDPs or batch jobs) without requiring Bearer authentication. #405 - Recommendation for UDF runtime names. #409
- Processes: Added
dimensionsschema for subtypedatacube - Collections: Added
geometrydimension type tocube:dimensions - New endpoint for metadata filters (queryables):
/collections/{collection_id}/queryables. Also adds a new rel type to the collection links. #396
Changed
- Updated STAC specification examples and references to v1.0.0, please see the STAC changelog for all changes between 0.9 and 1.0.
cube:dimensions:reference_systemis allowed to be PROJJSON, too.- Relaxed requirement that unsupported endpoints must return HTTP status code 501. Instead also HTTP status code 404 can be used (and is regularly used in practice). #415
- Minimum value for
costsandbudgetis 0. GET /jobs/{job_id}/estimate: If a batch job can't be estimated reliably, aEstimateComplexityerror should be returned. #443- The
/conformanceendpoint is now generally used for OGC APIs, STAC API and openEO.conformsTois also exposed inGET /for STAC APIs. The openEO API and all extensions got individual conformance classes. #186
Fixed
- Explicitly mention the use of HTTP content negotiation
- Clarify that the default charset is UTF-8 #462
- Fixed inconsistencies in errors.json: removed
ProcessGraphIdDoesntMatch, clarifiedProcessGraphMissing, addedProcessInvalidandProcessGraphInvalid. #394, #395, #401 - Fixed the default value for the version number in the API url (
v1.0->v1) and improved the description for API versioning. #393 - Fixed the Collection example to use
gsdinstead ofeo:gsd. #399 - Clarify use of
user_id. #404 - Clarify that the relation type
version-historyshould include/.well-known/openeoin the URL. - Clarify that clients should (re-)request capabilities and discovery endpoints with token if available and supported. #416
- Clarify the fields
plan(for processing requests) andbilling_plan(inGET /andGET /me). #425 #426 - Clarified ambiguous batch job status changes.
- Reflect that the
debugprocess has been renamed toinspect. - Clarified uniqueness constraints for identifiers. #449 #454
- Clarified schematically the applicability of JSON Schema extensions (
parameters,returns,dimensions) and their relation to the subtypes GET /: Removed the superfluous default value forcurrency. #423GET /credentials/oidc: Clarify that clients may add additional scopesGET /me: Clarify the behavior of the fieldbudget.GET /jobs/{job_id}/logs,GET /services/{service_id}/logsandPOST /result: Clarified the formatting of themessageproperty. #455GET /jobs/{job_id}/estimate: Don't require that the costs are the upper limit. Services may specify the costs more freely depending on their terms of service.GET /servicesandGET /services/{service_id}: Clarify thatenabledis required by removing the default value. #473- Several appearances of
nullablewere clarified according to the lint report by Spectral - Clarify how the well-known document works #460
- Clarify handling of JSON Schema versions