Legend:

|| `regex_extract(input, regex, group)` || This function extracts information from a string using regex; input is the string you parse, regex is the regular expression, group is the regex group you want to select || `datetime(regex_extract('${file:name}', '(.*)_(.*)_(.*)_(\\d\\d\\d\\d-\\d\\d)(.*)', 4), 'YYYY-MM')` ||

for GRIB, it is as same as netCDF to add uom for bands, except, you use the different expression to fetch this data from any metadata of GRIB file.

167

168

{{{

169

"bands": [

170

{

171

"name": "Temperature_isobaric",

172

"identifier": "Temperature_isobaric",

173

"description": "Bands description",

174

"nilReason": "Nil value represents missing values.",

175

"nilValue": 9999,

176

"uomCode": "${grib:unitsOfFirstFixedSurface}" # can be any

177

other metadata from GRIB file

178

}

179

]

180

}}}

181

182

}}}

183

184

185

=== Band, Dimension's metadata to support in encoding netCDF ===

155

186

Beside the global metadata of coverage for GDAL, netCDF, GRIB axes, you can add the metadata for each band and each defined axis in the ingredient file. Then, when you encode the output result from WCS, WCPS in netCDF, you will see the metadata is copied to the corresponding sections.