-
Notifications
You must be signed in to change notification settings - Fork 5
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
Issues with aggregate_spatial
#84
Comments
Re 3: In general, it would be very useful to keep the GeoJSON properties so that people can actually identify the Features they've provided in the results. I'm not sure if the processes describe this well enough, but we can probably clarify this in general for vector file formats that handle properties. |
I think it's best to submit these independent issues separately, otherwise this thread will become unmanageable . Quick feedback though:
|
Alright, thanks for the feedback! Opened the above issue for the bug. |
ok thanks, it's best to close this one then. |
I wanted to use
aggregate_spatial
in a research project but am running into some problems. The use case is to extract raster values at point locations and return as a vector cube (I understand from processes#37 that this is still pretty much up toaggregate_spatial
).aggregate_spatial
doesn't seem to work when not
dimension is present. I am not sure whether this is definition compliant or not. Fails with error "'SpatialKey' object has no attribute 'instant'". I tried to simply add back a temporal dimension after reducing it, viaadd_dimension
, but that didn't work either. Example Graph:The text was updated successfully, but these errors were encountered: