139-slope-collection

[kvantricht]

Load slope from global collection when on CDSE backend

[GriffinBabe]

Some minor remarks, except for the OpenEO client version

Also I would move the slope computation directly to the PatchFeatureExtractor superclass in GFMAP in the future, as it can be useful to everyone

[GriffinBabe]

I would wait for this ticket to close before changing the OpenEO version

Open-EO/openeo-gfmap#151

[kvantricht]

ok but we can't merge this PR without bumping the version because the new slope collection cannot be loaded with 0.29.0. Something in the python client changed and the former version cannot work with it.

[GriffinBabe]

Okay, I'll try to close this issue GFMAP today

[GriffinBabe]

@kvantricht Nevermind sorry! this issue will come with Version 0.32 and the feature is not yet merged on the client repository

• extend job database interface to allow more granular querying on status Open-EO/openeo-python-client#607

[kvantricht]

Some minor remarks, except for the OpenEO client version

Also I would move the slope computation directly to the PatchFeatureExtractor superclass in GFMAP in the future, as it can be useful to everyone

yeah but the way it's implemented now (especially with the required change to force computation at 20m) is probably not generic enough. I think what would be better instead is a slope (or terrain attributes) process in openEO, which can then be accessed in GFMAP in a transparent way.