This zipped folder contains the following folders:

climate (dir)

contains:
- the climate files generated by hillslope in .prn and .cli formats
- the watershed climate file
- the original daymet/gridmet data that was used to generate the .cli files

dem (dir)

contains:
- the 30-m DEM map used in the analysis
- topaz folder containing the watershed delineation and all the maps created during the watershed delineation

export (dir)

• contains channels and subcatchments files in ArcGIS format containing topographic characteristics (such as slope, aspect, or length), input data (soil and management), and output information (runoff, lateral flow, baseflow, sediment, pollutant, etc.). The file also contains the several GeoTIFF maps used in the model run.

landuse (dir)

• contains landuse map (e.g. ascii map with the 2016 National Land Cover Database (NLCD) for US Locale. The NLCD codes are translated into WEPP-equivalent managements based the mapping for the configuration._

observed (dir)

• observed data (if) provided by the user

soils (dir)

• contains the soil files in WEPP format by mukey and a ssurgo.asc map

watershed (dir)

• contains files with slope information for each channel and hillslope

wepp (dir)

• with sub-folders:
  
  • wepp/flowpaths -- contains model input and output based on the flowpaths option, if selected. If the flowpath option is selected, the WEPP model will be run for each map pixel. This folder contains a runs folder with all the input data and an output folder with the runoff and soil loss for each flowpath.
  • wepp/output -- contains the main model outputs for the watershed
  • wepp/plots -- contains model plots -- generally empty
  • wepp/runs -- contains all the main input data for the model
  • wepp/stats -- generally empty

nodb files

• JSON serialized instances of wepppy.nodb classes used by WEPPcloud. These contain metadata related to the project. They are viewable in FireFox/Notepad++ etc.

More on NoDB Files

WEPPcloud project runs are designed to be self-contained and to not rely on a centralized database. This is accomplished by storing model run information in JSON (JavaScript Object Notation) files. These are the .nodb files in the project’s root folder. The .nodb files are serialized Python class instances that greatly simplifies modeling from a programmatic perspective. Even for non-programmers these files can be informative.