-
Notifications
You must be signed in to change notification settings - Fork 16
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
Histogram process #41
Comments
Could you come up with a concrete JSON-based proposal? If it's required for the four core use cases it should be in the 0.4 release. |
I don't think it needs to be in 0.4! |
@jdries Could you come up with a concrete JSON-based proposal for the next version? |
Telco: Agreed to add. Not sure whether it's a reducer though, depends on the outcomes of #73, I guess. If there's a volunteer to help define this function, I'd appreciate it. |
Histogram as a reducer process with discrete buckets might look like this: #97. No user-defined buckets are supported yet. |
Seems to be relevant for UC3 (Platform), so giving it some priority. @jdries |
Would this really go through reduce_dimension? I think it might need to go through apply_dimension (with a target_dimension?) instead as the histogram returns more than a single value, right? |
In some of our zonal statistics use cases, we compute histograms. I believe this is basically a type of reducer.
When the input data cube uses a type with a limited range, like byte, we compute a histogram with 256 buckets, and keep track of nodata. For float/double data types, we might need user definded buckets.
The text was updated successfully, but these errors were encountered: