Land Data Toolkit (LDT): LDT 7.3 Users' Guide

LDT provides an environment for processing LSM data and parameters, restart files and data assimilation based inputs (e.g., for bias correction methods). LDT offers and will offer a variety of user options and inputs to processing datasets for use within LIS and even stand-alone models. LDT is being designed with not only LIS in mind but for other independent models and data processing systems as well. This intended design is facilitated by the use of common data formats, like NetCDF, which provide detailed data header information.

LDT shares similar object oriented framework designs as LIS, with a number of points of flexibility known as “plugins”. Specific implementations are added to the framework through the plugin-interfaces. LDT uses the plugin-based architecture to support the processing of different types of observational data sets, ranging from in-situ, satellite and remotely sensed and reanalysis products.

The key capabilities of LDT can be summarized as follows:

LDT is developed on Linux/Unix platforms. Its build process expects a case sensitive file system. Please make sure that you unpack and/or git clone the LDT code into a directory within a case sensitive file system. In particular, if you are using LDT within a Linux-based virtual machine hosted on a Windows or Macintosh system, do not compile/run LDT from within a shared folder. Move the LDT source code into a directory within the virtual machine.

The LDT public release 7.3 source code is available both on LISF’s web-site under the “Source” menu and on GitHub under the NASA-LIS organization at https://github.com/NASA-LIS/LISF under the “Releases” link.

After downloading the LISF tar-file:

The LDT source code is maintained in a git repository hosted on GitHub. If you wish to work with the latest development code (in the master branch), then you must use the git client to obtain the LDT source code. If you need any help regarding git or GitHub, please go to https://github.com.

Unpacking or cloning the LISF source code (according to the instructions in Section Obtaining the Source Code) will create a directory named LISF. The LDT specific source code is in LISF/ldt.

Processed documentation may be found on LISF’s web-site under the “Docs” menu.

This code has been compiled and run on Linux PC (Intel/AMD based) systems and Cray systems. These instructions expect that you are using such a system. In particular you need:

In order to build the LDT executable, the following libraries must be installed on your system:

The following libraries are not required to compile LDT. They are used to extend the functionality of LDT.

LDT running mode: specifies the running mode used in LDT. Acceptable values are:

Processed LSM parameter filename: specifies the output filename (with netcdf extension) of the LSM parameters processed in LDT to go into LIS. See a sample lis_input.d01.nc (Appendix Description of output files from LDT) file for a complete specification description.

LIS number of nests: specifies the number of nests used for the run. Values 1 or higher are acceptable. The maximum number of nests is limited by the amount of available memory on the system. The specifications for different nests are done using white spaces as the delimiter. Please see below for further explanations. Note that all nested domains should run on the same projection and same land surface model.

Number of surface model types: specifies the number of surface model types selected for the LIS simulation. Acceptable values are 1 or higher.

Surface model types: specifies the names of the surface model types. Options include (but to be expanded later):

Land surface model: specifies the land surface model to be run. Need to select the model you want to run in LIS, so the appropriate model parameters are included in the output netcdf file for LIS. Acceptable values are:

Lake model: specifies the lake model type used in a LIS run. Currently, only the FLake lake model is incorporated in LIS, and both LDT and LIS are set up for additional support of lake model installation and development. For now, the option “none” is recommended.

Routing model: specifies the river routing model used in a LIS run. Both HYMAP and HYMAP2 routing scheme parameters are supported in LDT.

Water fraction cutoff value: specifies what gridcell fraction is to be represented by water (e.g., 0.6 would be 60% covered by water pixels). This value acts as a threshold in determining which gridcell will be included as a water or land point (used also in deriving the land/water mask).

Number of met forcing sources: specifies the number of met forcing datasets to be used. Acceptable values are 0 or higher.

Met forcing sources: specifies the meteorological forcing data sources used for a LIS run.

For more information about LIS’s meteorological forcing data reader options, please see the “Land Information System (LIS) Users’ Guide” for more information. Acceptable values for the sources are:

Blending method for forcings: specifies the blending method to combine forcings if more than one forcing dataset is used. User-entry activated only when the “Metforce processing” run mode is selected. Acceptable values are:

Met spatial transform methods: specifies the type of spatial transform or interpolation scheme to apply to the forcing dataset(s) selected. Acceptable values are:

Bilinear interpolation uses 4 neighboring points to compute the interpolation weights. The conservative approach uses 25 neighboring points. This option is designed to conserve water, like for precipitation. Also, nearest neighbor can be used, which may better preserve large pixels (e.g., 1x1 deg), if needed. “Average” can also be selected if upscaling from finer-scale meteorological fields (e.g., going from 4 km to 0.25 deg).

Topographic correction method (met forcing): specifies whether to use elevation correction on select forcing fields. Acceptable values are:

Current meteorological forcing datasets supported for applying this lapse-rate adjustment to the temperature, humidity, pressure and downward longwave fields, include: NLDAS1, NLDAS2, NAM242, GDAS, PRINCETON, and ECMWF. Future forcing dataset options will include: GEOS, GLDAS, GFS, ECMWF_reanalysis, and possible others.

ECMWF and GDAS forcing types include several terrain height maps and not just one overall, either due to change in versions or gridcell size, respective.

Temporal interpolation method (met forcing): specifies the type of temporal interpolation scheme to apply to the met forcing data. Acceptable values are:

The linear temporal interpolation method computes the temporal weights based on two points. Ubernext computes weights based on three points. Currently the ubernext option is implemented only for the GSWP forcing.

Enable new zterp correction (met forcing): specifies whether to enable the new zterp correction. Acceptable values are:

Defaults to .false..

This is a scalar option, not per nest.

This new zterp correction addresses an issue that occurs at sunrise/sunset for some forcing data-sets when running at small time-steps (like 15mn). In these cases, swdown has a large unrealistic spike. This correction removes the spike. It also can affect swdown around sunrise/sunset by up 200 W/m2. Users are advised to run their own tests and review swdown to determine which setting is best for them.

For comparision against older LIS runs, set this option to .false..

Temporal downscaling method: specifies the temporal downscaling method to disaggregate a coarser forcing dataset into finer timesteps (e.g., go from daily to hourly).

User-entry activated only when the “Metforce temporal downscaling” run mode is selected. Acceptable values are:

Processed metforcing output interval: specifies the output interval for the processed meteorological forcing files. Entries are character-based names, like 6hr or 1da.

Metforcing processing interval: specifies the processing temporal interval for which meteorological forcing files are commonly and temporally aggregated (or downscaled) to when temporally downscaling a dataset.

Statistical downscaling mode: specifies the type of statistical downscaling method to be applied.

User-entry activated only when the “Statistical downscaling of met forcing” run mode is selected. Acceptable values are:

Statistical downscaling method: specifies the method for downscaling or for climatology forcing generation. Current acceptable values are:

Forcing climatology temporal frequency of data: specifies the output time interval to which the forcing climatology will be calculated on and written to.

Bayesian merging seasonal stratification type: specifies what?

