Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

different land cover classification data for mother and nested domains

Orzu1998

New member
Dear WRF Community,
I'm using WPS-4.3.1 version and 2 domains. Mother domain - 15000, nested - 5000. I chose USGS 30 arc-second classification land cover data over my domain, so in namelist.wps my geog_data_res = 'usgs_30s', 'usgs_30s'. When running ./gegorid.exe, it successfully generates two geogrid files - geo_emd01.nc and geo_emd02.nc. When trying to visualize LU_INDEX parameter using ncview command, geo_emd01.nc scale has 24 land categories, while geo_emd02.nc scale shows only 21 land categories (I attached the photos). What's the reason? Is it because in my nested domain some land classes are not present? but still, the scale should depict all 24 classes, no?

Then I checked my geogrid.log, and saw some warning messages like:
INFORM: For HGT_M, couldn't find interpolator sequence for resolution usgs_30s.
2023-04-16 17:54:39.623 --- INFORM: Using default interpolator sequence for HGT_M.
2023-04-16 17:54:39.623 --- INFORM: For HGT_M, couldn't find usgs_30s data source.
2023-04-16 17:54:39.623 --- INFORM: Using default data source for HGT_M.
2023-04-16 17:54:39.623 --- INFORM: Using usgs_30s interpolator sequence for LANDUSEF.
2023-04-16 17:54:39.623 --- INFORM: Using usgs_30s data source for LANDUSEF.
2023-04-16 17:54:39.623 --- INFORM: For SOILTEMP, couldn't find interpolator sequence for resolution usgs_30s.

There's no LU_INDEX parameter, but what does "For HGT_M, couldn't find usgs_30s data source, Using default interpolator sequence for HGT_M." mean? Is the geogrid.exe using default MODIS elevation data for the HGT_M elevation parameter?

I attached my namelist.wps, both geogrid files and geogrid.log. As for static data, I downloaded "High resolution of each mandatory field" and some optional fields like "urbfrac, lakes_depth, clayfrac, irrigation, and etc". Also attached the screenshot of my WPS_GEOG.

I would appreciate if you could answer to my questions,

Orzu
 

Attachments

  • geo_emd02_visualization.jpg
    geo_emd02_visualization.jpg
    120.5 KB · Views: 8
  • geo_emd01_visualization.jpg
    geo_emd01_visualization.jpg
    109.8 KB · Views: 8
  • geogrid.log
    43.8 KB · Views: 2
  • namelist.wps
    707 bytes · Views: 6
  • geogrid_files.zip
    1.4 MB · Views: 0
  • WPS_GEOG.jpg
    WPS_GEOG.jpg
    70.3 KB · Views: 8
Last edited:
Hi Orzu,

The geogrid output files will only show the landuse types that are found within the domain. So for your domain, the types "mixed tundra," "bare ground tundra," and "snow or ice" aren't found in your nested domain, which probably makes sense, based on its location.

Setting geog_data_res to usgs_30s only refers to the landuse type, and not the other static fields, such as HGT_M. The recommended way to set that field, when using something other than the default is, for e.g.,

Code:
geog_data_res = 'usgs_30s+default', 'usgs_30s+default'

This will not remove the 'INFORM' messages you're seeing, though. Those messages just let you know that the first (or only) landuse type you chose (usgs_30s) does not include HGT_M information, so it's going to pull from the default for HGT_M, which is actually "topo_gmted2010_30s." You can use the geogrid/GEOGRID.TBL file as a reference for which static data are default.
 
Top