CMOR checker does not check CMIP6 generic levels

[bouweandela]

The CMOR check does not check generic levels, see e.g.

ESMValCore/esmvalcore/cmor/check.py

Line 333 in c460cea

# Cannot check generic_level coords as no CMOR information

However, generic level definitions are available in the CMIP6_coordinates.json file, e.g. (notice line 500)

ESMValCore/esmvalcore/cmor/tables/cmip6/Tables/CMIP6_coordinate.json

Lines 479 to 501 in c460cea

	"depth_coord": {
	"standard_name": "depth",
	"units": "m",
	"axis": "Z",
	"long_name": "ocean depth coordinate",
	"climatology": "",
	"formula": "",
	"must_have_bounds": "yes",
	"out_name": "lev",
	"positive": "down",
	"requested": "",
	"requested_bounds": "",
	"stored_direction": "increasing",
	"tolerance": "",
	"type": "",
	"valid_max": "12000.0",
	"valid_min": "0.0",
	"value": "",
	"z_bounds_factors": "",
	"z_factors": "",
	"bounds_values": "",
	"generic_level_name": "olevel"
	},

Therefore it would be good if the checker could be improved so it checks these coordinates if a definition is available.

[sloosvel]

There are several coordinates sharing the same generic_level_name . So I am not sure how they could be distinguished when loading the table information for each variable in table.py .

Taking thetao as an example, the information that is given in the tables regarding its dimensions is:

"dimensions": "longitude latitude olevel time"

And in CMIP6_coordinates there are five coordinates that have the generic_level_name set to olevel (depth_coord, ocean_double_sigma, ocean_s, ocean_sigma, ocean_sigma_z). How could you know which one to load?

[jvegreg]

How could you know which one to load?

We can not, we must check against the five and raise issues if none of them comply