CORDEX record review

[agstephens]

Hi @rhysrevans3, looking good. Here is my review of this CORDEX record with a few tweaks:

Record location: https://files.slack.com/files-pri/T0E163VL6-F061FM5LPMZ/cordex.output.eur-11.mohc.cnrm-cerfacs-cnrm-cm5.historical.r1i1p1.mohc-hadrem3-ga7-05.v2.3hr.clt.v20201111.json

• reference_file asset: please put this in as the first asset (unless time-consuming to do so) - as this is likely to be the most important one.
• the kerchunk_href item in properties
• datetime can be removed from properties
• member_of_recipes: what does this represent? Is it internal? Is it needed?
• the assets are not ordered alphabetically (by key) and are therefore not sorted by time - please sort them so that they appear in time order (except the reference_file asset)
• what should we include in stac_extensions - are there any defaults that we are using?
• what should live in the geometry field? Try just copying planetary computer - e.g. : https://planetarycomputer.microsoft.com/api/stac/v1/collections/nasa-nex-gddp-cmip6/items - I think it is just derived from the bbox.

[rhysrevans3]

• Yes I can do that.
• Missed that. datetime and geometry are needed for STAC even if they're null.
• member of recipes is internal (it's used for creating the collection that the items belong too)
• Ah I didn't realise you could order dictionaries I'll add that.
• I wasn't sure what extensions we were using or the STAC version I'll have a look into it.
• Geometry is allowed to be null if bbox is set but I'll see if I can set it like planetary computer does.

[agstephens]

👍