You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
6
6
7
7
## Unreleased / Draft
8
8
9
+
## 1.0.0-rc.2 - 2020-02-20
10
+
9
11
### Added
10
12
-`PUT /process_graphs/{process_graph_id}` to store and replace custom process-graphs. [#260](https://github.com/Open-EO/openeo-api/issues/260)
11
13
-`/jobs/{job_id}/logs` and `GET /services/{service_id}/logs`: Reintroduced the missing `offset` parameter.
Copy file name to clipboardExpand all lines: README.md
+7-6Lines changed: 7 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,17 @@
2
2
3
3
openEO develops an open API to connect R, Python and JavaScript clients to big Earth observation cloud back-ends in a simple and unified way. This repository contains this API, the openEO (core) API.
***[Latest Version of the Specification](https://api.openeo.org)**
6
6
7
-
## Versions
7
+
## Versions / Branches
8
8
9
-
The openEO (core) API is currently released in version **1.0.0-rc.1**. **This branch is an unreleased draft!**
9
+
The [master branch](https://github.com/Open-EO/openeo-api/tree/master) is the 'stable' version of the openEO API specification. It is currently version **1.0.0-rc.2** of the specification. The [draft branch](https://github.com/Open-EO/openeo-api/tree/draft) is where active development takes place.
|[draft](https://api.openeo.org/draft)| planned | Bug fixes based on developer feedback, introduce extension concept. Potentially version 1.0.0-final. |
14
-
|[**1.0.0-rc.1**](https://api.openeo.org)|**current**| Release candidate for first stable version of openEO, see the [changelog](CHANGELOG.md#100-rc1---2020-01-31). |
13
+
|[draft](https://api.openeo.org/draft)| planned |*Unstable* - Bug fixes based on developer feedback, introduce extension concept. Potentially version 1.0.0-final. |
14
+
|[**1.0.0-rc.2**](https://api.openeo.org)|**current**| Release candidate 2 for first stable version of openEO, see the [changelog](CHANGELOG.md#100-rc2---2020-02-20). |
15
+
|[1.0.0-rc.1](https://api.openeo.org/1.0.0-rc.1)| legacy | Release candidate 1 for first stable version of openEO, see the [changelog](CHANGELOG.md#100-rc1---2020-01-31). |
15
16
|[0.4.2](https://api.openeo.org/v/0.4.2)| legacy | Bugfix release, see the [changelog](CHANGELOG.md#042---2019-06-11). |
16
17
|[0.4.1](https://api.openeo.org/v/0.4.1)| legacy | Bugfix release, see the [changelog](CHANGELOG.md#041---2019-05-29). |
17
18
|[0.4.0](https://api.openeo.org/v/0.4.0)| legacy | Improved discovery, added processes catalogue, new process graph structure and [more](CHANGELOG.md#040---2019-03-07). |
@@ -26,7 +27,7 @@ See also the [changelog](CHANGELOG.md) and the [milestones](https://github.com/O
26
27
27
28
This repository contains a set of files formally describing the openEO API, each with a human-readable and easily browseable version:
28
29
29
-
*[openapi.yaml](openapi.yaml)([human-readable version](https://api.openeo.org/draft/)) provides the [openAPI](https://www.openapis.org/) 3.0 definition of the openEO API.
30
+
*[openapi.yaml](openapi.yaml) provides the [OpenAPI](https://www.openapis.org/) 3.0 definition of the openEO API. See the table above for human-readable versions of the OpenAPI definition.
30
31
*[errors.json](errors.json) is a list of potential global error codes and messages, excluding specific exceptions separately available for each process.
31
32
*[subtype-schema.json](subtype-schema.json) defines data types (subtypes) for JSON Schema used in openEO.
32
33
* The [assets](assets/) folder contains some useful additional files such as examples or schemas. All of these are non-binding additions. The source of truth are the top-level specification files.
Copy file name to clipboardExpand all lines: openapi.yaml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
openapi: 3.0.2
2
2
info:
3
3
title: openEO API
4
-
version: draft
4
+
version: 1.0.0-rc.2
5
5
description: |-
6
6
The openEO API specification for interoperable cloud-based processing of large Earth observation datasets.
7
7
@@ -193,7 +193,7 @@ info:
193
193
A **process** is an operation that performs a specific task on a set of parameters and returns a result. An example is computing a statistical operation, such as mean or median, on selected EO data. A process is similar to a function or method in programming languages. In openEO, processes are used to build a chain of processes ([process graph](#section/Processes/Process-Graphs)), which can be applied to EO data to derive your own findings from the data.
194
194
195
195
A **pre-defined process** is a process provided by the *back-end*. There is a set of predefined processes by openEO to improve interoperability between back-ends.
196
-
Back-ends SHOULD follow these specifications whenever possible. Not all processes need to be implemented by all back-ends. See the **[process reference](https://processes.openeo.org/draft)** for pre-defined processes.
196
+
Back-ends SHOULD follow these specifications whenever possible. Not all processes need to be implemented by all back-ends. See the **[process reference](https://processes.openeo.org)** for pre-defined processes.
197
197
198
198
A **user-defined process** is a process defined by the *user*. It can directly be part of another process graph or be stored as custom process on a back-end. Internally it is a *process graph* with optional additional metadata.
0 commit comments