support for data discovery #102
Labels
Projects
Comments
angus-g
added a commit
to angus-g/cosima-cookbook
that referenced
this issue
Jun 7, 2019
This goes some of the way to solving COSIMA#102, by setting up a table of longnames that can be queried.
angus-g
added a commit
to angus-g/cosima-cookbook
that referenced
this issue
Jun 13, 2019
This goes some of the way to solving COSIMA#102, by setting up a table of longnames that can be queried.
angus-g
added a commit
to angus-g/cosima-cookbook
that referenced
this issue
Jun 18, 2019
This goes some of the way to solving COSIMA#102, by setting up a table of common variables, along with attributes like `long_name`, `standard_name` and `units`, which are all defined in the CF Conventions.
|
I have been playing around with A simple prototype using tables to select experiments and variables is here: but needs to be run live to see the table select boxes. When an experiment is selected it refreshes the table showing the available variables
|
This was referenced Jun 29, 2020
|
Yes, magnificently! thanks @aidanheerdegen |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think it would be helpful to enhance the database to better support data discovery, e.g. to allow implementation of a
cc.discover(pattern)function that would take a pattern and do a GLOB and/or LIKE SQL query to return any (variable, experiment, ncfile, longname, units) tuples that match (which could then be used to callget_nc_variable). It might also be handy to have optional experiment and ncfile arguments to restrict the search.It would be most useful if this would also search longnames so that a user can discover what variable names are used for particular physical quantities. I guess for compactness this would be best stored as a separate table that just contains all the unique variable names and their associated longname, which would need to be updated by
build_index.The text was updated successfully, but these errors were encountered: