1.1.0
A lot of changes and new processes since v1.0.0, see the changelog below for details. We introduced a folder with proposals that are unstable and may break in the future but are worth experimenting with.
Note: Some changes are breaking changes, but none of the processes had been (widely) implemented yet.
Documentation: https://processes.openeo.org/1.1.0/
[1.1.0] - 2021-06-29
Added
- New processes in proposal state
array_append
array_concat
array_create
array_create_labeled
array_find_label
array_interpolate_linear
#173array_modify
date_shift
is_infinite
nan
reduce_spatial
- Added return value details (property
returns
) for the schemas with the subtypeprocess-graph
. API#350 apply_neighborhood
: Clarify behavior for data cubes returned by the child processes and for that add the exceptionDataCubePropertiesImmutable
.- Added a guide for implementors that describes numerours implementation details for processes that could not be covered in the specifications itself, for example a recommended implementation for the
if
process. #246
Changed
- Added
proposals
folder for experimental processes. Experimental processes are not covered by the CHANGELOG and MAY include breaking changes! #196, #207, PSC#8- Moved the experimental process
run_udf_externally
to the proposals. - Moved the rarely used and implemented processes
cummax
,cummin
,cumproduct
,cumsum
,debug
,filter_labels
,load_result
,load_uploaded_files
,resample_cube_temporal
to the proposals.
- Moved the experimental process
- Exception messages have been aligned always use ` instead of '. Tooling could render it with CommonMark.
load_collection
andmask_polygon
: Also support multi polygons instead of just polygons. #237run_udf
andrun_udf_externally
: Specify specific (extensible) protocols for UDF URIs.resample_cube_spatial
andresample_spatial
: Aligned with GDAL and addedrms
andsum
options to methods. Also added better descriptions.resample_cube_temporal
: Process has been simplified and only offers the nearest neighbor method now. Theprocess
parameter has been removed, thedimension
parameter was made less restrictive, the parametervalid_within
was added. #194
Deprecated
GeometryCollection
s are discouraged in all relevant processes.
Removed
- Removed the experimental processes
aggregate_spatial_binary
andreduce_dimension_binary
. #258
Fixed
- Clarify that the user workspace is server-side. #225
- Clarify that the
condition
parameter forarray_filter
works also on indices and labels. - Clarify contradicting statements in
filter_temporal
for the default value of thedimension
parameter. By default all temporal dimensions are affected by the process. #203 - Clarify how the parameters passed to the overlap resolver correspond to the data cubes. #184
- Improve and clarify specifications for
is_nan
,is_nodata
,is_valid
. #189 - Improve and clarify specifications for
all
andany
. #189 array_element
: Clarify thatArrayNotLabeled
exception is thrown when parameterlabel
is specified and the given array is not labeled.array_apply
,array_element
,array_filter
: Added theminimum: 0
constraint to all schemas describing zero-based indices (parameterindex
).array_labels
: Clarified the accepted data type for array elements passed to the parameterdata
.merge_cubes
: Clarified the dimension label order after the merge. #212merge_cubes
: Clarified the fourth example. #266- Fixed typos, grammar issues and other spelling-related issues in many of the processes.
- Fixed the examples
array_contains_nodata
andarray_find_nodata
. - Fixed links to openEO glossary and added links to data cube introduction. #216
- Fixed description of
apply_dimension
with regards to reference systems. Made description easier to understand, too. #234 - Clarified disallowed characters in subtype
file-path
. - Clarified that UDF source code must contain a newline/line-break (affects
run_udf
). aggregate_spatial
,aggregate_spatial_binary
: Clarified that Features, Geometries and GeometryCollections are a single entity in computations. Only FeatureCollections are multiple entities. #252aggregate_spatial
: Clarified that the values have no predefined order and reducers such asfirst
andlast
return unpredictable results. #260load_collection
, parameterspatial_extent
: Clarified that all pixels that are inside the bounding box of the given polygons but do not intersect with any polygon have to be set to no-data (null
). #256load_collection
: Clarified that the parameters are recommended to be used in favor offilter_*
processes.aggregate_temporal
andaggregate_temporal_period
: Clarified that reducers are also executed for intervals/periods with no data. #263dimension_labels
: Clarified that the process fails with aDimensionNotAvailable
exception, if a dimension with the specified name does not exist.