Release openEO processes v1.2.0

[m-mohr]

Background

We've collected improvements and useful new processes for almost another half a year. This publishes clarifications and improvements to the public so that we don't need to work on the draft any longer. It also gives a clean basis for the upcoming (potentially) major changes for the vector data cubes and as such the release doesn't need to be held back for those larger changes.

You can review the changes at Open-EO/openeo-processes#311 (it would be great if at least one of you could also approve the PR itself)

The following changes have been made to the processes:

Added

• New processes in proposal state
  • fit_curve
  • predict_curve
• ard_normalized_radar_backscatter and sar_backscatter: Added options parameter
• array_find: Added parameter reverse. #269
• load_result:
  • Added ability to load by (signed) URL (supported since openEO API v1.1.0).
  • Added parameters spatial_extent, temporal_extent and bands. #220
• run_udf: Exception InvalidRuntime added. #273
• A new category "math > statistics" has been added #277

Changed

• array_labels: Allow normal arrays to be passed for which the process returns the indices. #243
• debug:
  • Renamed to inspect.
  • The log level error does not need to stop execution.
  • Added proposals for logging several data types to the implementation guide.

Removed

• Removed the explicit schema for raster-cube in the data parameters and return values of run_udf and run_udf_externally. It's still possible to pass raster-cubes via the "any" data type, but it's discouraged due to scalability issues. #285

Fixed

• aggregate_temporal_period: Clarified which dimension labels are present in the returned data cube. #274
• ard_surface_reflectance: The process has been categorized as "optical" instead of "sar".
• array_modify: Clarified behavior.
• save_result: Clarify how the process works in the different contexts it is used in (e.g. synchronous processing, secondary web service). #288
• quantiles:
  • The default algorithm for sample quantiles has been clarified (type 7). #296
  • Improved documentation in general. #278

Proposal

I'm proposing to release openEO processes 1.2.0 once the PSC vote is through.

I'll inform you here if any additional changes come in until we approved the release here.

Additional context

Deadline: December 29, 2021

[m-mohr]

+1

Hmm, as no one else has voted yet I assume that the notifications did now work properly. So pinging directly: @edzer @neteler @mkadunc @lforesta @jdries @aljacob

[jdries]

+1

[mkadunc]

+1

[edzer]

+1

[m-mohr]

This has been accepted already according to the PSC guideline, but I'm still leaving this open for at least two days so that others can check and veto if required.

[neteler]

This has been accepted already according to the PSC guideline, but I'm still leaving this open for at least two days so that others can check and veto if required.

Well, what about the "Deadline: December 29, 2021" mentioned above?

[m-mohr]

@neteler The PSC guideline says that "A proposal will be accepted if it receives +3 (including the proposer) and no vetoes (-1) or has not received enough votes in 20 business days." and "Proposals need to be available for review for at least two business days before a final decision can be made."

That means once we reach +3 without vetoes and the vote is up to at least two business days it can be seen as accepted unless anyone vetoes in the time it is still open. The "deadline" that I've mentioned above refers to the date where a proposal will be accepted if it has not received enough votes. Admitedly, it is a bit weird that once 3 positive votes come in the vetos are somewhat time dependant and that the term "deadline" could be misleading here.

Anyway, my message above is basically to inform about that in the current state it could be accepted already and that I'm planning to do that soon. This allows people to jump in and say that they may need more time and I'm always happy to grant that if needed as otherwise I try to get to acceptance as soon as possible to not block things for the remaining business days.

[neteler]

(Thanks for your feedback, @m-mohr!)

+1

[aljacob]

+1

[m-mohr]

Accepted, thanks. I'll release it today.