Forcing variables list file: specifies the file containing the list of forcing variables to be used. (Please refer to Section “Specification of Input Forcing Variables” in the LIS Users' Guide for a complete specification description of this file.)

LDT diagnostic file: specifies the name of run time LDT diagnostic file.

Mask-parameter fill diagnostic file: specifies the name of the output diagnostic file for wherever mask-parameter points have forced agreement for a given landmask and parameter.

LDT output directory: specifies the directory name for outputs from LDT. Acceptable values are any 40 character string. The default value is set to OUTPUT.

Undefined value: specifies the undefined value. The default is set to -9999.

Add buffer to parameter grid domain: adds a set buffer around a parameter file target domain. Acceptable values are:

The default value is 0.

Buffer count in x-direction: adds a set number of pixels that buffer around a parameter file target domain, both in the x- and y-directions. Acceptable values are:

The default value is 5, and only activated if buffer option is selected.

Number of ensembles per tile: specifies the number of ensembles of tiles to be used. The value should be greater than or equal to 1.

The following options are used for subgrid tiling based on vegetation or other parameter types (e.g., soil type, elevation, etc.), and are required for generating an ensemble restart file or downscaling to a single-member restart file from an ensemble one. See the section on ensemble restart files for more information.

Maximum number of surface type tiles per grid: defines the maximum surface type tiles per grid (this can be as many as the total number of vegetation types). Note: Allowable values are greater than or equal to 1. Note that the entry here should exactly match the entry used in the lis.config file.

Minimum cutoff percentage (surface type tiles): defines the smallest percentage of a cell for which to create a tile. The percentage value is expressed as a fraction. Allowable values are greater than or equal to 0. Note that the entry here should exactly match the entry used in the lis.config file.

Maximum number of soil texture tiles per grid: defines the maximum soil texture tiles per grid (this can be as many as the total number of soil texture types). Allowable values are greater than or equal to 1. Note that the entry here should exactly match the entry used in the lis.config file.

Minimum cutoff percentage (soil texture tiles): defines the smallest percentage of a cell for which to create a tile. The percentage value is expressed as a fraction. Allowable values are greater than or equal to 0. Note that the entry here should exactly match the entry used in the lis.config file.

Maximum number of soil fraction tiles per grid: defines the maximum soil fraction tiles per grid (this can be as many as the total number of soil fraction types). Allowable values are greater than or equal to 1. Note that the entry here should exactly match the entry used in the lis.config file.

Minimum cutoff percentage (soil fraction tiles): defines the smallest percentage of a cell for which to create a tile. The percentage value is expressed as a fraction. Allowable values are greater than or equal to 0. Note that the entry here should exactly match the entry used in the lis.config file.

Maximum number of elevation bands per grid: defines the maximum elevation bands per grid (this can be as many as the total number of elevation band types). Allowable values are greater than or equal to 1. Note that the entry here should exactly match the entry used in the lis.config file.

Minimum cutoff percentage (elevation bands): defines the smallest percentage of a cell for which to create a tile. The percentage value is expressed as a fraction. Allowable values are greater than or equal to 0. Note that the entry here should exactly match the entry used in the lis.config file.

Maximum number of slope bands per grid: defines the maximum slope bands per grid (this can be as many as the total number of slope band types). Allowable values are greater than or equal to 1. Note that the entry here should exactly match the entry used in the lis.config file.

Minimum cutoff percentage (slope bands): defines the smallest percentage of a cell for which to create a tile. The percentage value is expressed as a fraction. Allowable values are greater than or equal to 0. Note that the entry here should exactly match the entry used in the lis.config file.

Maximum number of aspect bands per grid: defines the maximum aspect bands per grid (this can be as many as the total number of aspect band types). Allowable values are greater than or equal to 1. Note that the entry here should exactly match the entry used in the lis.config file.

Minimum cutoff percentage (aspect bands): defines the smallest percentage of a cell for which to create a tile. The percentage value is expressed as a fraction. Allowable values are greater than or equal to 0. Note that the entry here should exactly match the entry used in the lis.config file.

This section specifies the 2-d layout of the processors in a parallel processing environment.

This is a new feature within LDT.

The user can specify the number of processors along the east-west dimension and north-south dimension using Number of processors along x: and Number of processors along y:, respectively. Note that the layout of processors should match the total number of processors used. For example, if 8 processors are used, the layout can be specified as 1x8, 2x4, 4x2, or 8x1.

Output methodology: specifies whether to write output as a 1-D array containing only land points or as a 2-D array containing both land and water points. 1-d tile space includes the subgrid tiles and ensembles. 1-d grid space includes a vectorized, land-only grid-averaged set of values. Acceptable values are:

The default value is “2d gridspace”.

Output data format: specifies the format of the model output data. Acceptable values are:

The default value is “netcdf”.

Output naming style: specifies the style of the model output names and their organization. Acceptable values are:

The default value is “3 level hierarchy”.

This section of the config file specifies the LIS running domain (domain over which the simulation is carried out). The specification of the LIS Run domain section depends on the type of LIS domain and projection used. Section Overall driver options lists the projections that LIS supports.

Map projection of the LIS domain: specifies the output LIS domain grid to be used with LIS. Acceptable values are:

Landcover data source: specifies the land cover dataset source to be read in. Current landcover source options include:

Landcover classification: specifies the land cover classification type. Land cover or use classification types have been developed over the years by various organizations (e.g., USGS, IGBP) and research groups (e.g., satellite missions associated with groups, like UMD, BU, etc.). For more information on some of these different land classifications and their characteristics, please refer to: https://lpdaac.usgs.gov/documents/101/MCD12_User_Guide_V6.pdf and https://www.usgs.gov/media/files/global-land-cover-characteristics-data-base-readme-version2. Acceptable values are:

Landcover file: specifies the location of the vegetation classification file.

Landcover map projection: specifies the projection of the landcover map data.

Landcover spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the landcover map. Options include:

Note: “tile” is a special case for landcover, which allows for reading in landcover data already in tiled form, or creating tiles from finer resolution landcover data.

Landcover fill option: specifies the landcover classification data fill option. Options include:

Landcover fill value: indicates which landcover value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing landcover point, a value of 5 could be assigned if no nearest neighbor values exists to fill).

Landcover fill radius: specifies the radius with which to search for nearby value(s) to help fill the missing value.

This section also outlines the domain specifications of the landcover (and for now landmask) data. If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying landcover data. Note: The Landcover grid domain inputs below are really only required for the “_LIS” data source options and that do not include “_Native” in the data source entries. All native parameters do not require the below inputs for LDT. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Create or readin landmask: offers the user the option to create or read in land/water mask file information. Options include the ability to impose the mask on landcover and also the other parameter fields.

Landmask data source: specifies the land mask dataset source to be read in. If the user is interested in only using the selected landcover data source, then the user can select the same option for the landmask data source.

Other current landmask source options include:

Landmask file: specifies the location of land/water mask file. Note: If reading in the MOD44W land-water mask, make sure to enter “MOD44W” Landmask data source entry.

Landmask spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the landmask map. Options include:

Landmask map projection: specifies the projection of the landmask map data.

This section also outlines the domain specifications of the land water/mask data. The landmask map projection and extents are only needed if you specify “readin” for mask type and if the landmask data source is “MOD44W” or “_LIS”.

If the map projection of parameter data is specified to be “latlon”, the following extents and resolution configuration should be used for specifying landmask data. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Future landmask data sets will have the projection, grid extents and resolution on the data reader side and not needed to be specified in the ldt.config file, depending on the data source.

Lakecover data source: specifies the data source for lake depth and/or fraction for lake models, like FLake.

Lake depth map: specifies the location of the lake depth file (in meters), which is also used to derive the lake gridcell fraction for lake models, like FLake.

Lake depth QC map: is a file that specifies the location of the QC flag for the origin of the lake depth values, which is an optional field specified. This file can be used by lake models, like FLake, if needed.

Lake params spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the lake depth maps. Options include:

Lake wind fetch value: is the user-specified input value for lake-based wind-fetch (in meters) in association with lake models like FLake. This value is constant (or global) for now until 2-D fields become available.

Lake bottom sediments depth value: is the user-specified input value for the thermally active layer depth of bottom sediments (m) in association with lake models like FLake. This value is constant (or global) for now until 2-D fields become available.

Lake bottom sediments temperature value: is the user-specified input value for the outer edge temperature (K) of the thermally active layer of the bottom sediments in association with lake models like FLake. This value is constant (or global) for now until 2-D fields become available.

Inland waterbody data source: specifies the inland water body (e.g., lake types) dataset source to be read in. Current option is only:

Inland waterbody type map: specifies the inland water body map file and path.

Inland waterbody spatial transform: specifies the inland waterbody spatial transform. Current options are:

Regional mask data source: specifies a regional land mask dataset source to be read in. Should either match grid domain or be smaller to the LIS run domain.

Regional mask file: specifies the location of a regional mask file. This file can be either an index-based state, country, basin, catchment, etc. map used to mask further beyond the main water/land mask.

Regional mask map projection: specifies the projection of the regional mask albedo map data.

Clip landmask with regional mask: A logical-based option that uses the regional mask to “clip” the original landmask that is read-in or created. .true. turns on the “clipping” option.

Regional mask spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to a regional mask map. Options include:

This section also outlines the domain specifications of the regional-based land mask data. If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying regional mask data.

See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Rootdepth data source: specifies the source of the vegetation root depth dataset. Options include:

Root depth file: specifies the path and name of the root depth file. Options include:

