Skip to content

Different LU_INDEX between wrfinput and met_em files #2152

@lpilz

Description

@lpilz

Describe the bug
When using USGS landuse data augmented with LCZ information by W2W, the LU_INDEX field in the wrfinput file is different from the one in the met_em file (cf. screenshots).

I think the reason for this is the following lines of code from 2018 (before LCZ were introduced):
https://github.com/wrf-model/WRF/blame/d66e442fccc04111067e29274c9f9eaccc3cef28/dyn_em/module_initialize_real.F#L3155-L3158

To Reproduce
Steps to reproduce the behavior:

  1. Use compiler and version 'any, I use gcc+openmpi and v4.3.3'
  2. Use namelist options 'use_wudapt_lcz=1, num_land_cat=41 and surface_input_source=3 (default)'
  3. Output is 'cf. Screenshots'

Expected behavior
I would expect the LCZ urban information not to be overwritten in the LU_INDEX field of the wrfinput file and to be the same as in the met_em file.

Especially since the LU_INDEX information is used as the IVGTYP field in phys/module_sf_noahmpdrv.F and for determining urban type and morphology in phys/module_sf_urban.F. This urban type then, determined from IVGTYP is then used in phys/module_sf_bep.F to get the urban parameters.

Screenshots
wrfinput LU_INDEX field:
wrfinput LU_INDEX field
met_em LU_INDEX field:
met_em LU_INDEX field

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions