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

drop target_dimension in aggregate_spatial? #366

Closed
soxofaan opened this issue Apr 22, 2022 · 2 comments · Fixed by #382
Closed

drop target_dimension in aggregate_spatial? #366

soxofaan opened this issue Apr 22, 2022 · 2 comments · Fixed by #382

Comments

@soxofaan
Copy link
Member

While working on a vector cube implementation with aggregate_spatial I started wondering about the point of the target_dimension parameter: what is that for actually and how should that work?

aggregate_spatial starts from a raster data cube (e.g. x-y-t-bands) and aggregates spatially to a vector cube e.g. with dimensions geometry-t-bands.
So you start from a raster data cube and generate a completely new vector cube. You are not updating or appending to the original raster data cube, which this target_dimension seems to suggest in a way.

I don't think we need target_dimension. Unless that is about naming the "geometry" dimension (or whatever we are going to standardize on, I can't find the related issue at the moment)?

@m-mohr m-mohr added the vector label Apr 22, 2022
@m-mohr m-mohr linked a pull request Oct 9, 2022 that will close this issue
14 tasks
@m-mohr
Copy link
Member

m-mohr commented Oct 9, 2022

The new definition in #382 should clarify what target_dimension is used for in the future. Happy to receive feedback about it.

@m-mohr m-mohr added this to the 2.0.0 milestone Oct 9, 2022
@m-mohr m-mohr added the breaking label Oct 9, 2022
@soxofaan
Copy link
Member Author

ok thanks. With #382 being the way forwards, I think we can close this one

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

Successfully merging a pull request may close this issue.

2 participants