Incorporate crop information: specifies the logical flag with which to turn on the inclusion of crop information and also to allow the user to enter additional options that can ensure crop, landcover, and irrigation features are agreement.

Crop type data source: specifies the crop type map dataset source to be read in. Current landcover source options include:

Crop classification: specifies the crop classification system used to determine the range of crops indexed for a particular crop library source.

Crop library directory: specifies the source of the crop library and inventory of crop classes, related to the Crop classification: entry (see above).

Assign crop value type: specifies the type of crop presence, such as a “single” crop or “multiple” crops given within a gridcell. Currently, only the “single” option is supported.

Assign single crop value: specifies whether to assign a single crop value from an actual crop library inventory, such as FAOSTAT01, which is also known as the CROPMAP classification used in Ozdogan et al. (2010). By turning on this option (.true.), you can they specify what type of crop you want to assign, like “maize” to the user-specified option, Default crop type:. If “maize” was entered, then wherever the landcover map indicated a generic “cropland”, the crop type field would be given a dominant “maize” type.

Default crop type: specifies the default crop type that the user can enter and can be used in conjunction with assigning a single crop type value (see above).

Crop type file: specifies the location of a crop type file. This file contains different crop types that can be used in in conjunction with a selected land cover map (as above).

Crop map spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to a crop type map. Options include:

Irrigation type data source: specifies the irrigation method type dataset source to be read in. Current source options include:

Irrigation type map: specifies the location of an irrigation type file. This file contains different irrigation categories (types) that can be used in conjunction with an irrigation fraction map.

A special land-use/irrigation-related map, known as the Global Rain-Fed, Irrigated, and Paddy Croplands (GRIPC) Dataset (Salmon, 2013), has also been implemented as an option to LDT. Currently, no models in LIS utilize this map but opportunities exist for the user community to utilize for their landcover and irrigation modeling needs.

Irrigation type spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to irrigation-related maps. Options include:

Irrigation fraction data source: specifies the irrigation method type dataset source to be read in. Current source options include:

Irrigation fraction map: specifies the location of an irrigation fraction map file. This file contains irrigation fraction (gridcell-based) that can be used in conjunction with an irrigation type map.

Irrigation fraction spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to irrigation-related maps. Options include:

Irrigation fraction map projection: indicates the grid projection defines an input irrigation maps. Options include:

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying irrigation data, if the data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Soils maps

Sand fraction map: specifies the sand fraction map file.

Clay fraction map: specifies the clay fraction map file.

Silt fraction map: specifies the silt map file.

Gravel fraction map: specifies the gravel map file.

Porosity data source: specifies the soil porosity dataset source to be read in. Current source options include:

Porosity map: specifies porosity map file.

Soildepth data source: specifies the soildepth dataset source to be read in. Current source option is:

Soil depth map: specifies the soil depth map file.

Saturated matric potential map: specifies saturated matric potential map file.

Saturated hydraulic conductivity map: specifies saturated hydraulic conductivity map file.

b parameter map: specifies b parameter map file.

Quartz map: specifies quartz data map file.

Soil fraction data source: specifies the source of the soil fraction dataset. Options include:

Soil fraction number of bands: specifies the number of soil fraction bins to turn on soil fraction tiling capability.

Soils spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the soils maps. Options include:

Soils map projection: specifies the projection of the soils map data.

Soils fill option: specifies the general soil data (e.g., fractions) fill option. Options include:

By selecting the soils fill option, neighbor, this activates the need to enter values for the Soils fill radius and fill value, as shown below. If a porosity map is read in and the soils fill option is set to neighbor, the user can then enter a fill value for porosity to ensure mask-parameter agreement.

Soils fill radius: specifies the radius with which to search for nearby value(s) to help fill the missing value.

Soils fill value: indicates which soils value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing soils value, a value of 0.33 could be assigned if no nearest neighbor values exists to fill).

Porosity fill value: indicates which porosity value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing porosity value, a value of 0.30 could be assigned if no nearest neighbor values exists to fill).

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying soils data, if the data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Hydrologic soil group source: specifies the hydrological soil group (HSG) data source. Options include:

Hydrologic soil group map: specifies the path and filename for the HSG input file.

Bulk density data source: specifies the source of the soil bulk density data type. Currently no options supported at this time.

Water capacity data source: specifies the source of the water holding capacity data type. Currently no options supported at this time.

Rock volume data source: specifies the source of the amount of rock volume data type. Currently no options supported at this time.

Rock frag class data source: specifies the source of the rock fragment classification type. Currently no options supported at this time.

Permeability data source: specifies the source of the permeability data type. Currently no options supported at this time.

Soil texture data source: specifies the soil texture dataset source to be read in. Current soil texture source options include:

Soil texture map: specifies the soil texture file.

Soil texture spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the soil texture map. Options include:

Soil texture map projection: specifies the projection of the soil texture map data.

Soil texture fill option: specifies the soil texture data fill option. Options include:

Soil texture fill value: indicates which soil texture value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing soil texture value, a value of 6 could be assigned if no nearest neighbor values exists to fill).

Soil texture fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying soil texture data, if the data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Soil color map projection: specifies the projection of the soil color map data.

Soil color data source: specifies the soil color data source. Current option is: FAO

Soil color map: specifies the soil color map file. This soil map is mainly used by the Community Land Model (version 2).

Soil color spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the soil color map. Options include:

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying soil color data, data source option “FAO” or has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Elevation data source: specifies the elevation dataset source to be read in.

Slope data source: specifies the slope dataset source to be read in.

Aspect data source: specifies the aspect dataset source to be read in.

Curvature data source: specifies the curvature dataset source to be read in.

Current options include:

Elevation number of bands: specifies the number of elevation bands or bins to turn on elevation tiling capability.

Slope number of bands: specifies the number of slope bands or bins to turn on slope tiling capability.

Aspect number of bands: specifies the number of aspect bands or bins to turn on aspect tiling capability.

Curvature number of bands: specifies the number of curvature bands or bins to turn on curvature tiling capability.

Topography maps

Elevation map: specifies the elevation of the LIS grid. If the elevation map type selected is SRTM_Native, then the elevation file entry is actually just the directory path, which contains the tiled SRTM elevation files.

Slope map: specifies the slope of the LIS grid. If the slope map type selected is SRTM_Native, then the file entry is actually just the directory path, which contains the tiled SRTM elevation files.

Aspect map: specifies the aspect of the LIS grid. If the aspect map type selected is SRTM_Native, then the file entry is actually just the directory path, which contains the tiled SRTM elevation files.

Curvature map: specifies the curvature of the LIS grid.

Elevation fill option: specifies the elevation data fill option. Options include:

Elevation fill value: indicates which elevation value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing elevation value, a value of 100(m) could be assigned if no nearest neighbor values exists to fill).

Elevation fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

Slope fill option: specifies the slope data fill option. Options include:

Slope fill value: indicates which slope value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing slope value, an value of 0.1 could be assigned if no nearest neighbor values exists to fill).

Slope fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

Aspect fill option: specifies the aspect data fill option. Options include:

Aspect fill value: indicates which aspect value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing aspect value, an value of 2.0 could be assigned if no nearest neighbor values exists to fill).

Aspect fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

Topography map projection: specifies the projection of the topography map data.

Topography spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the topographic map. Options include:

This section should also specify the domain specifications of the topography data. If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying topography data, especially if the data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Albedo maps

Albedo data source: specifies the albedo climatology map dataset source to be read in. Current source options include:

Albedo map: specifies the path of the climatology based albedo files. The climatology albedo data files have the following naming convention: <directory>/<file header>.<tag>.1gd4r The tag should be either sum, win, spr, or aut depending on the season, or the tag should represent the month (such as jan, feb, mar, etc.). The file header can be anything (such as alb1KM). The albedo field is used by Noah LSM versions.

Albedo map projection: specifies the projection of the albedo map data.

Albedo climatology interval: specifies the frequency of the albedo climatology in months.

Albedo spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the albedo maps. Options include:

If selecting the Catchment LSM (F2.5 version), the model requires the near infrared (NIR) and visible (VIS) albedo factor files, as shown below for example. This particular albedo parameter set is currently only available for the Catchment LSM Fortuna 2.5 (CLSMF2.5).

