Hello everyone,
I am trying to run WPS v4.5 to incorporate Local Climate Zones (LCZ) using the CGLC MODIS LCZ global dataset (100m) for a domain over São Paulo, Brazil ($3\text{ km}$ resolution). However, my output geo_em.d01.nc has a completely flat LU_INDEX where every single grid point is classified as 17 (Water).
Here are the details of my setup and what I have verified so far:
Has anyone faced this "Water World" issue specifically with the CGLC LCZ dataset? Any insights on what might be causing geogrid to fail silently and default to water would be highly appreciated.
Thank you in advance!
I am trying to run WPS v4.5 to incorporate Local Climate Zones (LCZ) using the CGLC MODIS LCZ global dataset (100m) for a domain over São Paulo, Brazil ($3\text{ km}$ resolution). However, my output geo_em.d01.nc has a completely flat LU_INDEX where every single grid point is classified as 17 (Water).
Here are the details of my setup and what I have verified so far:
- Namelist.wps configuration:
- geog_data_res = 'cglc_modis_lcz+default'
- geog_data_path = '/home/samantha/WPS_GEOG/'
- Data Structure:
- The folder /home/samantha/WPS_GEOG/cglc_modis_lcz/ exists, contains the binary tiles, and a valid index file with type=categorical, category_min=1, category_max=41, wordsize=1, etc.
- GEOGRID.TBL:
- I am using a modified GEOGRID.TBL.ARW_LCZ linked correctly in both the WPS root directory and the geogrid/ subdirectory.
- Inside the table, the LANDUSEF section contains:
rel_path = cglc_modis_lcz:cglc_modis_lcz/
interp_option = cglc_modis_lcz:nearest_neighbor
landmask_water = cglc_modis_lcz:17,21
- Execution:
- geogrid.exe runs and finishes with "Successful completion of geogrid", but the resulting landuse field is entirely water.
Has anyone faced this "Water World" issue specifically with the CGLC LCZ dataset? Any insights on what might be causing geogrid to fail silently and default to water would be highly appreciated.
Thank you in advance!