diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index 4e8f4f28..29baf6db 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -5,7 +5,6 @@ on: push: branches: - draft - - draft-2.0 - master jobs: deploy: diff --git a/proposals/aggregate_spatial_window.json b/proposals/aggregate_spatial_window.json index 747db151..9e5dce4a 100644 --- a/proposals/aggregate_spatial_window.json +++ b/proposals/aggregate_spatial_window.json @@ -75,7 +75,7 @@ }, { "name": "boundary", - "description": "Behavior to apply if the number of values for the axes `x` and `y` is not a multiple of the corresponding value in the `size` parameter. Options are:\n\n- `pad` (default): pad the data cube with the no-data value `null` to fit the required window size.\n\n- `trim`: trim the data cube to fit the required window size.\n\nSet the parameter `align` to specifies to which corner the data is aligned to.", + "description": "Behavior to apply if the number of values for the axes `x` and `y` is not a multiple of the corresponding value in the `size` parameter. Options are:\n\n- `pad` (default): pad the data cube with the no-data value `null` to fit the required window size.\n\n- `trim`: trim the data cube to fit the required window size.\n\nUse the parameter `align` to align the data to the desired corner.", "schema": { "type": "string", "enum": [ diff --git a/proposals/vector_to_raster.json b/proposals/vector_to_raster.json new file mode 100644 index 00000000..05f8146b --- /dev/null +++ b/proposals/vector_to_raster.json @@ -0,0 +1,58 @@ +{ + "id": "vector_to_raster", + "description": "Creates a raster cube as output based on a vector cube. The values in the output raster cube are based on the numeric properties in the input vector cube.", + "summary": "Converts a vector cube to a raster cube", + "categories": [ + "cubes", + "vector" + ], + "experimental": true, + "parameters": [ + { + "name": "data", + "description": "A vector data cube.", + "schema": { + "type": "object", + "subtype": "datacube", + "dimensions": [ + { + "type": "geometry" + } + ] + } + }, + { + "name": "target", + "description": "A raster data cube used as reference for the target's extent, spatial resolution, and projection.", + "schema": { + "type": "object", + "subtype": "datacube", + "dimensions": [ + { + "type": "spatial", + "axis": [ + "x", + "y" + ] + } + ] + } + } + ], + "returns": { + "description": "A raster data cube with the provided extent, spatial resolution, and projection. The output cube contains bands where each pixel inside the provided polygons has the value related to that polygon in the vector cube and all pixels outside have no-data values.", + "schema": { + "type": "object", + "subtype": "datacube", + "dimensions": [ + { + "type": "spatial", + "axis": [ + "x", + "y" + ] + } + ] + } + } +} diff --git a/tests/docs.html b/tests/docs.html index 23ef98e4..04b1c192 100644 --- a/tests/docs.html +++ b/tests/docs.html @@ -113,8 +113,8 @@ props: { document: 'processes.json', categorize: true, - apiVersion: '1.1.0', - title: 'openEO processes (draft)', + apiVersion: '1.2.0', + title: 'openEO processes (2.0.0-rc.1)', notice: '**Note:** This is the list of all processes specified by the openEO project. Back-ends implement a varying set of processes. Thus, the processes you can use at a specific back-end may derive from the specification, may include non-standardized processes and may not implement all processes listed here. Please check each back-end individually for the processes they support. The client libraries usually have a function called `listProcesses` or `list_processes` for that.' } }) diff --git a/tests/package.json b/tests/package.json index 15f6d2e8..1da8693f 100644 --- a/tests/package.json +++ b/tests/package.json @@ -1,6 +1,6 @@ { "name": "@openeo/processes", - "version": "2.0.0", + "version": "2.0.0-rc.1", "author": "openEO Consortium", "contributors": [ {