Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data cube guide is wrong about aggregate_spatial #55

Closed
m-mohr opened this issue Dec 16, 2021 · 1 comment
Closed

Data cube guide is wrong about aggregate_spatial #55

m-mohr opened this issue Dec 16, 2021 · 1 comment
Assignees

Comments

@m-mohr
Copy link
Member

m-mohr commented Dec 16, 2021

The data cube guide talks about aggregate_spatial in a way that it can take 4D cubes and work on them, but the specification of aggregate_spatial only allows to work on 3D cubes:

The data cube must have been reduced to only contain two spatial dimensions and a third dimension the values are aggregated for, for example the temporal dimension to get a time series. Otherwise, this process fails with the TooManyDimensions exception.

We should probably remove the mention of aggregate_spatial and keep the description general. aggregate_spatial can then be mentioned as a variant that works on 3D only.

@m-mohr m-mohr self-assigned this Dec 16, 2021
@m-mohr m-mohr closed this as completed Dec 16, 2021
@soxofaan
Copy link
Member

soxofaan commented Jan 7, 2022

FYI: the VITO backend supports aggregate_spatial on 4D cubes (t, band, x, y), which is actually a feature we commonly use in demo's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants