-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Adapt GridInterfaces to support Histogram and QuadMesh data #547
Comments
After some discussion centered around making sure the design makes sense for different data backends, e.g. xarray and iris, we have come to the conclusion that we will also need an API to access the bin edges of key dimensions. The |
This is useful in some cases but I might want this method only at the interface level and not at the element level, simply because we use Alternatively, how about offering a utility to do this? The guessing process sounds like something very general that doesn't depend on the details of the element? If there are stored bin edges, that data should just be accessed directly without using such a guessing utility.
I believe this would be called Couldn't |
Definitely not happening as part of 1.7, will postpone until 1.8. |
Finally done! We're so close to converting all elements. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
We have long struggled to find an appropriate format to store Histogram and QuadMesh data, which store the edges of the bins in 2D and 3D. The dense data interface provides an opportunity to adapt these types to use a general interface. The major component of this work will be to generalize the GridColumns proposal to work with bin edges as well as discrete coordinates.
The steps to get this implemented should roughly follow:
The text was updated successfully, but these errors were encountered: