Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CF coding of variables on land use tile components #13

Open
jesusff opened this issue Sep 5, 2024 · 0 comments
Open

CF coding of variables on land use tile components #13

jesusff opened this issue Sep 5, 2024 · 0 comments
Labels
FPS-URB-RCC Issue relevant for FPS-URB-RCC

Comments

@jesusff
Copy link
Member

jesusff commented Sep 5, 2024

During the Annual Meeting in Bergen, Tomas mentioned the possibility of saving the internal values of the individual tiles of the LSM, which are averaged to produce the value of a given variable on the gridcell. In the context of urban modelling, this allows to isolate the variables of the urban part of the gridcells, e.g. to compute the UHI more accurately. This is not included in the I4C data request, but might be considered in the updates of the FPS-URB-RCC data request if models are able to write these values out.

Here I describe only how this can be coded in a CF compliant way. These variables are already considered in CMIP6. They have the suffix Lut (i.e.: by land use type). For example, this is how tasLut looks in the CMOR table and here is an example of a file coded in this way (3 MB) from ESGF.

This makes use of the second and more flexible way of applying statistics to portions of cells, as described in CF1.11, section 7.3.3. Thank you, @cofinoa, for noticing this. It seems that, with this approach, there is no need to introduce new area types into CF, but they can be user defined in a variable with the standard_name area_type which enumerates the area types where the statistic is sequentially applied along a new dimension.

This can be another option to code the variables for the different urban canopy model components (roof, wall, road, ...) discussed in #6 in a single variable (e.g. tasUrb) with an additional dimension along the different components. In this respect, note that in CMIP6 there are also variables for a single land use type, such as tasmaxCrops.

@jesusff jesusff added the FPS-URB-RCC Issue relevant for FPS-URB-RCC label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FPS-URB-RCC Issue relevant for FPS-URB-RCC
Projects
None yet
Development

No branches or pull requests

1 participant