execute_local_udf uses different datacube shape compared to Terrascope backend about openeo-python-client HOT 3 CLOSED

If you read in an image or netcdf into numpy/xarray it will also be of shape (height, width) so I believe it would make more sense to the user if we used (t-bands-y-x) wherever possible.

from openeo-python-client.

In the last discussion it was decided to ensure that the user writes code that works independent of the ordering of the input or output datacube. So they should use named accessors as much as possible. If they do return a datacube that is not in (t, bands, y, x) format then the backend will automatically transpose this to the correct order (using the dimension names as guide).

In the geopyspark-driver we already do this for spatiotemporal UDFs but not yet for spatial UDFs:
https://github.com/Open-EO/openeo-geopyspark-driver/blob/master/openeogeotrellis/geopysparkdatacube.py#L764

I will push a commit for this soon.

from openeo-python-client.

I think this now fixed and can be closed

from openeo-python-client.