Albedo NIR factor file: specifies the NIR albedo factor file.

Albedo VIS factor file: specifies the VIS albedo factor file.

These albedo parameter subroutines can be found in the albedo directory.

Albedo fill option: specifies the albedo data fill option. Options include:

Albedo fill value: indicates which albedo value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing albedo value, a value of 0.12 could be assigned if no nearest neighbor values exists to fill).

Albedo fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying albedo data where the albedo data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Max snow albedo data source: specifies the maximum snow albedo dataset source to be read in. Current source options include:

Max snow albedo map: specifies the map file containing data with the static upper bound of the snow albedo. The albedo field is used by all Noah LSM and RDHM-SAC LSM versions.

Max snow albedo map projection: specifies the projection of the max snow albedo map data.

Max snow albedo spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the maximum snow albedo map. Options include:

Max snow albedo fill option: specifies the max snow albedo data fill option. Options include:

Max snow albedo fill value: indicates which max snow albedo value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing snow albedo value, an value of 0.42 could be assigned if no nearest neighbor values exists to fill).

Max snow albedo fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying max snow albedo data, where the max snow albedo albedo data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Greenness fraction maps

Greenness vegetation fraction is considered the horizontal greenness fraction represented for a model gridcell. This parameter is used in the LSMs: all Noah LSMs, RDHM-SAC, Catchment F2.5.

Greenness data source: specifies the greenness fraction climatology dataset source to be read in. Current source options include:

Greenness map projection: specifies the projection of the greenness map data.

Greenness fraction map: specifies the source of the climatology based gfrac files. The climatology greenness data files have the following naming convention: <directory>/<file header>.<tag>.1gd4r. The tag should represent the month (such as jan, feb, mar, etc.). The file header can be anything (such as green1KM).

Greenness climatology interval: specifies the frequency of the greenness climatology in months. Only current option is: “monthly”.

Calculate min-max greenness fraction: specifies a logical flag option to offer the user the ability to calculate minimum and maximum greenness fraction values from a given climatology (e.g., monthly). Acceptable values are:

Greenness maximum map: specifies the file of the climatological maximum greenness data from the monthly greenness files.

Greenness minimum map: specifies the file of the climatological minimum greenness data from the monthly greenness files.

Greenness spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the greenness maps. Options include:

Greenness fill option: specifies the greenness fraction data fill option. Options include:

Greenness fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

Greenness fill value: indicates which greenness fraction value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing greenness value, a value of 0.2 could be assigned if exists to fill).

Greenness maximum fill value: indicates which maximum greenness fraction value to be used if an arbitrary value fill is needed.

Greenness minimum fill value: indicates which minimum greenness fraction value to be used if an arbitrary value fill is needed.

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying greenness data source, if the option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

LAI/SAI maps Leaf area index and stem area index maps are used to describe the vertical representation of leafy vegetation and the woody-branch areas within a given gridecell (respectively). LAI/SAI are used in the Community Land Model (CLM), Mosaic LSM, and Catchment LSM, version F2.5.

LAI/SAI map projection: specifies the projection of the LAI/SAI map data.

LAI data source: specifies the leaf area index (LAI) climatology dataset source to be read in. Current source options include:

SAI data source: specifies the stem area index (SAI) climatology dataset source to be read in. Current source options include:

LAI map: specifies the source of the climatology based LAI files. The climatology data files have the following naming convention: <directory>/<file header>.<tag>.1gd4r. The tag should be represent the month (such as jan, feb, mar, etc.). The file header can be anything (such as avhrr_lai_1KM).

SAI map: specifies the source of the climatology based SAI files. The climatology data files have the following naming convention: <directory>/<file header>.<tag>.1gd4r. The tag should be represent the month (such as jan, feb, mar, etc.). The file header can be anything (such as avhrr_sai_1KM).

LAI/SAI climatology interval: specifies the frequency of the LAI or SAI climatology in months. Current option is: “monthly”.

Calculate min-max LAI: specifies a logical flag option to offer the user the ability to calculate minimum and maximum LAI values from a given climatology (e.g., monthly). Acceptable values are:

LAI maximum map: specifies the file of the climatological maximum LAI data from the monthly LAI files.

LAI minimum map: specifies the file of the climatological minimum LAI data from the monthly LAI files.

LAI/SAI spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the LAI and SAI maps. Only “none” option works for the “AVHRR” or “CLSMF2.5” LAI data source entries. Other spatial options for the include:

LAI/SAI fill option: specifies the LAI/SAI data fill option. Options include:

LAI/SAI fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

LAI fill value: indicates which LAI value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing LAI value, a value of 1 could be assigned if exists to fill).

LAI maximum fill value: indicates which maximum LAI value to be used if an arbitrary value fill is needed.

LAI minimum fill value: indicates which minimum LAI value to be used if an arbitrary value fill is needed.

SAI fill value: indicates which SAI value to be used if an arbitrary value fill is needed.

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying LAI/SAI data, if the data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Slope type data source: specifies the slope type index dataset source to be read in. Current source options include:

Slope type map: specifies the slope type index as used in all Noah LSM versions.

Slope type map projection: specifies the projection of the slope type map data.

Slope type spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the soils maps. Options include:

Slope type fill option: specifies the slope type data fill option. Options include:

Slope type fill value: indicates which slope type value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing slope type value, an index value of 1 could be assigned if no nearest neighbor values exists to fill).

Slope type fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying slope type data, if the data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Bottom temperature data source: specifies the bottom temperature dataset source to be read in. Current source options include:

Bottom temperature map: specifies the bottom boundary temperature data. This parameter is currently required by the Noah LSM versions and the recently added RDHM-SAC/Snow-17 models.

Bottom temperature map projection: specifies the projection of the bottom temperature map data.

Bottom temperature spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the bottom temperature map. Options include:

Bottom temperature fill option: specifies the bottom boundary temperature data fill option. Options include:

Bottom temperature fill value: indicates which bottom soil temperature value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing bottom temperature field, a value of 287 K could be assigned if no nearest neighbor values exists to fill).

Bottom temperature fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

Bottom temperature topographic downscaling: specifies the option with which to adjust bottom temperature field due to topographic impacts.

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying bottom temperature parameter data, if the data source option has a “_LIS” in the name. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Noah-MP PBL Height Value: specifies the option which to set the planetary boundary layer height (PBLH) value for the Noah-MP model.

If selecting the Community Land Model (4.5 version), the following config entires are also required.

CLM45 parameter mode: specifies whether to “readin” the CLM-4.5 parameters from pre-processed files. Currently, only the “readin” option is available.

CLM45 domain file: specifies the CLM-4.5 domain file. The domain file is used to define the grid and the landmask.

CLM45 surface file: specifies the CLM-4.5 surface data parameter file.

CLM45 param spatial transform: indicates which spatial transform type is to be applied to the CLM-4.5 surface file. Currently, only “none” is supported, as it is assumed that the domain and surface files are on the same grid as the desired LDT output domain.

CLM45 param map projection: indicates the projection of the CLM-4.5 domain and surface files.

CLM45 lower left lat: specifies the lower left latitude of the CLM-4.5 domain and surface files.

CLM45 lower left lon: specifies the lower left longitude of the CLM-4.5 domain and surface files.

CLM45 upper right lat: specifies the upper right latitude of the CLM-4.5 domain and surface files.

CLM45 upper right lon: specifies the upper right longitude of the CLM-4.5 domain and surface files.

CLM45 resolution (dx): specifies the grid spacing in degrees in the x-direction (longitudinal) of the CLM-4.5 domain and surface files.

CLM45 resolution (dy): specifies the grid spacing in degrees in the y-direction (latitudinal) of the CLM-4.5 domain and surface files.

Potential Evapotranspiration (PET) maps

PET directory: specifies the source of the monthly climatology based PET files. The climatology data files have the following naming convention: <directory>/<file header>.<tag>.1gd4r. The tag should be represent the month (such as JAN, FEB, MAR, etc.). The file header can be anything (such as avhrr_pet_1KM). Currently, this parameter is used only with the RDHM-SAC model.

PET map projection: specifies the projection of the PET map data.

PET adjustment factor directory: specifies the source of the m monthly climatology-based PET adjustment factor files. The climatology data files have the following naming convention: <directory>/<file header>.<tag>.1gd4r. The tag should be represent the month (such as JAN, FEB, MAR, etc.). The file header can be anything (such as avhrr_petadj_1KM).

PET climatology interval: specifies the frequency of the PET climatology in months. Current option is: “monthly”.

PET spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to the PET maps. Options include:

PET fill option: specifies the PET climatology data fill option. Options include:

PET fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

PET fill value: indicates which PET value to be used if an arbitrary value fill is needed. (For example, when the landmask indicates a land point but no existing PET value, a value of 1 could be assigned if exists to fill. 10 pt

If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying PET data. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

CLSMF25 map projection: specifies the projection of the CLSMF25 map data.

CLSMF25 tile coord file: specifies the location of a CLSM F2.5 coordinate file. This file contains catchment tile coordinate information that can be used in Catchment LSM (CLSM) Fortuna 2.5 version model run.

CLSMF25 soil param file: specifies the location of a CLSM F2.5 soils file. This file contains catchment soil parameter information that can be used in Catchment LSM (CLSM) Fortuna 2.5 version model run.

CLSMF25 topo files: specifies the locations of a CLSM F2.5 topo parameter files. These files contain catchment topographic parameter information that can be used in a Catchment LSM (CLSM) Fortuna 2.5 version model run.

CLSMF25 topo ar file: specifies the table file containing topographic shape parameters for the CLSM F2.5 model.

CLSMF25 topo bf file: specifies the table file containing topographic baseflow paramters for the CLSM F2.5 model.

CLSMF25 topo ts file: specifies the table file containing water transfer timescale parameters for the CLSM F2.5 model.

CLSMF25 surf layer ts file: specifies the location of a CLSM F2.5 tau parameter file. This file contain catchment surface layer timescale (ts), tau, parameter information that can be used in Catchment LSM (CLSM) Fortuna 2.5 version model runs.

CLSMF25 top soil layer depth: specifies the top soil layer depth. This parameter value specifies the depth of the top soil layer depth (unit: meters) and is needed in processing other parameters for a Catchment LSM (CLSM) Fortuna 2.5 version model run.

CLSMF25 spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to CLSM F2.5 parameters. Options include (only “none” works at this time):

This section also outlines the domain specifications of the Catchment LSM Fortuna 2.5 data. If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying CLSM data. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

RDHM356 constants table: specifies the location of the constants table required by the Research Distributed Hydrologic Model (RDHM) version 3.5.6 models, SAC-HTET and SNOW-17. This table file contains constant values for any listed SAC-HTET or SNOW-17 parameter types. If a constant value is >= 0., then the constant value is assigned for all gridcells for a parameter entry. If the value is negative, a 2-D gridded a priori map is read in. Also, the negative constant value can be used as a scaling factor of the 2-D grid by taking its absolute value and multiplying the entire field by it, if the value is other than -1.

RDHM356 universal undefined value: specifies an universal undefined value that can be used by either the SAC-HTET or SNOW-17 models for run-time purposes.

Create or readin soil parameters: specifies how the soil parameter files are either generated or brought in to the SAC-HTET model. Options include:

SACHTET soil parameter method: specifies the method that can generate the SAC soil parameters. Options include (for now):

SACHTET Cosby soil parameter table: specifies the path of the Cosby soil parameter table needed for the SAC-HTET soil parameters, especially for the generation of the parameters.

SACHTET parameter files: specifies the locations of SACHTET 3.5.6 parameter files. These files contain soil-based and other model parameter information that can be used in SAC-HTET model runs. Most parameter files will come in the HRAP domain and XMRG-binary format found commonly in NOAA NWS/OHD/RFC applications. For the soil parameters, LZ indicates “lower zone” and UZ refers to “upper zone”.

SACHTET soiltype parameter table: specifies the dominant soiltype parameter table file.

SACHTET vegetation parameter table: specifies the vegetation parameter table file.

SACHTET parameter spatial transform: specifies generally the SAC-HTET grid spatial transform. Current option is “none”, and future options will be supported.

SACHTET parameter fill option: specifies generally the SAC-HTET parameter fill option. This option is not currently supported but can be in the future.

SACHTET parameter fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

SACHTET parameter fill value: indicates which SACHTET parameter value to be used if an arbitrary value fill is needed.

SACHTET map projection: specifies the general SAC-HTET parameter grid projection. Currently, “hrap” is supported and soon other projections, like “latlon” will be.

SACHTET LZFPM map: specifies the lower zone primary free water (slow) maximum storage [mm]

SACHTET LZFSM map: specifies the lower zone supplemental free water (fast) maximum storage [mm]

SACHTET LZPK map: specifies the lower zone primary free water depletion rate [day\(^{-1}\)]

SACHTET LZSK map: specifies the lower zone supplemental free water depletion rate [day \(^{-1}\)]

SACHTET LZTWM map: specifies the lower zone tension water maximum storage [mm]

SACHTET UZFWM map: specifies the upper zone free water maximum storage [mm]

SACHTET UZTWM map: specifies the upper zone tension water maximum storage [mm]

SACHTET UZK map: specifies the upper zone free water latent depletion rate [day \(^{-1}\)]

SACHTET PFREE map: specifies the fraction percolation from upper to lower free water storage [day \(^{-1}\)]

SACHTET REXP map: specifies the exponent of the percolation equation (percolation parameter) [-]

SACHTET ZPERC map: specifies the maximum percolation rate [-]

SACHTET EFC map: specifies the fraction of forest cover [-]

SACHTET PCTIM map: specifies the impervious fraction of the watershad area [-]

SACHTET ADIMP map: specifies the additional impervious area [-]

SACHTET SIDE map: specifies the ratio of deep recharge to channel base flow [-]

SACHTET RIVA map: specifies the riparian vegetation area [-]

SACHTET RSERV map: specifies the fraction of lower zone free water not transferable to tension water [-]

SACHTET TBOT map: specifies the bottom boundary soil temperature [C]

SACHTET STXT map: specifies the SAC-HTET domain soil texture map file.

SACHTET CKSL map: specifies the ratio of frozen to non-frozen surface (increase in frozen ground contact, usually = 8 s/m) [s/m]

SACHTET RSMAX map: specifies the maximum residual porosity (usually = 0.58) [-]

SACHTET ZBOT map: specifies the lower boundary depth (negative value, usually = -2.5 m) [m]

SACHTET offset time map: specifies the path to the time offset map.

SACHTET soil albedo map: specifies the soil albed map.

SNOW17 parameter files: specifies the locations of SNOW-17 parameter files. These files contain snow and soil-based parameter information that can be used in the SNOW-17 model run.

SNOW17 ADC directory: specifies the location of the multiband Snow-17 curve coordinates.

SNOW17 ADC number of points: specifies the number of areal depletion curve (ADC) points along the curve defining snow depletion rates.

SNOW17 PGM map: specifies the ground melt (in mm) input map.

SNOW17 parameter spatial transform: specifies the general grid spatial transform option for SNOW-17. Only current option for now is “none”.

SNOW17 parameter fill option: specifies the general SNOW-17 parameter fill option. This option is not currently supported but can be in the future.

SNOW17 parameter fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

SNOW17 parameter fill value: indicates which SNOW17 parameter value to be used if an arbitrary value fill is needed.

SNOW17 map projection: specfies the general SNOW-17 parameter map projection. Currently only “hrap” is supported. Others like, “latlon”, will be supported in the future.

SNOW17 MFMAX map: specifies the maximum melt factor [mm/(6hrC)]

SNOW17 MFMIN map: specifies the minimum melt factor [mm/(6hrC)]

SNOW17 UADJ map: specifies the the average wind function during rain-on-snow periods [mm/mb]

SNOW17 ALAT map: specifies the latitude [-]

SNOW17 ELEV map: specifies the elevation [m]

SNOW17 SCF map: specifies the snow fall correction factor [-]

SNOW17 NMF map: specifies the maximum negative melt factor [mm/(6hrC)]

SNOW17 SI map: specifies the areal water-equivalent above which 100 percent areal snow cover [mm]

SNOW17 MBASE map: specifies the base temperature for non-rain melt factor [C]

SNOW17 PXTEMP map: specifies the temperature which spereates rain from snow [C]

SNOW17 PLWHC map: specifies the maximum amount of liquid-water held against gravity drainage [-]

SNOW17 TIPM map: specifies the antecedent snow temperature index parameter [-]

SNOW17 LAEC map: specifies the snow-rain split temperature [C]

SiB2 static parameter directory: specifies the location of Simple Biospheric v2 (SiB2) Model parameter files. These files contain vegetation- and soil-based parameter information that can be used in the SiB2 model run.

SiB2 parameter spatial transform: specifies the general grid spatial transform option for SiB2. Only current option for now is “none”.

SiB2 map projection: specfies the general SiB2 parameter map projection. What projections are available?

SiB2 parameter fill option: specifies the general SiB2 parameter fill option.

SiB2 parameter fill radius: specifies the radius with which to search for nearby value(s) to help fill in the missing value.

SiB2 parameter fill value: indicates which SiB2 parameter value to be used if an arbitrary value fill is needed.

Climatology parameter maps

PPT climatology data source: specifies the monthly precipitation (PPT) climatology fields. Current source options include:

PPT climatology maps: specifies the source of the climatology based precipitation files. The climatology precipitation data files can have the following naming conventions, depending on the data source:

PRISM: <directory>/<file header>.<tag>.txt

WORLDCLIM: <directory>/<file header>.<tag>.1gd4r

PPT climatology interval: specifies the frequency of the precipitation climatology in months. Current option is: “monthly”

TMIN climatology maps: specifies the source of the climatology based minimum temperature files.

TMAX climatology maps: specifies the source of the climatology based maximum temperature files.

Climate params spatial transform: indicates which spatial transform (i.e., upscale or downscale) type is to be applied to climate parameters. Only “average” spatial transform works currently for the “WORLDCLIM” climatology files. Options include:

This section also outlines the domain specifications of climatology-based parameters, like higher scaled monthly precipitation or min/max temperatures. If the map projection of parameter data is specified to be lat/lon, the following configuration should be used for specifying climatology data. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

Input restart file directory: specifies the LIS output directory containing the restart files. It should be the same path as listed in “Output directory:” in the lis.config file used to generate the restart files.

Input restart file naming style: specifies the style of the LIS model and restart output names and their organization. Acceptable values are:

Input restart file output interval: specifies the output interval of the restart files from the LIS output.

Input restart model timestep used: specifies the timestep of the LSM or Routing model from the LIS output used to generate the restart files.

Input restart file format: specifies the file format of the LIS restart files. Can be “netcdf” or “binary”. If config entry is not present, LDT defaults to “netcdf”. Note that the “binary” option is only supported for processing restart files from the VIC.4.1.2 LSM.

Output restart file generation mode: specifies the method of generation of the LDT output restart preprocessing files. The only current option is “climatological average”.

Output restart file averaging interval type: specified the averaging interval of the LDT output restart preprocessing files. The only current option is “monthly”.

LIS restart source: specifices the land surface model restart file. Acceptable values are:

Input restart filename: specifies the name of the input restart file.

Output restart filename: specifies the name of the output restart file.

LIS restart source: specifies the surface model restart file source. Options are:

Ensemble restart generation mode: specifies the mode of ensemble restart generation. Options are:

Input restart filename: specifies the name of the input restart file.

Output restart filename: specifies the name of the output restart file.

Number of ensembles per tile (input restart): specifies the number of ensemble members used in the input restart file.

Number of ensembles per tile (output restart): specifies the number of ensemble members to be used in the output restart file.

The section describes some of the LDT-based NUWRF real input processing options.

LIS history file for land state initialization: specifies the file name of the LIS history file to use to initialize the land state.

Processed NUWRF file for input to real: specifies the file name of the generated file that is then used as input to the real.exe program in NUWRF.

The start time is specified in the following format:

The end time is specified in the following format:

LIS output timestep: specifies the LIS output time-step.

DA observation source: specifies the source of the observation data on which preprocessing is performed. Options are:

DA preprocessing method: specifies which preprocessing method should be used. Acceptable values are:

Name of the preprocessed DA file: specifies the name of the preprocessed DA file from LDT.

Number of bins to use in the CDF: specifies the number of bins to use while computing the CDF.

Temporal resolution of CDFs: specifies whether to generate lumped (considering all years and all seasons) CDFs or to stratify CDFs for each calendar month. Acceptable values are:

Enable spatial sampling for CDF calculations: Normally CDFs are calculated (for a given grid cell) by using the data values available at that grid point only. If this option is enabled, then values around a specified radius will be used in the CDF calculations, effectively improving the sampling density at the risk of reduced geographic specificity.

Spatial sampling window radius for CDF calculations: specifies the radius with which to search for nearby value(s) in the CDF calculations.

Group CDFs by external data: specifies whether to group CDFs for each pixel by an externally specified categorical map; for example, by landcover. Acceptable values are:

CDF grouping attributes file: specifies the name of an ASCII file that specifies the attributes of the CDF grouping, if enabled. A sample file is shown below. The first line is a description. The second line is the name of the file containing the external data for grouping. The third line is a descrition. The fourth line is the minimum value of the categorical data, followed by the maximum value of the categorical data, followed by the number of bins of the categorical data.

#category file
landcover.1gd4r
#min max nbins
1 19 18

Temporal averaging interval: specifies temporal averaging interval to be used while computing the CDF.

Apply external mask: specifies if an external mask (time varying) is to be applied while computing the CDF.

External mask directory: specifies the location of the external mask.

Observation count threshold: specifies the minimum number of observations to be used for generating valid CDF data.

LIS soil moisture output format: specifies the output format of the LIS model output. (binary/netcdf/grib1)

LIS soil moisture output methodology: specifies the output methodology used in the LIS model output (1d tilespace/1d gridspace/2d gridspace).

LIS soil moisture output naming style: specifies the output naming style used in the LIS model output (3 level hierarchy/4 level hierarchy, etc.).

LIS soil moisture output nest index: specifies the index of the nest used in the LIS model output.

LIS soil moisture output directory: specifies the location of the LIS model output.

LIS soil moisture output timestep: specifies the output timestep of the LIS soil moisture.

LIS soil moisture output map projection: specifies the map projection used in the LIS model output.

For Lat/Lon projections:

LIS soil moisture domain lower left lat: specifies the lower left latitude of the LIS model output.

LIS soil moisture domain lower left lon: specifies the lower left longitude of the LIS model output.

LIS soil moisture domain upper right lat: specifies the upper right latitude of the LIS model output.

LIS soil moisture domain upper right lon: specifies the upper right longitude of the LIS model output.

LIS soil moisture domain resolution (dx): specifies the resolution (in degrees) along the latitude of the LIS model output.

LIS soil moisture domain resolution (dy): specifies the resolution (in degrees) along the longitude of the LIS model output.

For Lambert and polar projections:

LIS soil moisture domain lower left lat: specifies the lower left latitude of the LIS model output

LIS soil moisture domain lower left lon: specifies the lower left longitude of the LIS model output

LIS soil moisture domain true lat1: specifies the true lat1 of the LIS model output

LIS soil moisture domain true lat2: specifies the true lat2 of the LIS model output

LIS soil moisture domain standard lon: specifies the standard longitude of the LIS model output

LIS soil moisture domain resolution: specifies the resolution of the LIS model output

LIS soil moisture domain x-dimension size: specifies the x-dimension size of the LIS model output

LIS soil moisture domain y-dimension size: specifies the y-dimension size of the LIS model output

For “WMO convention” style output

LIS soil moisture security class: specifies the security classification for the LIS model output file, used only for WMO-convention output.

LIS soil moisture distribution class: specifies the distribution classification for the LIS model output file, used only for WMO-convention output.

LIS soil moisture data category: specifies the data category for the LIS model output file, used only for WMO-convention output.

LIS soil moisture area of data: specifies the area of data for the LIS model output file, used only for WMO-convention output.

LIS soil moisture write interval: specifies the write interval for the LIS model output file, used only for WMO-convention output.

Synthetic soil moisture observation directory: specifies the location of the data directory containing the synthetic soil moisture data.

Synthetic soil moisture observation timestep: specifies the timestep of the synthetic soil moisture observations.

AMSR-E(LPRM) soil moisture observation directory: specifies the location of the data directory containing the LPRM AMSR-E data.

AMSR-E(LPRM) use raw data: specifies if raw data (instead of the retrievals CDF-matched to the GLDAS Noah climatology).

NASA AMSRE soil moisture observation directory: specifies the location of the data directory containing the NASA AMSR-E data.

ESA CCI soil moisture observation directory: specifies the location of the data directory containing the ESA CCI soil moisture data.

ESA CCI soil moisture version of data: specifies the version of the ESA CCI soil moisture dataset.

GCOMW AMSR2 L3 soil moisture observation directory: specifies the location of the data directory containing the GCOMW AMSR v2 L3 soil moisture data.

WindSat soil moisture observation directory: specifies the location of the data directory containing the WindSat soil moisture data.

Aquarius L2 soil moisture observation directory: specifies the location of the data directory containing the Aquarius soil moisture data.

SMOS L2 soil moisture observation directory: specifies the location of the data directory containing the SMOS soil moisture data.

SMOPS soil moisture observation directory: specifies the location of the data directory containing the real time SMOPS soil moisture data.

SMOPS soil moisture use ASCAT data: specifies if the ASCAT layer of SMOPS is to be used.

SMOPS soil moisture use SMOS data: specifies if the SMOS layer of SMOPS is to be used.

SMOPS soil moisture use AMSR2 data: specifies if the AMSR2 layer of SMOPS is to be used.

SMOPS soil moisture use SMAP data: specifies if the SMAP layer of SMOPS is to be used.

SMOPS soil moisture version: specifies the version of the SMOPS soil moisture datasets. Defaults to “date-based”. Acceptable values are:

There are three versions of the SMOPS datasets. According to the use by the 557th Weather Wing:

Also, NESDIS has regenerated SMOPS version 3.0 datasets starting from 2012-08-01.

The value “date-based” will use the dates 2016-10-31 and 2017-08-24 to determine the version of the SMOPS datasets.

The value “NESDIS V3.0 REGEN” will use the date 2012-08-01 to determine the version of the SMOPS datasets.

Should you need to explicitly state the version of the SMOPS datasets, then you may specify their version with either “1.3”, “2.0”, or “3.0”.

SMOPS search radius for openwater proximity detection: specifies the radius in which LDT search to detect open water. Then removes all pixels within the radius in the CDF calculations.

ASCAT (TUW) soil moisture observation directory: specifies the location of the data directory containing the TU Wein retrievals of ASCAT soil moisture data.

MCD15A2H LAI data directory: specifies the location of the data directory containing the MODIS MCD15A2H LAI retrievals.

MCD15A2H LAI data version: specifies the version of the MCD15A2H LAI retrievals. The default version is "006".

MCD15A2H LAI apply climatological fill values: specifies whether to fill in climatological LAI values if there are missing values.

MCD15A2H LAI apply QC flags: specifies whether to apply quality control flags for LAI retrievals.

GRACE raw data filename: specifies the name of the GRACE raw data.

GRACE baseline starting year: specifies the baseline starting year from which to establish the TWS climatology.

GRACE baseline ending year: specifies the baseline ending year from which to establish the TWS climatology.

GRACE scale factor filename: specifies the name of the file containing the GRACE scale factor. This is NetCDF file provided by JPL.

GRACE measurement error filename: specifies the name of the file containing the GRACE measurement error. This is a NetCDF file provided by JPL.

GRACE process basin averaged observations: specifies whether to process basin averaged observations. Default value is 0. Acceptable values are:

GRACE basin map file: specifies the file name of the basin map data.

LIS TWS output format: specifies the output format of the LIS model output (binary/netcdf/grib1).

LIS TWS output methodology: specifies the output methodology used in the LIS model output (1d tilespace/1d gridspace/2d gridspace).

LIS TWS output naming style: specifies the output naming style used in the LIS model output (3 level hierarchy/4 level hierarchy, etc.).

LIS TWS output nest index: specifies the index of the nest used in the LIS model output.

LIS TWS output directory: specifies the location of the LIS model output.

LIS TWS output map projection: specifies the map projection used in the LIS model output.

For lat/lon projection:

LIS TWS output domain lower left lat: specifies the lower left latitude of the LIS model output (if map projection is latlon).

LIS TWS output domain lower left lon: specifies the lower left longitude of the LIS model output (if map projection is latlon).

LIS TWS output domain upper right lat: specifies the upper right latitude of the LIS model output (if map projection is latlon).

LIS TWS output domain upper right lon: specifies the upper right longitude of the LIS model output (if map projection is latlon).

LIS TWS output domain resolution (dx): specifies the resolution (in degrees) along the latitude of the LIS model output (if map projection is latlon).

LIS TWS output domain resolution (dy): specifies the resolution (in degrees) along the longitude of the LIS model output (if map projection is latlon).

For Lambert and polar projections:

LIS TWS output domain lower left lat: specifies the lower left latitude of the LIS model output

LIS TWS output domain lower left lon: specifies the lower left longitude of the LIS model output

LIS TWS output domain true lat1: specifies the true lat1 of the LIS model output

LIS TWS output domain true lat2: specifies the true lat2 of the LIS model output

LIS TWS output domain standard lon: specifies the standard longitude of the LIS model output

LIS TWS output domain resolution: specifies the resolution of the LIS model output

LIS TWS output domain x-dimension size: specifies the x-dimension size of the LIS model output

LIS TWS output domain y-dimension size: specifies the y-dimension size of the LIS model output

Simulated GRACE data directory: specifies the directory containing the simulated GRACE observations.

Simulated GRACE configuration: specifies the simulated GRACE configuration. Acceptable values are:

Simulated GRACE baseline starting year: specifies the baseline starting year from which to establish the simulated TWS climatology.

Simulated GRACE baseline ending year: specifies the baseline ending year from which to establish the simulated TWS climatology.

LIS TWS output format: specifies the output format of the LIS model output (binary/netcdf/grib1).

LIS TWS output methodology: specifies the output methodology used in the LIS model output (1d tilespace/1d gridspace/2d gridspace).

LIS TWS output naming style: specifies the output naming style used in the LIS model output (3 level hierarchy/4 level hierarchy, etc.).

LIS TWS output nest index: specifies the index of the nest used in the LIS model output.

LIS TWS output directory: specifies the location of the LIS model output.

LIS TWS output map projection: specifies the map projection used in the LIS model output.

For lat/lon projection:

LIS TWS output domain lower left lat: specifies the lower left latitude of the LIS model output (if map projection is latlon).

LIS TWS output domain lower left lon: specifies the lower left longitude of the LIS model output (if map projection is latlon).

LIS TWS output domain upper right lat: specifies the upper right latitude of the LIS model output (if map projection is latlon).

LIS TWS output domain upper right lon: specifies the upper right longitude of the LIS model output (if map projection is latlon).

LIS TWS output domain resolution (dx): specifies the resolution (in degrees) along the latitude of the LIS model output (if map projection is latlon).

LIS TWS output domain resolution (dy): specifies the resolution (in degrees) along the longitude of the LIS model output (if map projection is latlon).

For Lambert and polar projections:

LIS TWS output domain lower left lat: specifies the lower left latitude of the LIS model output

LIS TWS output domain lower left lon: specifies the lower left longitude of the LIS model output

LIS TWS output domain true lat1: specifies the true lat1 of the LIS model output

LIS TWS output domain true lat2: specifies the true lat2 of the LIS model output

LIS TWS output domain standard lon: specifies the standard longitude of the LIS model output

LIS TWS output domain resolution: specifies the resolution of the LIS model output

LIS TWS output domain x-dimension size: specifies the x-dimension size of the LIS model output

LIS TWS output domain y-dimension size: specifies the y-dimension size of the LIS model output

NASA SMAP soil moisture data designation:

NASA SMAP soil moisture observation directory: specifies the location of the data directory containing the NASA SMAP data.

NASA SMAP vegetation optical depth observation directory: specifies the location of the data directory containing the L2 SMAP vegetation optical depth retrievals.

NASA SMAP vegetation optical depth data designation: specifies the type/source of VOD retrievals. Acceptable values are:

SMAP(NASA) soil moisture Composite Release ID (e.g., R16): specifies first three characters of the Composite Release ID (CRID) (e.g., R16)

SMOS NESDIS soil moisture observation directory: specifies the location of the data directory containing the SMOS soil moisture retrievals from NOAA NESDIS.

LPRM vegetation optical depth observation directory: specifies the location of the data directory containing the LPRM vegetation optical depth retrievals from LPRM.

LPRM vegetation optical depth data designation: specifies the type/source of VOD retrievals. Acceptable values are:

This section describes the parameters needed for the HYMAP and the HYMAP2 routing models. The config entries only have “HYMAP” within them, as they apply to both HYMAP versions.

HYMAP river width map: specifies the name of the HYMAP river width data file.

HYMAP river height map: specifies the name of the HYMAP river height data file.

HYMAP river length map: specifies the name of the river length data file.

HYMAP river roughness map: specifies the name of the HYMAP river roughness data file.

HYMAP floodplain height map: specifies the name of the HYMAP floodplain height data file.

HYMAP floodplain height levels: specifies the number of the HYMAP floodplain height levels.

HYMAP floodplain roughness map: specifies the name of floodplain roughness data file.

HYMAP flow direction x map: specifies the name of the x-flow direction data file.

HYMAP flow direction y map: specifies the name of the y-flow direction data file.

HYMAP grid elevation map: specifies the name of the grid elevation data file.

HYMAP grid distance map: specifies the name of the grid distance data file.

HYMAP grid area map: specifies the name of the grid area data file.

HYMAP drainage area map: specifies the name of the drainage area data file.

HYMAP basin map: specifies the name of the basin map data file.

HYMAP basin mask map: specifies the name of the basin mask data file.

HYMAP runoff time delay map: specifies the name of the runoff time delay data file.

HYMAP runoff time delay multiplier map: specifies the name of the runoff time delay multiplier data file.

HYMAP baseflow time delay map: specifies the name of the baseflow time delay data file.

HYMAP baseflow dwi ratio map: specifies the name of the baseflow dwi ratio data file. This is an optional parameter that is required only when “HYMAP2 routing model dwi flag” is set to 1 (turned on) in LIS in the lis.config file. If this flag is set to 0 in the lis.config file, the baseflow dwi ratio map is not required.

HYMAP runoff dwi ratio map: specifies the name of the runoff dwi ratio data file. This is an optional parameter that is required only when “HYMAP2 routing model dwi flag” is set to 1 (turned on) in LIS in the lis.config file. If this flag is set to 0 in the lis.config file, the runoff dwi ratio map is not required.

HYMAP river flow type map: specifies the name of the river flow type data file. This is an optional parameter that is required only when “HYMAP2 routing method” is set to “hybrid” in LIS in the lis.config file. If the routing method is set to a different option, the river flow type map is not required.

This section also outlines the domain specifications of the HYMAP parameter data. For the HYMAP parameters spatial transform option, only “none” is supported at this time, and the user is required to input the HYMAP parameters at the grid and resolution of interest.

If the map projection of parameter data is specified to be “latlon”, the following configuration should be used for specifying HYMAP parameters. See Appendix Cylindrical Lat/Lon Domain Example for more details about setting these values.

ANN input data sources: specifies what?

ANN mode (training/validation): specifies what?

ANN number of hidden neurons: specifies what?

ANN number of input data sources: specifies what?

ANN number of iterations: specifies what?

ANN number of parameters in each input source: specifies what?

ANN output data source: specifies what?

ANN training output file: specifies what?

USAFSI netcdf filename prefix: prefix used in constructing USAFSI netcdf filenames

USAFSI valid date (YYYYMMDDHH): valid date and hour (UTC) of analysis

USAFSI fractional snow data directory: directory with CDFS-II fractional snow data

USAFSI modified data directory: directory with legacy SNODEP “modified” data

USAFSI surface obs data directory: directory with surface snow reports

USAFSI SSMIS data directory: directory with SSMIS snow depth retrievals

USAFSI surface temperature data directory: directory with legacy 0.25 deg LIS ungribbed surface temperatures

USAFSI static data directory: directory with legacy SNODEP static data

USAFSI unmodified data directory: directory with legacy SNODEP “unmodified” data

USAFSI VIIRS data directory: directory with VIIRS TIFF files

USAFSI SSMIS raw data directory: directory with SSMIS BUFR files

USAFSI SSMIS snow depth retrieval algorithm: version of SSMIS retrieval algorithm. Acceptable values are:

USAFSI SSMIS forest fraction file: path to netCDF forest fraction file (for Foster et al (1997) algorithm)

USAFSI decimal fraction adjustment of snow depth towards climo): controls drift to climo in data void region

