Numerical attributes (i.e. not strings) are allowed in netCDF files and work fine in yaml files with addmeta but do not work with addmeta's templating.
With the incoming addition of geospatial bounds to the ACCESS data spec we need a solution for numbers.
Since we don't do any jinja preprocessing any templated attribute must be specified in yaml files as a string.
The best solution I've thought of so far is adding some more magic for addmeta. We could add a bogus jinja filter | number - number is not a valid jinja filter so it won't collide with any other jinja expressions. addmeta can check for this 'filter' and turn the result into a number.
Numerical attributes (i.e. not strings) are allowed in netCDF files and work fine in yaml files with addmeta but do not work with addmeta's templating.
With the incoming addition of geospatial bounds to the ACCESS data spec we need a solution for numbers.
Since we don't do any jinja preprocessing any templated attribute must be specified in yaml files as a string.
The best solution I've thought of so far is adding some more magic for addmeta. We could add a bogus jinja filter
| number-numberis not a valid jinja filter so it won't collide with any other jinja expressions. addmeta can check for this 'filter' and turn the result into a number.