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

Support queries on atomic dataset domains #93

Open
bnlawrence opened this issue Oct 14, 2022 · 1 comment
Open

Support queries on atomic dataset domains #93

bnlawrence opened this issue Oct 14, 2022 · 1 comment
Labels
use-case-requirement Something cfstore needs to be able to do

Comments

@bnlawrence
Copy link
Collaborator

We want to import "domain extents" while creating b-metadata. We'd do that by getting the range of the coordinates of each variable in an atomic dataset, and storing (separate) representations of each of the spatial bound box, and the the temporal bounding box (including calendar).

We also want "domain resolution".

How should we query this? We need to support simple use cases like:

  • looking for global fields
  • looking for X (cordex domain)
  • looking for Y (named domain) (do we need to name domains we find as we load data from limited area models)?
  • looking for a specific period
  • looking for a specific resolution

(this last is a property of a domain, but not of a bounding box, suggests we need to name resolutions as we import them)

@bnlawrence bnlawrence added the use-case-requirement Something cfstore needs to be able to do label Oct 14, 2022
@bnlawrence
Copy link
Collaborator Author

There is now a cf-python ticket which would prepare some of the ground for this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
use-case-requirement Something cfstore needs to be able to do
Projects
None yet
Development

No branches or pull requests

1 participant