Preparing Input Data Sets - Revision history

Dgroulx: /* Importing files into grass */

2009-10-12T18:31:44Z

Importing files into grass

Dgroulx: /* Developing timeseries data sets */

2009-10-12T18:30:01Z

Developing timeseries data sets

Dgroulx: /* Developing Timeseries Data Sets */

2009-10-12T18:02:37Z

Developing Timeseries Data Sets

Dgroulx: /* Setting a mask */

2009-10-12T18:02:24Z

Setting a mask

Dgroulx: /* Create Hillslope and stream maps */

2009-10-12T18:01:01Z

Create Hillslope and stream maps

Dgroulx: /* Setting a mask */

2009-10-12T18:00:44Z

Setting a mask

Dgroulx: /* Create Hillslope and stream maps */

2009-10-12T18:00:09Z

Create Hillslope and stream maps

Dgroulx: /* Create a watershed */

2009-10-12T17:59:46Z

Create a watershed

Dgroulx: /* Create a watershed */

2009-10-12T17:57:32Z

Create a watershed

Dgroulx: /* Create a watershed */

2009-10-12T17:57:09Z

Create a watershed

@@ Line 81: / Line 81: @@
 NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point.  However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
 d.zoom resets the region to the area you are zoomed in on.  Any additional functions
- you perform after zooming in would only process the area you are zoomed in on.  As you
+you perform after zooming in would only process the area you are zoomed in on.  As you
 may be zoomed in very tightly on a stream segment and the full area of the watershed
- you want to capture may not be displayed, you should reset your region with:<br>
+you want to capture may not be displayed, you should reset your region with:<br>
 '''grass> g.region rast=hjadem'''
@@ Line 91: / Line 91: @@
 Or to clear your monitor, use:<br>
 '''grass> d.erase'''
 ==Create a watershed==

@@ Line 280: / Line 280: @@
 NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt).  When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
-Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from Dos text format to UNIX format - which will remove the ^M characters from the file.  If you open one of the files with vi, you can see if the characters are present.
+Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file.  If you open one of the files with vi, you can see if the characters are present.
 ==Streamflow==

@@ Line 241: / Line 241: @@
 You have now created all the maps necessary for RHESSys to define the landscape representation.  For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.
-==Developing Timeseries Data Sets==
+==Developing timeseries data sets==
 Climate
 RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature.  These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

@@ Line 199: / Line 199: @@
 You should now have a much closer view of the DEM for new_basin_name.
 Zones
 Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station.  For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed.
@@ Line 214: / Line 216: @@
 '''grass> r.mapcalc 'K = new_basin_name * 2000' '''<br>
 '''grass> r.mapcalc 'm = new_basin_name * 120' '''<br>
-'''grass> r.mapcalc 'zero = 0' '''
+'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)
 (zero will be used as the road map as there are no roads in this watershed)
 When you created new_basin_name, it was assigned a value of 1.  The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2000, and a new map called m (decay of hydraulic conductivity with depth) with a value of 120.  You also created a road map equal to zero to indicate that there are no roads in this dataset.  K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).
-Patches
+==Patches==
 The final map required for a basic RHESSys run is the patch map.  Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics.  Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch.  Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed.  You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).
@@ Line 224: / Line 226: @@
 For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM.  The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories.<br>
 '''grass> r.clump input=hjadem output=new_map_name.cl'''
@@ Line 233: / Line 234: @@
-Stratum
+==Stratum==
 Strata define vertical, aspatial layers within the patch.  Processes such as photosynthesis and transpiration are modeled at the stratum level.  Strata usually have the same spatial structure as patches.  So the patch (new_map_name.cl) map will also be used to define the stratum object.

@@ Line 157: / Line 157: @@
 will list maps only in your personal mapset directory.
-==Create Hillslope and stream maps==
+==Create hillslope and stream maps==
 You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys.  RHESSys uses different spatial objects to model specific hydro-ecological processes.  These objects form a hierarchical representation of the landscapes key objects.  The hillslope and stream maps are necessary as they represent key landscape objects.  The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM.  You only want to create these maps for the new_basin_name portion of the DEM.

@@ Line 190: / Line 190: @@
 Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page.  You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.
-Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area.
+Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area.<br>
 '''grass> d.rast map=hjadem'''
@@ Line 196: / Line 196: @@
 '''grass> g.region raster=new_basin_name zoom=new_basin_name''' <br>
 '''grass> d.redraw'''
 You should now have a much closer view of the DEM for new_basin_name.

@@ Line 168: / Line 168: @@
 '''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''
+The proceeding was an abbreviation of:<br>
 '''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

@@ Line 107: / Line 107: @@
 watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!
-  Using the overlay option with a new map generated from an existing map<br>  When you create a new map that represents a portion of the extent of an existing map, you may need to run the GRASS command r.support in order to set all null       values to transparent.  For example, you would use r.support if you wanted to overlay new_basin_name on top of the DEM so that all areas outside of the new sub- basin were transparent, allowing the DEM underneath to show through.  You may find the command G> r.support helpful as you create new maps.
+  Using the overlay option with a new map generated from an existing map<br>
   When you create a new map that represents a portion of the extent of an
-r.support can only be run interactively.  To use it for the purpose of setting null values to transparent, accept the default (no) for the first six questions, but answer yes to the last question ‘Do you want to delete null file for map_name?’  Answer yes.
+ existing map, you may need to run the GRASS command r.support in order to set all null
-	***********************************************************************
+ values to transparent.  For example, you would use r.support if you wanted to overlay
 ==Preparing spatial input data sets==