USAFSI default snow depth (m) when actual depth unknown: bogus value for when snow detected but depth unknown

USAFSI minimum snow depth (m) for which to print a diagnostic: threshold for printing surface ob report

USAFSI maximum number of surface observations allowed: self-explanatory

USAFSI SSMIS shallow snow depth threshold (m): minimum SSMIS snow depth considered reasonable

USAFSI latitudes (deg * 100) for summer climo check: three latitude bands used for sanity checking snow reports

USAFSI elevations (m) for summer climo check: four elevations used for sanity checking snow reports

USAFSI temperature (deg K * 10) above which no snow is allowed: used to adjust snow analysis

USAFSI minimum ice concentration (%) needed to set ice flag: used when constructing binary sea ice field

USAFSI high latitude thresholds (deg) for sea ice:: 24 latitudes, each row defining a hemisphere (NH, then SH), each column defining a month (J F M A M J J A S O N D). Used to define “high latitudes” in SSMIS-based sea ice analysis.

USAFSI low latitude thresholds (deg) for sea ice: 24 latitudes, each row defining a hemisphere (NH, then SH), each column defining a month (J F M A M J J A S O N D). Used to define “low latitudes” in SSMIS-based sea ice analysis.

USAFSI max age of VIIRS pixels to use: used to ignore old VIIRS data

USAFSI min VIIRS fraction to mark point as bare ground: fraction of no-snow VIIRS pixels in LDT grid box required to mark as “no-snow”

USAFSI min VIIRS/CDFS-II fraction to mark point as snow: fraction of snowy VIIRS pixels or CDFS-II in LDT grid box required to mark as “snow”

USAFSI use CDFS-II fractional snow data: self-explanatory

USAFSI use VIIRS snow mask: self-explanatory

USAFSI observation error variance (m^2): error variance assigned to surface snow reports

USAFSI background error variance (m^2): error variance assigned to first-guess field

USAFSI background error horizontal correlation length (m): correlation length for spreading snow depth corrections horizontally

USAFSI background error vertical correlation length (m): correlation length for spreading snow depth corrections vertically

USAFSI elevQC difference threshold (m): threshold for sanity checking snow report elevation against LDT

USAFSI skewed backQC snow depth threshold (m): threshold for rejecting abnormally small snow depth reports

USAFSI bogus climatology snow depth value (m): bogus value for climatology if not available

USAFSI GOFS SST data directory: directory with GOFS sea surface temperature netCDF files

USAFSI GOFS CICE data directory: directory with GOFS sea ice netCDF files

USAFSI LIS GRIB2 data directory: directory with LIS GRIB2 2-m temperature analyses

USAFSI LIS GRIB2 security class: used for constructing LIS GRIB2 filename

USAFSI LIS GRIB2 data category: used for constructing LIS GRIB2 filename

USAFSI LIS GRIB2 data resolution: used for constructing LIS GRIB2 filename

USAFSI LIS GRIB2 area of data: used for constructing LIS GRIB2 filename

USAFSI GALWEM root directory: root directory for GALWEM data

USAFSI GALWEM subdirectory: subdirectory for GALWEM data

USAFSI GALWEM use timestamp directories: option to use YYYYMMDD in constructing full GALWEM directory; 1 is yes, 0 is no

USAFSI GALWEM nominal resolution (km): 17 or 10 (17 currently used in operations)

LIS OPT/UE output file: name of the OPT/UE output file generated from a LIS simulation

The LDT output file, like the NetCDF file, contains header information for the dimensions. The list can include:

This file can be used to determine the number of tiles used in a LIS model simulation. The number of tiles are specified in this dimensions header information.

The LDT output file, like the NetCDF file, contains header information for the variable or paremeter file attributes. The list can include: (for example)