Overview

Setting up a WAM scenario from scratch is an involved process that requires assembling the required spatial datasets and preparing them for import into a freshly created WAM_GIS_Database. Recall from the data requirements page that several datasets are required to run WAM. Each dataset listed below will be discussed in the order that they should be imported into the database.

  1. Sub-basin boundaries are polygons in a feature class that delineate boundaries of the sub-basins that make up the basin.

  2. Basin boundary is a polygon feature class that consists of a single polygon representing the model domain. During the process of importing the sub-basin boundaries, this feature class is generated automatically.

  3. Land Use is a polygon feature class defining the land use practices within each polygon.

  4. Soils is a polygon feature class that gives the predominant soil type within each polygon.

  5. Utility Zones is a polygon feature class that indicates if an area is served by a waterwater treatment facility or alternatively uses septic systems. Although the feature class covers the entire model domain, only urban areas will be affected by this dataset.

  6. Irrigation Source is a polygon feature class that indicates where a land use with irrigation demand obtains its water from.

  7. Reaches is a line feature class that delineates the stream network to be simulated.

  8. Structures is a point feature class that defines the location of hydrologic/hydraulic structures within the stream network. Typically these are added after the import process, but they can also be imported if a feature class is provided.

  9. Point Sources is a point feature class that defines the location of point sources or withdrawals from the stream network. As with the structures feature class, these are typically added afterward.

  10. Topography is a raster dataset, typically a digital elevation model (DEM) that provides the elevations within the model domain.