Can't process SLUCM-related fields (e.g., MH_URB2D, AHE) using ./geogrid.exe

[ZHOU Wan]

Hello,
I'm working on the WRF-Urban (4.6 Version). However, when using geogrid to obtain static geographical data, the following fields are not processed. What's the wrong? And what can I do to add these urban fields into analysis? Thanks in advance for your help. And I wish your response!

Optional fields not processed by geogrid:
MH_URB2D (priority=1, resolution='', path='')
ZD_URB2D (priority=1, resolution='', path='')
Z0_URB2D (priority=1, resolution='', path='')
BUILD_AREA_FRACTION (priority=1, resolution='', path='')
LF_URB2D_S (priority=1, resolution='', path='')
AHE (priority=1, resolution='', path='')
AHE (priority=2, resolution='', path='')

 

[ZHOU Wan]

Moreover, the slucm data has been downloaded and put in the right folder. According to GEOGRID.TBL.ARW, the related descriptions are as follows:
===============================
name = Z0_URB2D
priority=1
optional=yes
dest_type=continuous
fill_missing = 0.
interp_option = y2010_urb:average_gcell(4.0)+four_pt+average_4pt
interp_option = y2050_urb:average_gcell(4.0)+four_pt+average_4pt
rel_path = y2010_urb:slucm/urban_params/2010/z_0/
rel_path = y2050_urb:slucm/urban_params/2050/z_0/
===============================
name = BUILD_AREA_FRACTION
priority=1
optional=yes
dest_type=continuous
fill_missing = 0.
interp_option = y2010_urb:average_gcell(4.0)+four_pt+average_4pt
interp_option = y2050_urb:average_gcell(4.0)+four_pt+average_4pt
rel_path = y2010_urb:slucm/urban_params/2010/lambda_p/
rel_path = y2050_urb:slucm/urban_params/2050/lambda_p/
===============================
name = LF_URB2D_S
priority=1
optional=yes
dest_type=continuous
fill_missing = 0.
interp_option = y2010_urb:average_gcell(4.0)+four_pt+average_4pt
interp_option = y2050_urb:average_gcell(4.0)+four_pt+average_4pt
rel_path = y2010_urb:slucm/urban_params/2010/lambda_f/
rel_path = y2050_urb:slucm/urban_params/2050/lambda_f/
===============================
name = AHE
priority=1
optional=yes
dest_type=continuous
fill_missing = 0.
interp_option = y2010_ahe:average_gcell(4.0)+four_pt+average_4pt
interp_option = y2050_ahe:average_gcell(4.0)+four_pt+average_4pt
rel_path = y2010_ahe:slucm/AHE_2010s/2_bytes/
rel_path = y2050_ahe:slucm/AHE_2050s/2_bytes/
z_dim_name = month_hour

 

[ZHOU Wan]

I find the possible solution by writing geog_data_res = 'y2010_urb+y2050_urb+y2010_ahe+y2050_ahe+default'. Hope it helps for others!

 

[cenlinhe]

Yes, to use those special (non-default) WPS datasets, you will need to specify the name of those datasets in the geog_data_res namelist field.
FOr some urban parameters like MH_URB2D, it is derived from NUDAPT which is only available over continental US in WPS database. So for other regions, you will see an empty variable for this parameter in geo_em file.