make `load_stac` official

[clausmichele]

The load_stac process is still in the proposal folder, it should be moved up with the other official processes in my opinion. It's supported by the CDSE, VITO, EODC, Eurac and probably other back-ends.

I did try to move it already in an old PR @m-mohr , is there a reason for keeping it under proposals?

[m-mohr]

See #544, the main reason is that there are still some open issues related to load_stac in the issue tracker.

All processes in here are "official", they are just categorized into "stable" and "experimental" (means changes are likely, breaking changes may occur). In proposal we can do breaking changes without going to v3, once stable we need to issue v3 (which is unlikely anytime soon). So unless we are certain to not make breaking changes, we should probably keep it in proposals. Looking at the open issues, they don't look breaking on first sight, but haven't looked into details. If we don't think anything will break while resolving the other issues, we can consider moving it to stable.

[soxofaan]

Bumping this issue: what are the concrete issues that are still blocking here?

quick look through current load_stac issues:

• load_stac: stac_items #501
  • breaking, but old proposal that got stale by now?
• load_stac: support for resources behind auth wall #559
  • this is potentially blocking/breaking, but it's non-trivial and wide practical experience is pretty limited, I think. I'm not sure it's productive anymore to wait for this one to settle for v2, so I'd push this to a v3 (unless there are solutions that would involve non-breaking updates)
• load_stac: custom item filter/transform #541:
  • also potentially blocking/breaking, but like the previous one, I'm not sure if it's still useful to try to include this one in v2
• load_collection (and related): clarify antimeridian handling of spatial_extent parameter #568
  • is just a documentation clarification issue, not blocking I think
• Support STAC ItemCollection in load_stac #570
  • This is technically a breaking change, but easy to add (just a description tweak), and probably not that hard for implementers to add support for (because implementation already handle STAC ItemCollections anyway from STAC API usage)

Maybe good idea to go through this in the next openEO dev meeting?

[m-mohr]

Yeah, I agree. #568 and #570 we can probably add still for v2, all others are out of scope for v2.