Home

SGAT User Guide - Watershed Management Division

Contents

1. A test is performed to ensure that the shape file selected can be edited If it cannot then the shape file is either in use by another application or has its Read Only attribute set as would be the case for files copied from a CDROM The following error message will be issued in such circumstances 1004 Unable to edit S00LUCodes dbf data set Itis use by another application or has Read Only attribute set April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 69 Then a test is made to ensure that the table is not an attribute table associated with a shape file If itis the following error message will be issued SGAT User Error 1081 GeoSW Reg Theme Ibtselect x Stor 1081 The table selected s 0meandercl dbt is an attribute table for a theme shape file File selection ignored A test is then made to ensure that the table has not already been registered under another Alias If it is found to be registered the following error message will be issued 2 SGAT User Error 1082 GeoSW Reg Theme btSelei t x W082 The table selected 200Icluxtabhields dbf i registered for the Alias LoLusT abFields you must unregister the table as being associated with that Alias first by removing it from the project In the above situation an incorrect table was selected for Soils Top20_05 Unlike for themes there is no test for the ability to edit any tables being r
2. 38 Number of reach segments exceeds 02 Segment Id of for Reach Pt MOT Upon completion Alias of surface water theme modified SWSEG Legend file used to display surface water theme N A Alias of projected segmentation point theme SegPtsProj Legend file used to display projected segmentation point theme N A Upon completion the following message will be displayed to summarize the processing that took place A SGAT Info GeoSW FEHSegment lbtSegment Click x Themes FEHOTS WFEH shp modified by segmenting surface waters and FEHOTFEHPtsProy shp Segmentation Pts projected oO onto Sw created and saved in h geomorphologyversion4DenvdD ata and added to View SGAT The new theme containing the segmentation points projected onto the surface waters will be created and the surface water theme will be modified to reflect the reach segmentation Click on the button labeled Done to return to the Part D menu dialog April 2006 Part D Step SEGO1 Segment Reaches Page 198 Part D Feature Indexing The functions within this Part enable one to index features with respect to the surface waters As an example one may have identified a portion of a stream in which significant bank erosion has been and is occurring To index this as a feature one identifies the beginning and ending points of the erosion These points are converted to a series of polylines that represent the length of stream under erosi
3. Generally the error will show the sum of the sub watersheds being less than the area of the overall watershed In most cases this is an indication that one or more sub watersheds were not encountered during stream tracing This type of error and the general location of the stream segments missing Tributary Identifiers will be made visible through use of the legend file SubWSUsed avi as described earlier Check the assignment of Tributary Identifiers in Step 04 If modifications or additions are made to the Tributary Identifiers in Step 04 perform processing from Step 05 on April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 119 If the error message indicates that the sum of the sub watersheds is greater than the overall watershed there is a sub watershed line drawn above the confluence of two streams assigned tributary identifiers See figure to the right Note The sum of the sub watershed areas exceeded the area of the overall watershed because the sub watershed was encountered twice during stream tracing Watershed line crosses above the confluence of two streams Potential Error during Stream Tracing In order to create reach points the stream network will be composed of only those stream segments for which a tributary identifier was assigned in Step 04 All other stream segments are ignored Incomplete tracing can occur if one misses assigning a tributary identifier to an internal segment of
4. WARNING Since the resulting table is a dBase table it can be opened up in either Microsoft Excel or Microsoft Access for further analysis If those applications are to be used copy the table into another directory on the hard disk Open that version of the table with Excel or Access Then any necessary changes can be made without impact on the ArcView project Note If inadvertent changes are made to the structure of the table outside of ArcView it may not be useable within ArcView This in turn could result in corruption of the ArcView project which could render it unusable April 2006 Step 13 Sum Data to Upstream Watershed Area Page 174 Step 14 Summarize Area by Field Value Cross Tabulate This dialog summarizes areas based upon values in a field i e cross tabulation This is best described by using the soils data as an example Example Each soil mapping unit is associated with various characteristics The most frequently used characteristics are those listed in the Top20_05 dbf table One of those characteristics is the potential for flooding That potential is described by the values for the Flood field which are listed below Frequent None Not Rated Occasional Rare Water In Step 12 areas were summarized by soil mapping unit within a given stream corridor or sub watershed Each of those soil mapping units was assigned a value for its potential for flooding from the Top20_05 dbf table
5. S UIOd uolyejuawbas yoeay ulIj1 U99 J puLe N Je ul j juiod jo sisAjeuy Ayisueq sJuloquoeey s18 M IUNS peysuayem qns g Hed Woljsewey L 10pu100 Weeds Jo paysuayem qns uly Mm sainjyea ease JO payey JON JO SUON ley eudISeDNO jJuenbas4 Bulpoo s jo adA1 Aq sauce H SanfeA sINquiyy N797 S 0S Aq sease jo Avewwns pue 9S puea pue spu npuiddey sjos 104 ealy abeulesq pays e M JO poysueye M qNS JOPLIOD Weds Ul Bbeaoy 9 Hed WO pa eiaued eq asp pueq 18A09 pueq poyejnojen pejyesld 10 s w y WO Jq Esp pesinbey p ipoys w y Q0IN0S s u wajgeq pusbe7 juawaUlJUuOD Age A Aysnonuisjauueyy sadojs jauueyy Aayje A SUOIJEAS AIq YOROY SJOPIUOD WEIS yIpIM y 6ue7 eur lleA YIP MjeuueYy gt y 6ue7jeuueyy SWEAIIS JO y Gud7 ealy obeureiq Bally paysieye M qNS Hes WOIadUeISIG 1qyoeaY SISIJIJUSP JUIOd YOVOY away 1197 M soeNS UI SWE3I S 0 1 14 u p Arengu L jo 1udwubissy enuey Aseynqu JO Jalj11Uep JUIOg YOROY yore JO Jaye g Hed W01 pa 12u29 eq ng 10 S19 M 22L unG O SUONeDNHIPON 10 siaye M 23L n O SUOIJEOIJIPOY Adua sisuoDd pue SpsysisjJeM Qngs pue Aoeinooy 10 MalAdY 1947 M N JO SSUSY aAoge 99S g Yed SJOPIUOD WE31 S S qinod Aewld s JUloquoeey s18 M 2NG suave UNS peysueyem qns peysuayem qns peysusje M uolyeuljaq peysiayem qns ewey Id
6. for field Rey Eror 23 Buffer reference table SysButS hA dof associated with April 2006 Accessing the Stream Geomorphic Assessment Tools Page 55 If no errors are detected with regard to the buffer reference tables the initialization procedure will conclude If however any error conditions are detected access to the Tools is prevented In such a case the errors must be corrected in order to gain access The initialization procedure will always make backups of the critical system files that maintain the registration data and the og entries These backups will be placed in the Temp directory The following message will be issued only in the event that an error is detected during the procedure for Loading themes tables previously registered This is to serve as a reminder only pE I 2 SGAT Info 0030 GeoSW Common Projinit LoadSy xX SyeBT AegFields dbf and Syslog dbf placed in h geomorphologyversion4 test Temp prior to unregistrations O 30 Backups of critical system tables SysBaseT heme dbf One may have copied the system directory SysData for a previous project into a new directory but forgot to copy the themes tables from that project into the required directories In this case the error pertaining to registered data sets not found in the required directories described above will be issued Having realized that one can exit the SGAT extension copy the data sets into their appropriate dire
7. Note Impacts and related sub impacts and or locations are defined and maintained via the system function labeled Define Impacts for Feature Indexing 1 Select the impact This will establish the appropriate data fields on the dialog as well as whether the resulting feature will be a point or polyline feature 2 If applicable select the appropriate sub impact f no sub impacts are applicable there will be no entries available in the sub impact drop down list 3 If applicable select the appropriate location f no locations are applicable there will be no entries available in the location drop down list 4 Enter the Impact Feature Data Only the appropriate fields will be displayed for a given Impact and the name of data required will be displayed as the label to the left of each data entry field There may be anywhere from zero to two fields displayed In the preceding figure only one data field named Height is associated with the Erosion impact and is therefore displayed on the dialog The required data and format of the dialog will be set when one selects the Impact in 1 above As aresult always select the impact first April 2006 Part D Step FITOOb Feature Indexing Page 207 When entering values for the data elements be sure to enter numbers otherwise an error will be issued when you attempt to Set Impact Note The length of the field name or label is restricted to 10 characters as a result som
8. Note It is strongly recommended that you adhere to the procedures described in the warning message The background for this warning is provided in the Section entitled Accessing the Stream Geomorphic Assessment Tools April 2006 Setting Up for Using the Tools Page 15 When the Ok button is clicked the SetUp dialog for the Stream Geomorphic Assessment Tools will be presented This dialog is shown in the figure below Stream Geomorphic Assessment Tools er 4 00 Setup Dialog E 3 Primary Function User Qccess Type and Application Designatic User Type Regional Planning Application SGA Select Application for which SGAT is to be used Wiew to which themes will be added upon registration creatio view SGAT Set View Themes will be added to view shown Application Area ThemeT able Registration and Management Stream Geoamoarphic Assessment Tools SGA4T View Log System Functions The SetUp dialog represents the top level dialog in the Tools extension All other dialogs are accessed through this dialog In addition one must return to this dialog to exit the Tools extension by clicking on the Exit button Exiting the Tools extension removes any traces of itself and returns one to a pure ArcView environment It does not however unload the extension To unload the Tools extension Make the project window the active window in ArcView Click on the File Menu C
9. The intent of this dialog is to export the data associated with impacts that have been indexed The table resulting from the export will subsequently be used to import impact data in the DMS Data Management System used to maintain the data for geomorphic assessments collected throughout the state Part D FITO3 Export Feature Data to a dBase Table Input Theme Source of Input Theme C Reaches produced by Part D Step ATOT f Reach Segments produced by Part D Step FITOI Pi Impacts FITO PlrmnpactS eq shp Theme for Impacts Point with segmentation Ids assigned to be used Polpline Impacts FITC LnimpactSeg shp Theme for Impacts Polpline segmented to be used Output Table to be created Output Table Hame FIT Export dbt To be saved in H GeormorphologyYersion4 DernvdO ata Note for insertion into System Lo User Note Export To use this dialog The source of the impact themes to be used will automatically be selected If the segmented versions created via Step FITO7 are available they will be used If they are not available those created in Step F TOO will be used If neither version is available the Export button will be disabled and access to this function will not be available The theme containing point impacts created in Step FITO1 or Step FITO0a as dictated by the source to be used will be displayed The theme containing polyline impacts created in Step FITO71 or Step
10. User must ensure that the ends of polyline segments are snapped together if digitizing was stopped and then started again within a reach 2 Individual polylines drawn to represent meander centerlines can continue through multiple reaches 3 With the exception of terminal reaches the meander centerline must travel through the entire length of a sub watershed and must intersect the sub watershed boundary only twice Once upon entering the sub watershed and once upon exiting The meander centerline should never cross the sub watershed boundary except at the point of entrance and the point of exit 4 For terminal reaches the meander centerline will intersect the sub watershed boundary only once Upon entering the sub watershed April 2006 Setting Up for Using the Tools Page 21 5 The meander centerline should respect the boundaries of the valley walls if available for a given reach i e the meander centerline should remain inside of the boundary for the valley walls 6 At confluence points it will be necessary to have a small segment of the meander centerline traveling up the tributary fall within the sub watershed of the main stem or primary tributary This is required to meet number 3 above for the reach on the tributary The small dangling will be ignored in the development of buffering for the reach on the main stem or primary tributary An example of this is illustrated in the figure below Stream Centerline OX LZ Zo D
11. Export Feature Data Page 222
12. If data is entered in Step 10 and then Step 07 or 08 is run the changes made in Step 10 will most likely be lost In Steps 06 through 10 data is associated with each reach point Appendix C and D provide a detailed description of the attributes and identifies the processing steps in which they are assigned While the attributes are associated with the reach point theme one can relate that data to other themes for thematic mapping During processing in Steps 06 through 09 the Reach Point Identifier RchPtld is assigned to features for the surface waters from Step 05 sub watersheds valley lines Step 07 dissolved surface waters Step 08 and stream corridors Step 09 Using the Export button in Step 10 the data associated with the reach points can be exported to a dBase table One can relate that table to other themes using the Relate button in ArcView after identifying the AchPtld field in the exported table and then the theme of interest To access the dialog for this step click the button labeled Step 10 Data Entry Review of Reach Point Data on the Part B main dialog The dialog with sample data entered is illustrated below Part B Step 10 Data Entry Review of Reach Point Data Reach Point Theme Theme for Reach Paints to be used Theme SO6RPts01 shp v Reach Point Identifiers 5 Reach ID Mor v irie td M Distance ld M 000 000 Reach Point Data chet eieceg Tor
13. In Step 13 areas were summarized by soil mapping units within the stream corridor or sub watershed for the entire corridor or sub watershed upstream of a reach point The value for potential for flooding from the Too20_05 dbf table is carried forward from the input table In this step the soil mapping units are dropped and areas are summed by the value associated with respect to a soils characteristics i e potential for flooding The summation is performed within the stream corridor or sub watershed depending upon which theme was used as the boundary theme in Step 11 The stream corridor is used to continue the example The table resulting from this step will be the total area within a stream corridor for a given reach point associated with a specific potential for flooding The following table illustrates this cross tabulation Sid4soils_newtable dbf a 016136896967 0 OG 0 Tenn 3 OAOD SOOS S d eoleo teo tee erte er erori 0 0000000000 0 00000000 T EEE E Gpeceeecenenecewes heteeebeebeebeete l Bieeel e Meee m miT 00722728959 0 0016298254 0 0023537118 0 0670735150 0 0000000000 0 0012161438 0 0000000000 0 00000000 Ong M2 d 01079474252 0 0001448810 0 0000000000 0 0975583062 3062 0 0000000000 0 0102442380 _ 0 0000000000 0 00000000 i i 1 i AMAMI CHINN A ANTA E oO OE AAE E a OEE E ao NANNTE A EEEE A AAAA The field names in the preceding figure
14. Outlow Channel and Valley i Channel lt Units gt Valley Location Width ron Distance to Start 000 Feet Idth 13 e idth 0 Elevation W Feet Nat 6604 Langit 0 slopi 0 00 lt Percent gt Slope 0 00 State Plane Coordinates BE F inuasit 0 lt Ratio gt Confinement 0 437778 67 194434 96 Aleas Geographic Coordinates Reach Sub watershed 0 60 Sq Miles Reach Drainage Area Sq Miles mg 73 279040 Lal 44 247495 i Lal i Overall Watershed 1 51 Sq Miles Map Documentation for Reach Wuads te Orthos Ee HUEY Note for Reach Pt Calc Data Set Map Doc Export Data Done April 2006 Step 10 Data Entry Review of Reach Point Data Page 149 To use this dialog The dialog is set up for the user to review most data associated with the reach points created in Step 06 Only a limited set of data can be modified Data generated from Step 06 through Step 09 will be shown in the appropriate place in the dialog Those values where the field label is grayed out can not be changed Those values with a normal field label can be changed or data can be edited Warning If modifications are made in Step 10 to data calculated in another step examples Valley and Channel Width and Valley Length do not run that step again Doing so may result in canceling any changes made in Step 10 If Step 07 or 08 is re run then data should be thoroughly reviewed in Step 10 e The theme repr
15. REA Nho SU lt s X 2 f 2 f y Sea ST 4 UN etal oie 5 bie oy EA NNK Ay as h SEES ED Es PEF Us DN K t Q Nels RERAN TAR SNN h k S A d ry TN a YZ gt N if N KESAS ETEN BMA HY ANR BANAR RINE ore da NG ie KAEA p RE EA AOS Sena NA AAS STER E AA E aA h ICAS VINARI ASNA Ba NN BRS The figure to the right shows an enlargement of a section of the stream corridor Each different soil mapping unit is displayed in a different color April 2006 Step 11 Clip Theme to Boundary Page 162 Step 12 Summarize and Attach Descriptive Data This dialog summarizes data and performs a relational join to acquire descriptive data from another dBase table This is best described using soils data as an example In Step 11 the soils can be clipped to the boundaries of the stream corridors Within each corridor the same soil mapping unit may be found any number of times This step Step 12 creates a dBase table in which only one record is produced for each unique soil type withina given corridor The total area for each soil type occurring within a given corridor is calculated and entered into the field GeoSWArea The example cited the use of soils being clipped to the boundaries of the stream corridors Ina similar manner the soils could be clipped via Step 11 to the boundaries of the sub watershed This step would then summarize the area of soils by soil mapping unit within each sub watershe
16. SOOLcLuXT abFields dbf And the required source shape files are Huc 10 Boundaries Land Cover Land Use Meander Centerline delineation Ortho Photo Boundaries Reach Segmentation Points Soils Town Boundaries Sub watershed delineation Surface waters USGS Quad Boundaries and Valley Wall delineation April 2006 Setting Up for Using the Tools Page 27 Save the Project The ArcView project must be saved in order to use the Tools extension The following provides a brief outline of the procedure Make the project window active Select the File Menu Click on Save Project As In the resulting dialog box migrate to the directory in which the project to be saved and Enter the name of the project could be the name of the watershed oe aN The project must be saved in order for the Tools extension to identify the subdirectories in which the resulting shape files and dBase tables are to be saved When you access the Tools extension it will automatically create the subdirectories named BaseData DerivdData SysData and Temp under the directory in which the ArcView project file exists If these subdirectories already exist they will be used If you received an SGAT template on a CD than the appropriate directory structure is already set up for you In addition all of the standard shapefiles and tables are already registered and the view is named SGAT The only themes you should have to register are the valley wall
17. Step 17 input theme DataType Indicates the type of data theme used i e the data theme used in Step 11 Possible values are LcLu or Soils Value copied from Step 11 input theme SourceStep Will indicate which step created the output table Value inserted in this step is 12 SumLevel Will show to which level of aggregation that the data pertains Field is not used in this step however is created for subsequent use in other steps Value is set to blank Possible values are either Corridor Sub Watershed or Upstream SysRelFld identifies the relational field in the input theme used to relate to the descriptive table Field is used internally only and should not be altered All other data from the source theme Soils or Land Cover will be copied from the input theme In addition the data elements in the related record of the input table will be copied into the table created Click on the button labeled Done to return to the Part C menu dialog April 2006 Step 12 Summarize and Attach Descriptive Data Page 167 WARNING Since the resulting table is a dBase table it can be opened up in either Microsoft Excel or Microsoft Access for further analysis If those applications are to be used copy the table into another directory on the hard disk Open that version of the table with Excel or Access Then any necessary changes can be made without impact on the ArcView project Note If changes to a table being used
18. The last column contains the type of node represented by the Told Using the table begins with identifying the To node Then using the From node for that row look for its value in the To column to connect to the next downstream polyline Note Itis because the record numbers refer directly to records in the surface water theme that the route table must be kept consistent with the surface water theme If any changes are made to the surface water theme then the record numbers will change And if the record numbers change the route table will be referencing incorrect records April 2006 Step 04a Setup for Assigning Tributary Identifiers Interactively Page 99 A message similar to the following will be issued upon completion of the Setup procedure Setup Completed Successfully Required data set for tracing S035 CombT ribldSet dbf suiccesstully created and saved in directory H Geormorphologyersiond SDernvdD ata Processing completed in 16 seconds Upon completion one can proceed on with assigning tributary identifiers by clicking on the button labeled Assign Trib Ids Clicking on Done will return one to the Part A main menu April 2006 Step 04a Setup for Assigning Tributary Identifiers Interactively Page 100 Step 04b Assign Tributary Identifiers Interactively This dialog enables the one to assign tributary identifiers to selected polylines in the stream network This dialog is accessed by clicking on the button la
19. gt 25 NAA NAA NearDist gt 5 N A NZA NearDist gt 25 N A N A 1 multi part polygons 1 boundary overlaps 4 multi part boundary intersections 0 topology errors NAA NA SubWSld and SubWS Area fields added and updated User NAA Log entries for SO1Watershed shp purged 1 records deleted User NAA Theme SO1Watershed shp deleted NAA NAA 1 multi part polygons 1 boundary overlaps 4 multi part boundary intersections 0 topology errors NAA N A SubWSld and SubWSArea fields added and updated a Export Log Note Certain comments or user notes may be truncated in the Log Audit Notes window This appears to be due to a limitation in the length of a line If this is problematic export the log The resulting dBase table will be placed in the Temp directory Subsequently the table can be opened in Microsoft Excel to view the entire comments notes field The Date Time Step Number Name of Data Set and Alias will be listed in the log entry window only if the data set selected is All Themes Tables f a specific data set is selected these data elements will be listed elsewhere on the dialog along with the following O Data Set Source will be either Base source theme or table registered by the user or Derived data set created by the Tools Data Set Type will be either Theme or Table dBase table Active will indicate the data set which was last created or used for the given alias This will have
20. upstream All tables from this step start with S15 and end with the name of the input file The following table outlines the naming convention for distinguishing between corridor sub watershed and watershed data S15WR_themename_ Data summed for sub watershed area only S15WU_ themename_ Data summed for the sum watershed and summed for drainage area S15CR_themename_ Data summed for corridor area only S15CU themename_ Data summed for the corridor and summed for upstream corridor area Where R reach U Upstream W sub watershed and C Corridor The output table will have one record for each Reach Point Id found in the boundary theme sub watershed or stream corridor SourceStep Processing step within the Tools in which the data set was created i e 15 BndryType Values will be either Sub Watershea or Corridor to reflect the type of boundary theme used SumLevel Level to which data has been summarized Values for this field will be either Corridor Sub Watershed or Upstream If the value is Upstream then combine with field BndryType to reflect upstream drainage area for either sub watersheds or corridors GeoSWArea Area for which summation has occurred e g reach corridor reach sub watershed sum of upstream corridors or sum of upstream sub watersheds Units The type of units used in calculating densities Values will currently be Units Feet or Sg Miles depending upon w
21. 19 39 327027 3373 70 39 327027 0 00 39 327027 Page 158 Part C Soils Land Cover and Density Analysis Part A and B of the Tools extension were primarily devoted to data preparation This part builds upon that data and provides the user with the ability to obtain soils and land cover data for the stream corridors from Step 09 or for the source sub watershed theme To access the processing steps for Part C click the button labeled Part C Soils and Land Cover Analysis on the Main dialog for the Tools extension The dialog for Part C as illustrated below will be displayed Part C Soils Land Cover amp Density Analysis Data Extraction and Summary Step Run for Each Data Theme andor Boundary Them Step 12 Summarize and Attach Descriptive Data Step 13 Aggregate Data to Upstream Watershed Area Step 14 Summarize Areas By Field Value Cross T ab Step 15 Calculate Feature Density for Selected Boundaries View Log Done To access the dialog for any specific step simply click on the corresponding button It is important to understand that each step will be performed several times depending upon the requirements of the project For example Step 11 can be performed for the following combinations of input themes e Soils data theme with the stream corridors e Soils data theme with the sub watersheds e Land Cover Land Use data theme with the stream corridors e Land Cover Land Use data theme with the sub
22. 4 hitenverS GAT WwhitequlyOS white WDernvdD ata All missing values will then be written to a file having the same name as that specified for the output table but with the letters Mids appended referring to Missing dentifiers or missing values As an example the output table name for the message above was 12LC The name of the table containing the missing values ids is then 12LCMIds The dBase table containing the missing values will be saved in the DerivdData subdirectory under that in which the ArcView project file exists The table is also added to the ArcView project The figure to the right is an example of the missing ids table In this 12So0ilsChWdthx8Mids dbf example a blank value for the RT E GROUSS relational field Muid_c was found i once in the input theme i e a soil mapping unit was left blank in the soils theme which was clipped in Step 11 These missing values are an indication that either data in the relational table Top20_05 dbf or LuCodes dbf is out of date or there are attribute errors in the source themes used in Step 11 Any missing values should be recorded and investigated with the agency responsible for the data sets which would generally be VCGI Make note of the theme which was clipped in Step 11 what if any themes were merged to form that one and the relational table After you have recorded the information the tables containing the missing ids can be delete
23. 5035W Comb shp for SZW Combined between Sutput Theme S035WComb shp F Shae pts will be replaced To be saved in c projects 03 otter creek lewis little otterlemon fairsqat 2005 D erivdD ata Note for insertion into System Log User Note Combine Done e Each step can be performed multiple times without adverse affect on the data For example if you get a telephone call and don t remember if you clicked on the execute button usually the Clip Calc or Summarize button simply click on it again You may receive a warning that certain fields will be cleared and re used simply respond Ok Note You can view the log using the data set of All Themes Tables to determine the processing steps completed Simply scroll down to the last entries and identify the processing step resulting in the last entries being created April 2006 Organization Page 35 Organization of Dialogs in the Stream Geomorphic Assessment Tools SJBUIPJOQNS 31 SzIUBBJO 0 paan ae SauepUNOG ajcnop BUIAEL sapuepa Aq paqyuaraudad ase pyp spoeg ay FOHS4 gas a GB IBAB JOO a 40 WONdussap e Jo y xIpUaddhy opaa AOUE JOU QB eoa BUOdO apun ageeae SBoeip 241 SSS JO Po 34 Op EW YOOLD I4 PADUS USL WaUESISsy TINCMOWOES Wess PUL Nos gun suo suaKa 4o Ta a E BU LAAOP JOOS aa pA LO AUW ajd BU UO way suo guag g ayy uo pa uosuapya Soo L ayy peon al UOEUSKA SU PROIUN JON 280p Vana SIUL S00 UAUESSSSy Meas
24. Centerline SCLnoMCL A channel width multiplier used to create a buffer around the stream centerline for reaches where no meander centerline is present If the value is zero no buffer will be created Valley Toe ValleyToe A channel width multiplier used to create a buffer around the toe of the valley walls If the value is zero no buffer will be created Require Valley Walls RequireVW Permissible values are Y Yes or N No defining whether the valley toe feature must be present for a given reach to perform buffering of the meander centerline f the value is Y buffering of the meander centerline will only be performed if the valley toe feature is present for the reach If the value is N buffering of the meander centerline will be performed at all times regardless of the presence of a valley toe feature Note The channel width is calculated in Step 08 A channel width multiplier is a value that is multiplied by the channel width to arrive at a buffer distance April 2006 Step 09 Calculate Stream Corridors Buffers Page 140 When buffering is perform via this step the various combinations of data associated with a given reach are used to find a record in the buffer reference tableassociated with Step 9 The search goes from very specific combinations of the data to the most generalized form or default parameters to be used if no specific combination is found This permits one to define very specifi
25. Data Entry Review of Reach Point Data Page 154 Step 10 Set Map Documentation Fields Clicking on the Set Map Doc button on the dialog for Step 10 will establish the following map documentation fields for each reach USGS Quad Name VT Orthophoto Town Name HUC 10 Watershed Name When one clicks on the Set Map Doc button the dialog as shown below will be displayed Part B Step 10 Identify HUC10s Towns Quads Orthos for Reaches Identify Towns Quads and Orthophotos that each reach falls within Select Type of data to be associated with each Reach Point M HUCIOfs Theme used for HUC 10 Identification sOOhuc1 Obndry shp V YT Orthophoto s Theme used for YT Orthophoto Identification ytorthos shp P USGS Guacls Theme used for USGS Quad Identification Required field not selected M Towns Theme used for Town Identification Not Registered Identify the type of data to be associated with each reach point by clicking on the corresponding check box until a check mark appears If a check box is disabled therequired theme has not been registered Theme to be used is shown to right of check boxes Multiple selections can be processed at the same time Required Input Output Themes Surface Waters S05SWFinal shp TE Surface Waters clipped to Sub Watersheds to Reach Paints SO6RPts shp Theme for Reach Points to be used The HUC 10 Ids and Id s of the YT Orthophoto s that a reach falls within will
26. Data field if any dashes if none Varies with Fidivade Number ie lo Data value for Fid1Name Fid2name Character 10 Name of second Impact Data field if any dashes if none Varies ne impact _ Data value for Fld2Name a s value for Fid2Name oo 2 nnn Fid3value Character 36 0 Not currently used o Fid4name Character 10 0 Not currently used o Fid4value Character 36 0 Not currently used o Swtheme Character 32 0 Name of surface water theme used during indexing of impact Swdate Character 10 0 Date surface waterthemewascreated FEntrydate Character 10 o Date observation was entered imo SGAT teron Number fie 2 Forpoyines eng of mpact Character Upon Completion Upon completion of the export a message similar to that shown below will be issued SGAT Info GeoSW FITExport IbtExport click xj FITE sport dbf sawed in directory H Geomorphalogy version DernvdD ata Table has NOT been added to Arcyiew Project The export table FITSegExp dbf will be located in the DerivdData directory under the directory in which the ArcView project is located Note If the source of the themes used during the export is from Step FITOOa the name of the export table will be F TRchExp dbf April 2006 Part E Step FITO03 Export Feature Data Page 221 Click on the button labeled Done to return to the Main menu dialog for Feature Indexing April 2006 Part E Step FIT03
27. Do vou want the registered themes added 28 View SGAT from prior use of the Tools was not found but that View If the user selects Yes then all themes which have been registered will be added to the view during this step of the initialization procedure In adding the themes to the view a basic legend associated with the alias for the theme will be used If the user selects No then the view will have been created however no themes will be present in the view If it has been determined that the ArcView project directory has changed from the last session the user will be provided with the opportunity to load the registered themes into the User View 2r Project directory differs from last use of the Tools Do you GD want the registered themes added to View SGAT Note If an ArcView project file along with the themes tables referenced is moved to a different directory the user is prompted to locate each theme table referenced For each April 2006 Accessing the Stream Geomorphic Assessment Tools Page 52 theme table one must migrate to the new directory and identify the specific theme or table The opportunity to add the registered themes to the view as noted in the above message will automatically load those themes tables even though the location of the ArcView project file has changed Regardless of whether the User View is to be recreated each theme or table that is registered will be loaded in one of th
28. DocGUIs are removed thus leaving a pure ArcView environment April 2006 Accessing the Stream Geomorphic Assessment Tools Page 56 When one exits the SGAT extension it remains loaded as signified by the button with the squiggly line on the button menu when the active window is the project window or a view The extension can remain loaded while editing is performed the project is saved or ArcView is closed Any number of anomalous conditions may occur if one attempts to edit a theme attribute table or dBase table while the SGAT extension is active The extension will be active until one clicks on the Exit button on the Setup dialogs It is not possible to detail all combinations of events that can cause problems As a result it is best simply to follow the general guidelines of not editing while SGAT is active Note When assigning the Trib ID s in Step 04 always exit the SGAT extension Do not save the project while the SGAT extension is active Doing so will result in the hidden DocGUrs being saved with the project While this is generally not a problem these hidden DocGUTIs may cause problems if other extensions are used in the ArcView project When one clicks on the OK button for the above message the ArcView project window will be minimized and the icon representing that window will be displayed on the bottom left area of the ArcView window This is done to emphasize the concerns expressed above When one clicks on
29. Los Meander Centerline w meee Dangling Segment of Q Meander Centerline Sub watershed Boundaries 7 A meander centerline must be present in a given reach for which segmentation has been performed in order to develop a fluvial erosion hazard zone using the application of FEH Option 2 A meander centerline may be present in all other reaches 8 A meander centerline may be present in a given reach in order to develop a fluvial erosion hazard zone using the application of FEH Option 1 9 Meander centerlines do not have to be contiguous or continuous For example one may be digitizing the meander centerline for a tributary and come to a confined valley At this point one can stop digitizing the meander centerline If the tributary subsequently flows into a wide valley one can draw another meander centerline for that valley In such situations however remember the other rules listed above 10 A meander centerline will be used in the development of stream corridors via Part B Step 09 if and only if valley walls are present for the same reach If the above rules for digitizing the meander centerline are not followed erroneous data will likely be generated Where certain conditions are detected error messages will be issued in Part B Step 09 and Part D Step FEHOS Reach Segmentation Points The User must provide an ArcView shape file containing points defining break points or Phase 2 SGA reach segmentation points for
30. Measure to be used Linear Units Feet x Buffer Theme to be Created Output Theme sO yvw54 To be saved in h geomorphology version2 hapeFiles Recommended that you prefix output theme name s with SO to facilitate selection Status of Reach valley line is in subsequent steps being calculated for Percent of Step completed Calculating M05 valley line 10 of 113 Please wait 8 Stop AE Sa start A 2 AR E A RA gt 3 versionz arcview GIS 3 fi Step07 doc Mic EQOSdom se QF Mo 557m April 2006 Step 07 Calculate Valley Line and Data Page 131 The algorithm developed for calculating the valley walls is fairly complex and was tailored through testing in a wide range of valley wall delineations However there may be conditions under which the algorithm will not be able to define a valley line properly When such a condition is detected an error message similar to the following will be issued 17577 Calculation error 1153 Valley split by sub watershed boundary Cannot calculate Valley line for Reach Pt MOS Do pan want to continue with other Reach Pts When such an error occurs no valley line will be created for the reach identified in the message In addition the message provides the user with the opportunity to bail out at this point or continue If the No button is clicked the valley lines that have been created thus far will be saved in th
31. Operation column can be deleted 2 When the entry is highlighted the Delete Note button will be enabled Click on it to delete the selected comment or note After the above the following message will be issued 1079 The selected record will be permanently deleted from the System Log if you continue Do you want to Continue Click on Yes to delete the selected note or No to cancel the deletion To remove the selection of a note for deletion click on the Cancel button April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 75 The Tools Main Dialog The Main Dialog for the Tools extension is shown in the figure below This dialog serves as a table of contents into the major components or groupings of the Tools Stream Geomorphic Assessment Tools Main Dialog Sub Menus for Geomorphic Stream Assessment Tool Optional Tools for Checking and Building Themes Part 4 Data Development for Primary Watershed Part B Data Development for Sub Watersheds Part C Soils Land Cover and Density Analysis Pat D Steam Segmentation Part E Fluvial Erosion Hazard Analysis View Log Processing steps for Parts A B C and D are described in the following sections The Optional Tools are described in Appendix A Directions for processing Step E can be found in Appendix J Each of the buttons will in turn display a dialog showing the corresponding processing Steps As described ear
32. Phase 2 segments Incorporation of four steps within Part E that provide the ability to create the Fluvial Erosion Hazard FEH zones Modification of error messages to include a unique error number A Microsoft Access data base has been developed to include the error number message format message example and reason s message will be issued The data base is intended to be dynamic and facilitate adding more specific reasons for the occurrence of errors identified during technical support Ability to edit limits imposed in Step 10 for Channel Widths Elevation Valley lengths and Valley Widths via a system dialog Removal of Step 00 and the calculation of the VTId in Step 06 Other fixes and minor modifications were performed as needed Version 4 5 incorporated the following major enhancements Part D was subdivided into two sections Reach Segmentation developed in Version 4 0 and Feature Indexing Four steps are provided for Feature Indexing o Step FITOO provides capabilities for interactively indexing point e g grade controls alluvial fans etc and polyline e g erosion straightening etc features to the surface waters o Step FITOOc permits one to modify certain data associated with indexed features o Step FITO1 permits one to segment indexed features to correspond to any reach segmentation performed o Step FITO2 provides the capability for one to extract specific indexed features and potentially to offset th
33. Step SEGOO Setup Surface Water Theme Page 194 STEP SEGO1 Segment Reaches Processing will take points from a user supplied theme and project them onto the surface waters for a given reach The polylines representing the surface waters will then be broken at the location of the projected point The user supplied shape file must contain point features that define the approximate location at which the reaches are to be broken There is a limit of 702 to the number of segmentation points that can be associated with a given reach It is however expected that the number would normally be 5 or less Each point in the user supplied shape file must have two attribute fields one containing the Reach Point Id associated with the reach that is to be segmented and the other is a unique identifier for each segmentation point The field containing the Reach Point Id is used to ensure that the proper surface water polyline is being segmented The unique identifier for the segmentation points can be a sequential number or letter that restarts with each reach It is used solely in error messages if any errors are detected thus enabling the user to identify which segmentation point is associated with the error The figure to the bottom left illustrates one segmentation point labeled 1 that will be used to segment reach M11 The figure to the right illustrates the themes created or modified via this processing step The segmentation point at 1
34. User Type Implementation of an Application Required directory structure System Tables to maintain data on processing steps performed and to control the operation of the Tools An Alias in referencing themes tables and required field names in a theme or table o Theme table registration by the user for source data sets and by the Tools when creating a theme table and o Logging of processing steps and activities performed O O O O O All of the concepts have been implemented in the underlying software for the Tools User Type Considerable flexibility has been incorporated into the Tools This flexibility has broadened the applicability of the Tools to enable research analysis and testing of new concepts in Stream Geomorphic Assessment and to provide assistance in planning issues for local governments Given the flexibility available it becomes necessary to limit the scope of the Tools in order to provide users with only those capabilities required to perform their tasks This is accomplished by the implementation of a User Type There are four User Types System FEH Fluvial Erosion Hazard Regional Planning and Watershed Group with access as described below Watershed Group is restricted to the functions associated with stream geomorphic assessment Regional Planning is permitted access to certain additional system functions and stream geomorphic assessment FEH includes the capabilities provided for Regional Planning
35. a single version select the alias from the drop down list in the upper left of the dialog Then select the appropriate setting in the panel for Multiple Versions Allowed Yes enables multiple versions to be created and No restricts the alias to having a single version Note Only derived data sets will be included in the drop down list of aliases April 2006 Organization Page 41 Affect of Multiple Versions on Dialogs for Processing Steps The setting for Multiple Versions of an alias will be reflected on all dialogs for which the associated data sets are used either as an input or created as an output An informational note will be displayed on the dialog to the right of each control for an input or output data set This note will indicate the status of available data sets and provide guidance in selecting a data set where applicable The following illustrates the location and examples of the notes Part 4 Step O1 Dissolve Sub Watersheds into Overall Watershed Input Themes Sub Watershed s00subwehed shp N Theme for Sub Wyatersheds to be used Dialog Controls Primary Overal Watershed Theme to be Created Gutput Theme cot Watershed shp Theme will be created upon completion of this Step To be saved in h sgeomorrphologyyversions4D envdD ata Note for insertion into System Lo User Mote Dissolve Single Version When a data set is being created and the alias is restricted to a single versi
36. above error actually occurred due to the assigning of sub impacts to an impact that previously had none thus the value of means no value or a blank value When errors such as the above are issued for either the sub impact or location fields one will have the option of leaving the erroneous sub impact or location as is or selecting a current value If a current value is selected that becomes a change which can be made permanent by clicking on the Save button Upon Completion Click on the Done button to return to the Main dialog for feature indexing April 2006 Part D Step FITOOc Feature Data Modification Deletion Page 213 STEP FIT01 Feature Segmentation This dialog provides the capability of subdividing impacts indexed via Step FT00a into reach segments that are defined via the reach segmentation dialogs For point impacts this basically assigns the reach segment identifier For polyline impacts the polyline will be broken at reach segmentation points The reach segment identifier will be assigned to the corresponding polyline Part D FITO1 Segmentation of Features Indexed and or Assignment of Segment Id Input Theme Point Impact FIT OOPtmpact sho Theme for Impacts Point Features to be used Polvline Impact FT OOLnImpact shp Theme for Impacte Polyline Features to be used Segmented Sw SEGOISWSEGOT shp x Theme for Segmented Surface Waters to be used Segemented Themes to be Create PE Impa
37. and facilitates software distribution e Incorporation of the Floodway Determination application e Tracking of processing results and errors via a log e System Functions area permitting modification of channel width regression equation parameters based upon upstream drainage area reach point formatting establishing modifying units of measurement to be used log management and control of the number of output versions e Added verification for detecting digitizing errors e Single point for identifying the user view to which output themes are added The basic processing steps of Version 2 remain in version 3 However the need to identify a view the input themes tables and the output tables has been removed from the individual processing steps April 2006 Introduction Page 1 Version 4 incorporates the following major enhancements and or changes Modification to the calculation algorithm in Step 07 to more accurately depict valley lines Modification to Step 10 to include a function that will assign to each reach the Town Name Ortho Photo Ids USGS Quad Names and HUC Watersheds within which the reach falls Addition of Step 15 to calculate densities number of points total lengths and or total areas that fall within stream corridors and or sub watersheds Densities are calculated for both reach and upstream drainage areas Incorporation of two steps within Part D that provide the ability to segment a Phase 1 reach into
38. are Data Source Types Drives Feature Data Source c Valley Wall Delineation These will be provided via digitizing and must be of polygon class Valley walls need not be drawn for all sub watersheds Multiple polygons can be drawn to represent valley walls However to be used by the Tools the valley wall polygon must include the reach point and its immediate upstream neighboring reach point which is associated with the same Tributary Identifier See Step 04 for Tributary Identifier explanation If only one of the reach points is included in the polygon the valley walls will be ignored for that sub watershed or reach point If multiple polygons are drawn to represent valley walls it may be necessary to overlap the polygons to ensure that each pair of reach points is included within one and only one of the polygons For example if polygons were drawn to encompass reach points M01 and M02 and another polygon for M02 and MO3 the polygons would have to be drawn such that they both included reach point M02 i e overlapping each other at that reach point as shown in the following figure April 2006 Setting Up for Using the Tools Page 25 Reach M01 Overlapping Polygon at Confluence Points OVERLAP SECTION OF VALLEY WALLS L Valley Wall Reach Points Reach Points C Valleywall_qa shp A Surlacewater Surfacewater Reach MOZ A If a pair of reach points is included in more th
39. associated with specific Impacts and for Feature Indexing in Part D SysLimits Contains the upper and lower limits imposed during editing in Step 10 for Elevation Channel Width Valley Length and Valley Width Modifications to these limits can be made through a system dialog System Functions gt Edit Limits for Step 10 SysLog Repository of log entries for user notes entered actions taken or processing steps completed The results of the processing steps are noted and include identification of any critical errors encountered SysRptForm Maintains the current format being used for assigning reach point identifiers in Step 06 Calculate Reach Points User modification is allowed via System Functions gt Format Options for Reach Point ID s SysStatus Source theme table status per VCGI User can select the status associated with a source theme table during registration Defines permissible sub impacts associated with specific Impacts and for Feature Indexing in Part D SysSystem Maintains current system environment of the Tools User Type and Access Level Application and User View to enable seamless operation between different sessions with the Tools SysUnits Maintains units of measure to be used in calculating lengths and areas in the Tools and the Map Units to which views are to be set These units can be set via System Functions gt Measurement Units Included in the table also are the conversion factors from a view s Map Units to t
40. be created Note In certain applications multi part polygons are a valid representation of a real world situation For example a parcel can be divided by a road or a stream The parcel is represented by a single shape a multi part polygon in which one part lies on one side of the road or stream and the other part lies on the other side In the nterim theme created for use in resolving errors multipart polygons are broken up so that each polygon is represented as a single shape record in that theme If however parts of a multi part polygon share a common boundary those polygons are merged into a single polygon April2006 Step 01 Dissolve Sub Watersheds into Overall Watershed Boundary Page 85 Step 02 Extract and Clip the Surface Waters to Primary Watershed This step performs a number of operations which are summarized below e Extracts linear surface water features where necessary e Clips surface waters to overall watershed boundary and e Identifies the pour points outflow points for the overall watershed This point isthe one point at which the surface waters intersect cross over the overal watershed boundary To access the dialog click the button labeled Step 02 Extract Linear Surface Waters and Clip to Primary Watershed in Part A main dialog The dialog is shown below Part A Step 02 Extract Linear Surface Waters and Clip to Overall Watershed Primary Overall Watershed Theme ee
41. cases those polylines may be exceptionally short i e a few meters long This can make manual selection of the stream segments as is required for Step 04 difficult The figure to the right illustrates what occurs in this step The three streams which have been labeled have exceptionally short segments These segments would not be visible without zooming it to a very large scale This can lead to incomplete selection of all segments belonging to a given main stem or tributary which is required in Step 04 S a8 ge are SE ES This step concatenates stream segments between reach points and or point of confluence into single segments As a result greater ease Two segments and efficiency in performing subsequent steps is combined achieved To access the dialog click the button labeled Step 03 Combine Stream Segments between Points of Confluence in Part A main dialog The dialog is shown on the next page IMPORTANT NOTE If you have already assigned tributary identifiers and find that you have to go back due to an error in the sub watersheds or surface water and re run Steps 1 3 you can avoid having to re assign the tributary identifiers by using the following procedure Highlight the SO3swcomb shp shape file that contains the tributary ID s Make sure none of the polylines within the theme are selected or highlighted On the ArcView toolbar select theme and then Convert to shape file Sa
42. coverage for boundary theme i e W gt sub watershed or C gt Corridor An example of a name would be S12LC dbf for LcLu within the stream corridors As one selects the different combinations of radio buttons for the type and area it is possible that the following error message will be issued SGAT User Error 1031 GeoSW Common RegData x Stor 1037 Input Theme for LeLu Clipped to Corridors must be created registered before this function can be used The above error message simply means that the input theme required for the selected combination of radio buttons does not exist i e it has not been created via Step 11 If the data set identified in the message is required return to Step 17 and select the same combination of radio buttons and perform the Clip operation When you return to this dialog the error message for that data set should no longer be issued Note The above error message will also be issued if the themes for soils or LcLu or the tables for the Soils Top 20 or the LcLu Codes have not been registered Refer to the sections entitled Required Source Themes and Theme Table Registration and Management April 2006 Step 12 Summarize and Attach Descriptive Data Page 165 The default or pre selected set of radio buttons for the dialog is LcLu and Corridors As a result the above error message may be issued prior to the display of the dialog i e after the button labeled Steo12 Summarize an
43. dBase table that can subsequently be imported into the DMS data management system used to maintain the tabular data associated with geomorphic assessments April 2006 Part D Feature Indexing Page 199 Access to these steps is provided by clicking on the button labeled Part D Stream Segmentation and Feature Indexing on the Main Dialog The Part D Main Dialog as shown below will be displayed Part D Main Dialog Reach Segmentation Feature Indexing FITOOc Feature Data ModificationDeletion FITOT Feature Segmentation FITO Extract Feature s FITOS Export Feature Data View Log Done Clicking on the buttons for Steps FITOO FITO1 FITO2 or FITO3 will display the corresponding dialog box for that step Clicking on the button labeled Done will return you to the Part D Main Dialog April 2006 Part D Feature Indexing Page 200 STEP FIT00a Setup for Feature Indexing Feature indexing is a method where real world features referred to as impacts can be geographically located and identified with respect to affected surface waters For example one can identify the locations of specific grade controls e g dams water falls etc or lengths of streams along which an impact has been encountered e g straightening erosion etc This permits a variety of analyses to be performed as well as permits the development of maps displaying various impacts To perform indexing of impact fea
44. delineations will have to be acquired in shape file format of polygon class The delineations may be developed through on screen digitizing or through the use of the Spatial Analyst extension to ArcView 2 Valley wall delineations will have to be acquired in shape file format of polygon class The delineations will have to be developed through on screen digitizing 3 Delineation of the meander centerline will have to be acquired in shape file format of polyline class The delineation will have to be developed through on screen digitizing 4 Phase 2 reach segmentation points will have to be identified if reach segmentation is to be performed The points may be developed via on screen digitizing In the processing steps where these themes are used digitizing requirements will be provided Setup Installation of the Tools ArcView Extension The Stream Geomorphic Assessment Tools is provided as an extension to ArcView 3 2 The name of this extension is GGoSW4 avx To make the extension available it must be copied to the Ext32 subdirectory under the directory in which the ArcView software has been installed For normal installations this would be located at the following path C esri av_gis30 ArcView Ext32 Note If you are unsure as to where the Ex t32 directory is located you can use the Find program on the Start menu of Windows 98 or the Search program on the Start menu of Windows 2000 Simply enter Ext32 as the file or folder to s
45. duowoas a4p40 shoeip ayy pKa IRA uong S14 UO uwao uopng yy UO HUIS Mawon HAU favo Sl u uo phg Suo 2 Sey pra Roeg UIE py aug pawa Soge i S E349 Ao AKA OLAPIGE SUL CSE YoU 401 Kop a usad pA po dags AO uong a4 uo Buoys ED HUE 27010 da Jo SHoRIp o 88098 saphod Wn Ul BO BIp BU y pE J JO 50jep ayy yia paywWesaid aq jih JUW PUBL 400 BY UL JES paqe WONG e sey poeg dnyasrdnpeys aUL GL tL days Hoje BOB aed ay 07 MOA LUA EY A BURSEI SHOEIP Auguefg 24440 pea WOU a qe IeVe A Ao BOR WER Fs a4 uo oy MEd palage Yong ayy uo Bupa ig adua dod dnak oul soep P D S3 0 LOHJA Zh OL 80 90 das das days days days e amp OH AA OOH Jd El l 50 0 oo co days daps days days days days days days Oe d a Hed AE T Hd 0o puodo geg UEH ITOS CUO YSS opg dyas dnpes S O JUSLUSSeSSY DIUCIOWOeS wess euyy JO Ayas iH Boeg zae Peele parta g 24 eL Saal uoaa y aqe away Page 36 SLAC Se A dp sayy poq abn draal pun JUa WANES 21545 ILEJE 4 LICE Whi UWE Pl dd H7734 19 SuUOndC je wu 4 Organization OF dats 40 SY Up AINJA MO pag fae SUONSUN WaeAS April 2006 Common Dialog Operations Messages in the Tools Extension The dialogs were designed to function in a similar manner to minimize the learning required In addition certain features have been incorporated to assist in the use of the dialogs Each of these common features is describ
46. field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data The overall watershed boundary is used to select and clip those surface waters which fall within the boundary In other words the resulting theme will be a subset of the much larger source coverage This reduces the number of polylines that are involved in subsequent steps April 2006 Step 02 Extract and Clip the Surface Waters to Primary Watershed Page 86 The one place where the surface water crossed the exterior watershed boundary is called the outflow As a result it is imperative that the intersection points determined here fall on the same point for the sub watershed boundaries Specifically the overall watershed boundary obtained from Step 01 must be used as an input theme for this step In addition the older surface water themes provided by VCGI contain entities defining lakes including ponds islands banks of rivers streams dummy lines tile lines and network lines To perform the geomorphic assessment only the linear features may be used Therefore if you are using the old themes you_must use the Extract Selected Linear Features to select only those features required Note If you are using the 1 5000 Vermont Hydrography Data VHD set you DO NOT need to extract any entities Make sure both boxes are un checked and process The figure to the right ill
47. field will not be registered until the Save button is clicked Take the time to ensure that the correct field has been selected Incorrect selection will cause error conditions in subsequent processing steps that may be difficult to interpret Note The Field Name need not be defined at the same time as Theme is selected However the theme will not be considered registered until all required fields have been defined Note To remove a field selection click on drop down list for field and select Not Selected Whenever a theme is selected or changes to data on the dialog have been made the Save and Cancel buttons will become enabled Any selection or changes will not take affect until one has clicked on the Save button If one clicks on either the Cancel or Done buttons after selection or changes have been made the following warning message will be issued SGAT Y N 1057 GeoSW Reg Theme IbtCancel Click 1057 The last changes have not been saved IF you continue they will be lost Do wou want to Continue If the changes are to be canceled click on Yes in the above messages Any selection or changes made will be ignored If the changes are not to be canceled click on No This will return to the dialog with the changes remaining To save the changes click on the Save button The following illustrates the completed dialog for registering the soils theme Registration Theme definition for Soils Shape File Hame
48. form the basis for valley lines The valley lines and associated data will be created in Step 07 e The stream segments that were assigned a tributary identifier in Step 04 will form the basis for stream corridors The stream corridors will be created in Step 09 To access the dialog for this step click the button labeled Step 05 Clip Linear Surface Waters to Sub watershed Boundaries on the Part B main dialog The dialog for this step is illustrated below Part B Step 05 Clip Linear Surface Waters to Sub Watershed Boundaries Input Theres EET Theme for Sub Watersheds to be used sub Watershed 00subwshed shp Surface Waters SqaswComb shp Meg for SAW Combined between confluence pts to be Surface Water Theme to be Create a Ta Existing Theme 5055W Final shp for Surface Waters ALLE nerna s055WFinal shp clipped to Sub Matersheds will be replaced To be saved in h geomorphologyversions D envdD ata Note for insertion into System Lo User Mote April 2006 Steps 05 Clip Linear Surface Waters to Sub Watershed Boundaries Page 112 To use this dialog e The theme representing sub watershed boundaries will be displayed e The theme for surface waters combined between points of confluence as produced in Step 03 and to which the tributary identifiers should have been added in Step 04 will be displayed e The pre defined name for the output theme that will contain the surface water segme
49. input theme and the input relational table The following attributes are included in the table created RehPtld Reach point identifiers copied from the input theme Tribld Tributary Identifier for the main stem tributary associated with the reach point for the stream corridor or sub watershed Values copied from the input theme GeoSWArea Will contain the sum of the areas for a soil mapping unit or land cover within the given boundary area stream corridor or sub watersheq CordrArea Will be included if the boundary theme used in Step 11 was stream corridors from Step 09 The values for CordrArea will be the area of the stream corridor and will be copied from the input theme SubWSArea Will be included if the boundary theme used in Step 11 was sub watersheds The values for SubWSArea will be the area of the sub watershed and will be copied from the input theme April 2006 Step 12 Summarize and Attach Descriptive Data Page 166 Note The CordrArea or SubWSArea are included to facilitate user calculations of area percentages following Step 12 and or Step 13 The following fields are included in the table created to verify proper table selection in subsequent processing steps and to provide internal documentation as to the derivation of the table BndryType Indicates the area for which data is being summarized i e the boundary theme used in Step 11 Possible values are sub watershed or corridor Value copied from the
50. is first opened Not Selected will be shown for the data theme To select a theme click on the down arrow on the right side of the control This will result in the display of Select Shape File as shown in the figure below Data Theme and Extraction Criteri Theme Not Selected Data Values l Fress Shift key to select multiple Units ae To select a shape file from the hard disk click on Select Shape File This will result in the display of the File Select dialog as illustrated below A Select shape file to be used in calculating densities x File Mame Directories 0K h geomoarphologyversion4 basedat Py exp s00bas3 shp gt bh Cancel Py exp01s00subwshed shp gt geomorphology fy marshfieldesite shp gt version4 G monktonesite shp G G c FA monktonrds shp nwi 4 shp rchzegpts shp 00bas3 sho x List Files of Type Drives Shape Files h April 2006 Step 15 Calculate Densities Page 185 Use the right side of the File Select dialog to migrate to the directory in which the shape file is located Then use the left side of the dialog to select the actual file When the shape file has been selected it will be entered into the data theme control The Density Units control will be populated based upon the feature type for the selected shape file units for Point features feet for Polyline features and sq miles for polygon features If the selecte
51. is projected onto the surface waters and the two segments labeled A and B result from breaking the surface water at the projected point For more examples of how to create the segmentation point shape file refer to section Required Source Themes in this user manual M12 X Reach Point g Xx Reach Point g Z Z B 2 C ker D Segmentation Point 2 Segmentation Point gt AMA _ p Reach Segment M11 Reach Point M11 Reach Point April 2006 Part D Step SEG01 Segment Reaches Page 195 As reach segments are created they are assigned a sequential identifier beginning at A at the downstream end The identifier is incremented as one moves upstream to B C etc The sequence restarts at A for each reach This segment identifier is maintained in the attribute field named AchSegld The combination of the reach point id RchPtld and the reach segment id RchSegld provides a unique identifier for each segment If a reach is not segmented the segment identifier will be a single dash Note The identifier formed by appending the value for the RchSeg d field to the value of the RchPtld field is used to form the unique identifier for a reach reach segment This processing step creates one new theme which will contain the segmentation points as projected onto the surface waters In addition the surface water theme will be modified to reflect the segmentation of reaches To access th
52. it becomes essential to alter that value it will have to be performed by manual editing of that table Note The unit of measurement for areas is managed via System Functions gt Measurement Units The area of each polygon is compared with this value If the area is less than the MinArea value then a potential error condition is set The GeoSWRevu field will be assigned a value of A for the polygon record to indicate that it falls below the MinArea value This test is used primarily to detect sliver polygons i e small polygons that are a result of digitizing errors It may be possible that an actual sub watershed can be delineated with an area less than that set for MinArea For such cases this error should be ignored Multiple boundary segments Under normal conditions neighboring polygons sub watersheds will share only a single common boundary In some cases however they may share more than one common boundary An example of such situations is shown in the figure on the next page In the figure there are two situations in which neighboring sub watersheds surround an intervening sub watershed As a result the neighboring sub watersheds share two separate and distinct common boundary segments This obviously is not an error However if the intervening polygon was a Sliver polygon resulting from digitizing errors it would be an error These need to be corrected prior to continuing Sliver polygons may not be visible i
53. list of derived themes tables until the desired data set is found Click on the data set of interest to highlight it When a data set is selected the remaining controls on the dialog will display the associated data This data is as follows O O O OO O Data Set Source will be either Base source theme or table registered by the user or Derived data set created by the Tools For the data sets displayed on this dialog this will always be Derived Data Set Type will be either Theme or Table dBase table Active will indicate the data set which was last created or used for the given alias This will have meaning only if multiple versions of a given alias can be created Multiple Version will be either Yes or No and will indicate whether multiple versions of data sets can be created for the given alias Note The ability to create multiple versions is controlled by a setting in one of the system tables This setting can be changed via System Functions gt Multiple Output Versions As a general rule only a single version will be allowed to avoid any confusion Note In rare circumstances multiple versions may be desirable in order to compare results For example it may be desirable to create multiple stream corridors via Step 09 to compare different buffering criteria When multiple versions are enabled the output data set names will have a sequence number appended i e S09Corridor01 shp S09Corridor02 shp etc Alias associated wit
54. meter Then you can use the dialog for Step 10 to compare the length that you have measured with that calculated in this step This step calculates the average valley width by dividing the area of the valley falling within the sub watershed by the valley length April 2006 Step 07 Calculate Valley Line and Data Page 133 Specific considerations to keep in mind while reviewing the valley line theme also include the following With the exception of confluence points valley lines are drawn from reach point to reach point At points of confluences no line is drawn to connect the tributaries Such a line is irrelevant in calculating valley length or width for either tributary Where valley lines are drawn for the terminal segment of a tributary the valley line is drawn to the terminal reach point and not to the end of the valley wall polygon Drawing the valley line to the end of the valley wall polygon would distort the valley length when compared to the channel length and therefore produce incorrect values for Sinuosity If valley lines are missing check the continuity of the Tributary Identifiers for the reach point and all of the neighboring upstream reach points If the Tributary Identifier of the reach point is not the same as one of the upstream reach points no valley line will be drawn Valley lines may also be missing due to errors encountered during processing Messages will inform the user of such errors Refer to th
55. now become the active window Click on the Table menu on the menu bar then click on Start Editing Click on the field name for Trib d in the table window The Trib d field name will appear depressed If it does not then click on it again Click in the View window to make it the active window Click on the Select Features button on the button bar Click anywhere in the view away from any stream segments This will clear any selections which have previously been made In the View window select the stream segments which are to be assigned a unique tributary identifier i e the stream segments belonging to the main stem or a single tributary The selected segments will be displayed in yellow After you have selected the first segment hold the Shift key down to select additional segments Note Selecting a highlighted feature i e one that was previously selected will un select that stream segment Work at a scale in the View window that enables you can clearly see the stream segments Be sure to un select any stream segments that have been erroneously selected especially at points of confluence After you have selected all the segments for a given tributary or periodically during the selection process click on the title bar of the table window This will make the table window the active window Don t click on any field or record in the table as that may clear the selections made Click on the Calculate button on the butto
56. or since editing began will be lost Click on No to retain the changes made If one clicks on Done or Export the user will be warned of pending changes via the message shown above All pending changes must either be saved or canceled prior to quitting the dialog via the Done button or performing an export via the Export button Warning If modifications are made in Step 10 to Channel Width do not run Step 08 again This will result in canceling any changes made in Step 10 Warning If modifications are made in Step 10 to Valley Width or Valley Length be cautious about running Step 07 again If Valley Walls have been drawn for a reach in the user supplied theme the values for Valley Width and Valley Length will be calculated in Step 07 This will result in canceling any changes made in Step 10 to the corresponding reaches Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages Step 10 Calculating Derived Data Clicking on the Calc Data button calculate data button on the dialog for Step 10 will calculate values for the following e Channel Slope If the reach point and its upstream neighboring reach point have been assigned elevations and the Channel Length is available the Channel Slope will be calculated Channel Slope is the difference in elevation at the upstream end of the channel and the downstream end of the channel divided b
57. polylines that are not connected with the first group So in effect two tributaries now have the same identifier In this case the second validation would result in the tributary identifier of T2 S1 as having two parts The results of this validation test are shown in the lower part of the Validation Results panel All tributary identifiers having more than one part will be listed along with the number of parts Review of the polylines and correction is best done using both the attribute table and the view as with the first validation April 2006 Step 04b Assign Tributary Identifiers Interactively Page 105 If no errors were detected during validation the following message will be displayed SGAT User Error 1187 GeoSW SetTribID2 bt ahte Gd x 1187 Assignment of Tributary Identifiers appears to be okay for theme 5035W Comb hp As indicated in the message the validation check indicates that assignment of Tributary Identifiers appears to be okay This does not guarantee that no errors exist A careful review should be conducted to ensure proper assignment Upon Completion Click on the Done button This will return you to the Step 04 dialog Clicking on the Done button on that dialog will return you to the Part A Main dialog April 2006 Step 04b Assign Tributary Identifiers Interactively Page 106 Step 04x Assign Tributary Identifiers Manually Proper execution of Steps 01 through 04 is crit
58. pre defined name for the output table will be displayed Note That the output from this step is a table The output table name will reflect O O The step number i e S74 The first character of the topic i e S gt soils or L gt LcLu The first character of the coverage for boundary theme i e W gt sub watershed or C gt Corridor and The step number creating the input table i e 12 or 13 An example of a name would be 14SC12 dbf for LcLu within the stream corridors April 2006 Step 14 Summarize Area by Field Value Cross Tabulate Page 177 As one selects the different combinations of radio buttons for the type area and aggregate level it is possible that the following error message will be issued 1031 Input Table for LeLu Areas Summed to Reach Corridor must be created registered before this function can be used The above error message simply means that the input theme required for the selected combination of radio buttons does not exist i e it has not been created via either Step 12 or Step 13 If the data set identified in the message is required return to Step 12 or Step 13 and select the same combination of radio buttons for type and area and perform the Summarize operation When you return to this dialog the error message for that data set should no longer be issued The default or pre selected set of radio buttons for the dialog is LcLu Corridors and Reach As a result the above e
59. reaches that are to be segmented The points must be placed near the surface water feature polyline that is to be segmented It is not necessary that the points be placed exactly on the polyline April 2006 Setting Up for Using the Tools Page 22 The Phase 1 reach break points for the reach i e the bounding reach points should not be included as segmentation points The Tools will automatically detect the reach points to be used The following figure illustrates a Reach being segmented into five reach segments View1 il Segmentpts shp a 2 SOBRPtO1 shp Tribld M Infl e ReachPtld M03 Outflow Segmentation Pts il SOOs ubwshed shp In the preceding figure four points segment reach points identify the locations where the reach is to be segmented into five parts These points must be provided by the user in an ArcView shape file theme In that shape file attribute fields must exist that contain the following a reach number identifier for the reach identifier RchPtla and b segment ID a unique identifier within the reach for each segmentation point In the above figure the value for RchPtld is M03 and the identifiers for the segment reach points are 1 2 3 and 4 The AchPtld will be used to ensure that the proper stream feature is selected for segmentation and the unique identifiers for the segmentation points are used to communicate errors to the user during segmentation Note In
60. system table SysAops dbf not found in 20 Buffer reference table SysBurSGa dof associated with Stor sustem directory H Geomorphologyversiond Test SusD atan If the dBase table is found in the SysData directory a review of the required fields is conducted If any of the required fields are missing the following error message is issued 21 One more fields missing from buffer reference table Spbu GA dbf associated with application SGA A field named Key is present in the buffer reference table The values contained within that field define a specific stream type or stream grouping and associated with that key value are the factors which are to be used in creating the buffers for specific feature types and or conditions This provides the mechanism to isolate particularly sensitive streams for special buffering However the bulk of the streams will be dealt with in a uniform manner This is enabled through the use of a key value of Defaulf In other words if a key value cannot be found to match the conditions associated with a specific reach the buffering parameters associated with the key value of Default will be used The final verification test is to ensure that a record containing a value for the Key field of Default exists If such a record is not found the following error message will be issued application SGA via system table Sys4pps dbf does not contain a record with a value of Default
61. the BaseData directory Source data sets include any data sets themes which have been digitized by the user and data sets themes and tables created or compiled by other organizations All data sets themes and tables created derived from source data sets by the Tools will be located in the DerivdData directory The Tools is distributed with a number of system tables and ArcView legend files All of these files are located in the SysData directory System Tables A number of system tables will be distributed with the Tools and must be located in the SysData directory under the directory in which the ArcView project file is located It is strongly recommended that no changes be made to any of the system tables without clear understanding of the impact of those changes Inappropriate changes will have unpredictable results including corruption of the ArcView project file and potential corruption of any data sets being used Note Some dialogs in the System Functions area permit limited and controlled changes to certain system tables Avoid making any changes to the system tables not provided through these dialogs The system tables provide flexibility in the use of the Tools control the operation of certain processing steps and carry data forward from one session with the Tools to the next The system tables are listed along with a brief description in a table near the end of this section Alias An alias is similar to a nickn
62. the DMS It may also be desirable to work with the data associated with reach points in other applications such as Microsoft Excel or Microsoft Access To accomplish this one must use the Export button on the dialog By clicking on this button a copy of all of the data for each reach point is made in a dBase table That table can subsequently be opened via the other application Note That the export function produces a table and not a theme Warning The attribute table for the reach point theme is also a dBase table It will have the same name as the theme but with the file extension of dbf Do not open the attribute table of any theme in another application Inadvertent changes may corrupt the theme making it unusable in ArcView Click on the Export Data button after all reach points have been reviewed and any additional entries changes and or calculations have been completed All pending changes must be saved prior to exporting the reach point data If changes are pending a message will be issued to that effect and will prevent access to the export function The Export function will always create a dBase table named AchData dbf in the DerivdData directory Prior to continuing with the export a check is made to determine if that table already exists indicating that the Export function has previously been run If the table is found the following message is issued SGAT Y N 1091 GeoSW Revu IbtExport Click 1091 Th
63. the Exit button on the Setup Dialog the project window will be returned to its prior state The Setup Dialog will then be displayed Use of this dialog is described in the next section April 2006 Accessing the Stream Geomorphic Assessment Tools Page 57 Setup Dialog for the Stream Geomorphic Assessment Tools The Setup Dialog provides access to all of the functions necessary to setup for using the Stream Geomorphic Assessment Tools This dialog is illustrated below Stream Geomorphic Assessment Tools er 4 00 Setup Dialog Primary Functions User Access Type and Application Designation User Type System v Application SGA v Select Application for which SGAT is to be used View to which themes will be added upon registration creation EVY SGAT i Set View Themes will be added to view shown Application Areas Theme T able Registration and Management Stream Geomorphic Assessment Tools SGAT View Log System Functions Note The options available on this dialog may vary based upon the intended use or user As a result certain controls may be predefined and disabled The use and application of the data established on this dialog however is described in this section User Type The User Type can be one of four options System This User Type is reserved for user Support personnel and certain advanced users as it permits access to system parameters and functions via the Sy
64. the Stream Geomorphic Assessment Tools Page 71 If the changes are to be canceled click on Yes in the above messages Any selection or changes made will be ignored If the changes are not to be canceled click on No This will return to the dialog with the changes remaining in place To save the changes click on the Save button The following illustrates the completed dialog for registering the soils table Registration Table definition for Soils Top 20 Attributes dBase FileName s00top20 dbf intemal Alias Used SoilsTop20 Identify Required Fields Table Documentation Select Names for 1 fields identified below Soil Mapping Unit Identifiers Field Muid Source NACS AVCGI Current As OF April 2003 Status Complete Notes Obtained with SGAT extension Table Information Location h geomorphologyiversion3SBaseD atas Log udit Records Save Cancel Done Removing a Table Registration To remove a table registration select the table to be removed from the Theme Table Registration and Management dialog Once the registration dialog is displayed click on the Remove button Note The Remove button will be enabled only if a table has previously been registered The following message will be displayed after clicking on the Remove buiton SGAT Y N 1080 GeoSW Reg TablebtRemove Click from this project This action takes effect immediately
65. the area identified with the soils data for water was one square mile and that the area of the corridor of interest was three square miles Since the area occupied by water represents 1 3 of the total corridor any characteristics developed in the cross tabulation would be significantly biased toward the values associated with water Continuing with the example the Soils Top20 table lists the flooding characteristic of water as Not Rated If water is not excluded from the soils data April 2006 Step 14 Summarize Area by Field Value Cross Tabulate Page 178 then already 1 3 of the corridor area would be associated with the Not Rated value for the flood potential This obviously would not reflect the actual condition of the corridor By excluding water from the summary the areas calculated for the fields selected to cross tabulate will reflect the areas for actual soils The area associated with water will be reported in the separate field named WaterArea Reference tables The reference tables which will be displayed in the area for Table With Field Value Names are e S00SoilXTabFields 05 dbf For use with soils refer to Appendix E e S00LcLuXTabFields dbf For use with land cover refer to Appendix F These are described in the appendices and should not be altered without a clear understanding of their use in the Tools Those who wish to use Land Cover Land Use and or soils coverage other than thos
66. the geographic location and or extent of impact and the following data e Impact Type e Reach Id s e Impact ld and e Impact Name If it is necessary to change any of the above then the impact will have to be deleted Then a new impact indexed via Step FITO00a All other data can be modified via this dialog To modify data type in or select the revised values Once a change has been made the Save and Cancel buttons will be enabled Using the Save and Cancel Buttons The Save or Cancel buttons will be enabled once any changes to data have been made This includes the deletion of an impact All changes to data or deletions are pending To make changes permanent click on the Save button To cancel all changes since the start of the session or since the last Save operation click on the Cancel button Potential Issues The lists of permissible sub impacts and locations are maintained in system tables SysSublmpact dbf and SyslmpactLoc dbf While it is not likely it is possible that the lists will be changed If either a sub impact or a location is deleted from those system tables the display of any impact to which the deleted sub impact or location was assigned will result in the following error being displayed SGAT User Error 1215 GeoSW FITMod SetSubimpa x 1275 Sublmpact value of ts no longer valid not in system Stor table SyeSublmpact dbt Select appropriate action in Sublmpact control on dialog The
67. the top of the dialog is a dropdown list that displays all of the tributary identifiers assigned thus far The list is updated if successful assignment occurs following use of the Set Trib Id button Abbreviated Instructions Available from the Dialog To review an abbreviated set of instructions similar to those above click on the nstructions button This will display a separate dialog box with the instructions listed The nstruction dialog can be closed or it will automatically be closed when the primary Step 04b dialog is closed Show View Button on the Dialog The Show View button is simply a short cut for displaying the user view If the view is already visible there will be no apparent action when one clicks on the Show View button Clearing All Trib Ids The button labeled Clear All Trib Ids is provided for those who want a clean start The value for the Trib Id attribute for all polylines in the surface water theme will be set to blank In addition the dropdown list of tributary identifiers used thus far will be emptied Validation of Continuity The button labeled Validate Continuity provides two checks to help ensure proper assignment of tributary identifiers 1 Assignment of tributary identifiers is made in a continuous manner from the outflow of the overall watershed to all terminal points where assignment of a tributary identifier stops 2 Each tributary identifier is assigned in a continuous manner The first valida
68. the user checks the option box Dissolve Surface Water the theme will be added to the view but will not be turned on automatically The figure to the right shows the Dissolved Surface Waters and the reach points While not visible all of the stream segments polylines associated with the same reach point and tributary identifiers are combined into a single polyline This theme is intended solely for use in thematic display of data pertaining to reaches or tributaries This theme should not be used for any analytical purposes Click on the button labeled Done to return to the Part B menu dialog April 2006 Step 08 Calculate Channel Width and Stream Data Page 139 Step 09 Calculate Stream Corridors Buffers This step enables one to create stream corridors or buffers using the themes for valley walls meander centerline sub watersheds surface waters and reach points The stream corridors will only be created for the main stem and tributaries i e those stream segments to which a tributary identifier was assigned by the user in Step 04 o The corridors generated in this step reflect the process described in the Vermont Stream Geomorphic Assessment Phase 1 Handbook Appendix E Users should be familiar with the information provided in Appendix E of the handbook before completing this step If the application selected on the Setup Dialog is either FEH Option 1 or FEH Option 2 then the button to access Step 09 will
69. the value of M 006 945 That would imply that the reach point is located on the tributary M and is 6 945 miles upstream from the primary pour point for the overall watershed This identifier provides an address for the reach point DnStrmRPt and UpStrmRPt These fields will contain the reach point identifiers see RchPtld above immediately downstream and upstream respectively from the current reach point UpSirmDA The upstream drainage area in square miles for each reach point identified in the PptType field as an Inflow point The values in this field will be carried over from the Primary Pour Point theme created in Step 02 SubWSArea The area of the sub watershed associated with the reach point Note A sub watershed can have one and only one outflow point That point is referred to as the reach point for the sub watershed DrngArea The sum of sub watershed areas for all of the sub watersheds above the reach point This reflects the catchment area contributing flow to the reach point Latitude and Longitude The latitude and longitude of the reach point SP_XCoord and SP_YCoord The VT State Plane X and Y coordinates of the reach point respectively SysRptType The internal system value used to control the software in Steps 07 and above Warning Unpredictable results including infinite loops will occur if values in this field are altered Attribute Fields Created for Sub Watershe
70. then continues upstream from one stream segment to the next As each new polyline is traced a sequential number is assigned to the upstream vertex The downstream vertices of all polylines connecting to that point are assigned the same sequential identifier The end result is that connectivity can be determined simply through the identifiers assigned thus providing a rapid method for indexing features i e identifying those surface water polylines that connect point A to point B When tracing if a point of confluence is encountered then the stream segment chosen will be the one forming the hardest right turn from the perspective of the direction in which stream network is being traced April 2006 Part D Step FITO00a Setup for Feature Indexing Page 203 If it is found that no other segments are connected to an end vertex stream tracing is then reversed and proceeds downstream Using the above as an outline the figure below illustrates the order of stream tracing Assume that tracing begins at the confluence point in the upper right corner and the red arrows show the upstream direction and the green arrows show the downstream direction Tracing occurs in the numerical order shown Only those stream segments to which tributary identifiers have been assigned are shown Upstream Tracing Downstream Tracing If one misses assigning a tributary identifier to a segment in the middle of the main stem or a t
71. to be extracted to the same shape file select All Locations If the impact selected is represented by a polyline feature the ability to offset the features during extraction will be enabled If an offset is desirable enter the distance and the direction The direction is based upon facing downstream A default name for the extraction shape file is entered The name is constructed of the step id FIT02 and an abbreviation assigned to the given impact One can over ride the default name by replacing the name of the shape file to be created When the extraction requirements have been established click on the Extract button If one selects All Impacts in the Impact control then all other controls will be disabled All features for a given impact regardless of sub impact and or location will be extracted All records for a specific impact name will be placed in the same shape file having a name created from the step id FIT02 and the abbreviation for the impact Note The abbreviations for the impacts are assigned during definition of the impact in the system functions To view the abbreviations click on each impact and review the name of the output shape file All extract files will be saved in the DerivdData directory under the directory in which the ArcView project is located April 2006 Part E Step FITO2 Extract Feature s Page 218 Applying Offsets The measurement units used for Offsets are in accordance with the distan
72. to develop cross tabulations for Land Cover data This appendix provides a listing of the source field potential values and names of the cross tabulation fields which will be created G Top 20 Soils Attribute Documentation October 2005 This is a reproduction of the description for the Top 20 soils attributes available from Vermont Center for Geographic Information VCGI and the Natural Resources Conservation Service USDA H The step by step approach to developing the stream corridors buffers in Step 09 is illustrated to assist those users who would like to understand the process or who wish to develop custom stream corridors I Documentation for using the System Functions provided with the Stream Geomorphic Assessment Tools extension J Processing Steps For the Development of Fluvial Erosion Hazard Zones K Development of Stream Corridor Buffers And Fluvial Erosion Hazard Zones Note The Appendices are provided as separate documents April 2006 Appendices Page iv Introduction Overview The Stream Geomorphic Assessments Tools were developed to provide assistance to organizations performing Phase of the Stream Geomorphic Assessment as specified in Draft 4 of the Handbook for Stream Geomorphic Assessment Phase I Vermont Agency of Natural Resources April 1 2005 History Version 1 of the Stream Geomorphic Assessment Tools was released in April of 2002 Key components of the software were developed under the funding a
73. values for SubWSArea will be the area of the sub watershed and will be copied from the Boundary Theme Note The CordrArea or SubWSArea are included to facilitate user calculations of area percentages following Step 12 Step 13 and or Step 14 The following fields are added to the theme to verify proper theme selection in subsequent processing steps and to provide internal documentation as to the derivation of the theme BndryType Will indicate the type of boundary theme used as depicted by the selection for Area for Boundary Theme on the dialog i e sub watershed or corridor DataType Indicates the type of data theme used as depicted by the selection for Type of Data Theme on the dialog i e LcLu or Soils SourceStep Will indicate which step created the output theme Value inserted in this step is 11 SumLevel Identifies the level of aggregation for the data Field is not used in this step however it is created for use in subsequent steps Value is set to blank Possible values are either Corridor Sub Watershea or Upstream All other data from the source theme Soils or Land Cover will be included in the resulting theme The figure below on the left illustrates the soils theme as the data theme The stream corridors from Step 09 were used as the boundary theme The output theme shown on the right below resulted from processing in this step Pr d At LL Os jj N NO Sas ay hie SAA or
74. 1 04 T1 03 T1 02 T1 01 T1 00 M22 M21 M20 M19 M18 M17 M16 M15 M14 M13 M12 M11 M10 Mog M08 M07 M06 M05 M04 M03 M02 M01 Moo RehDistld T1 009 277 T1 009 041 T1 008 501 T1 008 024 T1 007 549 T1 007 153 T1 006 132 T1 005 698 T1 005 090 T1 004 601 T1 003 870 M 016 351 M 015 673 M 014 899 M 013 968 M 013 247 M 012 397 M 011 877 M 010 587 M 009 711 M 008 559 M 008 038 M 007 278 M 006 440 M 005 176 M 004 444 M 003 863 M 003 169 M 002 598 M 002 101 M 001 414 M 000 986 M 000 638 M 000 000 April 2006 PPtType OutFlow Tribld T1 T1 T1 T1 T1 T1 T1 3 Sf 5524 52 22 552 2 2252 252522 Z zZ z oo SubWSArea 0 070075 0 058722 0 249549 0 628477 0 889277 0 510812 1 604505 1 236342 0 642182 0 363156 0 179034 0 149543 0 344307 0 227179 0 526752 3 055453 2 379931 0 268149 3 309752 3 145203 3 568017 0 400790 0 992884 1 219941 0 985904 4 041336 3 155768 1 496978 0 567072 0 589377 1 034062 0 905158 0 116192 0 415148 DrngArea 0 070075 0 128797 0 378346 1 006823 1 896100 2 406912 4 011417 5 247759 5 889941 6 253097 6 432131 0 149543 0 493850 0 721029 1 247781 4 303234 6 683165 6 951314 10 261066 13 406269 16 974286 17 375076 18 367960 19 587901 20 573805 24 615141 34 203040 35 700018 36 267090 36 856467 37 890529 38 795687 38 911879 39 327027 TotStrmLen 1773 22 1243 57 2852 15 7365 32 2786 80 8896 06 18011 68 18197 00 5190 09 2
75. 5220 0 5Po 0 013220 Po MO Mog 0 066220 tiste Qo0iia7 Te MOO 0 055220 0150n 0 014920 On WATER LESS THAN 40 ACRES aA E E E E A A E E T a a 08GB ABD NII CLO BB RIE a RIES EOD AD IRIE GOB ECE EBA LCE EOIN PERU FINE SANDY LOAM 8T0 15 PERCENT SLOPES Mprnnnnrnnnnnnnrnnnnnnnnnnn Mprnrnnnnnnnrnnnnnnnrnnnnnnnnnnannnnnnnnnnnnnnnnnnnnnn nnana Dol rrr nr nnn rrr nnn ence eee eee COLTON DUSBURY COMPLEX amp TO 15 PERCENT SLOPES SS cana A a a a E a a esos gc eed woe waa ea en eee CRG Sosa a Ura esac ua ER Vala Oud aaa A S Seer eeeeeeeecee senses sceeeceeee neces eeneeceeescecee eens cee eeneeceeeenee ces seeecee eens eee eens een eeeeeseeeeeeeeeeeeeeeee eens een eeeeneeeeeeeeeeeeeeeneeeeeeeeeeneeueeeeeeeeeeeeeeeeeereseeeereeeeeeeresueeereeeeeeereeeeeereeeeeereeeeeereeeeeereeseeereeeeeereeeeereeeeeeeeeeeeeeseeeeeeeeeeeeeeesueeeeeeeueseeeseeeeeeeseeeeeeeeseeeeeeseueeeeesseneneny PODUNK FINE SANDY LOAM a E OP nna Noten SU Se aerate team Se Ure OE een UMC E a rEN A Yeon Benny ater E Ose aad E E Rennes te Piet A Wien tt eee Rares nS tn NC ec ce ERR Var SUN Es nee E nnn oR me na ARES Com NODS soe TaOaE a MARS Niece E UDIFLUVENTS FREQUENTLY FLOODED RUMNEY FINE SANDY LOAM SO nnn nn eerereorinnnr nner oor e eee eerennnnnncreloeneee seen eeeeeseeeee eee eee e eee e eee ence geen ee ene epee eee eee eee eee eee eee eee eee eee WATER LESS THAN 40 ACRES MannnnrnnnnnnnnnnnnnnnnAnnnnnnnnnNANANNNNNANNNNNNNANANNNNNANAN
76. 581 20 3860 49 3670 31 7442 16 4084 82 4920 18 60831 07 28930 81 2744 59 26891 49 42155 61 43594 05 2751 91 19005 38 10948 07 10908 12 42194 01 40879 05 14622 83 10956 83 9085 41 18339 13 16320 62 1833 49 8409 75 ChanlLen 1773 22 1243 57 2852 15 2517 03 2511 95 2090 43 5391 15 2292 33 3207 50 2581 20 3860 49 3670 31 3578 37 4084 82 4920 18 3805 39 4488 66 2744 59 6812 88 4622 77 6082 96 2751 91 4011 58 4422 77 6677 58 3865 71 3064 43 3666 09 3013 28 2622 25 3628 58 2262 59 1833 49 3373 70 ChanlWidth 2 69 3 65 6 26 10 21 14 02 15 79 20 39 23 32 24 71 25 46 25 82 3 94 7 15 8 64 11 37 21 12 26 32 26 84 32 61 37 27 41 94 42 43 43 63 45 05 46 17 50 51 59 54 60 82 61 31 61 80 62 66 63 41 63 50 63 84 Step 10 Data Entry Review of Reach Point Data DistToStrt WSArea 48984 54 39 327027 47740 96 39 327027 44888 81 39 327027 42371 78 39 327027 39859 83 39 327027 37769 41 39 327027 32378 25 39 327027 30085 93 39 327027 26878 43 39 327027 24297 23 39 327027 20436 75 39 327027 86334 59 39 327027 82756 22 39 327027 78671 40 39 327027 73751 22 39 327027 69945 83 39 327027 65457 17 39 327027 62712 58 39 327027 55899 70 39 327027 51276 93 39 327027 45193 97 39 327027 42442 05 39 327027 38430 47 39 327027 34007 71 39 327027 27330 13 39 327027 23464 41 39 327027 20399 98 39 327027 16733 89 39 327027 13720 61 39 327027 11098 36 39 327027 7469 78 39 327027 5207
77. 6 The values to be used can be acquired by performing Step 07 through Step 06 inclusive The values will then be in the attribute table for the reach point theme One can then produce a map with the reach points labeled with the ids or obtain the values by inspection with the dentify tool in ArcView CordrArea The field for the area of the corridor must be a decimal field with a length of 16 and precision of 10 The values can be calculated using the Calculate button in ArcView All areas must be in square miles To convert from square meters to square miles divide the area in square meters by 2 589 988 11 Note An outline of the procedure to accomplish this is listed on the following page April 2006 Step 09 Using Alternative Stream Corridor Buffers Page 146 Procedure for Using Alternative Stream Corridors Buffers in the Tools Extension 1 Add the alternative stream corridor theme to the view in which the other themes for the watershed exist 2 Run Steps from 01 through 08 inclusive 3 In order to use a theme within the Tools extension it must be registered The process of registering is performed automatically when a theme table is created within a processing step At present there is no way to register a stream corridor theme that is not created by Step 09 For the time being the following work around can be used a b C m o QavoOsRg7ATATSO Run Step 09 solely to create a theme for stream corridors and h
78. AAAAAAANHANANAAANAAAAAAANANAAANANAAAAAAANHAANNNAANAAAAAAANHNNNNNANAAANNNANENENEE PODUNK FINE SANDY LOAM E E T T Mponsnnrnnnnnannnnnnnnninna shuncaueauuacaeeaneacaueaneasaspaeeaceeaneaneneaneanuenaeeauteaneeaeeeaueaueeeaueaueaeaueaueauaeeaueauauaueeaunuauesasneautagassagtagaeeesagtteueseteageegestageegetsaesageteaesaestaueeaessausausssaesageasaesagtasaeeuessetoaesatetauteasesagtautesaetageteaseaestauteatstautaateeaetagtaeassaetauateatsaagtaateaestaare SALMON VERY FINE SANDY LOAM 25 TO 50 PERCENT SLOPES ERODED Serer eeneecee eens essa nen cee eenea cee eenen sense encee eens cen eenenceneenen ces seen see eeeeneeneeneneeaeeeeeeeeeeen eee eeeeneeeeeeeneeaeeeeneeeeeeeneeeeeeeneeeeeuen ena eeeeeeaeeeeeeaeeeeereeeeeereeeueereeeeeeereeeeeereeeeeereeeeenereueeeereeeeenereeeeeaereeeeeeereeeeenereeeeen ese eeeee eeu eeeeaeeeeeeeeeSeeSKeeSONS000 00000000 000000 0000000000000 00000 000000088 COLTON DUXBURY COMPLEX 25 TO 50 PERCENT SLOPES ManannrnnnnnnnnnnnnnnnndAnnnnnnnnnnAnnInnANANNNNNANANNNNANANNNNNNNANNNNNNANNNNNANANANNNNNANANNNANANANNNANANNANNANANANNNNNANANNNNNANANNNNNANANANANANANNNNNANANNNNNANANNNNNAANNNNNNANANNNANANANNNANANANANANANANNNANANANANANANANANANANANANANANANANANANANANANANANNNANANANANANANNNNNANANNNINANANANNNANANANANANANANNNANANANNNANANANANANANANNNANANANNNANANANNNANANANNNANANENNNNNANEN M MOO 0055220 05w 7 008087 w MoO 0055220 M5CoD 0 000173 Cod MOO 0 055220 i 015Ud 0 004340 i Ud MOO 0 055220 O15Ru 0 001660 Au MOO 0 05
79. Are you 1080 All references to the Table s00top20 dbf will be removed Sure Vou want to remove this Table Clicking on No in the above message will abort the remove operation and will return you to the table registration dialog If the table is to be unregistered click on Yes After the table has been unregistered it is also removed from the ArcView project The following message will then be issued SGAT Y N 1078 GeoSW Reg Table btRemove Click E ON 1078 Table 00top20 dbf has been removed Do you want to clear the ester log file of primary entries for this theme April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 72 lf the table being unregistered has been used in any processing steps select No This will retain the entries in the log should they be needed at some future point for support or simply seeing the order of events that have taken place Clicking on Yes will remove all og entries pertaining to the table Managing Derived Themes and or Tables Derived themes and tables are as the name suggests derived from the source themes and tables discussed in prior sections The derived themes and tables are the output or result of the processing steps within the Jools Note If no changes are made to the environment e g units channel width parameters etc or the source themes tables re running a processing step should produce the same result The dialog shown below provid
80. Chan Width Width of the channel in feet per equation c a x e The default calculation of the channel width is through the equation 0 0 10 18 DrngArea Where DrngArea is in Square Miles from Step 06 and Step 02 Note The constant coefficient and exponent in the equation can be modified by via Setup Dialog gt System Functions gt Channel Width Calculation Note The user may subsequently alter the values for Channel Width in Step 10 If altered the derived value for Valley Confinement must be re calculated in that step Warning If modifications are made in Step 10 do not run Step 08 again This will result in canceling any changes made in Step 10 TotStrmLen Total length of all streams within the boundary of the sub watershed served by the reach point ChanlLen Length of channel in feet for the main stem or tributary from the reach point to the next upstream reach point ChanlSlope Channel slope is the difference in elevation at the upstream end of the channel and the downstream end of the channel divided by the Channel Length Elevation of the reach points can only be entered in Step 10 following completion of Step 06 The values will be calculated if the elevation data is available ChanlSnuos Channel sinuosity is the Channel Length ChanLen divided by the Valley Length ValyLen The values will be calculated if Valley Length information is available from Step 07 or Step 10 Note The us
81. Data is being Summarized C Soils C Sub Watersheds Land Cover Land Use Corridors Theme with data to be summarized from Step 11 Theme Not Registered x Themes required for LcLu Clipped to Corridors has not l been created or registered Relational Field Gridcode Relational T able dBase containing descriptive data for theme e g Top20 dbf lable sO0lucodes dbf Table for Land Cover Land Use Codes to be used Relational Field Code Output Table dBase for Summary Data Gutput Table STAC abt Table will be created upon completion of this Step To be saved in h geomorphologyversion3 D erlydD ata Note for insertion into System Log User Note l Done To use this dialog This dialog is specifically tailored to the themes resulting from Step 11 and to the soils and land use land cover data for the State of Vermont e Select the type of data soils or land cover that is to be summarized When the type of data is selected the corresponding relational table and fields will be entered on the dialog e Select the Area for which the data is being summarized sub watersheds or corridors e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data April 2006 Step 12 Summarize and Attach Descriptive Data Page 164 Once the radio buttons for the type and area have been selected t
82. Dissolve sOOsubwshed shp N A N A 1 multi part polye 2003 11 04 05 49 29 01 Dissolve sOOsubwshedshp N A N A SubWwSld and 2003 11 04 16 59 08 01 Dissolve sOOsubwshed shp N A N A 1 multi part polye 2003 11 04 16 59 12 01 Dissolve sOOsubwshedshp N A NAA SubWSld and 2003 11 04 17 02 08 06 FPts SO02PPt01 shp SO5SWFinalshp sOOsubwshed shp AchPtld Tribld lt 2003 11 13 11 04 00 06 FPts S02PPt01 shp SO5SWFinalshp sOOQsubwshed shp AchPtld Tribld lt 2003 11 13 11 04 43 06 FPts S02PPt01 shp SO5SWFinalshp sOOsubwshed shp FAchPtld Tribld lt 2003 11 13 11 05 15 06 FPts S02PPt01 shp SO5SWFinalshp sOOQsubwshed shp AchPtld Tribld lt i l i i ee ee Note to be added to Log Note Export Log Done If one selects a specific data set a comment or note can be entered in the bottom field on the dialog Such notes can be invaluable aids in understanding any issues regarding the data sets For example during Step 01 digitizing errors may be identified These errors are subsequently corrected and Step 01 is run again It would be advisable to enter a note to indicate the type and number of corrections made for the sub watershed theme This will provide a record of how the data was developed Further if support in the use of the Tools becomes necessary such information will be invaluable A special data set named System may be found if one scrolls through the list of available data sets This is a non exist
83. Dissolve Sub Watersheds into Overall Watershed Boundary Page 81 ae aan Code Nunberofpate RR Use Potential Error Condition M Number ofparts Multi part polygon Number of boundary Common boundary between neighboring polygons is segments more than one Topology Self intersecting polygon boundary rr Polygon overlap between neighboring polygons N A Polygon area is less than minimum set in the system table SysUnits dbf Error Correction and Use of the nterim Theme It is expected that the errors can be corrected somewhat easier in the interim theme than in the original source theme Corrections for the following error conditions will automatically be applied if possible in the interim theme Topology Self intersecting polygon boundaries Self intersections occur when the boundary of a polygon crosses over itself like the shape of a bow tie or figure eight A Clean operation is performed which should break the polygon up into multiple parts Each part will then be placed in the interim theme as a separate polygon record Multi part polygons Multi part polygons will be broken up into separate polygons in the interim theme If any of the individual polygons share a common boundary segment they will be combined into a single polygon Any remaining potential error conditions will require correction by the user The following describes the potential error conditions in more detail If correction
84. F TO0a as dictated by the source to be used will be displayed The output dBase table name of F TExport dbf will be displayed and cannot be changed Enter a note to be entered into the system log upon completion of export processing April 2006 Part E Step FITO3 Export Feature Data Page 220 Export Table Format The format of the export table is shown in the following table Field Type Length i escription O Value of 1 if Phase 1 or unsegmented data from Step FITO00a Phase Number was used to create export or value of 2 if Phase 2 or segmented data from Step FITO1 was used to create export Impacttype Character 8 O Either Point or Polyline identifying feature type of impact rimpactid Number 8 o Unique numeric identifier tor impact Tribid Character 32 0 Tributary Identifier of surface water along which impact is located l Combination of RchPtld and RchSegld forming unique Rehptid Character 50 0 Reach point id for surface water along which the impact is located _ Rchseic ee C A A ahdni Bera one id if any dash if none along which the impact is Name of Impact o aie a a O Location Character 32 0 Name of Location if any Cid Date Character 10 0O Date of Observation S Person Character a6 o Person making deta Doae oe 38 0 Organization responsibie a O Desorption Gharacter 127 o Detailed description of impact Bidinan Character 10 fo o first Impact
85. J sO0soils shp Internal Slias Used Sails Identify Required Field Select Hames for 2 fields identified below Soil Mapping Unit Identifier Field Marne Muid Soll Mapping Unit Symbol Field Marne Musym Theme T able Documentatia Source NRC Current As OF Ap 20020 Status Compee O O o l Source Scale pa Hotes Downloaded from YEG in May 2002 Theme T able Informatio Location ee Log 4udit Records Save Cancel Done April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 67 Removing a Theme Registration To remove a theme registration select the theme to be removed from the Theme Table Registration and Management dialog Once the registration dialog is displayed click on the Remove buiton Note The Remove button will be enabled only if a theme has previously been registered The following message will be displayed after clicking on the Remove button SGAT Y N 1080 GeoSW Reg Theme lbtRemove Click r 1080 All references to the Table exp0ss00subweshed shp will Gp be removed from this project This action takes effect Inmediately Are vou sure you want to remove this Table Clicking on No in the above message will abort the remove operation and will return you to the theme registration dialog If the theme is to be unregistered click on Yes After the theme has been unregistered it is also removed from the ArcView project The f
86. NANNANANNNNNANANNNANANNNNANNANANNNNNANANNNNNANAANANNANANNNNNANANNNNNANANNNNNANANANANANANNANNANANNANNANANANNNAAANNANNANANNANNANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANANNNANANANANANANANANANANANANANANANANANANANNNANANANANENANENENENENEN April 2006 MOO 0055220 015Sak2 0 000299 Sak MOO 0055220 O1SCoE gt 0 010334 CoE MO 0 032967 015w 0 003609 w MOI 0032967 DI5AdE 0 008868 AdE MOI 0032967 DI5AdC 0 000809 AdC MO F 0032967 015PeC 0 004124 PeC MOI F 0032967 D15CoC 0 000487 CoC MO 0 032967 O15CoD 0 005399 CoD MOI F 0032967 0150n 0 003558 On MOI 0032967 015Po 0 002792 Po PMOT 0032967 Maud 0 00952 Ud MOI 0032967 015Ru 0 001168 Ru MOZ 0 040708 O15 004610 W IMOZ 0040708 015Ud 0 004185 Ud Step 12 Summarize and Attach Descriptive Data UDIFLUVENTS FREQUENTLY FLOODED Page 168 Possible Error Condition As each soil mapping unit or land cover land use type is summarized an attempt is made to find the corresponding record in the relational table If a record is not found in the relational table it is maintained in an internal list At the end of processing an error message such as that shown below will be issued Missing Yalues in Relational Table a xX 1 values in field Muid of theme 5112c shp were mot found in feld Muid of table top20_ vt dbf Stor Missing values in table 5125CMld dbf saved in H Geomorphology Support
87. Note Buffer To use this dialog The theme representing the valley walls will be displayed The theme representing the meander centerline will be displayed The theme representing the sub watershed delineations will be displayed The theme representing the surface waters clipped to the sub watershed boundaries from Step 05 will be displayed The theme representing the reach points from Step 06 will be displayed The pre defined name for the stream corridor output theme will be displayed Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data Note The linear distance and area units are displayed on this dialog They however cannot be changed Starting the process After the required information has been entered on the dialog click on the button labeled Buffer Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages April 2006 Step 09 Calculate Stream Corridors Buffers Page 144 Upon completion Alias of output theme for stream corridors Corridor Legend file used to display stream corridors theme Corridor avl A message will be displayed to indicate how many reach points and terminal reach points were utilized in creati
88. OSCoridorO1 shp Corridor Do vou want bo continue Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages Upon completion Alias of output theme will vary LC LcLu clipped to stream corridors LW LcLu clipped to sub watersheds SC soils clipped to stream corridors or SW soils clipped to sub watersheds Legend file used none The output theme will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This theme is added to the user view identified on the Main dialog The output theme will have all of the attribute fields from the data theme In addition the following attributes will be added RehPtld Reach point identifiers copied from the Boundary Theme Tribld Tributary Identifier for the main stem tributary associated with the reach point for the stream corridor or sub watershed Values copied from the Boundary Theme April 2006 Step 11 Clip Theme to Boundary Page 161 GeoSWArea Will contain the area of each polygon in the output theme e g the area of each polygon for soil mapping units or LcLu Type CordrArea Will be included ifthe boundary theme is stream corridors from Step 09 The values for CordrArea will be the area of the stream corridor and will be copied from the Boundary Theme SubWSArea Will be included if the boundary theme is the sub watersheds The
89. Optional Tools The tool Review Polyline Theme for Geometry GIS Errors can provide assistance in verifying that the digitizing or correction process was performed accurately April 2006 Organization Page 31 Overview of the Processing Steps in the Tools Extension The diagram on the following page illustrates an overview of the flow of data between the major components of the Tools extension Multiple processing steps are included in the areas shown as Part A Data Development for Primary Watershed Part B Data Development for Sub Watersheds Part C Soils and Land Cover Analysis and Part D Reach Segmentation and Part E Fluvial Erosion Hazard Zone The processing steps for each part are described in subsequent sections Note Access to Steps SEGOO and SEGO1 of Part D is provided to all users The remaining steps Part E are restricted to specific users The Stream Geomorphic Assessment Tools were designed to be used in a step wise fashion i e finish one step and proceed to the next Much like a stream flowing downhill the data must flow sequentially from one step to the next If an error condition is encountered that requires one to revert back to a processing step run all steps in sequence from that point on April 2006 Organization Page 32 s uozZ PJEZEH UO SOJF jenn Ayjiqe eaepaywry sluloduoije1uewbes ye p ju wp s suajem MUNS s19 M 8deLINS 0 UO pe 0efoidsjulog uolyeuswbes q Hed Woljpereiauad eq
90. Save Edits click on Yes Setting Reach Point Identifiers and Tributary Identifiers At present assignment of the Tributary Identifier Tribld and the Reach Point Identifier RchPtld will have to be assigned manually or through other means Potentially the Spatial Join and or Select By Theme functions in ArcView may provide a more automated method for transferring these data elements from attribute tables of other themes such as the sub watershed theme April 2006 Step 09 Using Alternative Stream Corridor Buffers Page 148 Step 10 Data Entry Review of Reach Point Data The dialog for Step 10 provides the ability to review and or edit certain data associated with reach points The dialog can be used at any point following Step 06 If one attempts to access Step 10 prior to running Step 06 an error message will be issued Step 10 provides the user with the ability to enter or modify a limited set of data that is associated with a reach point Elevation Channel Width Valley Length Valley Width among other documentation type fields Step 10 is the only place where elevations can be assigned to reach points Elevation data can be assigned at any point following Step 06 Valley Length and Valley Width however will be calculated in Step 07 for those reaches for which valley walls have been drawn Channel Width will be calculated in Step 08 for all reaches As a result one must use caution in entering or modifying data in Step 10
91. Setup procedure Setup Completed Successfully a X Required data set for tracing 5055W FinalT ribldS et dbf successtully created and saved in directory H Geomorphology Version4 DenvdD ata Processing completed in 4 seconds Upon completion of the Setup procedure one can proceed on with indexing features by clicking on the button labeled ndex Features Clicking on Done will return one to the Part D main menu for feature indexing April 2006 Part D Step FITO00a Setup for Feature Indexing Page 205 STEP FITOOb Feature Indexing This dialog enables the one to index features to the stream network The process of indexing features is simply defining the location and extent of a real world feature using the surface waters Features are referred to as impacts such as alluvial fan grade controls etc Features are represented by either a point or a polyline geographic entity This dialog is accessed by clicking on the button labeled Index Features on the Step FIT00a dialog Once that button is clicked the following message is displayed theme 5055WfFinal shp or that theme has been re created you MUST run Setup click on Setup button first Do you want to continue The above message is issued to provide a warning that the surface water theme and the data created via the Setup function must be consistent If they are not consistent unpredictable results may occur when indexing features including in
92. Shape Properties a x Shape Type Multi Polygon H of vertices 10 down the menu and select Shape Properties As shown to the right the shape properties dialog will appear Scroll down until you find a Multi Part Separator If coordinates follow that separator then the Point 0 682 0 696 n edit Point 0 638 0 312 i Paint 0 246 0 42 a Point 0 216376 0 553309 _ Delete polygon is composed of multiple parts You can also use the Shape Properties dialog to locate vertices of the polygon boundary If you select a vertex point in the list of points a solid point symbol will be placed in the view showing the location Closing the Shape Properties dialog will cause the point symbol to be removed from the view Update Shape Attributes OF Cancel While it is not likely that a self intersecting shape will be found a Clean operation is performed on each polygon placed in the interim theme created This should convert any self intersecting polygons into a multi part polygon These in turn are then broken up into individual single part polygons separate records in the shape file as described below Multi Part Polygons Polygons composed of multiple polygons will be generated either by performing polygon operations clipping etc via the Geoprocessing Wizard an ArcView extension or by digitizing The preceding discussion provided one example of how such multi part polygons can
93. Surface Water SEGOTSWwSEGOT shp Theme will be created upon completion of this Step To be saved in Ae geomorphologyversiond DenvdD ata Note for insertion into System Lo User Note I April 2006 Part D Step SEGOO Setup Surface Water Theme Page 192 To use this dialog e The theme representing surface waters clipped to the sub watershed boundaries produced in Part B Step 05 will be displayed e The name of the theme representing the surface waters to be created will be displayed e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data Starting the process After the required information has been entered on the dialog click on the button labeled Setup Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools in the SGAT User Manual for common error and warning messages Upon completion Alias of surface water theme created SWSEG Legend file used to display surface water theme None Upon completion the following message will be displayed to summarize the processing that took place SGAT Info GeoSW FEHSetup lbtSetup Click x Surface Water theme SEG0TSWSE GOT shp successfully created from theme 5055 WFinal shp and saved in directory he geomorphology version4D
94. T Select Area for Boundary Them Theme Name sodsubweshed shp f Sub Watershed Source Theme for Sub Wyatersheds to be used Data Theme and Extraction Criteri Theme Not Selected Feature Selection Criteri Use Feature Selection Data Values l Press Shift key to Field Hame select multiple Density Unit Unita C Output Tabl Table Hame Data Theme Mot Selected To be saved in H Geomorphologyyversiond DenydD ata Mote for insertion into System Lo User Note Calculate Density Done To use this dialog A variety of options that provide a great deal of flexibility are available on the dialog Specific options are as follows e Select the radio button identifying whether the densities are to be calculated for the sub watersheds or stream corridors The registered theme corresponding to the button selected will be shown in the area to the right of the radio buttons e Select the data theme for which densities are to be calculated The theme will be selected from the hard disk rather than one which has been previously registered Refer to the section below entitled Selecting the Data Theme e f a subset of the features in the data theme is to be used in calculating densities place a check mark in the Use Feature Selection control This enables the control Field Name e fa check mark precedes the Use Feature Selection control use the Field Name control on the dialo
95. Valley and Channel Width data Refer to description of Valley Width field as the software may not generate Valley Width values for all reaches e Areas April 2006 Reach Sub Watershed Area of the sub watershed associated with the reach point The reach point will serve as the pour point for the sub watershed Reach Drainage Area Drainage area upstream of the reach point Overall Watershed Drainage area of overall watershed at the primary pour point Step 10 Data Entry Review of Reach Point Data Page 151 e Map Documentation and Notes Comments for Reach Note The contents of the USGS Quad names VT Orthophoto identifiers Town Names and HUC 10 watersheds can automatically be filled in by clicking on the button labeled Set Map Doc This will require that themes defining the boundaries for the USGS Quads VT Orthophotos Towns and HUC 10 watersheds be available and have been registered Use of the dialog associated with the Set Map Doc bution will be described subsequently o USGS Quads List of USGS topographic quads 1 24000 or 1 25000 scale which cover the main stem or tributary for the geomorphic reach List should include commas separating individual USGS quad names e g South Mountain Bristol etc o VT Orthos List of VT orthophotos which cover the main stem or tributary for the geomorphic reach List should include commas separating individual orthophoto identification e g 088192 088196 o Towns List of towns which co
96. Vermont Agency of Natural Resources Stream Geomorphic Assessment SGAT User Guide w s gm he oe a r Fia T m ia u i J as a j a m a E B a ra i E is a F i of Ti k aa sa p i 7 lan OP an 1 z al Tr ot E nra p a2 m i as 1 s ae a a a a a a eee st e nal peo E as s r 2 mat A J a P i a al a hh J r cI a k Fa Tip E ji T aif ai Lark es CEN a z Ea f h a F a if ie a i n ia is a ate 2 le ATF i i J ai i J i n s i oar A g mE z ae iy p J i a m x n Lee a Pal A a i oe oe A img F a a E u a i i pP for F a m z n E Stream Geomorphic Assessment Tools Version 4 5 An ArcView Extension Software Design and Development By C L Davis Consulting Associates Ltd Weybridge Middlebury VT For the Vermont Agency of Natural Resources April 2006 Development of the Stream Geomorphic Assessment Tools and User Guide was supported by grants from the Clean and Clear Funds US Fish and Wildlife Agency State Grants Version 4 Federal Emergency Management Agency Project Impact EMB 200 GT 0005 CFDA 83 551 Version 1 Pre Disaster Mitigation Project CFDA 83 557 Version 2 US Environmental Protection Agency Section 319 Grant Version 3 Contracting for Version was provided by the Lamoille County Regional Planning Commission Michele Boomhower Executive Director Addison Count
97. a distance Stor of 0 25 Meters of multiple sub watersheds Cannot establish starting point for tracing April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 123 The figure to the right illustrates the situation In this case modify the boundary of the sub watershed such that it will be located more than the connecting feature search distance away from the Primary pour point Alternatively one could modify the connecting feature search distance via the dialog described earlier lt is also possible that the initial sub watershed has been duplicated i e copied on top of itself If this is the case the duplication will not be apparent To identify this situation select the sub watershed theme as the active Click the cursor in the middle of the initial sub watershed Then open the attribute table for the theme Identify the number of records that are highlighted selected If there are two or more records highlighted then the sub watershed has been copied onto itself Simply delete one of the records or as many records as it takes to have only one record left Make sure that the boundary of the remaining sub watershed is coincident with all neighboring sub watersheds sub watershed boundaries Circle representing Search Distance Primary Pour Pt Do not proceed beyond Step 06 without cleaning up all errors Doing so will not only produce incorrect results but will adversely affect the norm
98. al processing performed in the subsequent steps The operation of the subsequent steps depends upon correct input data Unpredictable results may occur such as infinite loops internal ArcView errors e g index out of range nil objects Segmentation Violations etc April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 124 Step 07 Calculate Valley Line and Data Valley lines travel from one reach point to its upstream neighboring reach point near the center of the valley and in straight line segments Specifically valley lines do not follow the meandering path of a stream The following figure illustrates a Valley Line and its relationship to the valley walls stream centerline sub watershed boundaries and reach points Valley Walls p A N Upstream Reach Pt Cc ZED a A Downstream Reach Pt Valley Line Sub watershed Lines lt is important to note that valley lines are used solely for the purposes of determining valley length and an average width of the valley These two values are then combined with similar data for the stream channel to arrive at Channel Sinuosity and Valley Confinement using the following equations Sinuosity Channel Length Valley Length Confinement Valley Width Channel Width Valley Slope Elevation difference between upstream amp downstream reach breaks Valley Length Note Sinuosity Confinement Valley Slope are calculated in Steps 07 08 and or 10 if
99. ame for a person When referring to a person by their nickname not everyone will know who that person is However if the others are told who the nickname refers to then they can relate the nickname to a person and then to knowledge about that person In a similar manner aliases have been implemented in the Tools to refer to themes and tables When one first starts using the Tools the specific names of the themes shape files or tables are not Known Through a process called registration the user will associate a theme or table with an alias Then wherever that specific alias is used in the Tools a translation will occur to reference the specific shape file or table Whenever a theme or table is created in the processing steps of the Jools that data set will automatically be associated with an Alias This provides a consistent use of aliases for all data sets referenced in the Tools The alias is also used in the following manner o A theme or table created by the Tools will be assigned a name that is based upon the alias For example the name of the theme resulting from Step 07 will be S01Watershed shp where Watershed is the Alias used for the overall watershed o Themes will be displayed in the User View using a default legend named alias avl e g watershed avi The default legend may however be overridden if specific conditions are to be displayed e g potential errors The aliases used are listed in a table at the
100. an one valley wall polygon an error will be generated by the Tools The polygons should not be clipped to the sub watershed boundaries as the Jools will detect the polygon to be used for a sub watershed and will clip it to the sub watershed boundaries However the only place the valley walls should cross the watershed boundaries is at the reach point A polygon extending way beyond the terminal reach point may cause errors in SGAT Note For digitizing geographically referenced images of the 7 1 2 minute USGS quads are available from VCGI and the orthophotos are available from the Tax Mapping Program VT Tax Department Refer to Appendix A Optional Tools for tools to assist in digitizing Note Separate polygons should be generated for each tributary These polygons will overlap with the mainstem polygon in the valley bottom The tributary polygon must only encompass the tributary reach points and cannot cross the mainstem surfacewater The figure above and to the right illustrates the multiple overlapping polygon for the mainstem and tributary reach points Appendix B provides a Data Tracking Form for documenting source themes among other items This can provide essential documentation for future reference April 2006 Setting Up for Using the Tools Page 26 Setup The ArcView Project File It is recommended that you provide a clean environment under which the Tools extension is to be used Specifically perform the following 1 Cre
101. anagement Section VT Agency of Natural Resources Boundary Themes Ortho Photo Town and USGS Quad The Ortho Photo Town and USGS Quad Boundaries are available from VCGI in Arclnfo Export format in a state wide coverage The data must be converted into a shape file Note The mport71 program supplied with ArcView will convert from ArcInfo Export format to shape files The Merge operation of the Geoprocessing Extension of ArcView can be used to merge the ti es into a single shape file April 2006 Setting Up for Using the Tools Page 20 Land Cover Land Use The LCLU coverage is available from VCGI in either ArcInfo Grid format or ArcInfo Export format For the Grid format The entire state is provided as a single file It is necessary to convert the Land Cover from a Grid format to a shape file polygon class for use with the Tools To limit the size of the resulting shape file the area should be restricted to that which encompasses the watershed being assessed Note Conversion from Grid format to shape file format requires the Spatial Analyst extension to ArcView For the Export format The coverages are generally available by special order from VCGI with the geographic area covering a USGS quad The data must be converted into a shape file and all quad areas must be merged into a single shape file Note Contact VCGI for special processing It may be less problematic and less expensive to have the extraction into a single Ex
102. and location of those data sets will automatically be established Depending upon specific system settings for the specific output data set either a single version or multiple versions may be created For most situations only a single version will be allowed If one is repeating a step and either a single version is allowed or multiple versions are allowed but an existing data set is selected to be replaced you will be warned that the existing data set will be replaced In such cases the following message will be issued SGAT Y N 1012 GeoSW Common ShapefFile Edit 1072 Output data set S055 Final shp is registered and exists in the output director and will be replaced if you continue Do vou want to continue If you do want to replace the file click on Yes otherwise click on No If you click on No the operation will be canceled and the following message will be issued If you repeat a step and want to replace the prior version click on Yes If you click on Yes the following message will confirm the replacement April 2006 Organization Page 38 Certain dialogs especially those in Parts A and B create attribute fields and calculate values for those fields If you repeat a given step those fields may already exist If the fields do exist the dialog will issue a message similar to the following SGAT Y N 1001 GeoSW CalcChan IbtCalc Click 1001 Field s TotStrmLen Chanllen Chankyidth ChanlSnuo
103. are somewhat cryptic due to a ten character limitation Appendix E and F associate the field names used in the cross tabulations with the source field names and values from the Top20 and LuCodes source tables One record will be present in the resulting table for each reach point This will contain the area summations for a corridor sub watershed upstream corridors or upstream sub watersheds as dictated by the area of interest and the input table i e from Step 12 or Step 13 April 2006 Step 14 Summarize Area by Field Value Cross Tabulate Page 175 In the preceding figure Fld_Freq relates to frequent flooding potential Fld_None relates to no flooding potential Fld _NR relates to flooding potential not rated Fld_Occas relates to occasional flooding potential Fid_Rare relates to rare flooding potential and Fid_Bink relates flooding potential not available The field WaterArea represents the area designated as water bodies in the soils coverage The values for each of the cross tabulation fields are in square miles The field CordrArea represents the area of the corridor for the given reach point By dividing the WaterArea and each of the values for a given characteristic by the CordrArea one can then obtain percentages Using RchPtld m12 in the above figure as an example the following percentages for the potential for flooding would be obtained Area from above figure Percentage of Corridor Water Area WaterArea 0 01 Fre
104. aries shp If the legend file PPtType avl exists in the SysData directory it will be used to display the Primary Pour Point theme If multiple intersection points have been found they will be labeled as Unknown in the View as illustrated above lt is reasonable to have multiple intersection points For example the study area watershed may be defined such that the main stem enters at one point and leaves at another As Illustrated to the right multiple intersections may also occur when only a portion of a larger watershed is being reviewed In such cases tributaries will be entering from the upstream areas of the watershed Main Stem entering om upstream watershed If there are multiple points of intersection the user should investigate them as they may signify incorrect sub watershed delineation and or incorrect stream digitizing See Potential Surface Water Problems at the end of this section Review the stream layer and watershed layer to be sure that the watershed bounds extend beyond the end of the stream layer Rerun this step once corrections have been made Tributary entering from upstream watershed Outflow of watershed April 2006 Step 02 Extract and Clip the Surface Waters to Primary Watershed Page 91 Potential Surface Water Problems The resulting surface water theme should be reviewed to ensure that the Extraction Clipping process occurred correctly Potential problems th
105. as been created using the Spatial Analyst extension to ArcView or through digitizing The theme must be provided in ESRI shape format and contain polygons representing the sub watersheds Note It is recommended that sub watersheds be delineated using polylines The capabilities provided in the Optional Tools menu can be used to verify the geometry of the polylines and subsequently build polygons This procedure will minimize the types of digitizing errors described at the end of this section Such errors can take a significant amount of time to resolve Further if the errors are not corrected unpredictable errors will occur in subsequent processing steps To access the dialog click the button labeled Step 01 Dissolve Sub Watersheds into Overall Watershed in Part A main dialog The dialog is shown below Part 4 Step 01 Dissolve Sub Watersheds into Overall Watershed Input Themes Sub Wwatershed e0Qsubwehed shp Theme for Sub Watersheds to be used Primary Overall Watershed Theme to be Create Output Theme S01 Watershed shp Existing Theme SOT atershed shp for Overall Watershed Will be replaced To be saved in Aegeormorphology version sD envdD atas Note for insertion into System Lo User Note Dissolve April2006 Step 01 Dissolve Sub Watersheds into Overall Watershed Boundary Page 78 Required Input Data sets not registered or created If the theme representing sub watersheds has not been
106. as well as the functions associated with creating fluvial erosion hazard zones and System has full access to all functions The User Type is set via the Setup Dialog which is described in a subsequent section Itis possible that the User Type will be pre selected and locked to prevent alteration If this occurs it is performed solely to prevent one from inadvertently changing and using the Tools inappropriately Application At present there are three applications to which the Tools may be applied Stream Geomorphic Assessment FEH Option 1 and FEH Option 2 The latter two are associated with planning issues and are therefore available to only the User Types of FEH and System The three Applications primarily dictate the parameters to be used for buffering specific features in Step 09 Create Stream Corridors The Application is set via the Setup Dialog which is described in a subsequent section It is possible that the Application will be pre selected and locked to prevent alteration If this occurs it is performed solely to prevent one from inadvertently changing and using the Jools inappropriately April 2006 General Concepts Page 8 Required Directory Structure A required directory structure is imposed and is based upon the directory in which the ArcView project file is located There are four sub directories that are required BaseData DerivdData SysData and Temp All source data sets themes and tables must be located in
107. at in which the ArcView project file exists This theme is added to the user view identified on the Main dialog Click on the button labeled Done to return to the Part B menu dialog Special Consideration for the Results of Step 06 If the legend file RPts av exists in the SysData 4 S0Greachpts shp directory the Reach Point Theme will be displayed she Inflow using that legend As shown on the right reach points will be displayed in accordance with the PPtType Ke assigned in this step i e Outflow Terminal and a De dnd ar Standard The reach point types Outflow and are determined in Step 02 and are carried over into the Reach Pointtheme Terminal represents those reach points that are at the end of the stream segment for which a TribID was assigned in Step 04 Standard represents all other reach points which are determined where streams having been assigned a Tributary Identifier TribID cross a sub watershed boundary Note The value in the PPtType field for those reach points displayed as Standard will be blank The figure below illustrates a reach point theme created in Step 06 TAN T x y La April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 118 The figure to the right illustrates the reach points created with labels applied It is useful to note the correlation of the reach points stream network and sub wat
108. at may occur are the following Fragments of streams extend into the overall watershed This would be indicative of errors in digitizing Gap in Stream the surface waters or incorrect sub Nery Orr watershed delineation Stream Fragments Gaps in the linear stream network This would be indicative of incorrect field values selected in the Linear Feature Types or Flow Regime or incorrect assignment of those values in the surface water theme To obtain a confirmation of the correctness of the resulting surface water theme you can run the Review Polyline Theme for Geometry GIS Errors in the Optional Tools This is described in Appendix A lf problems are identified they should be corrected and the process repeated As appropriate corrections can be made to the source themes for the surface waters and or the sub watershed boundaries If modifications are made to the sub watershed boundaries that affect the overall watershed boundary repeat the process starting at Step 07 Otherwise simply rerun Step 02 April 2006 Step 02 Extract and Clip the Surface Waters to Primary Watershed Page 92 Step 03 Combine Stream Segments between Confluence Points The surface water coverages are developed in a general nature in order to serve a variety of purposes Therefore it is reasonable to expect that a number of stream segments polylines will be used to represent the path of a stream from one point of confluence to the next In some
109. ate to a dBase table containing the definition or description of the LcLu classification Refer to LcLu Codes Descriptions table VT field will usually be GridCode MeanderCL OrthoBoundary Ortho photo Ids Identifier associated with photo boundary SegPtsUser Reach Pt Ids Identifier associated with reach to be segmented These would be the same identifiers as created in Step 06 SegPtsUser Segment Pt Ids Numerical identifier uniquely identifying a segmentation point within a given reach Recommend that values begin with the number 1 for each reach and increase as one moves upstream Soils Soil Mapping Unit Values in field will identify the soil type represented by a polygon Identifiers This field and the values within it is used to link to a dBase table containing characteristics attributes of the soils The characteristics will vary based upon the Soil Mapping Unit Identifier Refer to Soils Top 20 Attribute table This field will usually be MUKEY if in VT Soils Soil Mapping Unit Field is used in Step 14 to identify soil polygons that represent Symbols water i e has a field value of w or W This field will usually be MUSYM if n VT April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 66 To select a Field Name click on the drop down list and scroll up down to find the appropriate entry Then click on the field name This identifies the field to be used however the
110. ate a directory in which the ArcView project will be saved This will be referred to as the project directory 2 Create the required sub directories under the project directory Refer to earlier section on the Required directory Structure 3 Copy the required system tables into the SysData directory Do not copy these tables from another project Always copy them from the Distribution CD to ensure that unrelated data and or errors are not transferred into the new project Start with a new ArcView project Unload all ArcView extensions other than the Tools Do not create any Views Do not load any tables Save the ArcView project into the project directory eS ore The Setup dialog in the Tools will require you to identify a View the User View to which any themes registered or created will be added This view will be created by the Tools All data sets themes and tables to be used within the Too s must be registered This is accomplished by accessing the Theme Table Registration and Management dialog from the Setup dialog During the registration process any themes will automatically be added to the User View From the preceding steps the dBase tables provided with the Tools extension and the source shape files should be available in the BaseData directory under the directory in which the ArcView project file is located To summarize the dBase tables are SOO0Top20_05 dbf SO00LuCodes dbf SO00SoiIXTabFields 05 dbf and
111. ately alongside of the polylines representing surface waters Working at small scale may cause inaccurate location of the points and thus errors to be generated This dialog is accessed via the Index Features button on the Feature Indexing Setup dialog As a result the following registered theme names will be available from the Feature Indexing Setup dialog Surface water SO5SWFinal shp Primary Pour Point SO2PPt shp Point Impact F TO0Ptimpact shp and Polyline Impact F TOOLnImpact shp Since a specific impact is associated with either a point or a polyline feature type it is important to first enter the impact and other data then perform feature indexing i e identify location point or points The following order is recommended Part D FITOOb Feature indexing Impact Feature to be Indexe Impact Sublmpact oO Location Left Bank z Impact Feature Dat Height Description Observation Dat Date Person Organization Procedures for Assigning Impacts to Reache Distance from Points to Search for Polyline Search Distance poo Meters Set Start End Pts Enables point locations to be identified for indexing a feature Clear point locations identified via above Index feature defined above Save features indexed since startup or since last Save Cancel features indexed since startup or since last Save Show yew Instructions Done
112. atures entirely which enables one to re index via Step FITOO a given feature to reposition its geographic location The dialog for this step is illustrated below Part D FITOOc Feature Data Modification Deletion Impact Theme Eoint Theme FIT00Ptmpact shp w Theme ftor Impacts Point Features to be used Palpline Theme FITOOLnlmpact shp Theme for Impacts Polyline Features to be used Identification Data Cannot be modified 1 Impact Typ 2 Reach Id Mo 3 Impact Id Boo Impact BankAmoringandRevetment 00 Reachles M03 M02 MO Attribute Data can be modified Sub lmpact Rip Rap Location Right Bank Impact Feature Dat f Point Impact f Polvline Impact Description Extends updown stream of crossing with Route 16 Observation Dat Date 03 02 2006 Ferson E Organization cldca Note for Insertion into System Lo User Note Modifications based upon final review of 4 76 2006 Delete Save Cancel Done To use this dialog e The theme containing point impacts created in Step FITOO will be displayed e The theme containing polyline impacts created in Step F TOO will be displayed e Enter a User Note to be entered into the system log upon completion of performing updates April 2006 Part D Step FITOOc Feature Data Modification Deletion Page 211 The following describes the approach to be used for modifying a given Impact 1 Inthe mpact Type panel s
113. ave it registered Make note of the name assigned to the stream corridor theme Exit the Tools extension Remove all references in any Views and from the Tables area to the theme created in a Using Windows Explorer migrate to the DerivdData directory in which the theme from a is located Delete all component files for the stream corridor theme created in a Copy all component files for the theme to be used for stream corridors into the DerivdData directory In ArcView open a view From the File menu select Manage Data Sources In the dialog resulting from h migrate to the DerivdData directory Select the theme copied in f Click on Rename Type in the name of the theme from a Exit the Manage Data Sources dialog Start up the Tools extension Click on View Log Select the data set name for a and above Enter a Note to reflect that the SGAT generated theme for corridors was replaced by a user defined theme Note The above takes advantage of the registration of an SGAT generated theme but replaces that theme with another i e it is a way of fooling SGAT 4 Continue with Step 11 Step 12 Step 13 and Step74 Warning The theme to be used must be of polygon class meet the requirements outlined in this section including the requirement for the fields Tribld RchPtld and CordrArea If these requirements are not met unpredictable results will occur when Step 11 is run April 2006 Step 09 Using Al
114. ave to go back due to an error in the sub watersheds or surfacewater and re run Steps 1 3 you can avoid having to re assign the tributary identifiers by using the following procedure O O April 2006 Highlight the SO3swcomb shp shapefile that contains the tributary ID s Make sure none of the polylines within the theme are selected or highlighted On the ArcView toolbar select theme and then Convert to shapefile Save the theme into your base data folder with a new name Go into SGAT theme registration and unregister your old surface water and register the theme you just created as your surfacewater Start SGAT over from Step 1 or 2 depending on whether you changed the eaterior watershed boundary As shown in the figure below in Step 3 Combine Stream Segments between confluence points under Options select All Fields This will carry along your trib ID s to the new SO3swcomb shp and you will not have to re assign them Organization Page 34 Part 4 Step 03 Combine Streams Sec Input Theme s Surface Waters 02SWClipped shp w Theme for Surface Waters for Watershed to be used Fields and Data to Transfer from Surface Water Theme to Output Theme Options Select Fields 7 l Swid j All Fields Hold Shift key Tribid down to select No Fields more than one Swrevu Select Fields via List Box to Right E Surface Water Theme to be Created EER Existing Theme
115. be associated with each Reach Point Identify The top part of the dialog contains check boxes for each of the boundary themes of interest To the right of the check boxes will be a message indicating the availability of the theme or the name of the theme being used for the given boundary If a check box for a theme is disabled either the theme or a required field for the theme has not been registered The specific reason will be identified in the message to the right of the check box area In the above a required field has not been registered for the theme containing USGS Quad boundaries and the theme containing the Town boundaries has not been registered Themes for the HUC 10 watershed boundaries and VT Orthophoto boundaries are available Ifa theme is available the check box will be enabled and initially will be checked If a check mark is in the check box the theme will be used If no check mark is present the theme will be ignored If for some reason one does not want to use a specific theme simply click on the check box to remove the check mark April 2006 Step 10 Data Entry Review of Reach Point Data Page 155 When all of the desired changes if any are made click on the dentify button to define the USGS Quads VT Orthophothos Towns and HUC 10 watersheds that each reach falls within The following message will be displayed after one clicks on the dentify button SGAT Y N 1006 GeoSW Ident
116. be disabled Buffering to create fluvial erosion hazard zones is conducted in Part E of the Tools In addition the following message will be displayed when the Part B dialog is selected from the Main Dialog 1108 Application selected on Setup Dialog prevents use of O buffering via Step 09 Use FEH Part D for creating FEH ones Use of all other steps are permitted The parameters may vary for the development of individual buffers around different features e g stream centerlines meander centerlines and valley walls These parameters are defined in a buffer reference table associated with each application Once an application is selected via the Setup Dialog the buffer reference table is automatically identified Through a buffer reference table the component buffers to be used in defining a stream corridor are identified The following list certain fields included in those tables and identify their use Default buffer DefaultBuf A fixed distance to be used in creating a buffer around the stream centerline If the distance is zero no default buffer will be created Stream Centerline StreamCL A channel width multiplier used to create a buffer around the stream centerline If the value is zero no buffer will be created Meander Centerline MeanderCL A channel width multiplier used to create a buffer around the meander centerline If the value is zero no buffer will be created Stream Centerline without a Meander
117. be provided in shape file format e Must adhere to acceptable GIS standards Specifically there must be no overlap of the corridors During development it is possible to create individual buffers for different tributaries Where these buffers meet it is possible that they will overlap each other This overlap or common area must be removed e Must be clipped to or unioned with the sub watershed boundaries The approach used to do this will vary depending upon how the corridors were initially defined In particular a stream corridor must be constrained by the boundaries of the corresponding sub watershed Note Use of the ArcView Geoprocessing Extension may provide the needed functions Attribute fields The following attribute fields must be added to the attribute table for the alternate stream corridor theme They must be present in order to use this theme in Step 11 Tribld The field for Tributary Identifiers must be a String field type with length long enough to hold the values to be assigned Each corridor or buffer must have the value of the Tribld for the stream flowing through the corridor For additional information review Step 04 RchPtld The field for Reach Point Identifiers must be a string field type with length long enough to hold the values assigned Each corridor or buffer must have the value of the AchPtid for the outflow or pour pt of the corridor For additional information review Step 0
118. be used would be identified For example the source theme for soils must have a field uniquely identifying the soil mapping unit identifiers the MUKEY field in Vermont In addition the source table for the soil attributes must have a similar field which is also MUKEY for the Top 20 soil attributes in Vermont The user must identify the field containing the identifiers when registering the soil theme and the soil attribute table During the initialization process the records contained in the system tables SysBaseTheme dbf and SysBTReqFields dbf are compared with a hard coded list to ensure that all necessary records are in those tables If a record is missing that record will automatically be created No error messages will be issued Load themes tables previously registered The final step in the initialization process is to verify the registered themes and tables from prior sessions with the Tools and to load them into the system DocGUls The User View to which themes are to be added upon user registration or creation in a processing step is identified by the user on the Main dialog The name of the view selected or created is saved in the system table SysSystem dbf During an earlier step in the initialization procedure it is determined whether the User View exists in the ArcView project If it does not then the following message will be issued SGAT Y N 0028 GeoSW Common Projinit LoadSysBas os Sil a hat been created
119. being executed SysView SysDir dbf syshuc10 dbf User Note ee SysLog dbf 3 SysRPtForm dbf Dialogs SysStatus dbf a SysSystem dbf Format for Reach Point Identifiers is SysUnits dbf SysUserT ype dbf Main Stem M01 M from Step 04 Tributary 171 01 T1 from Step 04 EA sinl xi e dbf Astart Hage A R Gjversion3 M usermanua E arcvies Certain steps most notably Steps 03 06 07 09 and 11 may require a significant amount of processing time The actual time will depend upon the hardware environment and the size of the watershed being assessed It may be difficult to be sure that processing is occurring The only manner to be somewhat assured is the shape of the cursor If it is in the form of an hour glass then processing is being performed Occasionally the ArcView message status line may show a blip of activity and then disappear Have patience To the best of our testing and knowledge no known infinite loops exist April 2006 Organization Page 44 Upon completion of processing a message such as that shown below will be displayed This message will reflect the final disposition of the step Copy of subwatershed Expl4s00subywehed shp saved in director A geomorphologyversion4 Temp Limited if any comections applied Remaining Multi Part polygons exploded Theme added to View SAT but NOT registered The Note Field on the Dialogs for Processing Steps A dialog con
120. beled Assign Trib Ids on the Step 04 dialog Once that button is clicked the following message is displayed g 1206 IF any changes have been made to the surface water theme SO3SS Comb shp or that theme has been re created wou MUST run Setup click on Setup button first Do you want to continue The above message is issued to provide a warning that the surface water theme and the data created via the Setup function must be consistent If they are not consistent unpredictable results may occur when assigning tributary identifiers including infinite loops As a result if any changes have been made to the surface water theme or it has been recreated a ways run the Setup function before assigning tributary identifiers Click on No to return to the preceding dialog or Yes to continue on If you continue on the following message will be displayed SGAT Y N 1184 GeoSW SetTribld2 digOpen 1184 tis recommended that a backup of the surface water theme be made prior to assigning Triblds Do you want to create a backup Assigning tributary identifiers involves actual changes to the attributes of the surface water theme As a result it is recommended that one create a backup of the surface water theme before proceeding This will enable one to restore the surface water theme should errors occur during the assignment of tributary identifiers If a backup is not desired click on No Otherwi
121. ble BndryType Indicates the type of boundary theme used Possible values are sub watershed or corridor Value copied from input table DataType Indicates the type of data theme used Possible values are LcLu or Soils Value copied from input table SourceStep Will indicate which step created the output theme This is used in subsequent steps to verify proper input theme selection Value inserted in the step is 14 SumLevel Field indicates to which level of aggregation that the data pertains Value is set to that of the input table Possible values are either blank or Upstream Field Value Name s the area represented by each possible value for each user selected field WARNING Since the resulting table is a dBase table it can be opened up in either Microsoft Excel or Microsoft Access for further analysis If those applications are to be used copy the table into another directory on the hard disk Open that version of the table with Excel or Access Then any necessary changes can be made without impact on the ArcView project Note If inadvertent changes are made to the structure of the table outside of ArcView it may not be useable within ArcView This in turn could result in corruption of the ArcView project which could render it unusable Possible Error Condition As each value for a soil characteristic or a land cover land use type is Summarized an attempt is made to find the corresponding record in the re
122. buffers will be created or not depending upon the criteria in the buffer reference table Additional criteria the user should adhere to for digitizing meander centerlines 1 Meander centerlines must be drawn as lines polylines User must ensure that the ends of polyline segments are snapped together if digitizing was stopped and then started again within a reach 2 Individual polylines drawn to represent meander centerlines can continue through multiple reaches ee Multiple Reaches Ee Co Meander Centerline April 2006 Step 09 Calculate Stream Corridors Buffers Page 141 3 With the exception of terminal reaches the meander centerline must travel through the entire length of a sub watershed and must intersect the sub watershed boundary only twice Once upon entering the sub watershed and once upon exiting The meander centerline should never cross the sub watershed boundary except at the point of entrance and the point of exit 4 For terminal reaches the meander centerline will intersect the sub watershed boundary only once Upon entering the sub watershed 5 The meander centerline need not be continuous This is illustrated in the following figure i Downstream Reach Point i Non continuous Meander Centerline Contains both upstream and i downstream reach points A Upstream Reach Point Reach Point V ee Meander Centerline P j Meander Centerline i starts again 6 The meander cen
123. button is clicked the changes are applied to the attribute table associated with the reach point theme Note The Save and Cancel buttons will become enabled only after a change has been made to a data value After the first change these buttons will remain enabled until the changes are saved via the Save button or canceled via the Cancel button For Terminal reach points the only data element that is appropriate and required is the elevation Channel Width Valley Width and Valley Length are not appropriate and will not be used The corresponding values for downstream reach point will be used for the sub watershed As with all software it is recommended that changes be saved periodically This will prevent loss of data should an abnormal situation such as hardware or software error occur In addition April 2006 Step 10 Data Entry Review of Reach Point Data Page 152 saving changes at known points will enable one to remember what changes need to be re entered should one have to cancel changes at a later time If after having made any number of edits to data one wants to cancel those changes click on the Cancel button The following message will be displayed SGAT Y N 1057 GeoSW Revu lbtDone Click 1057 The last changes have not been saved fF you continue they will be lost Do vou want to Continue Click on Yes if you want to cancel all pending changes Remember that all changes pending since the last Save
124. c buffering criteria for specific conditions In addition as research progresses and data becomes available buffering parameters can be added or modified as necessary to the buffer reference tables Note The methods of combining data to form a key and the rules for searching fora record are too complex for presentation here Appendix H provides such details Source Data required for Stream Corridor Development Valley walls and a meander centerline need to be digitized before this step can be completed and are required only for unconfined valleys Unconfined valleys are often found along the main stem of the river or along the main stem of major tributaries In some instances unconfined valleys may also be found on smaller tributaries The process for defining where to delineate valley walls and a meander centerline are described in Stream Geomorphic Assessment Phase 1 Handbook Appendix E Refer to Step 07 for additional criteria for digitizing valley walls For reaches where valley walls and a meander centerline are not available the following may be created o A default corridor for example 100 feet on either side of the stream centerline and or o A buffer created around the stream centerline as a multiple of the channel width for example 2 5 times the channel width on either side of the stream centerline If both of the above are created the resulting stream corridor will be the sum of the area covered Note The above
125. calculated are shown as green dots Note that reach points are calculated up to about the midpoint of the main stem Somewhere above that reach point a Tributary Identifier was not assigned to a stream segment The last segment to which one was assigned in a continuous fashion becomes the terminal segment and no further reach points are calculated above that segment Even though Tributary Identifiers were assigned above that segment they will be ignored because the continuity in assigning those identifiers was broken As Step 06 traces the stream network a record is kept of each time a sub watershed is encountered Again the stream network is composed of only those surface water segments that have been assigned a Tributary Identifier When a sub watershed is entered by the stream the sub watershed is marked as being used In addition the area of the sub watershed is added to the tally of sub watersheds that have been used Upon completion of processing the area of the sub watersheds used is compared with that of the overall watershed If a discrepancy between the areas is detected an error message similar to that shown below will be issued 1706 Sum of sub watershed areas 22 0704 associated with reach points i not equal to area of overall watershed 25 1075 If the sum of the areas in the message is less than that of the overall watershed then a Tributary Identifier has not been assign
126. calculated as the channel length divided by valley length This data does not get imported into the DMS but can be used within the SGAT program ValySlope Valley slope will be calculated only if the elevation data is available for the reach point and its upstream neighboring reach point Valley slope is calculated as the difference between the elevation of upstream reach point and the elevation of reach point divided by the valley length The result is then converted to a percentage by multiplying by 100 This data does not get imported into the DMS but can be used within the SGAT program SysValyLen Software generated value for valley length refer to ValyLength above Maintained separately for comparison with value of ValyLength should the user modify that value in Step 10 SysValyWid Software generated value for valley width refer to ValyWidth above Maintained separately for comparison with value of ValyWidth should the user modify that value in Step 10 As indicated above ValyConfin and Sinuosity will be calculated only if the required channel data is available This will occur if Step 07 is run again after Step 08 If the channel data is not available which would be normal if the processing steps are run in sequence these values will be calculated in Step 08 Valley Slope will be calculated only if elevation data is available This would imply that the elevation data was entered via Step 10 and then Step 07 was run When el
127. ce units established for SGAT via the System Functions This is normally feet The direction of offset will be relative to facing downstream The method for applying offsets is by taking the first and the last vertices of the polyline representing the impact A line is calculated between those two points The offset angle is calculated as or 90 degrees depending upon the offset direction All vertices are then moved the offset distance at that angle to form the offset polyline This strict definition of offset can result in situations such as that displayed in the following figure A La lt In the above figure the original impact is represented by the heavier magenta polylines and the offsets are the lighter magenta Upon Completion Alias of extract theme created None Legend file used to display extract theme None Upon completion a message similar to the following will be displayed to summarize the processing that took place The last line will indicate the offset applied if any SGAT Info GeoSW FITExt IbtExtract Click x features in directory H Geomorphology ersiong SDenvdD ata 1214 Extract shape file FIT Aluvial shp created with 6 Point i Offset Hot Applied Offset Mot Permitted for Point Features Click on the button labeled Done to return to the Main menu dialog for Feature Indexing April 2006 Part E Step FITO2 Extract Feature s Page 219 STEP FITO3 Export Feature Data
128. cel gt geomorphology CG basedata CG buffertables C communications C detivddata F doc List Files of Type Drives Shape Files hr In the right directory structure side of the above dialog migrate to the directory in which the theme is located Then click on the file name and then on the OK button or simply double click on the file name This will select the file to be used At this point the selected file will be reviewed with respect to certain edit criteria to help ensure that the correct shape file has been selected and that it is in the correct directory First a test is performed to ensure that the theme is not corrupted or invalid If this test is failed the following error message will be display and the theme selection will be ignored 2 SGAT System Error 0056 GeoSW Reg Theme btSel x 58 Data set S00Subw atersheds shp selected ts comupted or Invalid Selection ignored A test is performed to ensure that the shape file selected can be edited If it cannot then the shape file is either in use by another application or has its Read Only attribute set as would be the case for files copied from a CDROM If so an error message will be issued A test is made to ensure that the shape file has not already been registered under another Alias If it is found to be registered the following error message will be issued 1082 The theme selected s00huc1 Ubndry shp is registe
129. ciated with Incorrect Assignment of Tributary Identifiers Certain processing steps specifically those from Step 06 on will operate only on those stream segments which have been assigned a tributary identifier The importance of properly assigning the Tributary Identifier is outlined in the summaries of the processing steps to follow Step 05 processes all stream segments regardless of whether a tributary identifier has been assigned Following completion of Step 05 the stream network will be displayed in the view in accordance with the legend file named TribldAssigned av assuming that legend file is in the SysData directory The stream segments will be displayed in different colors based upon whether a Tribld was assigned in this step Step 04 Step 06 will calculate reach points starting from the primary pour point for the overall watershed from Step 02 For this step the stream network is composed only of those stream segments which have been assigned a tributary identifier When a terminal stream segment is encountered i e no stream segment is attached that has been assigned a Tributary Identifier no further reach points will be calculated upstream of that segment This means that if you missed assigning an identifier to a stream segment then no reach points will be calculated above that segment An example of this is shown in the figure to the right following Step 06 processing In the figure the reach points that were
130. complete assignment of tributary identifiers will adversely affect the results produced f you find that you need to modify the tributary identifiers assigned simply return to this step Make the modifications necessary and proceed from this step forward Be sure to perform each step in sequence April 2006 Problems Associated with Incorrect Assignment of Tributary Identifiers Page 110 Part B Data Development for Sub Watersheds Part A of the Tools extension was primarily devoted to data preparation for the overall watershed This part creates the data to be used in analyses and is oriented around the sub watersheds The following processing steps are included in Part B Step 05 Clip Linear Surface Waters to Sub Watershed Boundaries Step 06 Calculate Reach Points and Reach Point Data Step 07 Calculate Valley Line and Data Step 08 Calculate Channel Width and Stream Data Step 09 Create Stream Corridors Buffers Step 10 Data Entry Review of Reach Point Data Note Requirements for stream corridors buffers other than those created in Step 09 is presented following that section Note Step 10 can be used to review data following Step 06 Use caution in altering any data as it may be over written by other steps Refer to the section on Step 10 To access the processing steps for Part B click the button labeled Part B Data Development for Sub Watersheds on the Main dialog The dialog for Part B as illustrated below wil
131. completed April 2006 Organization Page 43 If an input data set has the ability to have multiple versions the following will occur o When only a single version has been created it will be displayed in the control and the control will be disabled o When multiple versions have been created the list of versions will be displayed in the control with the most recently created as the first entry The control will be enabled to permit selection If multiple versions of a data set are to be used it is strongly recommended that a Note be entered for the data set s in the step that creates them This will be the only manner in which the data sets can be distinguished The Note will be entered into the log and associated with the data set being created Refer to the Section entitled Using the Log One can manage multiple versions of a derived theme using Setup Dialog gt Theme Table Registration and Management gt Manage Derived Themes Tables Through this dialog one can delete from the hard disk and project or remove from the project any version of a data set Processing Time and Patience When the Execute button is clicked the processing step will be initiated During processing various messages will be displayed in the ArcView message status line which is found on the bottom left of the ArcView application window In addition the cursor will assume the shape of an hour glass thus reflecting that the processing step is
132. confined valleys are often found along the main stem of the river or along the main stem of major tributaries In some instances unconfined valleys may also be found on smaller tributaries The process for where to delineate valley walls is described in Appendix E April 2006 Step 07 Calculate Valley Line and Data Page 126 Additional criteria to which the user should adhere for digitizing valley walls are as follows 1 Valley walls must be drawn as or converted into polygons For each reach point it and its upstream reach point must be contained within a single polygon representing valley walls Refer to preceding figure 3 Valley walls can be drawn such that they include multiple reaches The figures below illustrate a polygon drawn for valley walls that encompass multiple reaches However separate polygons must be drawn for the mainstem and tributary reaches overlapping at the confluence point __ Valley Wall Surfacew ater e Reach Points _ 01watershed shp lt Separate valley wall polygons drawn for AK tributaries One valley wall polygon drawn for mainstem reaches be 4 Valley walls do not need to be contiguous or continuous For example one may be digitizing valley walls for a tributary and come to a highly confined valley At that point one should stop digitizing valley walls If the tributary subsequently flows into a wide valley one would draw another polygon for those valley walls In
133. ct file exists This theme is added to the user view identified on the Main dialog Click on the button labeled Done to return to the Part A menu dialog The top figure below illustrates the input Source surface water theme and the overal watershed theme The bottom figure below illustrates the resulting surface water and the primary pour point themes Primary Pour Point April 2006 Step 02 Extract and Clip the Surface Waters to Primary Watershed Page 89 Critical Evaluation Required by the User The Primary Pour Point theme will contain three attribute fields Pptid contains a unique identifier Sequential number for each point PPtType is used to identify the type of pour point represented by the point There must be one and only one point record in the theme which has the value Outflow in this field UpStrmDA is used for defining the upstream drainage area The value is relevant only for those points identified as Inflow points in the PPtType field An accurate value is critical for proper calculation of Channel Width in Step 08 If the legend file PPtT ype avl exists in the SysData directory the Primary Point Theme will be displayed in the view with the legend shown to the right That legend will display each point in accordance with the PPtType assigned in this step i e Outflow and Unkown If a single intersection point of the stream network and the overall watershed boundary is foun
134. ct the attribute fields which are to be transferred to the output theme e The pre defined name for the surface water output theme will be displayed e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data Selecting Attribute Fields to Transfer It is not possible to predict the attribute fields which will be included in the source theme for surface waters and therefore the surface water theme resulting from Step 02 Most of those fields will have little value in Stream Geomorphic Assessment and many will not be valid when the stream segments are combined in this step Note If the TribID s are already assigned in the surfacewater shapefile you MUST select that field to carry them onto the next step Either select all fields or selected fields You can select to have all fields transferred from the input theme to the output theme no fields or selected fields by clicking on the corresponding radio button on the left side of the dialog Should you elect to transfer selected fields then the Select Fields box on the right will be enabled Select those fields to be transferred by clicking on the first field of interest Then hold down the Shift key while clicking on any other fields Among the fields that may be available and may be useful are RivName and Rivid The RivName field may contain the name or a code w
135. ctories and restore the system tables SysBase Theme dbf SysRegFields dbf and SysLog dbf from the Temp directory to the SysData directory When the SGAT extension is then started the data sets previously registered will be found and one can proceed with using the Tools If any errors are detected during the initialization procedure the following error message will be displayed 2 SGAT System Error 44 GeoSW Splash IbtContinue Cli x 44 Fatal System Error Access to extension prevented When a fatal system error has been detected the hidden DocGUrls created SysTable and Sys View will be removed from the ArcView project and you will be returned to ArcView Remember that the SGAT extension remains loaded it simply is not being used Refer to the earlier section for unloading the SGAT extension from ArcView If no errors have been detected during the initialization procedure the following warning message will be displayed To AVOID corruption of the project file themes or tables DO NOT 1 modify any themes 2 modity any tables 3 save the T project or 4 close the project while in the SRAT extension ALWAYS exit the SRAT Extension click the Exit button on the Main Dialog prior to any of these actions SGAT will remain active until one clicks on the Exit button on the Setup Dialog Until that time the hidden DocGUFs will remain in the ArcView project When one clicks on the Exit button the hidden
136. cts FITO Piimpact eq shp Existing Theme FITOTPtImpactieg shp for Impacts Point with segmentation Ids assigned will be replaced Polvline Impacts FIT oH LrlmpactSeq shp lt Existing Theme FITOI Lnlmpact eg shp for Impacts Polwine segmented will be replaced To be saved in H Geomorphologp wersion DenvdD atas Note for insertion into System Lo User Hote Segment Done To use this dialog e The theme containing point impacts created in Step F T00a and potentially modified by Step FITO0Oc will be displayed e The theme containing polyline impacts created in Step F T00a and potentially modified by Step FITO0c will be displayed e The theme containing segmented surface waters created in Step SEGO7 will be displayed e The theme to be created that will contain the segmented point impact features that have been indexed will be displayed e The theme to be created that will contain the segmented polyline impact features that have been indexed will be displayed e Enter a note to be entered into the system log upon completion of segmentation processing April 2006 Part D Step FITO1 Feature Segmentation Page 214 Starting the process After the required information has been entered on the dialog click on the button labeled Segment Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment To
137. ctually traces the stream network starting at the primary pour point of the overall watershed created in Step 02 or manually assigned by the user following Step 02 The stream network traced is composed solely of those stream segments which were assigned a tributary identifier in Step 04 Attribute Fields Created for Reach Point Theme All fields pertaining to the reach points are created in the attribute table of the reach point theme once Step 06 is completed While all fields are created during this step however not all fields are populated with values in this step Refer to Appendix C and D for the list of fields associated with each reach point and identification of the step in which the fields are populated Note All fields are created at this point to enable the user to have access to the dialog in Step 10 for reviewing data associated with reach points Note For technical reasons the fields required for the mport capabilities provided in Step 10 are not created in this step They instead are created during the mport function itself This provides the mechanism to detect whether the import has occurred In addition the formats of the fields in the import table are used to define the fields within the attribute table for the reach point theme The fields that are populated in Step 06 are as follows RchPtid As the stream network is traced a Reach Point is created each time a watershed boundary is crossed This point is a
138. culate Reach Points and Reach Point Data Page 116 Accessing the Dialog To access the dialog for this step click the button labeled Step 06 Calculate Reach Points on the Part B main dialog The dialog for this step is illustrated below Part B Step 06 Calculate Reach Points E iinput Themefs sub Watershed s00subwshed shp Theme for Sub Watersheds to be used Primary Pour Pt 502PP01 sh 02PPt01 shp Theme for Primary Pour Pt to be used Surface Waters Sos5swrinal sh Theme for Surface Waters clipped to Sub Watersheds to sik be used Units in which Distances and Areas will be calculated Linear Units Feet 3 rea Writs sq Mies Output Theme for Reach Pts Themes resulting from this step have been created Reach Pts S06RPts02 shp v Select Theme to be replaced or New Version to create a new version To be saved in h geomorphology wersion3 D ervdD ata Note for insertion into System Log User Note Format for Reach Point Identifiers is Main Stem MO1 M from Step 04 Tributary 71 01 T1 from Step 04 Calculate Done To use this dialog e The theme representing sub watershed boundaries will be displayed e The theme representing the primary pour point for the overall watershed produced in Step 02 will be displayed e The theme representing surface waters clipped to the sub watershed boundaries produced in Step 05 will be displayed e The pre def
139. d In a like manner one can use the Land Cover Land Use LcLu theme as the data theme Step 11 could clip the LcLu theme to either the stream corridor or the sub watershed This step would then aggregate the areas by LcLu code or land cover land use type falling within each unique boundary corridor or sub watershed of the selected boundary type The following table illustrates the various combinations that can result from Step 11 Boundary Theme Data theme used as input in used in Step 11 Step 11 Stream Corridors X X Sub Watersheds an x The X s represent a theme resulting from Step 11 This step then takes that theme and summarizes the areas for each of the unique classifications found in the Data Theme i e soils mapping unit for soils and LcLu type for LcLu for each of the unique boundaries found in the Boundary Theme i e each stream corridor or each sub watershed The output table will have one record pertaining to each unique combination of classification and boundary as illustrated in the following table Record Boundary Classification Area Other Descriptive Stream Corridor or Soil Mapping Unit or Assigned Data Tae aE LcoLu qT TPS o n Also refer to the figure at the end of this section for a specific example of a table produced by Step 12 April 2006 Step 12 Summarize and Attach Descriptive Data Page 163 After the summation occurs data from the corresponding
140. d that point will re automatically be assigned as the outflow for the G2 Attributes of S02ppt shp watershed That point will be defined as the initial reach Shape Pptid Ppttype point on the main stem and the PPtType attribute field Point 1 Outflow for that point will be assigned the value of Outflow as ciii oT shown in the figure to the right Only one point can be assigned that value If multiple intersection points are found the following error messages will be issued The name of the output theme for the Primary Pour Pts will be identified in the second error message 2 SGAT Warning 1160 GeoSW ClipToWs IbEClip click x 1160 Warning The Surface Water theme contains multiple streams that Intersect the Watershed Boundary This signifies possible errors in either the Watershed Boundary or the Surface Waters Please perom review editing before continuing analyses 4 SGAT Warning 1161 GeoSW ClipToWs IbtClip Click x 1161 Warming Multiple Pour Pts exist for watershed Refer to the User Manual for identifying the Tnflow and Outflow points for the watershed Updates required to the fields named PFtT ype and UpstrmDA of theme SO2PPt shp April 2006 Step 02 Extract and Clip the Surface Waters to Primary Watershed Page 90 View2 of SO02ppt2 shp Inflow Outflow Unknown vv Lewis _creek_water shp _ SO2waters shp A Compiled_bound
141. d Attach Descriptive Data on the Part C menu dialog is clicked but before the dialog is actually displayed This occurs because the test for the existence of the theme is also conducted on the open event of the dialog If the theme representing the LcLu data theme clipped by the corridor boundaries does not exist the error message will be issued Simply click on the Ok button in the error message The dialog will appear and you can then select the desired combination of radio buttons Starting the process After the required information has been entered on the dialog click on the button labeled Summarize Processing may take a few moments depending upon the hardware used SGAT Y N 1006 GeoSW 5um btSum Click 1006 User supplied parameters okay Processing may take a few moments Do wou want to continue Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages Upon completion Alias of output table will vary 12LC for LcLu clipped to stream corridors 72LW for LcLu clipped to sub watersheds 12SC for soils clipped to stream corridors or 12SW for soils clipped to sub watersheds Legend file used N A The output table will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This table is added to the user tables area The output table will have all of the attribute fields from the
142. d Theme RchPtid There is a one to one correspondence between a sub watershed and its reach point The reach point serves as the pour point where all of the water flows out of the sub watershed The identifier of the reach point for the sub watershed is inserted into this field Note The AchPtlid field provides a link to the data associated with reach points for thematic display of that data using the sub watershed theme TribID The Tributary Identifier from Step 04 assigned is that of the stream flowing through the reach point and thus serving to provide drainage from the watershed SubWSArea Area of the sub watershed This field is originally calculated in Step 01 however it is recalculated in this step to ensure that the area reflects that of the sub watershed polygons Note It is possible that the user modified the boundaries of the sub watersheds to correct for errors or to simply adjust their configuration In such cases if Step 01 was not re run the area of the sub watersheds would not be accurate SubWSld A unique identifier for each sub watershed TribldSet Indicates whether a sub watershed was encountered in tracing the stream network using only those streams assigned a tributary identifier Field will contain a value of N or Y and is used in the display of the sub watershed theme in accordance with the legend file SubWSUsed avi see discussion later in this section April 2006 Step 06 Cal
143. d boundary theme by clicking on the corresponding radio button The data theme can be any theme and is chosen by selecting an ArcView shape file on the hard disk Unlike other themes the data theme does not need to be registered This provides greater flexibility and efficiency To select the theme simply browse to the directory in which the shape file is located on the hard disk and select the shape file When the data theme has been selected the units to be used in calculating densities will be displayed At present the units are as follows e For point features Number of units or count e For polyline features Feet e For polygon features Square Miles Once the shape file to be used for the data theme has been selected one can qualify which features are candidates for use in calculating densities To accomplish this one performs the following 1 Check the Use Feature Selection control Select the attribute field name for the data theme that contains the values identifying the features to be used and 3 Select the values of the attribute field that identify features to be used in calculating density April 2006 Step 15 Calculate Densities Page 183 To access the dialog for this step click on the button labeled Step 15 Calculate Densities on the Part C main dialog The dialog for this step is illustrated below Part C Step 15 Calculate Densities Boundary Theme Defining Areas for which Density will be Calculate FIRS
144. d containing the values identifying feature types If the Tools extension finds a field named Sw it will be displayed If that field does not exist then Not Selected will be displayed You must then select the correct field 3 Once the field has been selected the values for that field will be displayed in the larger box Select those values which are to be retained in the output surface water theme As indicated in the table above the values which should be retained are C N and S If one or more of those values are not listed in the larger box then the missing values were not found in the input surface water theme Be sure to scroll up and down in the larger box to ensure that you have selected all appropriate values To select a value simply click on it After that hold the shift key down to select additional values Note If you check the Extract Selected Linear Features check box but don t select a field name 2 above or at least one value 3 above an error message will be issued when you click on the button labeled Clip Using the Flow Regime extraction on the dialog The procedure described above can be used in the box on the left for Flow Regimes At present data values for Flow Regimes e g permanent intermittent or unknown have not widely been captured The ability to extract using flow regimes has been included in this dialog for use by those who have access to such data For example you may want to a
145. d from the ArcView project and the hard disk Warning Soils that were not found in the SOOTop20_05 dbf table will not be included in the table created by Step 12 This will cause the sum of the soils areas not to match the corridor or sub watershed area April 2006 Step 12 Summarize and Attach Descriptive Data Page 169 Step 13 Sum Data to Upstream Watershed Area This dialog utilizes the soils and or the land cover table produced in Step 12 Step 12 Summarizes the area for each unique classification i e soil mapping unit for soils and LcLu type for LcLu found within each unique boundary i e each stream corridor or each sub watershed This step simply adds another level of aggregation The area associated with each unique classification from Step 12 is summed for all boundaries located above a given reach point This in effect represents the catchment or drainage area above a reach point The areas pertaining to a unique classification for all stream corridors or sub watersheds located above a given reach point will be summed This for example enables one to determine how much of a specific type of soil lies above a given reach point To access the dialog for this step click on the button labeled Step 13 Sum Data to Upstream Watershed Area on the Part C main dialog The dialog for this step is illustrated below Part C Step 13 Sum Data to Upstream Watershed Area Input Theme s Reach Points SosRP
146. d theme is not of the Point Polyline or Polygon feature class the following error message will be displayed MonktonE site shp Feature class must be ether Point Polyline 1033 Invalid feature class of Pointe for shape file STOP or Polygon If the shape file is of the proper class then one can refine or qualify the features to be used in calculating the density To accomplish this click on the box preceding Use Feature Selection until a check mark appears This will enable the Field Name control The Field Name control will contain the list of attribute fields associated with the data theme selected Scroll down the list of fields until the desired field name is displayed and then click on the field name Once a field name has been selected the Data Values control will be enabled Note Only fields of tyoe Character or Decimal with no decimal places will be listed in the Field Name control The unique values for the selected field will be displayed in the dialog control for Data Values All values that represent features to be used must be selected To accomplish this click on the first value then hold the Shift key down and click on any remaining values When through selecting the values to be used move the cursor to the User Note field and enter any appropriate comment or note for the operation being performed The following figure illustrates the Use Feature Selection options where the appropriate data values have been se
147. d with it To Delete the impact currently displayed on the dialog click on the Delete button Following that a warning message similar to that illustrated below will be displayed 277 IF you continue the Impact Id 3 will be deleted from all reaches identified in the Reaches control on the dialog Do vou want to continue If the Delete button was clicked upon accidentally select No Otherwise click on Yes In the latter case all records if more than one associated with the impact will be marked for deletion It is possible that multiple records exist for a given impact represented by a polyline feature This will occur if the impact crosses sub watershed or reach boundaries In this case there will be one record for each reach in which the impact is located Note As indicated the records will be marked for deletion They will not actually be deleted from the impact theme until one clicks on the Save button Alternatively one can click on the Cancel button to remove any modifications made including marking records for deletion Once an impact has been deleted the Cancel and Save buttons will be enabled April 2006 Part D Step FITOOc Feature Data Modification Deletion Page 212 Modifying Impacts Once the 1 Impact Type point or polyline 2 Reach Id and 3 Impact Id have been selected the data associated with the impact can be modified Effectively all data can be modified except
148. de areas between adjacent sub watersheds and are not composed of multi part polygons If any of these conditions exist they can result in erroneous data sets being generated Further these types of errors may result in errors occurring in various processing steps The errors identified may not actually represent the true error and may occur in the latter processing steps This can result in a significant loss of time in determining the actual cause of such errors Surface Waters The surfacewater theme is available at the 1 5 000 scale from VCGI as a themes called the Vermont Hydrography Data Set or WaterHydro_VHD These are available from VCGI in Arclnfo Export format The entire state is subdivided into tiles Each tile has a geographic extent of a Huc 8 or Vermont planning basin based on the the Basin17 shapefile Multiple tiles may be required to obtain complete coverage for a watershed If starting with multiple tiles the data must be converted into a shape file and all tiles must be merged into a single shape file If starting with one tile you must use the route drain file NOT the route rch as shown in the following figure 2 Add Theme x Directory gis data nhd ct bellows falls to vernon _darnvhd01 080107 0k tae nhd gt och l Eed region rch gis data region wb nhd cl bellows falls to yvernon i route Irn vhd01 00107 route rch E info i Directories polygon C metadata nce BB
149. dentifier Trib Id Clear point locations identified via above Assign tributary identifier Trib ID entered above Save rib ld s assigned since startup or since last Save Cancel Trib d s assigned since startup or since last Save Validation Result Validate Continuity Clear ALL Trib Ids Show yew Instructions Blank Intenvening Polplinels 77777 Tribld Parts When assigning tributary identifiers the following order is recommended s Enter the value of the tributary identifier to be used at the top of the dialog 2 Establish a check mark in the checkbox control labeled Break polyline at upstream ending point A tributary identifier generally always starts at either the outflow point of the overall watershed or at a confluence point This by definition means at the initial vertex of a polyline Conversely most tributary identifiers are not directly associated with the terminal vertex of a polyline As a result if a check mark is located in the check box to break polyline the surface water will be broken at the point entered by the user and the use of the Trib Id value will stop at that point April 2006 Step 04b Assign Tributary Identifiers Interactively Page 102 If the check mark is missing from the check box to break polyline the use of the Trib Id value will extend to the end of the polyline which may be quite a ways upstream from the actua
150. dialog if the User Type has not been selected Stor 1066 Application has not been selected Please select in this dialog April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 59 User View Finally one must identify or create a View to which the themes registered by the user or created by processing steps within the Tools will be added To select a view click on the Set View button A message box similar to that shown below will be displayed that lists the existing views in the project and includes and entry for Create New View E Select iew to which themes will be added x Create New View Note If you have received an SGAT template from the RMS the view will already be set for you Click on the view to be used or click on Create New View If the latter is selected a message box will be displayed as shown below requesting the name to be assigned to the view Enter Name of iew to be created a x View Mame The default name of SGAT will be displayed Enter the name that is to be assigned to the view lf a name is entered that has been assigned to an existing view the following will be displayed SGAT Y N 1069 Geo5SW Main lbtSetYiew Click 1069 The name of an existing View has been entered Do you want themes to be added to the view SRAT The View must be selected prior to accessing any of the other functions on this dialog If the View is N
151. ding the one for which the value of SWUsed is greater than 2 Check the lengths of any polylines connecting to that segment or within the search radius If any are found to be less than the 0 25 or current value then the error may be caused by the value used for the search tolerance April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 122 To address this issue one can reduce the search tolerance To accomplish this use the Measurement Units dialog shown below The bottom portion of that dialog contains a control named Connecting Feature Search Distance Reduce the value shown perhaps by half Then re run Step 06 again Note To access the Measurement Units dialog go to the Setup Dialog and click on the button labeled system Functions in the lower left corner System Measurement Units used in Analyses View and Measurement Unit View Map Units Meters System Units in View Map Units Controls geographic searche Connecting Feature Search Distance 0 25 The connecting feature search distance is also used in Step 06 to establish the starting direction and point for tracing the surface waters If the primary pour point established in Step 02 is located within the connecting feature search distance of two or more sub watersheds then the error displayed below will be issued 2 SGAT System Error 0014 GeoSW Common Polygor F xX 14 Primary pour paint for overall watershed i within
152. e ChaniSnuos ValySlope and or ValuContin will be cleared and reused for theme SUBRPts shp Do vou want to continue Upon completion a message similar to that shown below will Summarize the number of reach points for which a given calculation was performed 2 SGAT Info GeoSW Revu lbtCalc Click aa xX Updates Calculated GP Channel Slope 0 Valley Slope 0 Sinuosity 8 and Confinement 8 If upstream reach points could not be associated with reach points a warning message will be displayed after calculations have been competed SGAT Warning 1092 GeoSW Revu lbtCalc click x 1092 2 reach points were not associated with upstream reach O pts No slope calculations were made for them User review and calculation required The above message could occur if the user assigned Trib Id s to all branches at a confluence point that differed from the stream draining from the confluence point In these cases there is no clear link between the neighboring reach points and therefore the slopes cannot be calculated If no calculations were made the message shown below will be displayed Stor 1093 No updates were calculated Required data missing or In Error Any calculations made in response to clicking on the Calc Data button are added to the pending changes To make these changes permanent click on the Save button or to cancel the changes click on the Cancel button April 2006 Step 10
153. e Theme for Overall Watershed to be used lente SO1Watershed01 shp v Surface Water Theme and Extraction Criteria Theme for Surface Waters to be used Theme s00swimodified shp v Flow Regime FReg Selection Linear Stream Feature Selection Extract Selected FReg s M Extract Selected Linear Features FReg Field Not Selected v Feature Field Sw v FReg Values A Feature Values a j usually C N S Press Shift key to I select multiple Press Shift key to in select multiple hd Themes to be Created Existing Theme 5025W Clipped shp for Surface Waters urface Waters 5025WClipped shp for Watershed will be replaced f l Themes resulting from this step have been created Primary Pour Pts 502PPt01 shp Z Select Theme to be replaced or New Version to create a new version To be saved in h geomorphology version3 DerivdD ata Note for insertion into System Log User Note Clip Extract Done To use this dialog The theme representing the overall watershed created in Step 07 will be displayed The source theme for surface waters will be displayed Identify extraction parameters if any for flow regimes Identify extraction parameters if any for linear feature types The pre defined name for the surface water output theme will be displayed The pre defined name for the primary pour point output theme will be displayed Enter a comment note in the Note text
154. e and AliasName must be unique Further there is a 10 character limitation for entries under AliasName Refer to Appendix E or F for additional information It is recommended that maintenance of the reference tables be performed at a central facility This would eliminate the need for all users to perform similar updates New versions of the table could then be forwarded to all users April 2006 Step 14 Summarize Area by Field Value Cross Tabulate Page 182 Step 15 Calculate Densities This dialog allows one to calculate densities of various features that lie totally or partially within either the sub watersheds or stream corridors Features can be such elements as structures roads wetlands etc These features must be represented as points polylines or polygons in an ArcView shape file Note Certain applications that may be used to create data sets representing features may use a subset of the primary classes of features namely points polylines or polygons For example some applications of which AutoCAD is an example may be used to create roads using the PolylineZ class Any classes other than the basic ones of Point Polyline or Polygon must be converted outside of the Tools prior to use in this Step Two themes are used in processing A boundary theme and a data theme The boundary theme will be either the sub watershed theme provided by the user or the stream corridor theme created via Step 09 One selects the desire
155. e dialog for this step click the button labeled Step SEGO1 Segment Reaches on the Part D main dialog The dialog for this step is illustrated below Part D SEGO1 Segment Reaches Input Themes Segmentation Pts rchseapts shp es User supplied Reach Segmentation Points to e used Surface Water SEGOISWSEGOTshp Theme for Segmented Surface Waters to be used Reach Points S06RPts01 shp Theme for Reach Points to be used Linear Units of Measure to be use Linear Urita Feet ss Theme to be Moditie Surface Water SEqn1SwSEGOI Sp la ve a a based upon Theme to be Create Segmentation Fts SEquISeqPtstroishp Theme will be created upon completion of this Step To be saved in h geomorphology version4 D enyvdD ata Note for insertion into System Lo User Note Segment To use this dialog The theme representing the user supplied segmentation points will be displayed The theme representing surface waters created in Steo SEGOO will be displayed The theme representing the reach points created in Part B Step 06 will be displayed Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data April 2006 Part D Step SEGO1 Segment Reaches Page 196 Starting the process After the required information has been entered on the dialog click on the button labeled Segment Proc
156. e export table RchData dbt exists in the directory H Geomorphology Support Cabot D envdD atas Do wou want to replace it If you wish to have the table replaced with a current version of the data click on Yes Otherwise click on No If you are periodically exporting data you can always copy or move the table generated to another directory This provides a method of retaining versions of data and backups The export table is not used in the Tools As a result this table can be moved or deleted as requirements dictate Upon completion The dBase table named RchData dbf containing the data associated with reach points will be saved in the DerivdData subdirectory under that in which the ArcView project file exists The table is NOT added to the ArcView project A sample of the table is illustrated on the following page Not all of the fields that are generated in the dBase table are shown due to size of table The Export function of Step 10 can be performed anytime subsequent to the completion of Step 06 This step simply exports the attribute data associated with reach points to a dBase table which can then be used in another application Upon completion of the Export operation you will be returned to the dialog for Step 10 Click on the button labeled Done to return to the Part B menu dialog April 2006 Step 10 Data Entry Review of Reach Point Data Page 157 RehPtld T1 10 T1 09 T1 08 T1 07 T1 06 T1 05 T
157. e number of parts of the polyline resulting from the processing This should always be one 1 e RchPtld Reach point identifier as calculated in Part B Step 06 e SWLength Length in feet of the Tributary or main stem extending through the reach e SWSegID A field that will be used to hold a segment identifier if the reach is segmented in Step SEGO1 This field is initialized to a single dash e Tribld Tributary Identifier assigned by the user in Part A Step 04 Records containing a zero value for ChanlWidth are deleted These will be the small segments of tributaries at confluence points The number of parts that the polyline representing the tributary or main stem is composed of is set in the NumParts field If any polylines are composed of more than one part are detected an error message is issued This represents a disconnected tributary or main stem If any error messages are issued the user should address and correct the errors This step should then be re run The iterative process should continue until no errors are detected To access the dialog for this step click the button labeled Step SEGOO Setup Surface Water Theme on the Part D main dialog The dialog for this step is illustrated below 2 Part D SEGOO Setup Surface Water for Reach Segmentation x Input Themel Surface Water Spsswrinal shp H e i Surface Waters clipped to Sub watersheds to Theme to be Create
158. e of the names may be cryptic Note The data fields in the Impact Feature Data panel will be identical for all sub impacts of a given Impact 5 It is recommended that one enter a description of the impact This may be the only way to distinguish between similar impacts within the same reach 6 Enter the values for the Observation Data Date on which the observation was made Person making the observation and the Organization to which the Person belongs 7 Once the data has been defined click on the button labeled Set Pt Location or Set Start End Pts depending upon whether the impact is represented as a point or polyline feature 8 Click on the title bar of the view to make it the active window 9 With the view as the active window use the zoom pan tools to navigate to the area of the point or starting point Work at a view scale where one can enter a point that can be associated with a specific surface water polyline If one works at a very small view scale incorrect selection of surface water polylines may occur This will lead to error conditions 10 When you are zoomed in to an appropriate scale for selecting the point click on the Feature Indexing tool This tool is the furthest to the right on the same line as the zoom pan identify tools and is represented by the eyeglasses icon With that tool selected click at a point in the user view where the Point feature or the starting point is to be located Note The poi
159. e output theme identified on the dialog and that theme will be added to the view identified on the Main dialog Clicking on Yes will cause the software to ignore the reach point identified in the error message and will continue on with the next reach Note Multiple occurrences of the above error continuation messages can happen If you encounter error conditions please refer to the digitizing rules described earlier in this section entitled Digitizing Modification of Valley Lines or Data f you have adhered to those rules the algorithm employed in this step has encountered a set of circumstances that prevent it from creating the valley lines In such cases you can use the Measuring Tool of ArcView to obtain the length and average width of the valley lines omitted and enter those values into the appropriate reach points using Step 10 Then click on the Calc Data button to have the derived data elements calculated Upon Completion Alias of output theme for valley line ValleyLine Legend file used to display Clipped Surface Waters theme ValleyLine avl The theme representing the Valley Line will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This theme is added to the user view identified on the Main dialog Click on the button labeled Done to return to the Part B menu dialog Upon completion of processing for this step a message similar to the following will be displayed This is a genera
160. e parts can be formed during the clipping procedure The figure to the right illustrates a stream segment blue flowing from east to west Due to digitizing errors in either the sub watershed boundary most likely or the surface waters the stream is shown leaving the sub watershed A on the east re entering it and then leaving again When this polyline is clipped both parts falling into sub watershed A are used to form a Stream segments forming multi part polyline in sub watershed A Sub W atershed A multi part polyline and the part falling into sub ee pate amp 7 watershed B forms a single part polyline SRG a a a B The attribute table for the output theme will A 6 contain a field named GeoSWRevu If a multi Sub Watershe part polyline is encountered this field will Boundary April 2006 Steps 05 Clip Linear Surface Waters to Sub Watershed Boundaries Page 113 contain the value Y to identify the polylines causing this error Further if the legend file named TribldError avl is located in the SysData directory the output theme will be displayed using that legend Any errors must be corrected prior to continuing If the error is in the sub watershed delineation correct the error and re run this step If the error is in the surface water theme correct the error in the surface water theme used as input to this step Then re run this step Remember however that now the surface water theme used as input to this s
161. e provided by VCGI will have to create versions of the SOOLuCodes dbf SO0Top20_05 dbf SOOLcLuXTabFields dbf and SOOSoilXTabFields_05 dbf Upon completion Alias of output table will vary 14SC12 reach data for soils clipped to stream corridors 14SW12 reach data for soils clipped to sub watersheds 14LC12 reach data for LcLu clipped to stream corridors 14LW12 reach data for LcLu clipped to sub watersheds 14SC13 reach watershed data for soils clipped to stream corridors 14SW13 reach watershed data for soils clipped to sub watersheds 14LC13 reach watershed data for LcLu clipped to stream corridors 14LW13 reach watershed data for LcLu clipped to sub watersheds Legend file used N A The output table will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This table is added to the user tables area dBase files impose a maximum of ten characters for field names As a result some of the field names may be cryptic in nature Refer to Appendix E or F to for a definition of the field names There will be a field in the table for each unique value Field Value Name for those fields selected on the dialog The values for those fields will be the area in square miles within the given corridor or sub watershed depending upon the boundary theme used for clipping in Step 11 Refer to the preceding figure showing the resulting table for flood characteristics of soil mapping units In addit
162. e rules stated at the beginning of this section If the appearance of the valley line seems suspect check to see if changing the length would alter the category to which the reach would be assigned for Sinuosity If altering the length would not affect the category then there is no need to alter the valley line other than for visual appearance on any maps to be produced The following figure illustrates certain of the considerations described above gt lt qh a Valley line segment not fl drawn at confluence points tee U Ais Valley Lines Red April 2006 Step 07 Calculate Valley Line and Data Page 134 Digitizing Modification of Valley Lines or Data One has the option to modify the theme in a variety of ways to improve the visual appearance of the valley lines or to increase their accuracy Specifically one can edit the valley line theme to include missing valley lines or alter existing one by moving vertices If modifications are performed to obtain more accurate valley lengths the attribute table will have to be edited to update the valley lengths in the field ValyLength Note Remember if the Calculate button of ArcView is used to update the valley lengths ArcView will return the lengths in the units set for Map Units for the view This will generally be in meters for the State of Vermont The following equation can be used in the Calculate Dialog to obtain lengths in feet Shape ReturnLeng
163. e system DocGUIs SysTable for tables and attributes of themes or the view RegThemes in SysView This provides rapid access for the Tools for all of the referenced themes tables The data associated with themes tables that have been registered is maintained from one session of the Tools in the system tables SysBaseTheme dbf and SysBTReqFields dbf n addition the directories in which these data sets should be located is automatically determined as noted earlier The directory structure is maintained in the system Table SysDir dbf During the process of adding the registered themes tables the following tests are performed o Does the referenced theme or table exist in the required directory o Can each data set be edited Note The system table SysBaseTheme dbf contains a field that indicates whether the data set is a base source or derived created by the Tools data set This is then translated into the corresponding directory for that type of data set Base data sets are to be located in the BaseData directory and derived data sets are to be located in the DerivdData directory If it is found that one or more of the registered data sets are not located in the required directories the following warning message will be issued required directories and hawe been unregistered Heview log 29 2 previously registered 56AT Warning 0029 Geos Comme T entries for data set named System to identity those NE After the initia
164. e the Pan tool to follow the streams up to the terminal reach points Check to see that the valley lines created reasonably follow the center of the valley walls As you review the valley lines keep in mind the following Only that part of the valley located within a sub watershed is considered If the valley walls extend laterally outside of the sub watershed the area outside of the sub watershed is ignored This will be most prevalent where tributaries meet at a confluence point Keep in mind that if you were measuring the length and width of a valley manually you would be working with USGS Topographic maps at a scale of 1 24000 or 1 25000 So trying to achieve accuracy to a high degree is not warranted The valley lines should be within a reasonable distance of the middle of the valley If you find a valley line that looks significantly off determine the length of a valley line that you would create To do this use the Measuring Tool of ArcView and click on points that you would use to draw a valley line ArcView will show the length of the last segment and the total length on the Status Line Double click to quit measuring Write down the downstream reach point identifier and the length indicated by ArcView on the Status Line Remember that the length reported by ArcView may be in meters or which ever type of Distance Units the user set in the View Properties Convert meters to feet by multiplying by 3 28084 feet
165. e was released by the source agency This will aid future users to identify more current data that may be available Status The status of the data i e preliminary release update in process etc The status levels were borrowed from those used by the Vermont Center for Geographic Information VCGI Note A free form text field for entering notes This can be a contact name for the data set a condition discovered with the data etc Note The source scale data available for themes is not applicable to tables The above data should be completed for each table registered It is not essential that the documentation information be entered at the time when the table is registered One can register the table and then return to the registration dialog for the given table to add or to update the documentation information as it becomes available Note All table registration data is maintained in the system table SysBase Themes dbf Field aliases are also used in identifying the names of fields required to be in the attributes of certain tables During the registration of the theme table specific fields will have to be identified for each of these aliases The following table lists those tables for which fields must be identified TableAlias Field Description SoilsTop20 Soil Mapping Unit Values in field will identify a soil type This field and the values Identifiers within it is used to relate to the soils theme in ord
166. eam end If the order is reversed then the vertex order is reversed in the surface water theme In this manner the tracing then continues upstream from one stream segment to the next As each new polyline is traced a sequential number is assigned to the upstream vertex The downstream vertices of all polylines connecting to that point are assigned the same sequential identifier The end result is that connectivity can be determined simply through the identifiers assigned thus providing a rapid method for indexing features i e identifying those surface water polylines that connect point A to point B When tracing if a point of confluence is encountered then the stream segment chosen will be the one forming the hardest right turn from the perspective of the direction in which stream network is being traced If it is found that no other segments are connected to an end vertex stream tracing is then reversed and proceeds downstream Using the above as an outline the figure below illustrates the order of stream tracing Assume that tracing begins at the confluence point in the upper right corner and the red arrows show the upstream direction and the green arrows show the downstream direction Tracing occurs in the numerical order shown Upstream Tracing Downstream Tracing April 2006 Step 04a Setup for Assigning Tributary Identifiers Interactively Page 98 Attempt to use Surface Water polylines more t
167. eam segment will begin at the outflow point That stream segment is acquired and the end vertex opposite end of the stream segment is used to find the next segment for tracing With the next stream segment its end vertex is used to find the next stream segment etc April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 120 In this manner the tracing then continues upstream from one stream segment to the next At the end of each stream segment a test is made to determine whether a sub watershed boundary is coincident with that point Remember that Step 05 clipped the stream segments with the sub watershed boundaries If a sub watershed boundary is found then a reach point is created at that point If a point of confluence is encountered then the stream segment chosen will be the one forming the hardest right turn from the perspective of the direction in which stream network is being traced If it is found that no other segments are connected to an end vertex a terminal reach point is inserted at that point Stream tracing is then reversed and proceeds downstream Using the above as an outline the figure below illustrates the order of stream tracing Note Neither sub watershed boundaries nor reach points are shown in that figure Assume that tracing begins at the confluence point in the upper right corner and the red arrows show the upstream direction and the green arrows show the downstream direction Traci
168. earch for After you have located the Ext32 directory simply copy the GeoSW4 avx file into that directory After copying the extension make sure that the Read Only attribute has been cleared 2 Extensions X Available Extensions To access the extension you must first start ArcView Then click on _ Digitizer the File menu as shown in the figure _ DNA Garmin Arciview eet to the right Then click on the _ DRG Tools Extensions item _ EDTaols Edit Tools vers 6 DEMO Reset _ _Geopracessing Make Default A list of extensions will be presented i Stream Geomorphic Assessment 4 00 amp to you Scroll down until you find the one named Stream Geomorphic Assessment 4 50 Click in the checkbox to the left of the name as shown to the right About Functions for assisting in Stream Geomorphic Assessment Werft O00 Then click Ok which will return you to ArcView April 2006 Setting Up for Using the Tools Page 14 If you have a project open and the active window is either the ArcView Project window or a View you will see a new button on the button bar with a squiggly line icon This icon is usually used to represent free hand drawing or sketching Just think of the icon as a stream centerline As illustrated in the figure to the right the button will usually be the furthest to the right This button provides access to the Stream Geomorphic Assessment Tools extension By clicking on t
169. ed below Each dialog will have an Execute button and a Done button Both of these will be located in the lower right corner of the dialog The Execute button may be labeled in a different way on each dialog but will reflect the operation which is to be performed Examples are Clip Dissolve Calculate Summarize etc Clicking on the Done button closes that dialog and returns you to the parent or next higher dialog in the hierarchy Refer to the figure on the preceding page Clicking on the Execute button causes the dialog to edit the information entered or selected on the dialog If information is incorrect or incomplete an error message will be issued The following is an example of such an error message occurring when a negative value for an elevation was entered for a reach point in Step 70 1095 The value 10 00 entered for Reach Pt Elevation is negative After clicking on the Execute button attributes of certain input themes may be edited This requires that the shape files pertaining to those themes be available for editing Specifically none of the files can be open in another application and the properties must not be marked as read only lf either of these conditions is detected the following error message is presented SGAT User Error 1004 GeoSW CalcChan IbtCale ch x 1004 Unable to edit Surface Waters data set Itis use by another application or has Read Only attribute set The most common situa
170. ed in Step FIT00a or Step FITO7 will be displayed The impact names that have been indexed in either the point or the polyline impact theme will be displayed in the mpact control Select the impact of interest to be extracted When a specific impact is selected the feature type either point or polyline used to represent the impact will be shown in the panel to the right If AIl Impacts is selected the feature type will not be displayed Only those sub impact names that are associated with the selected impact and that have been indexed will be displayed in the Sub mpact control If no sub impacts are present the phrase None Available will be displayed and the control will be disabled If only a single sub impact is present it will be displayed and the control will again be disabled If multiple sub impacts are present select the sub impact of interest to be extracted If all sub impacts for the impact are to be extracted to the same shape file select A Sub Impacts Only those location names that are associated with the selected impact and that have been indexed will be displayed in the Location control If no locations are present the phrase None Available will be displayed and the control will be disabled If only a single location is present it will be displayed and the control will again be disabled If multiple locations are present select the sub impact of interest to be extracted If all locations for the impact are
171. ed to a stream segment which flows from the sub watershed On the other hand if the sum of areas is greater than that of the overall watershed then the stream network composed of those stream segments that have been assigned a Tributary Identifier flows into a sub watershed more than once This would indicate a problem with the sub watershed delineation with respect to the surface waters Specifically it is likely that the sub April 2006 Problems Associated with Incorrect Assignment of Tributary Identifiers Page 109 watershed boundary has been drawn such that it crosses above a confluence point This would create two pour points for the sub watershed which is not valid Upon completion of processing Step 06 will display the sub watershed theme in accordance with the legend file SubWSUsed av assuming that legend file is in the SysData directory With that legend file the sub watersheds that have been used will be displayed in a color different from those that have not been used Use caution in interpreting the cause of the error as there may be both types of errors described above If the error message is displayed take time to review all of the source data sub watershed delineation sub watershed versus surface waters and assignment of tributary identifiers In calculating reach points in Step 06 each reach point is assigned the same Tributary Identifier as the stream flowing through it This is a critical attribute of
172. eds to be used Reach Points S06APts02 shp Multiple Themes for this input created Select Theme to be used last one created shown first Valley Walls sO0valley_walls shp z1 Theme for Valley Walls to be used Units of Measure to be used inear Units Feet t stS Buffer Theme to be Created Existing Theme SO7 alleyLine shp for Valley Line will valley Line S0 ValleyLine shp x be replaced To be saved in h geomorphology version3 D erivdD ata Note for insertion into System Log User Note Calculate To use this dialog The theme representing sub watershed delineations will be displayed The theme representing reach points from Step 06 will be displayed The theme representing valley wall delineations will be displayed The pre defined name for the valley line output theme will be displayed Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data April 2006 Step 07 Calculate Valley Line and Data Page 130 Starting the process Click on the Calculate button after all entries have been completed Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages During Processing The processing involved in creating valley lines is calculation intensive and can take several m
173. egistered All tables are used only in a read reference mode If the file selected is located in a directory other than BaseData the following message will be issued SGAT Y N 1085 GeoSW Reg Theme IbtSelectTheme Click 1085 The data set selected s00top20 dbf for the Alias Sails Top 20 Attributes i not located in the required directory H Geomorphology versiond Test BaseD ata Do you want the file s copied to that directory Clicking on No in the above message will abort the table selection as will be indicated by the following message SGAT User Error 1084 GeoSW Reg Theme lbtseledtt xj the directory H Geomorphology version T est BaseD atan 1084 Data sets for Base Themes T ables must be located in D File selection ignored Clicking on Yes will cause the table to be copied to the BaseData directory This ensures that the required directory structure is adhered to If no errors have been detected the selected table will be entered into the control labeled dBase File Name on the dialog Registration however will not occur until the Save button is clicked April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 70 The registration procedure also enables one to enter the following documentation for a table Source agency The organization agency or group responsible for creating and maintaining the data set Current As Of The date at which the table tabl
174. elect whether the impact is represented as a Point or a Polyline Feature This identifies which theme the impact will reside in either the point impact theme or the polyline impact theme In addition when the Impact Type is selected the control labeled Reach d will be populated with a list of those reaches for which impacts of the selected feature type have been indexed Note Only those RchPtld s for which impacts have been indexed will be listed in the Reach ld control 2 Select the Reach Id in which the Impact was indexed In certain cases an impact of the polyline feature type may cross multiple reaches All reaches in which a given impact is located will be listed in the disabled grayed out field labeled Reaches When a reach is selected the mpact Ids assigned to impacts that fall within the reach are listed in the control labeled mpact Id Note Only those mpactld s for impacts that are located within the given Reach Id will be listed in the mpact Id control 3 Select the Impact Id Once an impact id is selected the data assigned during feature indexing will be displayed on the dialog Always make sure that the correct impact has been selected prior to making any changes Using the description field may be the primary means of differentiating between similar impacts on the same reach Deleting Impacts Once the correct impact has been displayed one can either delete the impact or make modifications to the data associate
175. elete the data set from the BaseData directory without first un registering it using the options provided in the Tools Refer to the section Setup Registering Source Data DerivdData All data sets tables or themes created by any processing step in the Tools Temp will be located in this directory When a data set is created by a processing step it will automatically be registered Once a data set has been registered the user should not move or delete the theme from the DerivdData directory without first un registering the data set using the options provided in the Tools In certain processing steps in the Tools intermediate or temporary data sets are created These will be saved in the Temp directory Under normal conditions these data sets will be deleted upon completion of processing for the given step These temporary data sets will not be deleted if they can be useful to the user in correcting digitizing or attribute errors in the source data sets The user will be informed of the existence of these data sets at the end of the processing step Following the initialization procedure a copy of the critical system tables will be placed in the Temp directory These tables are SysBaseTheme dbf SysBTReqFields dbf and SysLog dbf Any data sets found in the Temp directory can be deleted without adverse affect on the operation of the Tools SysData Critical dBase tables and ArcView legend files are located in this directory The
176. end of this section April 2006 General Concepts Page 9 Theme Table Registration All themes or tables provided to or created by the user must be registered A primary reason for implementing a registration procedure is to associate a theme or table with its corresponding alias As a result a theme table is identified once and the Tools will then know the name of the data set to be used in all of the processing steps in which that theme table is to be used The registration procedure also enables one to enter the following documentation for a theme table Source agency The organization agency or group responsible for creating and maintaining the data set Current As Of The date at which the theme table was released by the source agency This will aid future users to identify more current data that may be available Status The status of the data i e preliminary release update in process etc The status levels were borrowed from those used by the Vermont Center for Geographic Information VCGI source Scale Much of the geographic data will have been electronically traced or digitized from various source documents such as the VT Orthophotos 1 5000 USGS Quads 1 24000 or 1 25000 and others etc The scales shown in parentheses provide guidance as to the relative accuracy of the data i e the smaller the number to the right of the colon the more accurate the data should be This documentation field will only be applicable to
177. enerally be due to one of two conditions o The data set is in use by another application For example one can open up a dBase table including the attributes to a theme using either Microsoft Access or Microsoft Excel among other applications If such is the case ArcView will recognize that it cannot apply edits o The data set has been copied from a CDROM When this occurs the attributes of a file as they exist on the CDROM will be carried forward to the copy on the hard disk Files on a CDROM will have the Read Only attribute set This prevents any modification of the files ona CDROM This attribute is also set on any copies made of the files to the hard disk Note Use Windows Explorer to clear the Read Only attribute of any files copied from a CDROM As indicated in the error message access to the SGAT extension is prevented until the error condition is corrected Initialize Buffer Reference Tables The final step in the initialization procedure is to verify the buffer reference tables In the Setup Dialog the user must select an Application The application permits one to use the Tools for different purposes such as Phase Geomorphic Assessment Fluvial Erosion Hazard Option 1 or Option 2 The selection of an application controls the processing and or functionality of the Jools At present the primary difference in the Jools is related to access to the fluvial erosion hazard zone in part E of the tool t The buffers are depend
178. ent data set and is used to post log entries of activities that take place during initialization or other system actions On the dialog is an Export button This can be used to export the log for a data set selected The Export button will create a copy of the log in dBase format in the Temp directory Upon completion a message will indicate the name of the exported log The name will vary depending upon the data set selected The resulting table can then be opened in either Microsoft Access or Excel for sorting formatting and or printing Due to limitations in the width of the og entry area on the dialog it is possible that the entire contents of the field for Comments including user notes will not be displayed By exporting the log one can then view the entire field Note If the selected data set is All Themes Tables the entire log will be exported April 2006 Using the Log Page 48 Accessing the Stream Geomorphic Assessment Tools With the extension loaded you can access the Jools button on the button bar of ArcView The Tools button will only be available when the active window in ArcView is either a View window or the Project window The figure to the left below illustrates the Tools button when the ArcView project window is active This button will usually be the furthest to the right on the button bar When the button is visible clicking on it will activate the Introductory or Splash screen shown below on the right for t
179. ent upon the following o Calculation of the channel width for each reach in Step 08 o Factor to be multiplied by the channel width associated with a feature type Due to the importance of these dBase tables the initialization procedure will verify their existence and format The following describes the verification process April 2006 Accessing the Stream Geomorphic Assessment Tools Page 54 The permissible applications are contained within the system table named SysApps dbf In that table one record will be present for each application Among other data the name of the buffer reference table to be used for the application will be included in each record If no buffer reference table is associated with an application the following error message will be issued SGAT System Error 0019 GeoS Common Projinit x 19 In system table Sys4pps dbf record for application SGA Stor does not have a value for field ButtrT able No butter reference table associated with application Note The above will occur if the value for the field BuffrTable is blank or contains Not Selected The buffer reference tables must exist in the SysData directory under the directory in which the ArcView project file is located If the table referred to in a given record is not located in the SysData directory the following error message will be issued A SGAT System Error 0020 GeoSW Common P ojinit x application SGA via
180. entation Page 215 Upon Completion Alias of segmented point impact theme created PtlmpactSeg Legend file used to display surface water theme PtlmpactSeg avl Alias of segmented polyline impact theme created LnimpactSeg Legend file used to display surface water theme LnimpactSeg avl Upon completion the following message will be displayed to summarize the processing that took place SGAT Info GeoSW FITSeg btSegment Click xj FIT IFtlmpact eg shp saved in directory H Geomorphology Yersiond SDenvdD atas Theme has been added to View SGAT FIT O1 LrlmpactSeg shp sawed in directory H Geormorphologysersion4l DernvdD ata Theme has been added to View SGAT Click on the button labeled Done to return to the Main menu dialog for Feature Indexing April 2006 Part D Step FITO1 Feature Segmentation Page 216 STEP FITO2 Extract Feature s Features indexed via Step F T00a are placed in one of two shape files One for point feature types FITOOPtImpact shp and one for polyline feature types FITOOPtImpact shp It is possible especially with polyline features that different impacts may overlay each other partially or completely In addition to the possible overlay of certain impacts it may be desirable to extract specific features for presentation on a map This dialog provides the capabilities of extracting features by a combination of impact name sub impact and location For polyline impact ty
181. entifier Tribld This is illustrated in the figure below In Step 04 the Tributary Identifier Tribld was changed from T7 to T7 01S1 and T7 01S3 at the point of confluence Since there is no continuity of the Tributary Identifier no valley line will be drawn In such cases the user must revert back to Step 04 and correct the assignment of Tributary Identifiers or determine the length and width of the valley and enter it in Step 10 If the latter action is taken the user must also use Step 10 to calculate Sinuosity Confinement and Valley Slope Attribute fields for the Reach Point theme See Appendix C and D for descriptions of all fields associated with the Reach Point theme The attribute fields calculated in this step are identified below Note All attribute fields associated with the Reach Point theme are created in Step 06 ValyLength Length in feet of valley line drawn ValyWidth Width of valley in feet This is calculated by obtaining the area of the valley walls that falls within the sub watershed and dividing that by the valley length ValyConfin Valley confinement will be calculated only if channel width data is available for a given reach This is calculated as the valley width divided by channel width This data does not get imported into the DMS but can be used within the SGAT program Sinuosity Channel sinuosity will be calculated only if channel length data is available for a given reach This is
182. entifier ends ae Note The starting point must fall on the downstream path between the ending point and the outflow point of the watershed If the starting and ending points do not lie on the same path an error message will be issued 11 Click on the dialog to make it the active window 12 If an error was made in selecting the points click on the Clear Start End Pts button Then re establish the points beginning with step 3 above 13 Once the Point s have been established and the dialog is active the tributary can be assigned by clicking on the Set Trib d button Warning The tributary identifier will not be permanently saved until one clicks on the Save button This permits one to cancel assignment if an error was made 14 To cancel pending updates click on the Cancel button This will clear all pending updates created since the start of the session or the last Save operation 15 To save pending updates click on the Save button This will permanently apply the assignments to the surface water theme As indicated in Steps 14 and 15 one must save the tributary identifier assignments If you attempt to quit the dialog by clicking on the Done button a check is made to determine whether any changes are pending If there are an error message is issued warning that the assignments will be lost if you continue April 2006 Step 04b Assign Tributary Identifiers Interactively Page 103 Tributary Ids Assigned Thus Far Near
183. envdD atan The attribute tables for surface water theme created will be updated as described earlier Click on the button labeled Done to return to the Part D menu dialog Possible Error Condition At the end of processing the number of parts of the polylines resulting from merging those with the same values for Tribld and RchPtld is counted If any polylines are found that have more than one 1 part the following error message will be displayed SGAT User Error 1056 GeoSW FEHSetup IbtSetup ch x 1056 Surface Water theme SEGOOSWSEG shp created Stor Surface Waters improperly divided into multiple parts A evie records in which field NumParts is not one 1 The occurrence of the error message means that the surface waters are not continuous through the reach i e there is a space separating different segments This is an error which should not occur at this point in the processing steps All such errors should have been detected early in the processing steps of Part A or Part B April 2006 Part D Step SEGOO Setup Surface Water Theme Page 193 Warning Ifthe above error message is issued review any records containing a value other than one 1 for the field NumParts and correct the condition causing the error in the source theme which would normally be the one resulting from Part A Step 04 Run all steps subsequent to that one including all steps in Part B and Part C as well as Step SEGOO April 2006 Part D
184. er may subsequently alter the values for Valley Length in Step 10 f altered the derived values Channel Sinuosity and Valley Slope must be re calculated in that step Warning If modifications are made in Step 10 do not run Step 07 or 08 again This will result in canceling any changes made in Step 10 April 2006 Step 08 Calculate Channel Width and Stream Data Page 136 SysChanWid Software generated value for Channel Width refer to Chan Width above Maintained separately for comparison with value of Chan Width should the user modify that value in Step 10 ValyConfin Valley Confinement is the Valley Width divided by the Channel Width The values will be calculated if Valley Width data is available from Step 07 or Step 10 Note The user may subsequently alter the values for either Valley Width or Channel Width in Step 10 lf altered the derived value for Valley Confinement must be re calculated in that step Warning If modifications are made in Step 10 do not run Step 07 or 08 again This will result in canceling any changes made in Step 10 Attribute fields for surface water theme The attributes listed below are calculated and added to the surface water theme RchPtlid Assigned to each stream segment This provides the user with the ability to select streams that fall within the sub watershed served by a given reach point SWLength The length of each stream reach ChanIWidth This value will be assigned to o
185. er to transfer the attributes to each soil area polygon Refer to Soils theme This field will usually be MUKEY if in VT SoilXTabFields None LcLuCodes LcLu Classification Values in field will identify the Land Cover Land Use classification Codes code This field and the values within it is used to relate to the LcLu theme in order to transfer the attributes to each LcLu area polygon Refer to LcLu theme This field will usually be GRID Code if in VT LcLuXTabFields To select a Field Name click on the drop down list and scroll up down to find the appropriate entry Then click on the field name This identifies the field to be used however the field will not be registered until the Save button is clicked Take the time to ensure that the correct field has been selected Incorrect selection will cause error conditions in subsequent processing steps that may be difficult to interpret Note The Field Name need not be defined at the same time as Table is selected However the table will not be considered registered until all required fields have been defined Note To remove a field selection click on drop down list for field and select Not Selected Whenever a table is selected or changes to data on the dialog have been made the Save and Cancel buttons will become enabled Any selection or changes will not take affect until one has clicked on the Save button April 2006 Setup Dialog for
186. ering it into the control labeled Note When a note is entered the Save and Cancel buttons will become enabled After the note has been entered click on the Save button to enter the note into the log The Log Audit area will then be updated to display the note along with the other entries Note Log entries are displayed in chronological order As a result a note entered via this dialog should be the last entry After entering a note clicking on either the Cancel or the Done button will result in the following message being issued SGAT Y N 1057 GeoSW Reg Derived lbtCancel Click 1057 The last changes have not been saved fF you continue they will be lost Do vou want to Continue Responding Yes to the above message will cancel entering the note into the log Responding No will return to the dialog however the note remains unsaved until one clicks on the Save button Deleting a User Note One can also delete a note or comment previously entered into the log These entries are identified by the term Commen in the Operation field To delete a note perform the following 1 Click on the entry in the Log Audit window that is to be deleted The entry should become highlighted If it does not then either a change is pending or an entry that cannot be deleted has been selected If a change entry of a note is pending click on either Save or Cancel Note Only those entries with Commen in the
187. ersheds Specifically the reach points fall at the intersection of the stream network and the sub watershed boundaries If the legend file SubWSUsed avl exists in the SysData directory Fil Compie boundaries sig the Sub watershed Theme will be displayed in the view with the C Subws Included legend shown to the right The legend will display each sub D Subws EXCLUDED watershed in accordance with the value for the field TribldSe fone en a which is assigned in this step The value for TribldSe will be set to Y if the sub watershed was encountered while tracing those streams for which a Tributary Identifier TribID was assigned in Step 04 Otherwise the value will be set to AN The legend will display the values Y and N as Subws Included and Subws EXCLUDED respectively An example is shown in the following figure A sub watershed displayed as Exc udea implies that the sub watershed was not encountered while tracing the stream network This in turn means that the streams entering the sub watershed were not assigned a Tributary Identifier in Step 04 In addition If the sum of the sub watersheds encountered during stream tracing does not equal the area of the overall watershed an error message similar to that shown below will be displayed 1106 Sum of sub watershed areas 22 0704 associated with reach points is not equal to area of overall watershed 23 1015
188. es the ability to manage the derived themes and tables Note This dialog cannot be used for any source themes or tables Their management is via the dialogs presented in the previous two sections Registration Manage Derived Themes Tables Derived Theme T able Information ___ Theme Table ESTs e DataSetSource Data Set Typ Active Multiple Versions Allowed Base fe heme fe Yes f ye Internal Alias SwClipped Derived Table C Wo fe Ho Jesription Surface Waters for Watershed Hit l step No fo2 Date 2003711704 Time 16 59 Pall h geomorphology version3 DerivdD atas Log Audit Notes ID Date Time RecNo Step Operation Input4 InputB Input Comment 21 2003 11 04 16 59 30 1 02 ClipTowS sOOswlmodified shp SOTwatershed shp N A Features C N S and Note to be added to Log Note Delete Theme Remove Theme Done This dialog is available via the button labeled Manage Derived Themes and or Tables on the Theme Table Registration and Management dialog This dialog is very similar in content and layout to that for viewing the Log The primary difference however is the ability to Remove or Delete a derived theme or table April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 73 To select a theme or table perform the following ie 2 3 Click on the drop down arrow next to the Theme Table control Scroll up down the
189. es will be registered separately although the same dialog will be used The specific table to be registered is selected by the button on the Theme Table Registration and Management Dialog The resulting dialog as shown below for Soils Top 20 Attributes will reflect the table being registered in the dialog Title To select a table click on the Select Table button In response the File Dialog will be displayed as shown below 2 Select File for Soils Top 20 Attributes X File Hame Directories aK h Wgeomorpholagy versions R fr Cancel Cg buffertables C communications C detivddata sul PA doc bd List Files of Type Drives dB aze Files h In the right directory structure side of the above dialog migrate to the directory in which the table is located Then click on the file name and then on the OK button or simply double click on the file name This will select the file to be used At this point the selected file will be reviewed with respect to certain edit criteria to help ensure that the correct table has been selected and that it is in the correct directory First a test is performed to ensure that the theme is not corrupted or invalid If this test is failed the following error message will be display and the theme selection will be ignored 2 SGAT System Error 0056 GeoSW Reg Table IbtSel xX 58 Data set s00lucodes dbf selected i corrupted or invalid Selection ignored
190. ese features from their original locations which would be coincident with the surface waters for cartographic purposes o Step FITO3 permits one to export data for indexed features for subsequent import into the DMS Part A Step 04 provides an interactive method for assigning tributary identifiers April 2006 Introduction Page 2 Credits Technical advice and review of the Tools during development were provided by the following Barry Cahoon Mike Kline Shannon Hill Staci Pomeroy and Ty Mack Agency of Natural Resources Department of Environmental Conservation Water Quality Division River Corridor Management Section Christa Alexander Agency of Natural Resources Department of Fish and Wildlife In Version 4 the algorithm for calculating valley lines in Step 07 was modified to use Thiessen Polygons Certain scripts for calculating Thiessen Polygons were extracted with permission from the ArcView extension Vector1 1 avx created by Francisco Olivera Ph D P E Department of Civil Engineering Texas A amp M University College Station TX An algorithm was then developed to trace the interior vertices to form the valley line Shayne Jaquith River Management Section Shannon Hill Waitsfield VT and Kristen Underwood of South Mountain Research and Consulting Bristol VT provided insight into the use of Version 2 that enabled improvements to the Version 3 Without the time and energy devoted by the above the software development wo
191. esenting reach points will be displayed e Select the Reach Point Id for which you would like to review data from Step 06 through Step 09 Reach Point attributes displayed on the dialog The following provides a brief description of the attribute fields associated with reach points that are displayed on the dialog For a more detailed description including identification of the step calculating a specific value refer to Appendix C or D e Identifiers o Reach Point Id is the value assigned in Step 06 to the reach points o Tribld is the value assigned in Step 04 for the stream segment that flows through the reach point o Distance Id Identifier for each reach point based upon distance from the primary pour point for the watershed e Reach Point Type Shows the PPtType assigned in Steps 02 and 06 Values that will be encountered in this field are Outflow for the primary pour point of the overall watershed Terminal for terminal reach points of the main stem or tributary and blank for all other reach points e Location Data o Distance to Start Distance from the primary pour point of the watershed to the reach point The primary pour point is that reach point assigned the value of Outflow for the reach point type o Elevation User must enter elevation value for the reach point Elevation can be entered in Step 10 at any time following the completion of Step 06 Note An elevation for Terminal reach points mu
192. esigner provided with ArcView Version 3 1 and later Use of dialogs within ArcView is dependent upon having the file named avadlog dl in the directory BIN32 This directory is located under the directory in which ArcView has been installed In normal installations of ArcView the path to the Bin32 directory is as follows C esri av_gis30 arcview bin32 Note It is unpredictable what may happen if the user attempts to load the Tools extension if the avdlog dll file is not found by ArcView in the BIN32 directory Due to the design of the dialogs it is recommended that screen resolution of 1024 by 768 be used A limited review of the dialogs on a 15 true visibility monitor at 800 by 600 resolution indicates that the dialogs will barely fit on the screen April 2006 Introduction Page 4 Restrictions Geographic Limitation The Tools have been designed to work with data developed for the State of Vermont This data is readily accessible from the Vermont Center for Geographic Information VCGI _ While it may be possible to use data other than that provided by VCGI there are no assurances that the Tools will function properly or provide meaningful results Soils Data Requirements Steps 12 and Steps13 of the Stream Geomorphic Assessment Tools provide the capability to extract data pertaining to soils for use in the assessment process VCGI and Natural Resources Conservation Services USDA NRCS recently published a CDROM contai
193. essing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools in the SGAT User Manual for common error and warning messages During Processing The reach numbers assigned to segmentation points in the user supplied theme are compared with those of the reach number theme created in Part B Step 06 If any reach numbers are found in the user supplied theme that don t exist in the reach point theme the following error message Is issued 2 SGAT User Error 1051 GeoSW FEHSegment lbtSer x 1051 Segmentation point theme rchsegpts shp contains 1 Stor reach point s not found in the reach point theme SDERPt01 shp Processing terminated If the preceding error message is issued the user must identify the reach number s that are in error and correct the assigned identifiers To assist in correcting the problems an additional error message as illustrated below will be issued that will list up to ten reach numbers found in the segmentation point theme but not the reach point theme 1052 Reach Pt lds in Seg Pt Theme rchsegpts shp but not Stor in Reach Ft theme 506A Ft01 shp a If the surface water for a given reach as represented by a polyline is found to be composed of multi parts the error message displayed below will be issued 1053 Surface waters disconnected for reach M0r Processing te
194. esult in Snapping to the incorrect vertices of connecting polylines whereas too small a value will require you to work at a very large view scale Work at a View scale which enables you to see the vertices of the theme which is being edited You should be able to clearly see the circle around the crosshairs representing the snapping tolerance Be sure to snap ends of polylines to each other Not doing so will prevent the Tools extension from properly tracing the stream network Note To set the snap tolerance in ArcView you must have the polygon or polyline theme you want to edit highlighted select the theme on the toolbar and select properties As shown below a box will appear Select the editing button and set both the general and interactive Snapping tolerance gj Field rea Definition Field type I Single a Union rule lt 5hape Areas xl Text Labels Split rule lt ohape Area l Ka snapping W Show snap tolerance cursor Geocoding W General Tolerance E W Interactive Tolerance a To assist in editing and determining the corrections to make the following data sets can be acquired Geographically referenced digital images of the USGS 7 1 2 minute quads can be obtained from VCGI Orthophotos can be acquired from the Tax Mapping Program Vermont Department of Taxes If significant errors are identified in the surface waters it is recommended that VCGI be notified Refer also to Appendix A
195. esult in two outflow points pour points for the sub watershed on the right streams flowing from northeast to southwest Sub Watershed Both of the above situations will result in errors being generated and or in invalid data being produced for the watershed and therefore the reach points Performing a careful review up front can save a significant amount of time and hopefully eliminate the confusion of trying to figure out the data resulting from incorrect inputs Meander Centerline and Valley Walls One should review the meander centerline and valley walls to ensure that proper digitizing techniques have been used and that the digitizing requirements set forth in the Section entitled Setup Required Source Themes have been followed Note It is important that the geometry established between the sub watershed valley walls surface waters and meander centerline make logical sense It would not make sense to have the surface waters or meander centerline traveling outside of the polygons established for the sub watersheds or valley walls If such geometry is included erroneous data and or error conditions are likely to occur April 2006 Organization Page 30 Editing the Source Shape Files Themes Editing of themes will require knowledge of the editing tools of ArcView When using these functions be sure to perform the following Set the snap tolerances in the Theme Properties to a reasonable value Too large a value may r
196. evation data is entered in Step 10 one can have Valley Slope calculated in that step by clicking on the Calc Data button April 2006 Step 07 Calculate Valley Line and Data Page 129 In Step 10 one can modify the values calculated for valley width and valley length Then by clicking on the Calc Data button in that step all derived values will be calculated f the valley width and or valley length are modified in Step 10 do not run Step 07 again any changes made in Step 10 will be lost Attribute fields for the Valley Line theme The following attributes are included in the resulting Valley Line theme RchPtld Identifier of the downstream reach point associated with the valley line Tribld Tributary Identifier associated with the reach points for the valley line UpStrmRPt Reach Point Identifier for the upstream reach point associated with the valley line ValyLength Length in feet of valley line drawn ValyWidth Width of valley in feet This is calculated by obtaining the area of the valley walls that falls within the sub watershed and dividing that by the valley length Using the dialog To access the dialog for this step click the button labeled Step 07 Calculate Valley Line and Data on the Part B Main dialog The dialog for this step is illustrated below Part B Step 07 Calculate alley Line and Data iinput Theme Definition GubsWatersheds sQ0subwshed shp Theme for Sub Watersh
197. ference table SOOSoiIX TabFields dbf or SOOLcLuXTabFields dbf If a record is not found in the reference table it is maintained in an internal list At the end of processing an error message such as that shown below will be issued Z SGAT Missing alues in Relational Table 2 Field alue combiration s in table 57250 dit were not found in table s00nenwsoillstabhelds2 dbf Stor Missing entries in table 57457 2Mlds dbf sawed in H Geomorphology Support hitenvers GAT white oS hite DernvdD ata April 2006 Step 14 Summarize Area by Field Value Cross Tabulate Page 180 All missing values will then be written to a file having the same name as that specified for the output table but with the letters Mlds appended referring to Missing dentifiers or missing values As an example the output table name for the message above was 14SC12 The name of the table containing the missing values ids is then S14SC12MIids The dBase table containing the missing values will be saved in the Tables subdirectory under that in which the ArcView project file exists The table is also added to the ArcView project The following figure is an example of that table s14_btest4mids dbf In this example the values 99 9 and 1 for the field WA TERSHALL were omitted from the reference table named SOOSoilXTabFields dbf These missing values are an indication that data in the reference tab
198. fier Trib ID entered above _ FEHOIFEHPts Proj e _ Segptsed01 shp Save Trib Id s assigned since e startup or since last Save OR AMA MD Mha Mee Q Attributes of S03SWComb shp Iof x Tibid Skipped TribldSet StwLUsed Cancel Trib Id s assigned since startup or since last Save Validation Results Blank Interyening Palulinels 9 Validate Continuity Clear ALL Trib Ids Show View Instructions vr Done Tribld Parts oa f SEGOTSWSEGOT d l e Astart 49 B e ea GJH Geomorphologytver fi UserManualver450_05 arcview GIS 3 2a song gaS 107m The second validation determines if a given tributary identifier has been assigned in a continuous fashion To accomplish this all polylines having the same tributary identifier are merged into a single polyline Then a test is done to determine how many parts that polyline is composed of If the assignment was performed in a continuous manner there will only be one part If more than one part exists then the assignment was not performed continuously Perhaps an easy way to visualize this potential error is to imagine that you have assigned the value T2 s1 to a series of polylines Then you continue on with the assignment of identifiers in other areas of the watershed When you get back to the initial area you use the same value T2 S1 and assign it to a sequence of other
199. finite loops As a result if any changes have been made to the surface water theme or it has been recreated always run the Setup function before assigning tributary identifiers Click on No to return to the preceding dialog or Yes to continue on Impacts features may also be further defined through the use of sub impacts For example the impact of Bank Armoring and Revetment is further subdivided into the following sub impacts hard bank Rip Rap or Other The location field where applicable enables the user to specify the ocation of the impact sub impact For example AB right bank or LB left bank will identify which bank on which the impact sub impact is located Where location terms right and left are used it is with the observer facing downstream The dialog for Feature Indexing is illustrated on the following page April 2006 Part D Step FITOOb Feature Indexing Page 206 To use this dialog The dialog was designed to be placed on the computer screen along with the view To start move the dialog to the right or left side of the screen Then click on the Show View button This will display the User View Move and resize the user view to fit alongside the dialog This will enable you to move back and forth between the view and the dialog When selecting points to geographically locate impacts zoom in to the area of interest Working at a large scale of the view enables one to place points accur
200. finition of the requirements for setting up and using the extension o Description of the general concepts and operation of the processing steps and o Identification and detailed description on the processing steps It is strongly recommended that the initial sections be read thoroughly and understood prior to using the Stream Geomorphic Assessment Tools These sections apply to the overall use of this extension and define common characteristics of the processing steps The description of the individual processing steps will identify the major errors which can be encountered during processing and where possible the cause s of those errors Where practical and feasible step by step instructions are provided to accomplish a specific function In many instances you will find Notes inserted into the text These provide ancillary information which might be useful April 2006 Format of Material Distributed Page 6 Contents of Distribution CD The Stream Geomorphic Assessment Tools is distributed on a CDROM As illustrated in the figure below there will be several directories at the root level of the CDROM Root Directory of CDROM Required System Soils LcLu Tables HUC 10 Tables ee eee Dh et ahs es eee ae ea ae l ArcView Legend GIS Themes may Files beincluded feet ae eae et tee eee The content of each directory is as follows Tools Contains four directories which are required to be pre
201. for the segmentation of reaches and for indexing features to the surface waters As illustrated in the figure below access to sub menus for each of these functions is provided via Part D Part D Main Dialog Feature Indexing View Log Done April 2006 Part D Reach Segmentation amp Feature Indexing Page 190 Part D Reach Segmentation The functions within this Part create a new version of the surface water theme resulting from Step 05 that is simplified and tailored to the development of reach segmentation The resulting theme is then segmented or divided into parts in accordance with a user provided theme containing segmentation points The points within that theme identify the geographic positions at which segmentation of the surface water is to occur The reach segmentation capability is provided to enable the users to visually display the location of geomorphic segments as well as be able to link the data back in from the DMS to the segmented surface water theme The following procedure may be used to create a segmented theme 1 Register the user supplied segmentation point theme To accomplish this go to Setup Dialog gt Theme Table Registration and Management gt Segmentation Points Then select the theme and required attribute fields as indicated on the dialog 2 The following processing steps are included in Part D Step SEGOO Setup Surface Water Step SEGO1 Segment Reaches Access to these steps is pro
202. g of the fields field values and field value names Warning It is imperative that the SOOTop20_05 dbf and the SO0SoilXtabFields_05 dbf tables be consistent It is recommended that the tables supplied on the Distribution CD be used S00LUCodes dbf is required for Step 12 This table contains a description for each code in the Land Use Land Cover coverage At present the set of codes that are in use is very limited One can review the descriptive codes by viewing the table in ArcView Note The field named Code is used to link these attributes with the geographic land cover land use coverages themes or shape files The field used in the geographic coverages may vary Contact the person organization providing the land cover land use coverage to determine the correct field to be used SOOLcLuXTabFields dbf is required for Step 14 This table identifies for the Code field in the SOOLUCodes dbf table all of the unique values that occur for that field and assigns a unique field name associated with the value Use of this table is similar to that of SOOSoilXTabFields dbf Appendix F provides a description and listing of the fields field values and field value names April 2006 Setting Up for Using the Tools Page 19 Note If the land cover land use coverage to be used is other than the LCLU coverage available from VCGI the two tables described above will have to be created for the specific coverage Further the field names and types must be ident
203. g themes will be presented subsequently To access the dialog for this step click the button labeled Step 11 Clip Data Themes to Selected Boundaries on the Part C main dialog lf a theme has not been registered for either the Soils or the LcLu the error message shown below will be issued A similar error will be issued if a theme has not been registered for either the sub watersheds or corridors In such cases the dialog for Step 11 will be displayed however the Clip button will be disabled 1003 Theme for either Soils or LeLu has not been registered Use of function prevented The dialog for Step 11 is illustrated on the following page To use this dialog e Click on the radio button to select the type for data theme e g either soils or Land cover Land use e Click on the radio button to select the Area for Boundary Theme e g sub watersheds or corridors e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data Once the radio buttons for the type and area for boundary theme have been selected the remaining controls on the dialog will be filled in The output theme name will reflect o The step number i e S77 o The first character of the type i e S gt soils or L gt LcLu and o The first character of the area for boundary theme i e W gt sub watershed or C gt Corridor An e
204. g to select the name of the attribute field to be used to qualify features for calculating densities e Ifa check mark precedes the Use Feature Selection control and a field has been selected in the Field Name control select the data values that identify features to be used e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data April 2006 Step 15 Calculate Densities Page 184 The output table name will automatically be generated based upon the options and data theme selected The name will reflect the following The step number i e S75 The first character of the boundary theme type i e W gt sub watershed or C gt corridor The name of the data theme e g Esite and The dbf file extension O O O O An example of a name would be S75CEsite dbf for densities of Esite structures within the stream corridors When the Dialog for Density Analysis is selected from the Part C Main Dialog the following error message will be issued if themes have not been registered for sub watersheds and stream corridors In this case access to the density analysis function will be prevented SGAT User Error 1163 GeoSW Density JbECIip Click E Stor 1763 No theme registered for either Sub w atersheds or Corridors Use of function prevented Selecting the Data Theme When the dialog
205. gly recommended that you exit the SGAT extension first Warning The dialog for Step 04b establishes the surface water theme to be available for editing with recovery This status for editing is established when the dialog is opened and remains in effect until the dialog is closed by clicking on the Done button If one inadvertently stops editing April 2006 Step 04b Assign Tributary Identifiers Interactively Page 104 with the dialog open unpredictable errors will occur that may even render the surface water theme unusable Do not edit or modify the editable status of the surface water theme while the SGAT extension is active 210 x File Edit Table Fjeld Window Help 8 of 31 selected Le Tk AET ME vil SO3SWComb shp S S Trib Id Set LV Not Set vil Tmpsetpt shp tr Start End F t0 1ptimpa cts eg st A Fit0 dinimpactseg st Trib Id Assignment Tributary Id T Break polyline at upstream ending point Tributary Ids assigned thus far x1 Y Procedures for Assigning Tributary Identifiers Distance from Points to Search for Polyline Search Distance 10 0 Meters Set start end points for use of Set Start End Pts tibutary identifier Trib Id Clear point locations identified via above _ FITOOLnImpactshp N f VY FITOOPtimpactshp A _ Fit02armoring shp A Z _ Fit02erosion shp Assign tributary identi
206. h the data set Description of alias Path identifying the location of the data set Step number in which data set was created Date and time when data set was created In the Log Audit control all entries in the Log will be displayed The data associated with a log entry is as follows O O O O Unique identifier for each log entry Date and time when log entry was made Record number In some cases multiple records are required for an entry Also any note entered by the user on the dialog will generally be entered into the log in the second or sometimes third record Step number in which log entry was made Operation performed in the step Input themes tables Up to three input data sets will be shown in a record If more than three are used multiple records will be created for the log entry These will be differentiated by the record number Comment This field will display the results of the processing step or activity for which the log entry was made User notes will also be in this field but will be included in a separate record By reviewing the og entries one can identify the steps in which the data set was created or registered modifications to the data set were made and or critical errors encountered during processing steps that create or modify the data set April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 74 Adding a User Note to the Log One can add a User Note to the log by simply ent
207. han twice Since stream tracing occurs upstream and downstream the maximum number of times any stream segment should be encountered is two As each stream segment is encountered during tracing the field SWUsed in the surface water extract theme is incremented and tested If the value exceeds two the following error message is issued 1104 Attempt to use Surbace Water polylines more than twice Stor Probable data eror Processing terminated To identify the surface water polyline query the attribute field named SWUsed for a value greater than 2 This will identify the polyline in error Usually reviewing the polyline its vertices and adjacent polylines will reveal the problem Because the search distance to find connecting polylines is set as 0 25 meters any surface water polylines less than 0 25 meters in length will cause such a problem In such cases one will have to edit the surface water theme to remove the small polylines and connect the others by snapping the end vertices Upon Completion The route table which will normally be named S03SWCombTribldSet dbf will be created and saved in the DerivdData directory A sample of a route table is displayed below RECNO FROMID TOID TOTYPE Co ee ee The record number in the surface water theme that is associated with a given polyline is shown in the first column The second and third columns represent the identifiers assigned to the starting and ending nodes
208. he Tools Clicking on the Continue button on that screen will display the Setup Dialog Clicking on the Exit button simply closes the ntroductory or Splash screen This does not however unload the extension The process for unloading the extension has been described earlier Siren Leonor pe eer Tens 90AT Persian d beta 27 2 Arc iew GIS 3 2a Stream Geomorphic Assessment Tools File Project etre Help Version 4 C ID a 2 demo apr Initialization Procedure When the Continue button on the Introductory dialog is clicked an initialization procedure is invoked This procedure performs a number of tasks to create and to verify the environment required for using the Tools The following steps describe the verification procedure undertaken ArcView Project A check is made to ensure that the ArcView project has been saved If the ArcView project has not been saved the following error message Is issued and access to the Tools is prevented 2 SGAT System Error 1107 GeoSW Splash IbtContinu xX 1107 SGAT Extension requires a Saved Project being active Please save the Project file Access to Extension prevented Directory Structure A test is made to verify that the required directories exist under the directory in which the ArcView project has been saved If one or more of these directories do not exist they are automatically created The following warning message will be issued indicating any miss
209. he Tools button you will be taken to the introductory or Splash screen for the Stream Geomorphic Assessment Tools This screen is shown below Sean Later pii Ae err U Tach SLAT Version a beta 32 P Stream Geomorphic Assessment Tools Version 4 By clicking on the Continue button on the ntroductory screen an initialization procedure will be executed This procedure will verify perform the following That the ArcView project has been saved That the required directory structure has been established That the required system tables are located in the SysData directory and finally Will load any themes tables that were registered in prior sessions na ee o The initialization procedure is described in detail in the Section entitled Accessing the Stream Geomorphic Assessment Tools Error conditions that are detected during the initialization process will be displayed in message boxes If an error is detected access to any functions of the Tools will be prevented Upon completion of the initialization procedure the following warning will be displayed x 2 SGAT Warning GeoSW Splash IbtContinue Click To AYOID corruption of the project file themes or tables DO NOT 1 modify any themes 2 modity any tables 3 save the T project or 4 close the project while in the SGAT extension ALWAYS exit the SGAT Extension click the Esit button on the Main Dialog prior to any of these actions
210. he remaining elements on the dialog that are required to perform Step 12 are automatically filled in These elements are as follows e The theme that is to be summarized which will be one produced via Step 11 The theme will correspond to the type and area selected e The relational field to be used for the theme This is a field which contains values that relate one to one with values in the relational field for the relational table When the type of data is selected the field registered for the data theme used in Step 17 will be entered automatically e The name of the relational table to be used The name is obtained from the dBase table registered for either the Soils Top 20 Attributes or LcLu Codes Descriptions The particular table will be dependent upon the type of data selected e The relational field to be used for the relational table The field displayed will be that which was identified during the registration of the relational table e The pre defined name for the output table will be displayed Note The output from this step is a table Note Refer to the Section entitled 7heme Table registration and Management for description of the themes tables and field registrations required and the procedure for performing registration The output table name will reflect o The step number i e S72 o The first character of the topic i e S gt soils or L gt LcLu and o The first character of the
211. he selected linear and area units of measure These are automatically calculated when one sets the Map Units Linear Units and or Area Units Included in this table is a parameter referred to as Connecting Feature Search Distance or Near Distance This controls the search distance to identify connecting features such as stream polyline segments This value can also be set via System Functions gt Measurement Units Two additional parameters which should not be altered by the user are Zero Value and Minimum Area The Zero Value parameter is used to identify equality in such things as coordinates The Minimum Area defines the area of a polygon in the view s Map Units below which the polygon is to be considered a sliver polygon resulting from digitizing errors SysUserType Identifies permissible User Type s and associates an Access Level with each The Access Level defines those applications and dialogs that are to be accessible to the User Type Note Additional dBase tables defining buffering specifications located in the SysData directory At present three such tables have been defined SysBufOpt1 dbf SysBufOpt2 dbf and SysBufSGA dbf The buffer tables are described in Appendix H April 2006 General Concepts Page 11 Alias Description y O Others Others Others Tools User Others Others User Others Others Tools User Others N A Others User ValeyWalls_ Valley Walls o oo Od O Derived RPts Reach Po
212. heme is associated with the alias of watershed Therefore the output theme name will be S01Watershed shp Depending upon system settings for the output theme it is possible that a sequence number will follow the alias in the name of the output theme This will occur only if multiple versions are allowed for the specific output data set This is described in the following section April 2006 Organization Page 40 Multiple Versions of Data Sets The capability to create multiple versions of data sets resulting from a processing step is available It is however restricted to certain User Types Refer to Section entitled Setup Dialog This capability is controlled for each data set via its alias by the value assigned to a field named BT Multiple in the system Table SysBaseTheme dbf Modification of this value is permitted through the dialog System Functions gt Multiple Output Versions This dialog is shown below System Multiple ersion Controls Number of ersions Permissible for Derived Data Sets Alias for which Multiple Versions may be changed Alias Watershed v Iheme table created in Step Number o Data Sets Registered under Alias Desription Overall Watershed Date Time Data Set Active 00 00 00 00 00 NotSelected N al h geomorphology wersion3 DerivdD ata Data Set Source Multiple Versions Allowed C Yes tf No Data Set Type Done Since access to t
213. hether the feature type of the data theme is point polyline or polygon respectively RehPtld Reach point identifiers copied from the input table NumUnits The density calculated for the given sub watershed or corridor Values will be in the units shown in the Units field April 2006 Step 15 Calculate Densities Page 188 The following is a table resulting from Step 15 in which the point locations for houses within a given town were summarized for sub watersheds In the table reach M08 had 42 dwellings within the sub watershed SOURCESTEP BNDRYTYPE SUMLEVEL GEOSWAREA UNITS RCHPTID NUMUNITS Sub Watershed Sub Watershed 0 595887683753 Units Mma Sooo o Sub Watershed Sub Watershed 0 395524771699 Units Mo2 o Sub Watershed Sub Watershed 0 521608079823 Unit Moo J o ol Sub Watershed Sub Watershed 1 204915729398 Wis ma f o Sub Watershed Sub Watershed 0 951415752595 Units To properly use this Step one should acquire the data that would cover the entire watershed under study This data would have to be merged into a single data set Then this step would identify the density within each watershed Using data for a single town as was done in the table shown above would provide information on the contribution to dwellings or roads etc by the town April 2006 Step 15 Calculate Densities Page 189 Part D Reach Segmentation and Feature Indexing Part D of the Tools extension provides capabilities
214. hich can be used to obtain the name of the stream e g Lewis Creek The Aivid will contain a unique identifier for the stream which might provide linkage to other data sets pertaining to the stream April 2006 Step 03 Combine Stream Segments between Confluence Points Page 94 Two additional fields that may be helpful for the user are SWL and SWRes The SWL will indicate the values selected in Step 02 The SWHes will show at what level of scale the stream line was digitized at It is important to note however that the SWRHes field may not be available on a uniform basis oWRes Value scale at which stream layer digitized o ae 2 1 100 000 4 1 24 000 6 1 5000 off orthophoto subjective Starting the process After the required information has been entered on the dialog click on the button labeled Combine Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages Upon completion Alias of Output Theme for Combined Surface Waters SWComb Legend file used to display Clipped Surface Waters theme SWComb avl The theme representing the Combined Surface Waters will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This theme is added to the user view identified on the Main dialog Click on the button labeled Done to return to the Pa
215. his dialog is restricted the button on the System Functions menu dialog may be disabled or not displayed In such circumstances only a single version of a data set is permitted This will result in replacing the output data sets if a processing step is re run lt is strongly recommended that one utilize single versions of output data sets This will minimize the amount of hard disk space required and eliminate any confusion as to which data set represents the version to be used in subsequent analysis In rare circumstances it may be desirable to create multiple versions of a data set for the purposes of comparison For example it may be desirable to create versions of the stream corridors from Step 09 for different applications Stream Geomorphic Assessment Fluvial Erosion Hazard Option 1 for comparison This discussion pertains to those circumstances One should always use the dialog shown earlier to modify the setting for creating multiple versions rather than attempting to manually modify the system table SysBaseTheme dbf This will ensure that the following rules are adhered to o Only derived themes and tables are allowed to have multiple versions Specifically base source themes and tables should never be permitted to have multiple versions o All records for a given alias in the system table SysBase Theme dbf must contain the same value for BT Multiple To set the ability for an alias to have multiple versions or to restrict to
216. ical to that in Appendix F for the SOOLcLuX TabFields dbf In order for processing Steps 12 and 14 to function the four tables described above must be registered in the Tools Refer to the section Setup Registering Source Data Appendix B provides a Data Tracking Form for documenting the required reference tables among other items This can provide essential documentation for future reference Setup Required Source Themes There are a number of themes which will have to be acquired prior to using the Tools extension HUC 10 Watershed Boundaries RMS Land Cover Land Use VCGI or others Ortho Photo Boundaries VCGI RMS Surface waters VCGI Note If using VHD SWL use the arc feature type Soils VCGI NRCS Town Boundaries VCGI RMS USGS Quad Boundaries VCGI RMS Meander Centerline delineation User supplied Reach Segmentation points Sub watershed delineations User supplied and Valley Wall Delineations User supplied Each of these themes will require some pre processing The general requirements are listed below for each of these themes Note For users new to ArcView it might be best to have this effort performed by others Certain steps may require the Spatial Analyst extension to ArcView Boundary Theme HUC 10 Watersheds The HUC 10 Watershed Boundaries have been created by merging more detailed HUC 12 sub watershed boundaries These are available in a shape file format from the River M
217. ical to the operation of the Tools These steps establish the basic set of geographic data that control the remaining steps and establish the underlying data for the analytical results to be developed in all of the remaining steps Assigning the Tributary Identifiers Using ArcView edit the Attribute Table for the Surface Water theme resulting from Step 03 In the field named Tribld enter the values to be used for tributary identifiers For the purposes of this manual the term tributary includes the main stem The rules for assigning values in the Tribld field are as follows Each tributary which is to be assessed must be assigned a unique identifier All stream segments comprising a tributary must be assigned the same value Stream segments which are not being assessed would not be assigned a value and The same Tributary Identifier must be assigned continuously from the initial surface water segment to the terminal segment For this purpose 14 a terminal segment is defined as the last polyline segment or the last a segment that is to be assigned a LF Tributary Identifier i e no upstream ie segments will be assigned any tributary identifier This is important at points of confluence Proceeding upstream from the confluence point one and only one stream must be E assigned the same Tributary Identifier as the stream flowing downstream from the confluence point The other stream flowing upstream from the confl
218. ify Ibtidentify click 1006 User suppled parameters okay Processing may take a few moments Do wou want to continue This provides a bail out point If one does not want to continue click on the No button Otherwise click on Yes Upon completion of processing a message similar to the following will be displayed 2 SGAT Info GeosSW Identify lbtidentify Click E x The HUC 10 idis and Idia of the WT Orthophoto s that a reach fall within have been associated with each Reach Point Click on the Done button to return to the dialog for Step 10 The map documentation fields will be filled in for the themes selected as illustrated in the figure below Note the identifiers are now listed in the fields for the VT orthophotos and the HUC 10 watersheds Had the Town boundary and USGS Quad themes been fully registered the names for the towns and quads within which the reach falls would have also been entered for each reach T Ji L pu 7 eur tur ce Saag Alas Geographic Coordinate PESE Rea Larg 72 326202 Lat 44 364800 1 Map Documentation tor Reac each AttriE Guads Stream Orthas 164204 164208 stream E Towns E HOETA 0201000302 F Hote for Reach Ft Calc Data Set Map Doc Import Data Export Data ake April 2006 Step 10 Data Entry Review of Reach Point Data Page 156 Step 10 Export Reach Point Data to dBase Table The data must be exported out of SGAT and imported into
219. igitizing sub watershed boundaries are as follows 1 Manually digitize the sub watersheds using polylines and use the built in SGAT optional tool to convert from polylines to polygons Each polyline would represent the common boundary between two adjacent sub watersheds One must also ensure that the ends of the polylines are snapped together The Review Polyline Geometry processing available in the Optional Tools can be used to check for proper polyline configuration It is strongly recommended that this processing be performed repeatedly until all errors identified have been corrected Then the Build Polygons processing available in the Optional Tools area can be used to convert the polylines into the required polygons 2 Manually digitize using polygons Using this option the user would start with one polygon representing the exterior boundary of the HUC 10 for the project area and use the ArcView split polygon tool to create additional polygons representing the sub watersheds If this option is used the user must make sure the resulting theme does not have either overlapping or sliver polygons before proceeding 3 Use other existing Digital Elevation Models and software such as spatial analyst or ArcGIS to automate the sub watersheds April 2006 Setting Up for Using the Tools Page 24 Warning If sub watersheds are delineated using polygons it is essential that the polygons do not overlap do not include sliver polygons do not inclu
220. ined name for the reach point output theme will be displayed e The format to be used for creating the reach point identifiers is displayed in the lower left corner of the dialog box e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data Note The format including length of the reach point identifiers can be modified via Setup Dialog gt System Functions gt Format Options for Reach Pt la s Starting the process After the required information has been entered on the dialog click on the button labeled Calculate Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages Upon completion Alias of output theme for reach points RPts Legend file used to display reach point theme RPts avl Legend file used to display sub watershed theme SubWSUsed avl April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 117 A message will be displayed to indicate the number of each type of reach point created A SGAT Info GeoSW RPts IbtCalc Click E E Outflow 1 Inflow 1 Count of Reach Points identified by type i Terminal 5 and Standard 22 The theme representing the Reach Points will be saved in the DerivdData subdirectory under th
221. ing directories which have been created DenvdData and Temp have been created under project 24 Required sub directories of SysData BaseD ata STOP directory of h geomorphology version test April 2006 Accessing the Stream Geomorphic Assessment Tools Page 49 System Tables A number of system tables are required These dBase tables control the operation of the Tools or are a repository of data Through these tables the status and data generated from one session using the Tools is carried forward into the next A test is made to ensure that all of the system tables reside in the SysData directory If one or more of these tables are missing the following error message will be issued 25 14 of the system table s is are not located in the system directory h geomorphology yversion4 test Sus Datar Following the error message another message box will attempt to display the names of those tables that are missing This is illustrated in the following 26 Missing system tables Sys4ops dbf SysBaseThe SusBT RegFields dbf SysChanParm dbf SysDialog dbf 247 2st Stor SyeDir dbt SysErrors dbf SpeLimits dbf Syslog dbf SysAPtForm dbt SysStatus dbb SysSustem dbt SysUnits dbt Note No validation of the format or contents is made for the system tables As a result user modification of these tables will cause unpredictable results when running the Tools including possible corruption of data and
222. inog Mew Ul POUSIBIE M E1940 JO ealy ebeureiqueaisda pue s d MojjINO MO ju joluawubissy enuen ulj1 U99 1 puL N sjoo u wss ssy DIYCIOWOS weas 3y JO M M ANQ Page 33 Organization April 2006 Using the Theme and Data Tracking Form A Theme and Data Tracking Form is included in Appendix B of this manual The form enables one to document the input themes tables and the output themes tables for each processing step By completing the form as you work through the steps for a watershed you will be establishing documentation for the project This can be an invaluable reference should additional analysis be required on the watershed at some future time It is recommended that the forms be completed for each watershed and filed in a central location Guidelines for using the Stream Geomorphic Assessment Tools The general guidelines are e Perform each step in sequence e f corrections are to be made to the interior watershed boundaries or the geography of the streams within the watershed then the procedure can be restarted at Step 02 e f additional sub watersheds are delineated i e reach points added start at Step 02 e If the sub watershed delineations are altered in a manner that affects the overall watershed boundary i e the outermost boundary of the sub watersheds then you will have to restart at Step 01 IMPORTANT NOTE If you have already assigned tributary identifiers and find that you h
223. ints HS Derived Corridor Stream Corridors Ci Derived Derived 11 D1 Fluvial Erosion Hazard FEH Zone Method 1 Fluvial Erosion Hazard FEH Zone Method 2 Note The Aliases associated with Step 00 are base themes tables described in other sections Those data sets whose Source is identified as User or Derived are described in the Sections pertaining to the Step in which they are created or required April 2006 General Concepts Page 12 Setting Up for Using the Tools Setup involves the following steps which are described in subsequent sections 1 Installing the ArcView extension for the Stream Geomorphic Assessment Tools 2 Creating the required directory structure to permit use of the Tools 3 Copying the System Tables to the SysData directory and 4 Copying the data sets themes and tables provided to the BaseData directory Note It might be best to copy the entire Tools directory from the CDROM onto your hard drive Then remove the Read Only attribute for all directories and data sets The Tools directory can then be renamed to a more meaningful name One must also obtain the required source data for each watershed for which assessment is being conducted and perform some level of pre processing The GIS coverages also referred to as themes or shape files and potential pre processing steps are as follows 1 Surface Water coverage s will have to be converted to shape file s and merged into a single shape file tha
224. inutes or more to complete The duration will depend upon the computer resources available processor speed amount of RAM and hard disk speed and the complexity of the valley wall configuration During processing the Status Line of ArcView will be used to indicate the progress The left part of the Status Line will indicate the Reach Point for which a valley line is being calculated as well as the number being processed and the total number to be processed The right portion of the Status Line will display a Progress Bar showing the percent done If you need to stop processing At the far right of the Status Line is a Stop button Clicking on that will terminate processing upon completion of the reach point under investigation Note Completion of processing for the valley line being created may take several seconds or minutes so have patience If you click on the Stop button processing will terminate normally and all valley lines created thus far will be saved 10 x Eile Project Window Help e IS 2 geoswy2s18run apr iol x Open Print Step 07 Calculate alley Line and Data Views Available in Project Project Views View Input Theme Definition Sub Watershed SO0stacisubwshed shp v Source theme for sub watershed delineations Reach Points SO6rpts shp v Reach Points created in Step 06 Valley Walls SO0cdmodvw shp Source theme for Valley Walls Polygons Units of
225. ion for each The registration process is required only for those themes tables which are not created by the processing steps in the Tools The registration process will be described in subsequent sections Themes and tables which are created within the Tools are referred to as derived themes These can be managed via a dialog that is accessed via the button labeled Manage Derived Themes and or Tables The only management options available for these data sets are o To remove the theme or table from the project The data set will remain on the hard disk o To delete the theme and or table from the hard disk It will also be removed from the project o To posta note to the log for a given theme or table o To delete a note posted to the log for a given theme or table Use of the dialog permitting management of derived themes and tables will be presented in a subsequent section Using the Export Theme Table List button one can export a list of the registered themes for subsequent use in either Microsoft Access or Microsoft Excel All themes which have either been registered by the user or created within the Tools will be included in the export file The export file RegList db will be located in the Temp directory 2 SGAT Info GeoSW Reg IbtExport Click E i x List of registered Themes ables along with user supplied documentation hawe been exported to dBase file named RegList dbf dBase file is located in direc
226. ion to the cross tabulation fields the output table will contain the following fields RehPtld Tribld CordrArea OR SubWSArea depending upon the boundary theme used for clipping in Step 11 BndryType DataType SumLevel and WaterArea RehPtld Reach point identifiers copied from the input table Tribld Tributary Identifier for the main stem tributary associated with the reach point for the stream corridor or sub watershed Values copied from the input table April 2006 Step 14 Summarize Area by Field Value Cross Tabulate Page 179 CordrArea Will be included if the boundary theme is stream corridors from Step 09 The values for CordrArea will be the area of the stream corridor and will be copied from the input table SubWSArea Will be included if the boundary theme is the sub watersheds The values for SubWSArea will be the area of the sub watershed and will be copied from the input table Note The CordrArea or SubWSArea is included to facilitate user calculations of area percentages WaterArea f the user is developing the cross tabulation for soils and has elected to exclude water from being summed into the areas of the cross tabulation fields the WaterArea field will contain the area of water bodies found within the corridor or sub watershed The following fields are added to the table to verify proper table selection in subsequent processing steps and to provide internal documentation as to the derivation of the ta
227. is or subsequent processing steps The edits performed on the sub watershed theme are to identify the following potential errors Polygons composed of multiple parts Polygons that share multiple boundary segments with an adjacent sub watershed Polygons that overlap adjacent polygons Self intersecting polygons and Polygons that are less than a system defined area O O O Or 0 The above errors will be described subsequently April 2006 Step 01 Dissolve Sub Watersheds into Overall Watershed Boundary Page 80 If any of these types of potential digitizing errors are detected an interim theme will be saved in the Temp directory The following sequence of messages will identify the errors detected and name of interim theme upon completion of processing 1036 Potential errors in sub watershed polygons 1 multi part polygons 1 boundary overlaps 1 multi part boundary Intersections O topology errors and O polygons less than 0 01 ag Miles Overall Watershed Polygon has 1 part s Copy of sub watershed Expl s00subywehed shp saved in directory H Geomorphologyversion44T est T emp Limited if any comections applied Remaining HMult Part polygons exploded Theme added to View SGAT but NOT registered The interim theme will be the name of the source input theme for the sub watersheds but will have the characters Exp and a sequence number prefixed As indicated in the latter message above the source
228. ivities have occurred SGAT Log Review Enter Note into the System Log Data Set All Themes T ables ThemeT able for which Log is to be viewed or a Note is to be entered into the Log April 2006 Using the Log Log Audit Notes 10 2003 11 03 12 28 43 2 Sys System 12LC Multiple User Comment NAA 11 2003 11 03 18 42 50 1 N A SysUnits dbf N A Units User NZA 12 2003 11 03 18 42 56 1 N A SysUnits dbf NAA Units User N A 13 2003 11 03 18 43 12 1 N A SysUnits dbf N A Units User NZA 14 2003 11 04 05 49 24 1 01 sOO0subwshed shp SubWatersheds Dissolve sO0subweshed shp NAA 15 2003 11 04 05 49 29 1 01 sOO0subwshedshp SubWatersheds Dissolve sO0subweshed shp NAA 16 2003 11 04 16 58 24 1 Reg System System Purge SOiWatershed shp User 17 2003 11 04 16 58 24 1 Reg System System Delete SOl Watershed shp User 18 2003 11 04 16 59 08 1 01 sOOsubwshed shp Subwatersheds Dissolve sO0subwshed shp N A 20 2003 11 04 16 59 12 1 01 sOOsubwshed shp Subwatersheds Dissolve sO0subwshed shp N A ai Export Log Done Page 46 Scrolling to the right provides additional information such as the results of a given step This is illustrated below SGAT Log Review Enter Note into the System Log Theme T able for which Log is to be viewed or a Note is to be entered into the Log All Themes T ables Data Set Log Audit Notes Multiple revisions for Alias 12LC changed to N N A NZA NearDist
229. l be displayed Part B Data Development for Sub Watersheds Data Development Functions for Sub VWatershed Step 05 Clip Linear Surface Waters to Sub atershed Boundaries Step OF Calculate Valley Line and Data Step 08 Calculate Channel Width and Stream Data Step S Create Stream Corridors Butters Step 10 Data Enti Review of Reach Point Data View Log Dore To access the dialog for any specific step simply click on the corresponding button Click on the Done button to return to the Main dialog for the Tools extension April 2006 Part B Steps 05 10 Data Development for Sub Watersheds Page 111 Step 05 Clip Linear Surface Waters to Sub Watershed Boundaries This step takes the surface waters from Step 04 and clips the stream segments at the sub watershed boundaries While this step provides no apparent benefit to the user it is critical to the operation of subsequent steps This step utilizes the theme created in Step 03 However it is imperative that the assignment of Tributary Identifiers be completed As indicated below the theme resulting from this step Step 05 is used as an input theme for many of the remaining steps e Points where stream segments which were assigned a tributary identifier in Step 04 cross a sub watershed boundary will become reach points The reach points will be created in Step 06 e The stream segments that were assigned a tributary identifier in Step 04 will
230. l documentation as to the derivation of the table BndryType will indicate the type of boundary theme used in Step 11 Value is copied from the input table Possible values are sub watershed or corridor April 2006 Step 13 Sum Data to Upstream Watershed Area Page 172 DataType indicates the type of data theme used in Step 11 Value is copied from the input table Possible values are LcLu or Soils SourceStep will indicate which step created the output theme Value inserted in this step is 13 SumLevel will show to which level of aggregation that the data pertains Value is set to Upstream Possible values are either blank or Upstream SysRelFld identifies the relational field in the input theme used to relate to the descriptive table Field is used internally only and should not be altered All other data from the input table will be included in the resulting table Click on the button labeled Done to return to the Part C menu dialog The shaded area in the figure below illustrates the sub watersheds for which data would be Summed in this step for reach point MO8 Shaded area shows Sub watersheds data for Reach Point M08 April 2006 Step 13 Sum Data to Upstream Watershed Area Page 173 The following figure illustrates a portion of the table produced Numerous fields to the right are omitted 13soilcorridors dbf 4 7881226384 OTH aos Oe mE HADLEY VERY FINE SANDY C Mu Coridor Upstream
231. l point entered by the user After 1 and 2 have been established click on the button labeled Set Start End Pts Click on the title bar of the View to make it the active window With the view active use the zoom pan tools to navigate to the area where assignment of the given tributary identifier is to start Work at a view scale where one can enter a point that can be associated with a specific surface water polyline If one works at a very small view scale incorrect selection of surface water polylines may occur This will lead to error conditions 6 When you are zoomed in to an appropriate scale for selecting the point click on the Assign Trib Id tool This tool is the furthest to the right on the same line as the zoom pan identify tools and is represented by the eyeglasses icon 7 With the Assign Trib Id tool selected click at a point on the surface waters in the user view where the starting point is to be located On e Note The points entered must be within the search distance set on the dialog of the surface water polylines If the points are located at a greater distance no polylines will be found and an error message will be issued Note You must always locate the downstream point first Use the zoom pan tools to navigate to the area where the end point is to be located Then again select the Assign Trib Id tool 0 Left click in the view at the point on the surface waters where use of the given tributary id
232. l summary of the processing that took place The number of Terminal Reach Points represents those which were identified in Step 06 as reach points at the ends of tributaries identified in Step 04 Valley Walls not drawn indicates the number of reaches for which no valley walls were drawn or errors were encountered and Valley Lines created indicates the number of valley lines that were successfully created Z SGAT Info GeoSW alley IbtCalc Click 2 E qi x Reach Points 29 Terminal Reach Points 6 Valley Walls rot drawn 3 Valley Lines created 21 April 2006 Step 07 Calculate Valley Line and Data Page 132 The following message will then identify the theme created and location on the hard disk where it has been saved SGAT Info GeoSW alley IbtCalc Click E x SOV alleyLine shp saved in director oO he geomorphology version D erwdD atar Theme has been added to View SGAT Following completion of processing review the valley lines created It is possible that this step may improperly calculate valley lines and therefore valley lengths and widths Reviewing the Valley Lines created Upon completion of processing open the View to which the theme was added Then Zoom In to a reasonable scale where you can view an entire sub watershed if necessary you can Zoom In closer It would be best to start at the Outflow point for the overall watershed as this gives a good point of reference In a systematic manner us
233. le SOOSoilX TabFields dbf or SOOLcLuXTabFields dbf is out of synch with the corresponding relational table SO0Top20_05 dbf or SOOLuCodes dbf used in Step 12 Any missing values should be recorded and investigated After you have recorded the information the tables containing the missing ids can be deleted from the ArcView project and the hard disk Problems can be corrected using ArcView and editing the appropriate reference table April 2006 Step 14 Summarize Area by Field Value Cross Tabulate Page 181 The following figure illustrates what caused the problem in the example cited above The records in error are highlighted in yellow By inspection you will note that the 99 9 and 1 entry under the field column labeled FieldValue appears offset to the right with respect to other entries in that column In fact there is a space preceding that value By editing the table and removing the space before the value the error was corrected A sO0soilxtabfields dbf WATERSHALL Fixed Decimal i Wats 1 5 A AAAI RR ES ODO PEET N OEE aE a TDA E SEE TE SE E ar A A p A O A T dal Doe E ON TEER T N AN E ON A E EA O E iWatS PIS a WATERSHALL Fiked Decimal e Le eee Ee rhea eden E AET Wats P20 WATERSHALL Fixed Decimal 1i wWeatS ag wats Pag lt may become necessary to add additional records to the table to reflect new values for individual characteristics Again one can edit the table and add new records The entries under FieldValu
234. lected for the field named Type Data Theme and Extraction Criteri Theme monktoneszite shp x Feature Selection Criteri IY Use Feature Selection Data Values l Fress Shift key to Field Name Type r select multiple Density Unit Units Units April 2006 Step 15 Calculate Densities Page 186 Use Feature Selection The Use Feature Selection Field Name and Data Values controls permit one to qualify which features to use in calculating density For example in the State of Vermont one can obtain an ArcView shape file containing ESite points These are point features representing locations that are relevant to emergency services Among the features are dwelling locations commercial buildings fire hydrants telephone booths etc In calculating densities for stream geomorphic assessment it is likely that certain of these features such as telephone booths or fire hydrants should not be used As a result the values representing those types of features would not be selected and therefore would be eliminated from the density calculations Starting the process After the required information has been entered on the dialog click on the button labeled Calculate Density Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages If the output theme already exists
235. legend files are used to display themes resulting from a given processing step In several cases these legend files will highlight error conditions detected during processing There are a number of dBase tables which are referred to as system tables located in this directory These tables control the operation of the Tools and therefore should not be altered in any manner When the Continue button on the Introductory or Splash screen is clicked an initialization procedure will be conducted This procedure will verify that the above directory structure exists and that the required system tables are located in the SysData directory Any errors detected during this procedure will prevent use of any functions within the Tools Note Refer to the Section entitled Accessing the Stream Geomorphic Assessment Tools April 2006 Setting Up for Using the Tools Page 18 Setup Required dBase Tables There are a number of dBase tables that are distributed along with this extension These tables are required in order to use various steps These tables are provided on the Distribution CDROM in the directory Tools BaseData Note These dBase tables must be copied to the directory BaseData under the directory in which the ArcView project file is located SOOTop20_05 dbf is required for Step 12 This table contains the twenty most frequently used attributes for soils mapping units e g flooding high low depth to water table etc The documen
236. les Attribute fields for the Reach Point theme See Appendix C and D for descriptions of all fields associated with the Reach Point theme The attribute fields calculated in this step are identified below CordrArea Area of the stream corridor in Square miles Note All attribute fields associated with the Reach Point theme are created in Step 06 To access the dialog for this step click the button labeled Step 09 Create Stream Corridors Buffers on the Part B main dialog April 2006 Step 09 Calculate Stream Corridors Buffers Page 143 The dialog is illustrated below Part B Step 09 Create Stream Corridors Buffers Input Theme Definition yf alley Walls sOOvalley_walls shp v Theme for Valley Walls to be used Meander Line sp0meandercl shp Theme for Meander Centerline to be used Sub Watershed sposubwshed sho Theme for Sub Watersheds to be used Cat Syne ee Theme for Surface Waters clipped to Sub Watersheds to urface Waters S05SWFinal shp ma E i Reach Points S06APts02 shp Theme for Reach Points to be used Units of Measure to be used Linear Units Feet amp rea Units sa Mies Buffer Theme to be Created cl Thane s Themes resulting from this step have been created utput Theme 09Corridor0 shp Z Select Theme to be replaced or New Version to create a new version To be saved in h geomorphology version3 D erivdD ata Note for insertion into System Log User
237. lick on Extensions Scroll down the list of extensions until you find Stream Geomorphic Assessment Click on the check box to the left of Stream Geomorphic Assessment The check mark should disappear 6 Click on Ok aS TE The Tools button should disappear from the Button Bar April 2006 Setting Up for Using the Tools Page 16 Setup Required Directory Structure The Tools requires that a specific directory structure be established The directory structure shown on a subsequent page is relative to the directory in which the ArcView project file is saved Specifically if the ArcView project is saved in a directory named LewisCreek then the directory structure shown must exist under the LewisCreek directory Imposing a directory structure provides the following benefits Ability to make backups Transferring data to other organizations Elimination of redundant data and therefore difficulty in maintaining current versions and Consistent organization throughout all organizations Note The required directory structure can be found on the Distribution CD under the directory named Tools The required directories are used in the following manner BaseData The source data sets which are required in one or more of the processing April 2006 steps of the Tools are located in this directory The source data sets are either dBase tables or ArcView shape files themes and are the original data sets obtained from other sources o
238. licking on No in the above message will abort the theme selection as will be indicated by the following message SGAT User Error 1084 GeoSW Reg ThemelbtSelec x the directory H Geomorphology version T est BaseD atan 1084 Data sets for Base Themes T ables must be located in Stor File selection ignored Clicking on Yes will cause the component files for the shape file to be copied to the BaseData directory This ensures that the required directory structure is adhered to If no errors have been detected the name of the theme selected will be entered into the control labeled Shape File Name on the dialog Registration however will not occur until the Save button is clicked April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 65 The registration procedure also enables one to enter the following documentation for a theme Source agency The organization agency or group responsible for creating and maintaining the data set Current As Of The date at which the theme table was released by the source agency This will aid future users to identify more current data that may be available Status The status of the data i e preliminary release update in process etc The status levels were borrowed from those used by the Vermont Center for Geographic Information VCGI Source Scale Much of the geographic data has been electronically traced or digitized from various source documents s
239. lier the dialogs for the processing steps are organized in a hierarchical manner The Main Dialog represents the top of the hierarchy Clicking on the Done button will close the Main dialog and will return you to the Setup dialog From that dialog clicking on the Exit button will return you to ArcView April 2006 The Tools Main Dialog Page 76 Part A Data Development Primary Watershed Part A of the Tools extension pertains to developing data for the entire watershed i e the sum of all of the sub watersheds to be analyzed This will be referred to as the Primary or Overall watershed in this manual The following processing steps are included in Part A Step 01 Dissolve sub watersheds into a Primary Overall watershed Step 02 Extract surface waters for linear features and clip to Overall watershed boundary Step 03 Combine stream segments polylines between points of confluence Step 04 User assignment of tributary identifiers to stream segments Access to these steps is provided by clicking on the button labeled Part A Watershed Data Development on the Main Dialog Clicking on that button will display the dialog displayed below Part A Data Development for Primary Watershed Part 4 Data Development for Primary Watershed Step 01 Dissolve Sub Watershed into Overall Watershed Step 03 Combine Streams Segments Between Confluence Points Step 4 l Following completion of the above steps you mu
240. lipped to stream corridors or 13SW for soils clipped to sub watersheds Legend file used N A The output table will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This table is added to the user tables area The output table will have one record for each unique combination of classification and boundary Each record will consist of the following attribute fields RehPtld Reach point identifiers copied from the input table Tribld Tributary Identifier for the main stem tributary associated with the reach point for the stream corridor or sub watershed Values copied from the input table GeoSWArea The sum of the areas associated with each unique classification found above the given boundary CordrArea Will be included as a field if the boundary theme used in Step 17 was the stream corridor theme from Step 09 This field will contain the sum of the area of the stream corridors upstream of the given reach point SubWSArea will be included as a field if the boundary theme used in Step 17 was the sub watershed theme and will contain the sum of the area of the sub watersheds upstream of a given reach point Note The CordrArea or SubWSArea is included to facilitate user calculations of area percentages following Step 12 Step 13 and or Step 14 The following fields are added to the table to verify proper table selection in subsequent processing steps and to provide interna
241. lization procedure has completed click on the View Log button and select the Data Set named System to identify those data sets that were not found As shown below one log entry for each data set not found will be included in the log under the System alias Lig Review Peter Hobe ibe the Sy eon Leg T harran Tbs hoa weber Log in bo be were w a Higie ip in be enwad min the Log Dati Se Sauce Dae Sa Tie Aiie Hiubgle Wis ians Airaid z i E r F Thana ahe DEHE an jon ae e r April 2006 Accessing the Stream Geomorphic Assessment Tools Page 53 If it is found that one or more of the registered data sets cannot be edited the following sequence of messages will be issued The first message will identify the number of data sets that cannot be edited The second message will inform the user as to the actual names of the first eleven data sets The message will indicate whether the list is a complete or partial list of data sets 31 13 of the registered data set s is are marked as Stor Read Only or in use by another application SGAT extension requires ability to edit data sets 2 SGAT Info 0032 GeoSW Common Projinit Loadsy xX 32 Partial list of RO or In Use data sets 00lulc shp ea sO0lucodes dbf s00soils shp s00top20 dbf s00yalley_walls shp s00meandercl shp s00swlmodified shp sO0nensollztabhelds dbf s00Iclustabhelds dbf vtorthos shp townbndry shp The inability to edit data sets will g
242. ls must be registered first The process of registering a theme or table involves identifying a theme or table that is assigned to an alias In other words the theme or table to be used for a specific purpose is identified by the user for example the theme to be used for surface waters Note Refer to the Section entitled General Concepts for a discussion on the term alias The primary dialog for Theme Table Registration and Management is shown below Registration Main Theme Table Registration Required Themes C3 ma Surface Waters ma Town Boundary na Meander Centerline y Soils 4 USGS Quad Boundary Y vf Valley Walls va LeLu Orthophoto Boundary C3 Segmentation Points HUC10 Boundary Required T ables A Soils Top 20 Attributes vf Soils XT ab Fields Step 14 ef LeLu Codes Descriptions ef LeLu xT ab Fields Step 14 Manage Derived Themes and T ables Manage Derived Themes and or T ables Export Theme T able List View Log Done For the required themes and tables a check mark will appear to the left of the button for a given theme table if it has been successfully registered A Stop Hand will signal that registration has either not been done or not completed April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 61 Registration of themes and tables is very similar and requires that the user obtain some descriptive informat
243. lygons will be pre registered in SGAT template otherwise must be obtained from VCGI USGS Quad Boundary as polygons will be pre registered in SGAT template otherwise must be obtained from VCGI and Valley Wall delineations as polygons as digitized by the user Each of the above themes will be registered separately although the same dialog will be used The specific theme to be registered is selected by the button on the Theme Table Registration and Management Dialog The resulting dialog as shown below for Soils will reflect the theme being registered in the dialog Title Registration Theme definition for Soils Shape File Hame NOT SFLECTED Internal Alias Used Soils dentity Required Fields Theme Table Documentation Source OSS Curent As Of fC OS Status Unknown SSS Source Seale Dea Hotes P Select Hames for 2 Helds identified below Soil Mapping Unit Identifiers Field Name Not Selected Soil Mapping Unit Symbole Field Hame Hot Selected Theme Table Information Location A geomorphology versiona B aseD ata Logtudit Records Select Theme Done April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 63 To select a theme click on the Select Theme button In response the File Dialog will be displayed as shown below 2 Select File for Meander Centerline x File Hame Directories OK i h geomorphology versions F F kA Can
244. mall polylines and connect the others by snapping the end vertices Upon Completion The surface water extract theme which will normally be named SO5SWFinalTribld shp will be created and saved in the DerivdData directory This will be displayed in the user view using the legend file named SWTrace avi The legend file must be located in the SysData directory in order for it to be used The route table which will normally be named SO5SWFinalTribldSet dbf will be created and saved in the DerivdData directory A sample of a route table is displayed below RECNO FROMID TOID TOTYPE The record number in the surface water theme that is associated with a given polyline is shown in the first column The second and third columns represent the identifiers assigned to the starting and ending nodes The last column contains the type of node represented by the Told Using the table begins with identifying the To node Then using the From node for that row look for its value in the To column to connect to the next downstream polyline Note It is because the record numbers refer directly to records in the surface water theme that the route table must be kept consistent with the surface water theme If any changes are made to the surface water theme then the record numbers will change And if the record numbers change the route table will be referencing incorrect records A message similar to the following will be issued upon completion of the
245. mber that processing may require 10 20 minutes or more If the route table has already been created the Index Features button will be enabled Click on that button to access the Feature Indexing dialog Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools in the SGAT User Manual for common error and warning messages April 2006 Part D Step FITO00a Setup for Feature Indexing Page 202 During processing When one first clicks on the Setup button a test is made to determine whether the route table and the extracted surface water theme already exist in the DerivdData directory If they do the following message will be issued SGAT Warning 1170 GeoSW FITSetup lbt5etup Click 1170 5055WFinalT ibldSet dbf and S055 FinalT ribld shp esista in directory H Geomorphology Yersion SD erivdO atas IF surface water theme has not been changed there i no need to re create this data set Do you want to continue and re create data set This is included in the event that an erroneous click on the Setup button was made Since this procedure can take a bit of time one can click on No to cancel the setup procedure If however there have been any changes to the surface water theme created by Step 05 or that theme has been re created click on Yes to re create the route table and theme containing the extract of the surface waters If the processing continues a query is made t
246. meaning only if multiple versions of a given alias can be created Multiple Version will be either Yes or No and will indicate whether multiple versions of data sets can be created for the given alias Note The ability to create multiple versions is controlled by a setting in one of the system tables As a general rule only a single version will be allowed to avoid any confusion Note In rare circumstances multiple versions may be desirable in order to compare results For example it may be desirable to create multiple stream corridors via Step 09 to compare different buffering criteria When multiple versions are enabled the output data set names will have a sequence number appended i e SO9Corridor01 shp SO9Corridor02 shp etc April 2006 Using the Log Page 47 The following illustrates the dialog showing log entries for a specific data set SGAT Log Review Enter Note into the System Log ThemeT able for which Log is to be viewed or a Note is to be entered into the Log DataSetSource Data Set Type Activ Multiple Versions Allowed Data Set sOOsubwehed shp e Base Theme iS Ye f Yes Interal Alles SubWatersheds DENEN Tk wi fe Desription Sub Watersheds Theme T able Created in on EE Stepo foo Date 2003 10 31 Time 17 0 Path Th geomorphology version3 BaseD atas Log Audit Notes Date Time RecNo Step Operation Input InputB InputC Comment 2003 11 04 05 49 24 01
247. modified which is the same as the one identified above will be displayed e Enter a note to be entered into the system log upon completion of setup processing April 2006 Step 04a Setup for Assigning Tributary Identifiers Interactively Page 96 Part 4 Step 04 Assign Tributary Identifiers to Surface Waters Primary Pour PE S02PPtshp w Theme tor Primary Pour Ft to be used Surface Water Theme to be bodite Surface walters s035 Comb shp To be saved in H GeormorphologyYersion4 DenvdD ata Note for insertion into System Lo User Note Setup Assign Trib Ids Done Starting the Process After the user note has been entered click on the Setup button This will create the route table necessary for indexing features Remember that processing may require 10 20 minutes or more lf the route table has already been created the Assign Trib Ids button will be enabled Click on that button to access the dialog for assigning tributary identifiers to the surface waters Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools in the SGAT User Manual for common error and warning messages During processing When one first clicks on the Setup button a test is made to determine whether the route table already exists in the DerivdData directory If it does the following message will be issued 1170 SOSS CombT ibldSet dbf exist s in directory H Geomor
248. n Required Directory Structure Required dBase Tables Required Source Themes The ArcView Project File Reviewing the Source Shape Files Themes Overview of the Processing Steps in the Tools Extension Using the Theme and Data Tracking Form Guidelines for using the Stream Geomorphic Assessment Tools Organization Common Dialog Operations Messages in the Tools Extension Input Output Data Set Registration Output Data Set Naming Registration Multiple Versions of Data Sets Processing Time and Patience The Note Field on the Dialogs for Processing Steps Using the Log Accessing the Stream Geomorphic Assessment Tools Initialization Procedure April 2006 WO AOAN DO aAaana ARARA HOA a A 16 19 20 27 29 32 34 34 36 37 39 40 41 44 45 46 49 49 Page i Setup Dialog for the Stream Geomorphic Assessment Tools 58 User Type 58 Application 59 User View 60 Theme Table Registration and Management 61 Registering Themes 63 Removing a Theme Registration 68 Registering Tables 68 Removing a Table Registration 72 Managing Derived Themes and or Tables 73 The Tools Main Dialog 76 Part A Data Development Primary Watershed T7 Step 01 Dissolve Sub Watershed Boundaries into Overall Watershed Boundary___ 78 Step 02 Extract and Clip the Surface Waters to Primary Watershed 86 Critical Evaluation Required by the User 90 Step 03 Combine Stream Segments between Confluence Points 93 Step 04a Setup for Assigning Trib
249. n These elements are as follows e The theme that is to be summarized which will be one produced via Step 12 The theme will correspond to the type and area selected e The pre defined name for the output table will be displayed Note That the output from this step is a table The output table name will reflect o The step number i e S73 o The first character of the topic i e S gt soils or L gt LcLu and o The first character of the coverage for boundary theme i e W gt sub watershed or C gt Corridor An example of a name would be S73LC dbf for LcLu within the stream corridors As one selects the different combinations of radio buttons for the type and area it is possible that the following error message will be issued 2 SGAT User Error 1031 Geos W Common Regi Stor 1037 Input Table for LeLu Areas Summed to Reach Corridor must be created reqistered before this function can be used The above error message simply means that the input theme required for the selected combination of radio buttons does not exist i e it has not been created via Step 12 If the data set identified in the message is required return to Step 12 and select the same combination of radio buttons and perform the Summarize operation When you return to this dialog the error message for that data set should no longer be issued The default or pre selected set of radio buttons for the dialog is LcLu and Corridors As a
250. n Step 05 will be displayed e The theme representing reach points produced in Step 06 will be displayed e Click in the check box for Dissolve Surface Water to place or to clear a check mark If a check mark is found in that check box a separate theme will be created containing the surface water segments dissolved In performing the dissolve all surface water segments having the same reach point identifier and tributary identifier will be combined into a single polyline The name of the resulting theme will be the same as the surface water theme selected as input with the letters Ds v appended to the ended See dialog box above for an example e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data Starting the process After the required information has been entered on the dialog click on the button labeled Calculate Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages During Processing During processing the reach point identifiers associated with a sub watershed in Step 06 are used to find the corresponding reach point in the reach point theme If amiss match occurs the following error message will be displayed SGAT Use
251. n a View without zooming in to a very detailed scale Ata normal scale the legend would cause them to appear similar to that shown for the overlapping boundary error in the figure on the following page Overlapping boundaries Overlaps will occur due to digitizing errors in which the boundaries for neighboring polygons cover a common area Any such conditions will result in an error As shown in the figure on the following page an overlap was detected with both polygons marked as having an overlap The overlap will occur on the common boundary All overlaps need to be corrected prior to continuing April2006 Step 01 Dissolve Sub Watersheds into Overall Watershed Boundary Page 83 Common Boundaries Boundary Containing Overlap Common Boundaries April2006 Step 01 Dissolve Sub Watersheds into Overall Watershed Boundary Page 84 Topology Self intersecting polygons It would be difficult to create self intersecting polygons in ArcView These will occur when the boundary for the polygon crosses over itself such as a bow tie or figure eight During digitizing if one crosses over the boundary such as shown to the right ArcView will create a multi part polygon Each of the polygons will be a separate part of the same shape To identify multi part polygons select the polygon with the feature selection tool to highlight it Then click and hold down the right button A pop up menu will appear Go 2
252. n bar Surround the identifier with double quotes e g M The values will be assigned to the Tribld field because you selected it in 5 above and will be assigned to only those records which have been selected in 9 above They will appear highlighted in yellow Repeat 8 through 12 until all tributary identifiers have been assigned Note Use the Zoom and Pan buttons on the button bar or as you are selecting features click the right button on the mouse and select Zoom or Pan from the pop up menu Attempt to work at a view scale where you can clearly see the stream segments between points of confluence Remember in Step 03 all stream segments between confluence points were combined If however changes to the sub watershed boundaries are made that affect the overall watershed boundary then the process must start again at Step 07 If this occurs follow the procedure outlined in Step 03 Combine Stream Segments between Confluence Points for retaining the trib ID s If during processing in other steps you find you need to modify or add tributary identifiers return to this step and make the necessary changes Then perform processing from Step 05 on Don t skip any steps You will get warnings that certain attribute fields already exist for various themes and that these fields will be cleared and reused In response simply click on OK April 2006 Step 04x Assign Tributary Identifiers Manually Page 108 Step 04z Problems Asso
253. n directory h geomorphologyversiondSyeDatas Review field SwWwUsed for values gt 2 bo find problem records Make comections in Original source themes and re run all steps in sequence To find the surface water segment which caused the error add the shape file to a view Then open the attribute table and query the field named SWUsea to find values greater than two You can then zoom to the selected segment to find the specific location of the error One cause of this error can be digitizing as was indicated in the error checking for Step 05 See section description for Step 05 lt is also possible that a stream segment with a length less than the search tolerance used for stream tracing has been encountered The search tolerance is used to find segments polylines connected to the end vertex of a polyline during tracing In effect the search tolerance defines the radius of a circle Any stream segments that intersect that circle are candidates for continuing the tracing When the Tools extension is distributed the tolerance is set to 0 25 in view units which would be meters If the segment that you have just completed tracing is shorter than 0 25 meters then stream segments connected to both ends will be candidates for the next stream to trace Depending upon the geometry it is possible that an incorrect segment will be selected As mentioned above load the temporary data set into a view and check all stream segments surroun
254. nalyze only those streams which have a permanen flow regime To do that make sure that a check mark exists for the Extract Selected FReg s identify the field containing the flow regime values and then select those values of interest Note One can use this area of the dialog to perform an extraction based upon any field It does not have to pertain to flow regimes Simply enter a check mark in the Extract Selected FReg s check box Select any field The values for that field will be displayed Select those values for which you want corresponding surface water features placed in the output theme Starting the process After the required information has been entered on the dialog click on the button labeled Clip Extract Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages Upon completion Alias of Output Theme for Clipped Surface Waters SWClipped Legend file used to display Clipped Surface Waters theme SWClipped avl Alias of Output Theme for Primary Pour Points PPT April 2006 Step 02 Extract and Clip the Surface Waters to Primary Watershed Page 88 Legend file used to display Primary Pour Points theme PPT avl The themes representing the Clipped Surface Waters and the Primary Pour Points will be saved in the DerivdData subdirectory under that in which the ArcView proje
255. nction is used Warning If any changes to the surface water theme used as an input have been made or the theme has been re created always perform the setup function before indexing any features Otherwise unpredictable errors may occur when indexing features since the route table previously defined may not be coincident with the new surface water theme The route table will be assigned a name based upon the name of the surface water theme from which it is created For example the surface water theme normally used by this step is S05SWFinal shp As a result the output dBase table will be named SO5SWFinalTribldSet dbf and will be located in the DerivdData directory under that in which the ArcView project file is located The extracted surface water theme used in creating the route table and for feature indexing will be named SO5SWFinalTribld shp will also be saved in the DerivdData directory Once the route table has been created then the button labeled ndex Features will be enabled Clicking on this button will result in the Feature Indexing dialog to be displayed April 2006 Part D Step FITO00a Setup for Feature Indexing Page 201 The Setup dialog for feature indexing is illustrated below Part D FITOO Setup for and Performing Feature Indexing Input Thernels Surface Waters So5s wFin al shp Theme for Surface Waters clipped to Sub Wy atersheds ta be used Primary Pour Ft SO2PPt shp w Theme for Primary Po
256. ng occurs in the numerical order shown Only those stream segments to which tributary identifiers have been assigned are shown Upstream Tracing Downstream Tracing If one misses assigning a tributary identifier to a segment in the middle of the main stem or a tributary stream tracing will stop at the ending vertex of the last segment for which the identifiers have been assigned to contiguous stream segments This vertex will be identified as a terminal reach point and any upstream segments beyond the one for which the tributary identifier was not assigned will be ignored See section description for Step 04 April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 121 Attempt to use Surface Water polylines more than twice Another error may also be encountered during stream tracing Since stream tracing occurs upstream and downstream the maximum number of times any stream segment should be encountered is two As each stream segment is encountered during tracing the field SWUsead in the temporary data set SW7rbnn shp is incremented and tested If the value exceeds two the following error message is issued 1104 Attempt to use Surface Water polylines more than twice Probable data eror Processing terminated Following the above message the following will be issued with the appropriate shape file name included 2 SGAT Info GeoSW RPts IbtCalc Click E xj Temporary shape file SW Trb1 shp sawed i
257. ng the corridors and how many stream corridors were created SGAT Info GeoSW ChanBuflbtBuffer Click 7 x Reach Points 29 Terminal Reach Points 5 Stream Corridors errors 0 Stream Corridors bypassed 0 Stream Corridors created 24 The theme representing the stream corridors will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This theme is added to the user view identified on the Main dialog An example of the stream corridors produced is illustrated in the figure to the right Click on the button labeled Done to return to the Part B menu dialog See Appendix H for details on the internal processing steps used to create the Stream Corridor April 2006 Step 09 Calculate Stream Corridors Buffers Page 145 Step 09 Using Alternative Stream Corridors Buffers Research on the development of stream corridors continues to evolve As a result it may be of interest to utilize stream corridors which have been created outside of the Tools extension In order to use those corridor delineations within the Tools extension the considerations discussed below must be kept in mind Note For insight into how Stream Corridors are created in Step 09 refer to Appendix H The steps used may provide some guidance as to how custom Stream Corridors may be created using the Geoprocessing Wizard extension to ArcView Requirements In summary the corridor delineations e Must
258. nhologysersiond SDenvdD ata IF surface water theme has not been changed there is no need to re create this data set Do you want to continue and re create data set This is included in the event that an erroneous click on the Setup button was made Since this procedure can take a bit of time one can click on No to cancel the setup procedure If however there have been any changes to the surface water theme created by Step 03 or that theme has been re created click on Yes to re create the route table April 2006 Step 04a Setup for Assigning Tributary Identifiers Interactively Page 97 If one elects to proceed the next step is to trace the surface waters to build the route table The route table simply defines the connectivity using arbitrarily assigned identifiers for the initial and ending vertices of the polylines in the theme Stream tracing will begin at the outflow or pour point for the overall watershed Since the outflow point is created in Step 02 as the intersection of the stream network with the overall watershed it is Known that a stream segment will begin at the outflow point That stream segment is acquired and the end vertex opposite end of the stream segment is used to find the next segment for tracing With the next stream segment its end vertex is used to find the next stream segment etc Note A check is made to determine if the vertex order of the polyline is correct i e that the vertex 0 is the downstr
259. ning the certified and uncertified soils data for the State of Vermont Included on that CDROM are dBase tables for each county that contain the Top 20 attributes used in interpreting soil data A revised set of Top20 tables were released by NRCS in October of 2005 This required modification of the SoilXTabFields 05 dbf table used by the Tools It is essential that these two tables be in synch A copy of these tables is included on the Distribution CD Step 12 and Step 14 of the Tools will work only with the version of soil data currently subsequent to October 2005 provided by VCGI Prior versions of soil data and the Top20 attribute table will not work due to technical changes in field names field values and field types ArcView Skills Use of the Stream Geomorphic Assessment Tools will require some working knowledge of ArcView Certain steps 02 and 04 will require the user to modify the attribute table associated with a theme Other steps may require knowledge of editing features in themes Feedback Comments or feedback on the Tools should be directed to State of Vermont Agency of Natural Resources Department of Environmental Conservation Water Quality Division River Management Section 103 South Main St Building 10 North Waterbury VT 05671 0408 802 241 3777 April 2006 Restrictions Page 5 Format of Material Distributed Format of This Document This document is organized in the following manner o De
260. nly those stream segments which have been assigned a Tributary Identifier in Step 04 This value will be used in Step 09 for creating stream corridors through buffering To access the dialog for this step click the button labeled Step 08 Calculate Channel Width and Stream Data on the Part B main dialog The dialog for this step is illustrated on the next page Part B Step 08 Calculate Channel Width and Stream Data Input Theres Sub Watershed s00subweshed shp z Theme for Sub Watersheds to be used Surface Water S05SwFinal shp Theme for Surface Waters clipped to Sub W atersheds to be used Reach Points SO6RPtsl2 sho xi Multiple Themes for this input created Select Theme to be used last one created shown first Linear Units of Measure to be use Linear Units Feet Combine Surface Water Segments with the Same Trib ID and Reach Pt IC IM Dissolve Surface Water Allows combining polyline segments with the same reach point and tributar identifiers for thematic display of Output Theme 05SwFinalDsly shp reacupont eae To be saved in h geomorphology versions DerydD ata Note for insertion into System Lo User Note l Calculate Done April 2006 Step 08 Calculate Channel Width and Stream Data Page 137 To use this dialog e The theme representing sub watershed delineations will be displayed e The theme representing surface waters clipped to the sub watershed boundaries produced i
261. nnot be edited the following error message will be issued x 31 14 of the required system table s i are marked as Stor Read Only or in use by another application SGAT extension requires ability to edit data sets lf the above error message is issued it will be followed by a second one listing the system tables that are marked as Read Only or in use by another application The following is an example 32 List of RO or In Use data sets SysApps dbf Sysbasel heme dbf Sysb TRegFields dbf SysChanParm dbf Stor SysDialog dbt SysDir dbf SysErrors dbt SysLinmits dbf SweLog dbt SysAPtFom dbf SyeStatus dbf SysSystem dbf As each table is loaded into the system GUI tests are made to determine if a table is corrupted or invalid If any are found the following messages will be displayed The first will identify the error condition and the second will identify the tables that are not useable 2 SGAT System Error 56 GeoSW Common Projinit L X 56 1 of the required systern table s is are corrupted or invalid Access to SGAT extension prevented Directory Structure The system table SysDir dbf is updated with the directory structure relative to the ArcView project file User View The User View to which themes are to be added when registered or created by the Tools is saved in the system table SysSystem dbf The initialization procedure obtains the name of the view if any iden
262. nts clipped to the sub watershed boundaries will be displayed e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data Starting the process Click on the Clip button after all entries on the dialog have been completed Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages Upon completion Alias of output theme for surface waters clipped to sub watershed boundaries SWFinal Legend file used to display output theme if no errors are encountered TribldAssigned avl Legend file used to display output theme if errors are encountered TribldError avl The theme representing the surface waters which have been clipped to the sub watershed boundaries will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This theme is added to the user view identified on the Main dialog During the clipping procedure the number of parts of which a polyline representing a stream segment is composed is reviewed If any polyline is composed of multiple parts an error condition is raised At the end of processing the following error message will be displayed 1029 1 multi part polylines created for surface waters Surface waters dipping in and out of sub watershed Polylines composed of multipl
263. nts entered must be within the search distance set on the dialog of the surface water polylines If the points are located at a greater distance no polylines will be found and an error message will be issued Note If you are locating the Start End Points for a polyline feature you must always locate the downstream point first 11 If an ending point must be entered use the zoom pan tools to navigate to the area where the end point is located Then again select the Feature Indexing tool and click in the view at the point where the feature ends Note If beginning and ending points are to be selected the starting point must fall on the downstream path between the ending point and the outflow point of the watershed If the starting and ending points do not lie on the same path an error message will be issued 12 Click on the dialog to make it the active window 13 If an error was made in selecting the points click on the Clear button Then re establish the points beginning with step 7 above 14 Once the Point s have been established and the dialog is active the feature can be indexed by clicking on the Set mpact button This establishes the feature as a pending update to the appropriate Point or Polyline impact theme Warning The feature will not be permanently saved until one clicks on the Save button This permits one to cancel feature definition if an error was made 15 To cancel pending updates click on the Cancel bu
264. o select only those records that contain a non blank value for the Tribld field i e those stream segments to which the user assigned a tributary Identifier in Step 04 The selected records are saved as the shape file named S05SWFinalTribld shp in the DerivdData directory This theme referred to as the surface water extract theme will be used in performing feature indexing Note The name of the theme is simply the letters Tribla appended to the name of the surface water theme used The next step is to trace the surface waters to build the route table The route table simply defines the connectivity using arbitrarily assigned identifiers for the initial and ending vertices of the polylines in the theme Stream tracing will begin at the outflow or pour point for the overall watershed Since the outflow point is created in Step 02 as the intersection of the stream network with the overall watershed it is Known that a stream segment will begin at the outflow point That stream segment is acquired and the end vertex opposite end of the stream segment is used to find the next segment for tracing With the next stream segment its end vertex is used to find the next stream segment etc Note A check is made to determine if the vertex order of the polyline is correct i e that the vertex 0 is the downstream end If the order is reversed then the vertex order is reversed in the surface water extract theme In this manner the tracing
265. of the screen Then click on the Show View button This will display the User View Move and resize the user view to fit alongside the dialog This will enable you to move back and forth between the view and the dialog When selecting points to identify the extent to which a tributary identifier is to be used zoom in to the area of interest Working at a large scale of the view enables one to place points accurately alongside of the polylines representing surface waters Working at small scale may cause inaccurate location of the points and thus errors to be generated This dialog is accessed via the Assign Trib Id button on the Assign Tributary Id Setup dialog As a result the following registered theme names will be available from the Feature Indexing Setup dialog e Surface water SO3SWComb shp e Primary Pour Point SO2PPt shp As tributary identifiers are assigned they are entered into the attribute field named Tribld in the surface water theme However the assignments are not permanent until one clicks on the Save Trib Ids button gP Part 4 Step 04b Locate Beginning and Endin Trib Id Assignment Tributary Id T Break polyline at upstream ending point Tributary Ids assigned thus Far Procedures for Assigning Tributary Identifier Distance from Points to Search for Polyline Search Distance poo Meters Set Start End Pts Set startend points for use of tributary i
266. ographic extent or location of a feature Instead one must delete the feature and then re index it Deleting a feature should be performed using the dialog provided in Step FITO0c Feature Data Modification Deletion This ensures for polyline features that all geographic entities related to the same impact are deleted Note If a polyline geographic feature spans more than one reach there will be one polyline record associated with each reach Since all impacts are saved in either the point or polyline impact theme it is possible that features may overlay each other That would be the case for polyline impacts when more than one impact is found along the same section of stream In such cases it would be difficult to select the appropriate polylines for deletion if selection were performed via a View As a result always use the dialog for Step FITOOc to perform deletions The dialog for Step FITOOc also enables one to update or modify the attribute data associated with a given impact It is strongly recommended that one enter a detailed description of the impact in the Description field This will ensure that one can accurately select features for modification and or deletion in Step Fit0Oc April 2006 Part D Step FITOOb Feature Indexing Page 210 STEP FIT00c Feature Data Modification Deletion This dialog permits modification of the data associated with impacts during the Feature Indexing of Step FITOO In addition one can delete fe
267. ollowing message will then be issued yan want to clear the system log file of primary entries for this 1078 Table exp03s00subwehed shp has been removed Do theme If the theme being unregistered has been used in any processing steps select No This will retain the entries in the log should they be needed at some future point for support or simply seeing the order of events that have taken place Clicking on Yes will remove all og entries pertaining to the theme Registering Tables Note If you have received the Version 4 template then all required tables have been pre registered If for some reason you need to register a table follow the directions below Table registration is nearly identical to that for themes Each table must be registered prior to its use within the Tools Only those tables supplied to or by the user need to be registered Specifically the following tables must be registered Soils Top 20 Attributes forwarded with SGAT extension to ensure compatibility with the Soil XTab Fields table Soil XTab Fields provided with SGAT extension to ensure compatibility with the Soils Top 20 Attributes LcLu Code Descriptions forwarded with SGAT extension to ensure compatibility with the LcLu XTab Fields table and LcLu XTab Fields provided with SGAT extension to ensure compatibility with the LcLu Code Descriptions April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 68 Each of the above tabl
268. ols in the SGAT User Manual for common error and warning messages During Processing Each point impact is assigned the value for the RchSegld associated with the surface water polyline upon which the impact is located In addition the attribute Ph2Segld value is constructed by appending the value for RchSeg d to the value for RchPtid f the impact does not fall ona reach segment then the value for Ph2Seg d is constructed by appending a dash to the value for the AchPtld Each polyline impact is subdivided into polylines that are consistent with the surface waters for reach segments The values for RchSegld and Ph2Segid are constructed in the same manner as described for point impacts The following figure illustrates the process of subdividing polyline impacts In the figure a single impact is shown that is located in three sub watersheds This impact is originally represented as three polylines one for each sub watershed After the segmentation process the impact is represented by seven polylines The middle polyline of the original set of three has been subdivided into five polylines consistent with the reach segmentation Sub watershed Boundary Original Impact Consisted of 3 Polylines 1 for Each Sub watershed Reach Polyline for this Reach Subdivided into 5 Polylines between Reach Segmentation Fts 1 for Each Reach Segmen Segmentation Pts Reach Pts April 2006 Part D Step FITO1 Feature Segm
269. on The starting and ending points are those established by the user however the polylines are extracted from those representing the surface water i e the polylines are coincident with the surface waters The process of indexing features enables one to establish multiple impacts e g bank erosion and subsequently relate those impacts to each other or to other conditions events or perhaps to predictive modeling The process of indexing features is provided in an interactive manner via step FITOO One can index two types of features Point feature which simply defines a location of a specific element such as a grade control e g dam waterfall etc or a Polyline feature which defines an extent along the surface waters e g erosion straightening etc The processing of indexing is performed interactively First one selects the impact that is to be indexed and then enters the appropriate data for that impact An impact is simply the definition of what is being indexed e g a dam or extent of straightening Then e Fora point feature one selects a point in the User View The extension projects that point onto the surface waters and then enters the point and associated data into a point impact theme e Fora polyline feature one selects a starting downstream end and an ending upstream end point in the User View The two points define the extent of the impact The extension projects each point onto the surface water polyline
270. on the data set names will be constructed by concatenating the letter S or SEG for processing steps within Part D two digits reflecting the step number in which the data set is created and the alias For example the data set created for the overall watershed in Step 01 will be named S01Watershed shp The first time that a step is run the following message will be shown to the right of the control on the dialog for the output data set Theme or Table will be created upon completion of this Step The assigned name for the data set will be shown in the control and the control will be disabled The second and subsequent times that the step is run a note similar to the following will be displayed Existing Theme S01Watershed shp for Overall Watershed will be replaced Again the assigned name for the data set will be shown in the control and the control will be disabled Any processing steps which require an input data set which is restricted to a single version will automatically display the name of the data set in the appropriate control on the dialog Since there is only one possible choice that control will be disabled Multiple Versions Multiple versions of a data set should be used only where absolutely necessary Only derived data sets are to be allowed to have multiple versions Base or source data sets should not be allowed to have multiple versions As stated earlier the dialog Multiple Output Ver
271. on Completion Alias of Output Theme for Overall or Primary watershed Watershed Legend file used to display output theme Watershed avl Legend file used to display input theme SubWSErrors avl The theme representing the overall watershed will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This theme is added to the user view identified on the Main dialog Click on the button labeled Done to return to the Part A menu dialog April2006 Step 01 Dissolve Sub Watersheds into Overall Watershed Boundary Page 79 The figure below on the left represents the source theme for sub watersheds and the figure on the right illustrates the theme representing the overall watershed resulting from this step Attribute fields created for sub watershed theme SubWSArea Area of the sub watershed Note It is possible that the user may modify the boundaries of the sub watersheds to correct for errors or to simply adjust their configuration following this step In such cases if Step 01 is not re run the area of the sub watersheds will not be accurate As a result this field will be recalculated in Step 06 to ensure accuracy SubWSld A unique identifier for each sub watershed Error checking conducted for the sub watershed theme During the processing of the sub watershed theme several edits of the sub watershed are made These are performed to identify potential digitizing errors that may cause errors in th
272. or the ArcView project file Hidden SysTable and SysView DocGUI s A DocGUI is a Graphical User Interface GUI for documents Doc in ArcView Examples of DocGUls are Views Tables Charts Layouts Scripts and Dialogs A document is an actual view table chart layout script or dialog Multiple documents are available under a DocGUI The Tools creates two DocGUIs named SysTable and SysView These provide a focal point for the Tools to quickly access themes attributes of themes and data from tables The SysTable and SysView DocGUls are made invisible to the user to prevent confusion and inadvertent modification to any of the documents The SysView DocGU will contain a single view named RegThemes All themes registered by the user or created through use of the Tools will be added to that view Whenever a theme shape file is registered or created within the Tools the associated attributes are added to the SysTable DocGUI In addition whenever a table is registered or created it is added to this DocGUII The following illustrates the two DocGUIs created Remember however that these will not be visible E ama A BB i i April 2006 Accessing the Stream Geomorphic Assessment Tools Page 50 Adding system tables to SysTable DocGUI The system tables are added to the SysTable DocGUI As each table is added to the DocGUI a test is made to ensure that the table can be edited If any table ca
273. ort entity This will provide the support person with the steps completed and any critical error conditions encountered Each entry in the log contains the following O O O O O Date and time of log entry Record number In some cases multiple records are required for an entry Also any note entered by the user on the dialog will generally be entered into the log in the second or sometimes third record Identification of step for which log entry was made This will either be the step number or a three character abbreviation for the step e g Reg for registration Ini for initialization Sys for system and N A for not applicable Name of the data set created or modified Alias associated with the data set Operation performed in the step Input themes tables Up to three input data sets will be shown in a record If more than three are used multiple records will be created for the log entry These will be differentiated by the record number Comment This field will display the results of the processing step or activity for which the log entry was made User notes will also be in this field but will be included in a separate record The following illustrates the dialog when the data set selected is All Themes Tables Using this overall data set log entries are shown in chronological order and is best when attempting to identify what activities have occurred and or the order in which act
274. ot Selectea other functions on the dialog will be disabled The following Warning message will be issued prior to the display of the Setup dialog if the View has not been selected SGAT Warning 1062 GeoSW Main digOpen x W062 View to which themes are to be added has not been selected Please set View in this dialog April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 60 When a View has been selected or created the Map Units for the view will be set in accordance with the field named MapUnits in the system table SysUnits dbf The User Type Application and User View will be maintained in the system table SysSystem dbf This ensures that the selections will be retained between different sessions in working with the Tools Once the User Type Application and View have been selected the remaining controls on the dialog will be enabled This permits access to the following Theme Table Registration and Management Stream Geomorphic Assessment Tools SGAT Viewing the Log System Functions O O O To begin using the Stream Geomorphic Assessment Tools one must first register the source themes and tables These have been described in earlier sections and can be registered via the Theme Table Registration and Management dialog This dialog is described in the next section Theme Table Registration and Management As has been presented in earlier sections each theme or table to be used in the Too
275. pes one can also offset the impacts during extraction for cartographic purposes The dialog for this step is illustrated below Part D FITO Extract Impacts with Offset Input Theme Source of Input Theme C Reaches produced by Part D Step FITOO f Reach Segments produced by Fart D Step FITOI Et Impacts FITO Ftlmpact5eq shp w Theme for Impacts Point with segmentation Ids assigned to be used Polite Impacts FITO Lnimpact5ea shp w Theme for Impacts Polyline segmented to be used Criteria for Extract Impact Bank Armoring and Aevetment r Sub dmpact Rip Rap Location Right Bank Port fe Polpline Criteria for Offset from Surface Water for Polyline Feature Type Offset Direction Facing Downstream Offset Distance 100 Feet C Right Output Theme to be created Output Theme Marne FIT O24 0rnoring shp To be saved in H SGeomorphologysersion4 DernyvdD ata Extract Done April 2006 Part E Step FITO2 Extract Feature s Page 217 To use this dialog Select the source of the impact themes to be used Reach created in Step F T00a or Reach Segment created in Step FITO1 If either or both of the point and polyline impact themes are not present in the DerivdData directory then the corresponding radio button will not be enabled The theme containing point impacts created in Step F T00a or Step FITO7 will be displayed The theme containing polyline impacts creat
276. point is retained 4 The resulting chain of polylines is merged by reach point id RchPtld If all polylines fall within the same sub watershed only a single record will be entered into the polyline impact theme FITOOLnImpact shp If the polylines cross two or more sub watersheds then a polyline record for each sub watershed or reach point id will be entered in to the polyline impact theme 5 A unique value is assigned to the attribute mpactid The same value is assigned to all records associated with a given impact 6 The data entered on the dialog is associated with each polyline record If the upstream and downstream points selected are not on the same downstream flow path from the upstream point to the outflow of the entire watershed an error message will be issued Abbreviated Instructions Available from the Dialog To review an abbreviated set of instructions similar to those above click on the Instructions button This will display a separate dialog box with the instructions listed The nstruction dialog can be closed or it will automatically be closed when the primary Feature Indexing dialog is closed Show View Button on the Dialog The Show View button is simply a short cut for displaying the user view If the view is already visible there will be no apparent action when one clicks on the Show View button April 2006 Part D Step FITOOb Feature Indexing Page 209 Modifying features One cannot modify the ge
277. port file performed by VCGI To ensure that the proper coverage is obtained provide the overall watershed boundary resulting from Step 01 of the Tools and request a buffer 500 meters area outside in the event that the watershed boundaries change during assessment Meander Centerline Delineation These will be provided via digitizing by the user The resulting theme must be of polyline class Meander centerlines need not be drawn for all sub watersheds but must be drawn 1 Where valley walls are present or 2 Reach segmentation is to occur The meander centerline is one of the key features that can be used in creating stream corridors or Fluvial Erosion Hazard zones In the buffering performed in Part B Step 09 to create stream corridors use of the meander centerline is optional Use of meander centerlines remains to be optional for the application of FEH Option 1 In contrast the meander centerline is a required feature for creating the fluvial erosion hazard zone using the application of FEH Option 2 when a given reach has been is being segmented Note In the FEH Option 2 application the meander centerline not only serves as an element used to develop a component buffer but it is also used to sub divide buffers in accordance with any reach segmentation performed during a Phase 2 assessment The following summarizes the digitizing requirements for the meander centerline 1 Meander centerlines must be drawn as lines polylines
278. quently Flooded Fid_Freq 0 0 0 00 Not Freq Flooded Fid_None 90 38 Not Rated Fid_NR 0 0 0 00 Occasionally Flooded Fid_Occas 0 0102442380 9 49 00 0 Rarely Flooded Fid_ Rare 0 00 0 00 Soil Value for Potential for Flooding No Value Fld_ Bink O07 Total CordrArea 0 1079474252 0 107947422 99 88 In the above example the option on the dialog to exclude Water Area From Summary was checked This resulted in accumulating all areas associated with water into the field WaterArea If that option had not been used the areas associated with water would have been accumulated into the field Fld _NR Not Rated which is the value that is assigned to the soil mapping unit for water in the Potential for Flooding soil characteristic For verification one can review the Top20_05 dbf table for soil characteristics To access the dialog for this step click the button labeled Step 14 Summarize Areas by Field Value Cross Tab on the Part C main dialog The dialog is shown on the following page Part C Step 14 Summarize Area By Field alue Cross Tab e g Acres for each Flood E Type of Data Being Summarized Select Standard Field s for Analysis Table Containing Field Value Names To be saved in h geomorphology version3 D erivdD ata Data of Interest Boundary of Interest Aggregate Level Sails C Sub Watersheds Reach Step 12 C Land Cover Land Use Corridor
279. r Error 1008 GeoSW RPts IbtCalc Click xj 1008 Unable to find reach point in internal list Check Stor sub watershed theme for digitizing errors AchFtld field blank and un processing steps in sequence from Step U6 on The occurrence of the error message generally means that the theme selected for sub watersheds is not the same one that was used in Step 06 when the reach point theme selected on the dialog for this step was created Verify theme selection and or restart the steps from Step 06 and run all steps in sequence Note It is critical that any given theme be used consistently in all steps For example the sub watershed theme supplied by the user should be used in all subsequent steps that require a sub watershed theme Data refer to Appendix C and D is added or modified in the attribute tables of themes in many steps Subsequent steps require that data to be present and consistent with other themes April 2006 Step 08 Calculate Channel Width and Stream Data Page 138 Upon completion Upon completion the following message will be displayed to summarize the processing that took place 2 SGAT Info GeoSW CalcChan btCalc Click E x SOBRPtsO1 shp updated with channel widths and lengths total stream lengths sinuosity valley confinement and channel slopes if reach pt elevations present The attribute tables for reach point theme and for the surface water theme will be updated as described earlier If
280. r developed for use with the Tools These data sets are listed in the following table DataSet Type Source Soils Top 20 Attributes Note In the source column the abbreviations refer to the following NRCS Natural Resources Conservation District RMS River Management Section VT Agency of Natural Resources and VCGI Vermont Center for Geographic Information Many of the geographic coverages available in Vermont are provided by VCGI in a tiled format i e the state is divided into a rectangular square grid much like a spreadsheet A tile pertains to a specific grid cell For surface waters and soils a tile usually encompasses the same area as nine of the orthophotos available from the VT Tax Mapping Program Setting Up for Using the Tools Page 17 lt will be normal to have to acquire multiple tiles for surface waters soils etc in order to cover the same area as the watershed being assessed Prior to use with the Tools these tiles will have to be merged into a single data set Refer to the sections entitled Setup Required dBase Tables and Setup Required Source Themes for additional considerations During Theme Table Registration the location of the specific data set will be reviewed If it is not located in the BaseData directory the user will be offered the opportunity of having the data set copied to that directory Once a data set has been registered for use within the Tools the user should not move or d
281. ract Feature s 217 STEP FITO3 Export Feature Data 220 April 2006 Page iii Appendices A Documentation for using the Optional Tools provided with the Stream Geomorphic Assessment Tools extension Two tools are provided Review Polyline Theme for Geometric GIS Errors and Build Polygons from Polylines B Theme and Data Tracking Form Forms are provided that can be used to track the source data including currency responsible agency source scale and date Additional forms are provided that can be used to document the input themes tables parameter values and output themes for each of the processing Steps Thus a written description can be available for future reference C Data Element Attribute Description by Processing Step A concise description of each Processing Step The input themes dBase files the output themes dBase files and the attribute fields that are created or updated are listed for each step D Data Element Attribute Description by Theme dBase File A concise listing by theme dBase file of the fields attributes and the processing Step in which they are added or updated E Cross Tabulation Field Names for Soils Step 14 provides the capability to develop cross tabulations for soils data This appendix provides a listing of the source field potential values and names of the cross tabulation fields which will be created F Cross Tabulation Field Names for Land Cover Step 14 provides the capability
282. reach points for all subsequent processing steps Do not proceed beyond Step 06 without cleaning up all errors Doing so will not only produce incorrect results but will adversely affect the normal processing performed in the subsequent steps The operation of the subsequent steps depends upon correct input data Unpredictable results may occur such as infinite loops internal ArcView errors e g index out of range nil objects Segmentation Violations etc Refer also to the description of Step 06 for illustrations of various types of errors Step 07 will calculate the valley line and data where valley walls are delineated and only for those streams which have been assigned a Tributary Identifier Step 07 will only produce valley lines for stream segments in a sub watershed where the reach point and its upstream neighboring reach point have been assigned the same Tributary Identifier This primarily affects sub watersheds which encompass a confluence of tributaries If the reach points for the tributaries entering the sub watershed are assigned different Tributary Identifier than that assigned to the outflow reach point no valley line will be drawn Refer to the description of Step 07 Step 08 will calculate channel width only for those streams which have been assigned a tributary identifier Step 09 will create a stream corridor only for those streams which have been assigned a tributary identifier In summary improper or in
283. red for the Alias HUCTOBoundary ou must unregister the theme as being associated with that Alias first by removing it from the project In the above situation an incorrect shape file was selected for Soils April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 64 For the themes to be considered for use in the Tools the feature class will be Polygon Polyline or Point In addition each of the required themes is expected to be of a particular feature class The following table identifies the alias description and feature class for the required themes Alias Description S Feature Class If the shape file selected is not of the correct feature class for the theme being registered the following error message will be issued and the selection will be ignored 2 SGAT User Error 1083 GeoSW Reg Themelb Sele xX feature class Required theme must be of Point feature clasa Selection ignored 1083 The theme selected s00subwehed shp it of Polygon If no errors have occurred thus far and the shape file selected is located in a directory other than BaseData the following message will be issued SGAT Y N 1065 GeoSW Reg Theme IbtSelectThem Cli 1085 The data set selected vt_towns_sqatv4 shp for the Alias Town Boundaries is not located in the required directory H WGeomoarphologyersion4 BaseD ata Do you want the file s copied to that directory C
284. registered prior to selecting this step the following error message will be issued SGAT User Error 1031 GeoSW Common RegData Inp x 1031 Input Theme for Sub tw atershede must be created registered before this function can be used The above error message will be issued after one selects the button on the Part A dialog for this Step and prior to the display of the dialog This is due to the fact that the test is performed in the open event for the dialog To use this dialog In general the input and output data sets will automatically be set Always review the instructions or notes to the right of each data set These will provide guidance based upon the configuration established via system settings o Since the theme for sub watersheds should have already been registered it will automatically be identified o The output theme is associated with the alias of watershea therefore the name of the output theme is defined by concatenating the letter S O07 step number and Watershed i e SO1Watershed shp o Enter a commenit note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data Click on the button labeled Dissolve to initiate processing Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages Up
285. relational table is appended to each record This permits one to analyze soils or LcLu within each corridor or sub watershed Note The Top20_05 dbf table is a product from VCGI NRCS that lists various characteristics of each soil mapping unit A document published by VCGI NRCS which describes that table is included as Appendix G Examples of characteristics are indications of flooding high low depths to water table parent geologic material etc The LUCodes dbf table is also a product from VCGI The table lists a descriptive phrase for each land use land cover code It is self explanatory and can be reviewed in ArcView Refer to the section Setup Required dBase Tables A version of these tables is provided on the Tools Distribution CDROM The names of those tables are SO0Top20_05 dbf and SOOLUCodes dbf Step 12 and Step 13 and Step 14 of the Tools will work only with the version of soil data currently subsequent to April 2002 provided by VCGI Prior versions of soil data and the Top20 attribute table will not work due to technical format changes To access the dialog for this step click the button labeled Step 12 Summarize and Attach Descriptive Data on the Part C main dialog The dialog is illustrated below Part C Step 12 Summarize and Attach Descriptive Data e g Sum acres by Soil Typ e Source Theme Table with Descriptive Data and Fields Type of Data Being Summarized Area for which
286. result the above error message may be issued prior to the display of the dialog i e after the button labeled Steo13 Aggregate Data to Upstream Watershed Area on the Part C menu dialog is clicked but before the dialog is actually displayed This occurs because the test for the existence of the theme is also conducted on the open event of the dialog If the theme representing the LcLu data theme clipped by the corridor boundaries does not exist the error message will be issued Simply click on the Ok button in the error message The dialog will appear and you can then select the desired combination of radio buttons April 2006 Step 13 Sum Data to Upstream Watershed Area Page 171 Starting the process After the required information has been entered on the dialog click on the button labeled Sum Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages A dialog box will prompt the user to verify the action and data for which the summation of data and will done SGAT Y N 1133 GeoSW SumD IbESum Click 1133 5125C dbf for Soils within Corridors will be summed to the upstream watershed area Do vou want to Continue Upon completion Alias of output table will vary 13LC for LcLu clipped to stream corridors 73LW for LcLu clipped to sub watersheds 13SC for soils c
287. ributary stream tracing will stop at the ending vertex of the last segment for which the identifiers have been assigned to contiguous stream segments This vertex will be identified as a terminal point and any upstream segments beyond the one for which the tributary identifier was not assigned will be ignored See section description for Step 04 Attempt to use Surface Water polylines more than twice Another error may also be encountered during stream tracing Since stream tracing occurs upstream and downstream the maximum number of times any stream segment should be encountered is two As each stream segment is encountered during tracing the field SWUsed in the surface water extract theme is incremented and tested If the value exceeds two the following error message is issued 1104 Attempt to use Surtace Water polvlines more than twice Probable data eror Processing terminated To identify the surface water polyline query the attribute field named SWUsed for a value greater than 2 This will identify the polyline in error Usually reviewing the polyline its vertices and adjacent polylines will reveal the problem April 2006 Part D Step FITO00a Setup for Feature Indexing Page 204 Because the search distance to find connecting polylines is set as 0 25 meters any surface water polylines less than 0 25 meters in length will cause such a problem In such cases one will have to edit the surface water theme to remove the s
288. rminated Note These errors should also have been detected during Steo SEGOO and corrected prior to running this step Refer to Steo SEGOO The occurrence of the error message means that the surface waters are not continuous through the reach i e there is a space separating different segments This is an error which should not occur at this point in the processing steps All such errors should have been detected early in the processing steps of Part A or Part B April 2006 Part D Step SEGO1 Segment Reaches Page 197 Warning If the above error message is issued review any records containing a value other than one 1 for the field NumParts and correct the condition in the source theme The source theme would normally be the one resulting from Part A Step 04 Run all steps subsequent to that one including all steps in Part B and Part C as well as SteoSEGOO The error message displayed below would generally indicate improper placement of the segmentation point Most likely the segmentation point falls before or beyond the beginning or ending point of the polyline representing the surface water Review the segmentation points identified and correct their location Segment ld of 4 does not fall on surface water line work 1054 Segment point identified by AchFtld of MO and Stor Processing terminated The following message should never occur as it indicates that in excess of 702 segmentation points exist for a given reach
289. rridors An Access Level is associated with each application that defines which User Type is permitted to use an application SysBaseTheme_ Contains critical data including an alias for each possible theme table to be used or created Maintains relationship between alias used within the Tools and the actual file name on the hard disk Identifies the active theme or table being used for a given alias SysBTReaFields Maintains relationship between an internal field alias and an actual field name SysChanParm Contains the constant coefficient and exponent to be used in the regression equation for calculation of the channel width in Step 08 Calculate Channel Width and Stream Data Enables use of different values for these parameters based upon drainage area upstream of a reach point Certain User Types can modify these parameters and or the applicable range of drainage areas to which they apply via System Functions gt Channel Width Calculation SysDialog Identifies for each dialog in the Tools the Part Steo Number and Title An Access Level is also associated with each dialog that defines which User Type is permitted access SysDir Maintains the current required directory structure relative to the directory in which the ArcView Project file is located Message numbers and message format for error info messages SysIlmpact Defines Impacts and associated data for Feature Indexing in Part D SyslmpactLoc Defines permissible locations
290. rror message may be issued prior to the display of the dialog i e after the button labeled Step14 Summarize Areas by Field Value Cross Tab on the Part C menu dialog is clicked but before the dialog is actually displayed This occurs because the test for the existence of the theme is also conducted on the open event of the dialog If the theme representing the LcLu data theme clipped by the corridor boundaries as produced by Step 12 does not exist the error message will be issued Simply click on the Ok button in the error message The dialog will appear and you can then select the desired combination of radio buttons Starting the process After the required information has been entered on the dialog click on the button labeled Sum Processing may take a few moments depending upon the hardware used Note Refer to the section entitled Common Dialog Operations in the Stream Geomorphic Assessment Tools for common error and warning messages A dialog box will prompt the user to verify the action and data for which the summation of data and will done SGAT Y N 1128 GeoSW SumByF IbtSum Click 1128 cross tabulation for table 5735C dbf having Sails Gp within sum of Upstream Corridors will be developed Do you want bo Continue More on Water Area As one might imagine the area encompassed by water bodies can be significant This is especially true when the boundary type is corridors Assume for example that
291. rt A menu dialog April 2006 Step 03 Combine Stream Segments between Confluence Points Page 95 Step 04a Setup for Assigning Tributary Identifiers Interactively Tributary Identifiers are used to identify those surface waters that are involved in geomorphic assessment within the Tools In effect only those surface water polylines that have been assigned a non blank value will participate in any of the remaining processing steps As a result it is important to properly identify the surface waters and to assign the tributary identifiers This step provides tools to assist in that effort To use the capabilities of this step one must first create a route table The route table identifies the connectivity between polylines and orders the connectivity for tracing the stream network In addition the order of the polyline vertices in the surface water theme is altered if necessary to ensure that the order is in the upstream direction i e vertex 0 is at the downstream end of the polyline and vertex n is at the upstream end The purpose is to facilitate rapid transversal of the stream network In summary the surface water theme from which the route table is created may be modified to ensure the upstream direction of vertices in the polylines The route table is created by clicking on the Setup button In order to create the route table the entire surface water theme is traced Processing times may be somewhat lengthy 10 to 20 minute
292. s ChanlSlope and or Waly Contin will be cleared and reused for theme SOBRPtsO1 shp Do vou want to continue If you feel that the situation is incorrect you can prevent re calculation by clicking on No To continue and have the fields re calculated click on Yes It is important to note that the Tools were designed such that you can repeat a step This can be useful if you have forgotten which step you had last performed When you do repeat a step always continue processing the remaining steps in sequence This will ensure that the data is consistent After the dialog edits the information entered and or selected on the dialog the following message will be issued SGAT Y N 1006 GeoSW CalcChan IbtCalc Click 1006 User supplied parameters okay Processing may take a few moments Do pou want bo continue This is a bail out point providing you with the opportunity to terminate the step This is provided in the event that you accidentally clicked on the Execute button Input Output Data Set Registration A process referred to as registration requires that every theme and table be identified prior to its use inthe Tools This means that the source themes and tables described in earlier sections must be registered by the user using the dialog entitled heme Table Registration and Management available from the Setup dialog This dialog will be described in a subsequent section Note All data sets
293. s The portion of the surface water polyline extending downstream of the starting point and the portion of the surface water extending upstream of the ending point are trimmed off Those polylines and all intervening polylines are extracted and placed into a polyline impact theme The ability to index features is provided in Part D Step FITOO The reach segmentation capability of Step F TO7 provides users with the ability to segment impacts indexed features in the identical manner in which surface waters have been segmented via Part D Reach Segmentation This enables one to visually display impacts by reach segments as well as be able to link to data maintained in the DMS All impacts or features that are indexed are maintained in one of two shape files FITOOLnImpact shp for polyline impacts and FITOOPtImpact shp for point impacts Since it is possible that multiple impacts may be partially or completely coincident the ability to extract specific impact types including sub impact and location is provided One identifies the impacts to be extracted whether the geographic representation for polylines only is to be offset left or right and offset distance and the name of the shape file in which the extracted impacts are to be saved The resulting shape files can be used for cartographic display of impacts on maps using various Offsets colors and line weights Finally the ability to export impacts is provided The export file is a
294. s input If aggregate level is Reach Watershed or upstream drainage area the table produced from Step 13 will be used as input Select to have the Water values within the soils theme excluded from the cross tabulation If water is to be excluded any soils with a mapping unit symbol of w will be tabulated separately into a column or field named WaterArea This provides a more accurate cross tabulation of soil characteristics Note The Top20 05 dbf table does include a soil mapping unit for water While this is potentially valuable information for different users it is recommended that water be excluded from the soils data Select one or more of the fields for which areas are to be calculated Click on the first field Then hold the Shift key down while clicking on the additional fields The list of fields from which you can select may be a subset of those found in the Top20_05 dbf table Note Click on the Select Standard Field s for Analysis button to choose only those parameters that are evaluated in the Phase 1 Geomorphic Assessment Once the radio buttons for type area and aggregate level have been selected the remaining elements on the dialog that are required to perform Step 14 will automatically be filled in These elements are as follows The theme that is to be summarized which will be one produced via either Step 12 or Step 13 The theme will correspond to the type area and aggregate level selected The
295. s perhaps more in very large watersheds or in watersheds with dense surface waters So have patience and plan for the processing time when this function is used Warning If any changes to the surface water theme used as an input have been made or the theme has been re created always perform the setup function before assigning any tributary identifiers Otherwise unpredictable errors may occur when assigning tributary identifiers since the route table previously defined may not be coincident with the newly defined surface water theme The route table will be assigned a name based upon the name of the surface water theme from which it is created For example the surface water theme normally used by this step is SO3SWComb shp As a result the output dBase table will be named SO3SWCombTribidSet dbf and will be located in the DerivdData directory under that in which the ArcView project file is located Once the route table has been created then the button labeled Assign Trib Ids will be enabled Clicking on this button will result in the dialog for Step 04b for assigning tributary identifiers to be displayed The Setup dialog for assigning tributary identifiers is illustrated on the following page To use this dialog e The theme containing surface waters created in Step 03 will be displayed e The theme containing the primary pour point for the watershed created in Step 02 will be displayed e The surface water theme that may be
296. s sub watersheds surface water and where applicable the segmentation points Note The system tables and ArcView legend files must be located in the SysData directory If the system tables are not found during initialization an error message will be issued and use of the Tools will be prevented If the project has not been saved and you attempt to use the Tools the following error message will be issued when you click on the Continue button of the introductory screen 1107 SGAT Extension requires a Saved Project being active Please save the Project file Access to Extension prevented Load the Stream Geomorphic Assessment Tools The procedure for loading the Tools extension into the project was described earlier in the section Setup Installation of the Tools Extension The procedure is briefly outlined below Make the project window the active window in ArcView Click on the File Menu Click on Extensions Scroll down the list of extensions until you find Stream Geomorphic Assessment V xxxx Click on the check box to the left of Stream Geomorphic Assessment V xxxx A check mark should appear 6 Click on Ok ao 2 E The Tools button should appear on the Button Bar Upon completion of the steps described in this section you can begin using the Stream Geomorphic Assessment Tools April 2006 Setting Up for Using the Tools Page 28 Reviewing the Source Shape Files Themes The key to successful and efficient use of
297. s C Reach Watershed Step 13 Option for Processing Water Bodies in Soils M Exclude water from summary Field with Soil Mapping Unit Symbols in Source Table Musym Source Table from Step 12 or 13 Fields to Sum by Value and Table of Field Value Names TAG Ssiscar Field s containing Values for which area l 5125C dbf is to be summarized Hold Shift key down to select more than one Field Selection for Cross T abulation ROCKDEEP SAND SLOPELOW SLOPEHIGH i WATERSHALL p lable sOOnewsoilttabfields dbf x or sO00newsoilxtabfields dbf WATERDEEP a Output Table dBase for Summary Data 5145012 dbf i Table will be created upon completion of this Step Note for insertion into System Log User Note Summarize Done Step 14 Summarize Area by Field Value Cross Tabulate Page 176 To use this dialog This dialog is specifically tailored to the tables resulting from Step 12 or Step 13 Select the type of data soils or land cover that is to be cross tabulated When the type of data is selected the corresponding Table containing Field Value Names and available Fields will be entered on the dialog Select the Area for which the data is being cross tabulated Sub watersheds or corridors Select the Aggregate Level for which the data is being cross tabulated reach or reach watershed Note If the aggregate level is Reach the table produced from Step 12 will be used a
298. s are applied to the interim data set it will subsequently have to be registered as the Sub watershed theme To accomplish this perform the following 1 Go to the theme registration dialog for sub watersheds Setup Dialog gt Theme Table Registration and Management gt SubWatersheds 2 Click on the Remove Theme button to un register the original sub watershed theme Respond Yes to Are you sure you want to remove this theme Respond No to Do you want to clear the system log file of primary entries for this theme This will preserve the log entries that identified the errors in the original sub watershed theme Click on the button Select Theme Select the theme to which the corrections have been applied Complete the Documentation Information Click on the Save button to register the theme o 02 After the above the theme to which the corrections have been applied will be used as the sub watershed theme in all processing steps April2006 Step 01 Dissolve Sub Watersheds into Overall Watershed Boundary Page 82 Less than Minimum Area set in SysUnits dbf The SysUnits dbf system table contains a field named MinArea that has arbitrarily been assigned a value of 0 01 one hundredth This value will be in the area units established for performing geomorphic assessment which by default are square miles Note No facility has been provided to alter the value for the MinArea field in the SysUnits dbf table If
299. s being created for the first time the output name will be entered into the dialog control Since this is the first time no alternative output versions are available As a result the control will be disabled o As illustrated in the figure below the second and subsequent times that the dialog is entered the data sets previously created will be listed in the output control along with an entry for New Version The data sets will be listed in the order created with the most recent version as the first entry The control will be enabled to allow selection of an existing data set or New Version Part A Step 01 Dissolye Sub Watersheds into Overall Watershed Input Theme s Sub Watershed sO0subwshed shp v Theme for Sub Watersheds to be used Primary Overall Watershed Theme to be Created Output Theme S01 Watershed01 shp v Themes resulting from this step have been created n E Select Theme to be replaced or New Version to SO1Watershed01 shp a create a new version To be saved in New Version HD ata Note for insertion i User Note Dissolve Done If an existing data set is selected it will be replaced If however New Version is selected then a new data set will be created The name will be assigned as described earlier with a sequence number one larger than any that are registered The name assigned will not be displayed in the control until processing has been
300. s in the system table SysBaseTheme dbf As a result the theme required for an alias is retained between different sessions with the Tools The existence of the themes tables referenced in the system table SysBaseTheme dbf are also verified during the initialization procedure for the Tools For example the source theme for surface waters has been assigned an alias of surfacewaters During registration the user may identify the theme to be used for surface waters as S00SWLModified shp Whenever the Tools requires the theme for surface waters it simply uses the alias of surfacewaters and an internal translation creates the reference to the actual shape file gt SOOSWLModified shp The benefits of this are many but for the purposes of the user it is primarily that a theme or table need only be identified once After that the Too s will refer to the theme or table that was identified during the registration procedure Output Data Set Naming Registration All themes and tables created by processing steps within the Tools are automatically registered Each output data set is associated with a specific alias Further the output data sets are automatically named The name assigned to a data set will be the concatenation of the letter S or SEG for processing steps in Part D the step number and the alias For example the output of Step 07 is the overall watershed formed by dissolving the sub watersheds This output t
301. se click on Yes If one elects to create a backup a message similar to the following will be issued after the backup is created SGAT User Error 1185 GeoSW SetTribld2 digpet xj 1185 Backup of theme 5035W Comb shp has been created oO Backup theme is named SUS5Y Comb BkUp O3 shp and iz located in directory path H Geomorphology Yersion4 147 emp The name of the backup will be constructed of the surface water theme name which is normally SO3SWComb with _BkUp_nn shp appended The nn will be replaced with a unique sequential number e g 01 All component files of the surface water theme will be backed up in the Temp directory under the directory in which the ArcView project is located April 2006 Step 04b Assign Tributary Identifiers Interactively Page 101 Following the above procedure one can proceed with the process of assigning tributary identifiers which is relatively straightforward Fundamentally one enters the value to be used for the tributary identifier indicates whether the upstream surface water is to be broken at the point entered and then enters two points defining the extent of the surface waters to which the tributary identifier is to be assigned The dialog for Assigning Tributary Identifiers is illustrated below To use this dialog The dialog was designed to be placed on the computer screen along with the view To start move the dialog to the right or left side
302. sent in order for one to be able to use the Tools extension The directories BaseData and SysData will contain data sets that are to be used with the extension All data sets contained in these directories are required and must be copied onto the hard disk to directories of the same name The Temp and DerivdData directories are included only to illustrate the required directory structure Extension Contains the ArcView extension for the Tools GeoSW4 avx Refer to section Setup Installation of the Tools Extension Documentation Contains this manual and each appendix in separate Portable Document Format pdf files Note Any data directories and or files copied from CDROM to a directory on your hard disk is assigned a Read Only attribute This will prevent any modifications from being made to those directories and data sets This attribute must be removed in order for the Tools extension to function properly To remove use Windows Explorer and select all directories and or files Click the right button on the mouse Select Properties Then remove the check mark on Read Only April 2006 Format of Material Distributed Page 7 General Concepts lt is essential to have a general understanding of certain basic concepts for using the Tools This section provides an introduction to the basic concepts each of which will be described in more detail in subsequent sections The basic concepts are as follows Implementation of a
303. sions available April 2006 Organization Page 42 under System Functions should be used to establish multiple versions This ensures that only derived data sets can be modified Note The ability to create multiple versions is restricted to certain User Types When a data set is being created and multiple versions are allowed the data set names will be constructed by concatenating the letter S of SEG for processing steps in Part D two digits reflecting the step number in which the data set is created the alias and a two digit sequence number For example the first version of the data set created for the overall watershed in Step 07 would be named S01Watershed01 shp and the second version will be S01Watershed02 shp etc Note Certain data sets such as the reach point data from Step 70 and the soils and land use cross tabulations resulting from Step 14 are to be imported into a Web Baed Data Management System The script used to import the data into the data base will be expecting a specific data set name When multiple outout versions are enabled one must use caution to ensure that the correct data set is being imported In addition one may have to rename the data set resulting from use of the Tools to match that expected by the import script When an output data set is created with the ability to have multiple versions the following will Occur o When entering the dialog in which a data set for an alias i
304. ssigned an identifier in accordance with the user specified format in the Format Options for Reach Pt Id s dialog which is accessible from the System Functions dialog TribID The Tributary Identifier from Step 04 assigned is that of the stream flowing through the reach point PPtType The field named PPtType is used to identify the type of reach point The values assigned to the PPtType field will be blank for normal reach points Outflow for the primary pour point of the overall watershed and Terminal for reach points that represent the terminus of the Main Stem or a Tributary Note A Terminal reach point represents the terminating vertex of the last polyline segment for the Main Stem or a Tributary or the terminating vertex of the last polyline segment for the Main Stem or a Tributary that was assigned a Tributary Identifier in Step 04 DistToStrt Is the distance in feet from the reach point to the primary pour point for the watershed RchDistld An identifier assigned based upon the distance calculated for DistToStrt The format for this identifier is as follows Tl mmm ttt Where TI is the tributary identifier assigned in Step 04 mmm is the distance in miles upstream from the primary pour point for the overall watershed and itt is the decimal part of the distance upstream in fractional miles April 2006 Step 06 Calculate Reach Points and Reach Point Data Page 115 Assume
305. st be entered in order for the slope to be calculated at the downstream reach point o State Plane Coordinates VT State Plane coordinates for reach point o Geographic Coordinates Longitude and Latitude coordinates for the reach point April 2006 Step 10 Data Entry Review of Reach Point Data Page 150 e Channel O Width Width of the channel calculated in Step 08 User may choose to enter a value based on field observations or other knowledge Length Length of channel in feet for the main stem or the tributary from the reach point to the next upstream reach point from Step 08 Note User does not need to enter channel width for Terminal reach points Slope Is the difference in elevation at the upstream end of the channel and the downstream end of the channel divided by the Channel Length Slope is calculated as a percentage Sinuosity s the Channel Length divided by the Valley Length Make sure this number is gt 1 0 or the DMS will not accept the data If the value is LESS THAN 1 the user must manually measure the valley length and enter it into the dialog box e Valley O Width Is an average width of the valley walls In Step 07 Channel Width is calculated by dividing the area of the valley walls that fall within a sub watershed by the Valley Length Note Step 07 will create a valley line and therefore the value for this field only if a valley wall polygon in the user supplied theme for valley walls encompasses
306. st use ArcView to assign values to the attribute field named TriblD This field must contain values which identify stream segments for each tributary Stream segments belonging to a given tributary must have the same value and the values must be unique for each tributary l For example all stream segments belonging to the main tributary could be assigned the letter M stream segments for the first tributary could be assigned T1 the next tributary T2 etc Then proceed to the sub Watershed analysis section Done Clicking on the buttons for Steps 01 02 or 03 will display the corresponding dialog box for that step Clicking on the button labeled Done will return you to the Main Dialog April 2006 Part A Steps 01 04 Data Development for Primary Watershed Page 77 Step 01 Dissolve Sub Watershed Boundaries into Overall Watershed Boundary The purpose of this step is to form a geographical boundary for the entire watershed that is consistent with the sub watershed boundaries The resulting watershed is referred to as the Primary or Overall watershed One might be able to acquire a theme representing the overall watershed from another source That theme however may not define the same geographic extent or coverage as the sub watersheds This step ensures geographic and geometric consistency between the overall watershed and the sub watersheds The Tools can use a theme representing sub watersheds that h
307. stem Functions dialog Due to the critical nature of these functions and the subsequent impact on data produced by the Tools these functions are disabled for other User Types FEH For the development of Fluvial Erosion Hazard Zones with all of the capabilities of the Regional Planning user type Regional Planning Regional Planning organizations have access to certain more system functions Watershed Group This User Type provides dedicated use of the Tools in performing Phase Geomorphic Assessment All applications and system functions not dedicated to that effort are disabled or removed as alternatives Note The User Type may be predefined and locked to prevent inadvertent selection of incorrect parameters In this case the control for defining the User Type will be disabled April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 58 The User Type must be selected prior to accessing any of the other functions on this dialog If the User Type is Not Selected other functions on the dialog will be disabled The following Warning message will be issued prior to the display of the Setup dialog if the User Type has not been selected Z SGAT Warning 1064 GeoSW Main digOpen a p xX 1064 User Type designation has not been selected Please select in this dialog Application The User Type selected will establish the alternatives available for the Application to which the Tools are to be applied It is
308. such situations however remember rule 2 above April 2006 Step 07 Calculate Valley Line and Data Page 127 The following figure illustrates a non contiguous polygon representing valley walls j Non continuous polygon contains both upstream and downstream Reach Pts 5 If separate polygons are drawn for valley walls that share a reach point then the polygons will have to overlap such that they both include the reach point In the following figure the two polygons drawn for valley walls overlap to include the common reach point Overlapping Polygons Valley Wall Polygon 2 Common Reach Pt Note Drawing overlapping polygons is generally not advisable in a Geographic Information System GIS as it can cause problems with normal GIS functions However since the valley walls are being drawn solely for use in the Tools extension this is acceptable If you subsequently need to use the valley walls polygons for other GIS functions they can be dissolved through use of the Geoprocessing Wizard extension provided with ArcView Following that exercise any overlaps will be removed and the adjoining polygons will be converted into a single polygon April 2006 Step 07 Calculate Valley Line and Data Page 128 In addition to the rules for digitizing the polygons representing valley walls valley lines will only be drawn if a reach point and its upstream neighboring reach point are associated with the same Tributary Id
309. t encompasses the geographic area for the entire watershed 2 Soils coverage s will have to be converted to shape file s and merged into a single shape file that encompasses the geographic area for the entire watershed 3 Land Cover Land Use coverage will have to be converted to a shape file covering the geographic area of the watershed The process required will depend upon the format in which the coverage is acquired e If in grid format it will have to be converted to a shape file of polygon class To reduce the size of the coverage the geographic area should be restricted to that area surrounding the watershed Note This format conversion requires the use of the Spatial Analyst extension to ArcView e If in Arc Info polygon format coverage s will have to be converted to shape file s and merged into a single shape file that encompasses the geographic area for the entire watershed 4 Coverages must be acquired that contain the boundaries for the following features HUC 10 watersheds Ortho photos Towns and USGS Quads These coverages or shape files will generally be provided on the CD ROM containing the extension The pre processing steps for the above are beyond the scope of this manual and may require the assistance from person s familiar with Arc Info and or ArcView April 2006 Setting Up for Using the Tools Page 13 User created or delineated coverages that must be available are as follows 1 Sub watershed
310. tation provided by VCGI NRCS is included as Appendix G Note The field named MUKEY is generally used to link these attributes with the geographic soils coverages themes or shape files Steps 12 and Steps14 of the Stream Geomorphic Assessment Tools provide the capability to extract data pertaining to soils for use in the assessment process VCGI and Natural Resources Conservation Services USDA NRCS has published a CDROM containing the certified and uncertified soils data for the State of Vermont Included on that CDROM are dBase tables for each county that contain the Top 20 attributes used in interpreting soil data Due to certain formatting issues a revised set of Top20 tables were released by NRCS in October of 2005 A statewide version of the Top20 was also developed A copy of this table named SOOTop20_05 dbf has been provided on the Distribution CD for the Stream Geomorphic Assessment Tools The table can be found in the BaseData directory on the CD Step 12 and Step 14 of the Jools will work only with the version of soil data currently subsequent to October 2005 provided by VCGI SO0O0SoiIXTabFields_ 05 dbf is required for Step 14 This table identifies for each field in the SO00Top20_05 dbf table all of the unique values that occur for that field and assigns a unique field name associated with the value Use of this table will be described by example in Step 14 Appendix E provides a description and listin
311. tension therefore no system requirements RAM or processor speed above or beyond that required for ArcView are imposed The file containing the Tools extension requires approximately 4 MB of hard disk space The shape files and dBase files produced by the Tools will be dependent upon the projects undertaken These may consume an extensive amount of hard disk space The Tools were developed and tested under ArcView Version 3 2a It is expected that the Tools should run on ArcView Versions 3 1 however no testing has been performed on versions other than 3 2a The Tools were developed and tested under Windows 2000 While it is expected that the Tools will perform in the same manner under other operating systems no testing has been performed in environments other than under Windows 2000 To prevent possible conflicts with other ArcView extensions perform the following l Start with a new ArcView project lI Unload any ArcView extensions other than the Tools Certain processing steps notably Step 03 Step 06 Step 07 and Step 09 within the Tools are computationally intensive Use of older computers with limited memory RAM and slower processor speeds can take a significant amount of time during those steps Newer computers with processor speeds 1GHz and up and with 512MB or more of memory RAM are recommended The Tools make extensive use of dialogs to facilitate user input of data These dialogs have been developed using the Dialog D
312. tep is out of synch with the original surface water theme as well as the themes derived via Step 02 and Step 03 When this step is re run use the Note field on the dialog to indicate that corrections were made and to which theme If no errors are detected and the legend file 7TribldAssigned av exists in the SysData directory the stream layer that is created in Step 05 will be displayed using that legend The legend as shown to the right will display each stream segment in accordance with whether a rib D value was assigned in y S0S5waters shp Step 04 Dark blue will indicate TribID Assigned light blue Tribld Assigned will indicate Trib D NOT Assigned The figure below displays Tribld NOT Assigned the theme added to the view with the legend file A SOSwaters shp JAZ Tribld Assigns Tribld NOT As vv SO2Zprimaryp ourpts tk Intlow Ke Outtiow Unknown SO2waters shp MA SO Iwatershed shp Lewis _oreek_water _ Compiled_boundari Review the stream network to ensure complete and proper assignment of the Tributar Identifiers Refer to the discussion under Step 04 While not visible the stream segments will be broken at the points of intersection with the sub watershed boundaries Click on the button labeled Done to return to the Part B menu dialog April 2006 Steps 05 Clip Linear Surface Waters to Sub Watershed Boundaries Page 114 Step 06 Calculate Reach Points and Reach Point Data This step a
313. terline should respect the boundaries of the valley walls if available for a given reach i e the meander centerline should remain inside of the boundary for the valley walls April 2006 Step 09 Calculate Stream Corridors Buffers Page 142 7 At confluence points it will be necessary to have a small segment of the meander centerline traveling up the tributary fall within the sub watershed of the main stem or primary tributary This is required to meet number 3 above for the reach on the tributary The small dangling will be ignored in the development of buffering for the reach on the main stem or primary tributary An example of this is illustrated in the figure below Stream Centerline ie Meander Centerline Dangling Segment of Q Meander Centerline Sub watershed Boundaries 7 8 A meander centerline must be present in a given reach in order to develop a fluvial erosion hazard zone using the application of FEH Option 2 9 A meander centerline may be present in a given reach in order to develop a fluvial erosion hazard zone using the application of FEH Option 1 Attribute fields for the resulting Stream Corridor theme The following attributes are included in the resulting Stream Corridor theme RchPtid Identifier of the reach point associated with the sub watershed Tribld Tributary Identifier associated with the sub watershed CordrArea Area of the stream corridor within a given sub watershed in square mi
314. ternative Stream Corridor Buffers Page 147 Outline of A procedure to calculate areas The following is a general outline of one procedure which can be used to calculate the areas of the alternative stream corridors 1 69 O os OR E 11 12 13 14 15 16 Open the view to which the alternate corridor theme has been added Make the alternate corridor theme active by clicking on it in the table of contents frame on the left hand side of the view Click on the Open Theme Table button on the button bar The attribute table for the theme will now become the active window Click on the Table menu on the menu bar Click on Start Editing Click on the Edit menu on the menu bar Click on Select None Click on the field name for CordrArea in the table window The field name will appear depressed If it does not then click on it again Click on the Calculate button on the button bar In the resulting dialog double click on the Shape field entry in the upper left hand side In the lower left hand box the term Shape will appear After the Shape enter a period followed by ReturnArea followed by 2589988 11 The complete entry should look like Shape ReturnArea 2589988 1 1 Remember the period after Shape Click on Ok The areas should then appear in the attribute table under the field column named CordrArea Click on the Table menu Click on Stop Editing In response to
315. th 3 28084 Valley widths will have to be obtained by measuring the width of the valley in several places The multiple readings would then have to be averaged and included in the attribute table for the field Valy Width WARNING The above approach will update the Valley Line theme however it will not affect the Reach Point theme which is the repository of all data calculated in the Tools The revised values for lengths and widths will also have to be entered into the reach point theme using Step 10 REMEMBER if you enter data via Step 10 Re running Step 07 will cancel any changes made via Step 10 April 2006 Step 07 Calculate Valley Line and Data Page 135 Step 08 Calculate Channel Width and Stream Data Using the data from Step 06 attribute values are calculated for the reach point and surface water theme All linear distance values will be calculated in accordance with the units feet specified on the dialog Note Do not attempt to change the units of the data Doing so will produce unexpected results Attribute fields for the reach point theme See Appendix C and D for descriptions of all fields associated with the Reach Point theme The attribute fields calculated in this step are identified below Note None of the calculations are imported into the DMS They can be used in SGAT and ten they are re calculated in the DMS Note All attribute fields associated with the Reach Point theme are created in Step 06
316. the reach point and its neighboring upstream reach point For those reaches which do not have valley walls in the user supplied theme the user must enter the value for Valley Width in Step 10 and calculate the derived value for Confinement in that step Note User does not need to enter valley width for Terminal reach points Length s the length of a generalized line running down the center of the valley walls The line is created in Step 07 and the length of that line is calculated and inserted in this field Note Step 07 will create a valley line and therefore the value for this field only if a valley wall polygon in the user supplied theme for valley walls encompasses the reach point and its neighboring upstream reach point For those reaches which do not have valley walls in the user supplied theme the user must enter the value for Valley Length in Step 10 and calculate the derived value for Sinuosity in that step Note User does not need to enter Valley Length for Terminal reach points Slope Is the difference in elevation at the upstream end of the valley Upstream Reach Pt and the downstream end of the valley at the reach point divided by the Valley Length Refer to description of Valley Length field as the software may not generate Valley Length values for all reaches Confinement Is the Valley Width divided by the Channel Width The value of this field can be calculated in Step 7 8 or 10 depending upon availability of the
317. the following warning message will be issued If the existing table is to be replaced simply select Yes SGAT Y N 1012 GeoSW Density IbtChip click 1012 Output data set STSM U_ monktonesite dbf exists in the output director and will be replaced if you continue Do wou want to continue Selecting No in response to the preceding message will abort the operation and result in the following message being issued A dialog box will prompt the user to verify the action and data for which the density calculation operation will be done SGAT Y N 1006 GeoSW Density IbEClip click 1006 User supplied parameters okay Processing may take a few moments Do wou want to continue April 2006 Step 15 Calculate Densities Page 187 Upon completion Alias of output table None Legend file used N A The output tables will be saved in the DerivdData subdirectory under that in which the ArcView project file exists This table is not added to the user tables area Two tables are created for each time you run this step one for the boundary you selected and the other for the boundary selected summed for the entire area upastream For example if you select to sum the mapped wetlands for the sub watershed than two tables will be created named S15WR_vermont_vswi dbf amp S15WU_vermont_vswi dbf representing the area of wetlands in the sub watershed as well as the area within the drainage area or sub watersheds summed
318. the main stem or a tributary Review the section describing Step 04 and Step 05 for additional errors that may occur during stream tracing To provide some background regarding potential errors a description of the method implemented for tracing the stream network and determination of reach points follows First a query is made to select only those records that contain a value for the Tribld field i e those stream segments to which the user assigned a tributary Identifier in Step 04 The selected records are saved as a temporary shape file in the Temp directory This theme will be assigned a name of SWTrbnn shp where ArcView will assign a sequential number in lieu of the nn The temporary data set will be deleted upon completion of processing unless an error is detected during stream tracing If an error is detected an error message will be issued alerting the user to the existence of the data set so that it can be used in correcting the error encountered The data set can be deleted by the user without adverse affect on the operation of the Tools Note If any temporary data sets having the prefix of SWTrb exist in the temporary directory ArcView will assign a sequential number that makes the data set unique Stream tracing will begin at the outflow or pour point for the overall watershed Since the outflow point is created in Step 02 as the intersection of the stream network with the overall watershed it is Known that a str
319. the preceding figure the surface water for the reach is represented by the blue polyline connecting reach points M03 and M04 During processing Step FEHO7 the segmentation points will be projected onto that polyline In addition the surface water will be subdivided into the five segments labeled A E April 2006 Setting Up for Using the Tools Page 23 User Defined Segment Breaks Segment Breaks Required Attribute Table Structure User Defined REACH M11 Segment Break wa m a CORo ho pho j z m 5 SGAT OUTPUT DATA SGAT Output Table J Rearh Segment MO2A M02B a aa e a a a A A A The above figure outlines the process for developing the reach break shape file required for segmentation in SGAT The segmentation shapefile must ONLY contain points for where the stream is to be broken The attribute table MUST have a field containing the Phase 1 reach number and a unique identifier for each segment break number or letter One of the outputs from SGAT is a segment break shapefile with the segment ID s as one attribute Soils These are available from VCGI on a CD in shapefile format Sub watershed Delineation These will be created by manually digitizing or through use of the Spatial Analyst extension of ArcView Either way the exterior boundary for the project must match the huc 10 boundary so that when merged with other projects within the state the exterior boundaries match The three options for d
320. the required data is available In performing a geomorphic assessment the calculated values are compared with fairly broad ranges of values to categorize a given reach For example the value for sinuosity is used to group stream channels into the following categories Low sinuosity Sinuosity value between 1 0 April 2006 Step 07 Calculate Valley Line and Data Page 125 and 1 2 moderate sinuosity Sinuosity value between 1 2 and 1 5 and high sinuosity sinuosity value above 1 5 As a result no attempt has been made in the processing of Step 07 to obtain highly accurate measurements for valley length and average width Note For information on sinuosity and confinement refer to the Stream Geomorphic Assessment Handbooks available from the River Management Section of the Department of Environmental Conservation Agency of Natural Resources Requirements for Digitizing Valley Walls In Step 07 a valley line will be created for those sub watersheds in which valley walls have been delineated The valley line should approximate the center of the valley walls In Step 09 the valley walls will be used to create stream corridors in accordance with the process described in the Vermont Stream Geomorphic Assessment Phase 1 Handbook Appendix E Users should read and be familiar with the Appendix E of the State assessment handbook before completing this step Delineation of valley walls is required only for unconfined wide valleys Un
321. theme for sub watersheds was SOOsubwshed shp The interim theme will be Exo01S00Subwshed shp The interim theme will be added to the user view to assist in reviewing the potential errors detected however it is not registered in the system tables The source input theme for the sub watersheds as well as the interim theme will have two fields added to their attribute tables GeoSWRevu and GeoSWCount The GeoSWRevu field will contain a code used to identify an error detected for the given sub watershed and the GeoSWCount field will identify where meaningful the number of occurrences for the given error and the sub watershed Each of these fields will be described subsequently The source theme and the interim theme will be displayed in the user view using the legend file SubWSErrors avl This will visually assist in locating and reviewing specific errors An example of the legend and the view is shown below Certain potential errors pertain to a specific sub watershed polygon e g self intersection area and multi part conditions Other potential errors pertain to a sub watershed polygon and a neighboring polygon e g overlaps and multiple boundary segments In the latter case the potential error condition is assigned to both polygons The following table identifies the potential error code used in the GeoSWRevu field and the legend the use of the GeoSWCount field and the potential error condition April2006 Step 01
322. theme registration Note A free form text field for entering notes This can be a contact name for the data set a condition discovered with the data etc The above data should be completed for each theme table registered All theme table registration data is maintained in the system table SysBase Themes dbf Field aliases are also used to identify the names of fields required to be in the theme attributes or in tables During the registration of the theme table specific fields must be identified for these aliases Logging A Log has been implemented to record key actions or the results of processing steps Critical errors encountered will be noted in the og entries The intent of the Log is to provide users with the ability to track where they are in the processing cycle and errors encountered In addition the log will also provide key information to the supporting organization s should any problems occur during use of the Tools Access to the log can occur on any of the Menu Dialogs In addition on the dialog in which the Log is displayed one can enter notes specific to a theme or table This can be an aid in documenting problems with the source themes or tables error conditions corrections applied etc Refer to the Section entitled Using the Log for more detailed information April 2006 General Concepts Page 10 SysApps Identifies permissible applications and name of buffering table to be used in Step 09 Create Stream Co
323. themes or tables created by the processing steps in the Tools are automatically registered Only those themes or tables that are used in a given step need to be registered before that step can be used For example Step 07 dissolves the sub watersheds into an overall watershed As a result only the theme representing sub watersheds needs to be registered prior to using Step 07 April 2006 Organization Page 39 lf an attempt is made to use a step for which the required input themes tables have not been created by the Tools and registered or registered by the user for source data sets an error message similar to the following will be issued 2 SGAT User Error 1031 GeoSW Common RegDat a x Stor 1031 Input Theme for Sub tw atersheds must be created registered before this function can be used Note The above error message will be issued after one selects button on the Menu dialog for a given processing Step and prior to the display of the dialog This is due to the fact that the test is performed in the open event for the dialog The registration procedure simply associates the name of the actual file s on the hard disk to be used with a given Alias The Tools will consistently refer to a theme table using its alias throughout all processing steps The use of an alias in this manner permits the actual file on the hard disk to have any name Note The registration process updates the record for the given alia
324. therefore essential to select the User Type first and then the Application The Application can be one of three options SGA This Application is for the Phase Geomorphic Assessment Buffering will be performed in Step 09 Create Stream Corridors per Appendix E of the Stream Geomorphic Assessment Phase Handbook available from the Vermont Agency of Natural Resources This Application is available to all User Types FEH Option 1 This Application is for the Fluvial Erosion Hazard Option 1 Buffering will be performed in Part D in accordance with Option 1 in the Technical Guidance for Determining Floodway Limits Pursuant to Act 250 Criterion 1 D dated 10 07 03 from the Vermont Agency of Natural Resources FEH Option 2 This Application is for the Fluvial Erosion Hazard Option 1 Buffering will be performed in Part D in accordance with Option 2 in the Technical Guidance for Determining Floodway Limits Pursuant to Act 250 Criterion 1 D dated 10 07 03 from the Vermont Agency of Natural Resources Note The Application may be predefined and locked to prevent inadvertent selection of incorrect parameters In this case the control for defining the application will be disabled The Application must be selected prior to accessing any of the other functions on this dialog If the Application is Not Selected other functions on the dialog will be disabled The following Warning message will be issued prior to the display of the Setup
325. this software is to take the time to review the initial geographic coverages prior to use A simple review can identify areas such as the following e Streams crossing over sub watersheds where they should not This represents incorrect stream digitizing or watershed delineation Using the digital versions of the USGS quads and the VT Orthophotos from the VT Tax Mapping Program one can fairly quickly resolve and correct these issues e Watersheds with multiple pour points i e where water flows out of the watershed Each sub watershed can have only one outflow point In many cases the watershed boundary may be near the confluence point of streams Verify that 1 The watershed boundary crosses downstream of the point of confluence or 2 The watershed boundary is above the point of confluence and that it crosses only a single stream The following figures illustrate correct watershed boundaries in relation to the stream network Watershed Line Stream Lines Watershed Line April 2006 Organization Page 29 The following figures illustrate data problems with either the sub watershed delineation or surface waters The figure on the left illustrates surface waters crossing over a sub watershed boundary This would be indicative of incorrect digitizing of the surface waters or incorrect sub watershed delineation The figure on the right illustrates the sub watershed boundary crossing upstream of a stream confluence This will r
326. tified in that system table If a view is identified via prior use of the Tools a check is made to determine if that View exists in the current ArcView project If it does not it is created and named in accordance with the name from SysSystem dbf In addition the Map Units for the View are set in accordance with the units from the system table SysUnits dbf No error or warning messages are issued at this time Validation of system tables for theme table registration Two system tables SysBaseTheme dbf and SysBTReqgFields dbf retain the registration data for any themes and tables registered by the user or created by the Tools Each theme table to be used or created April 2006 Accessing the Stream Geomorphic Assessment Tools Page 51 must be represented by at least one record in the SysBase Theme dbf table The data within that record defines the alias used within the Tools When a theme table is registered a shape file or dBase table becomes associated with that alias Through the alias then the Tools know which shape file or table is to be used in each processing step In a similar manner certain fields in themes or tables to be registered by the user are required to be present The Tools would not know in advance the names of those fields As a result an alias is used within the Tools to refer to a given field During registration the user must associate a specific field with that alias Through the alias then the specific field to
327. tion scans all surface water polylines from the upstream end at which the use of a tributary identifier ends to the outflow of the overall watershed If any polylines are encountered that do not have a value for the rib d attribute a counter is incremented The number of polylines encountered is displayed in the top portion of the Validation Results panel in the field labeled Blank Intervening Polylines In addition an attribute field named Skipped will be set to Y for those polylines To identify the polylines that have been missed open the attribute table for the surface water theme Then review each polyline having a value of Y for the attribute named Skipped By using the attribute table to identify the specific polyline and then reviewing the polylines and their neighboring polylines in the View the correction should become apparent To illustrate the situation displayed in the figure on the following page was created The heavy green line was properly assigned a tributary identifier However those that are highlighted in yellow were not Thus eight polylines were identified as having been skipped The values of the attribute field Skipped were set to Y as shown in the attribute table Assignment of the tributary identifiers to the skipped polylines can be accomplished via the Step 04b dialog or directly through the attribute table If modifications are to be performed by editing the attribute table it is stron
328. tions causing the above error condition are e Attribute table associated with the theme is open in another application such as Microsoft Excel If this is the cause then close the other application e Shape files were copied from a CD to the hard disk This operation generally causes the directories and files copied to have the Read Only attribute set Windows Explorer can be used to verify and modify the Read Only property See Introduction Contents of Distribution CD Sample Data for brief instructions on changing this property April 2006 Organization Page 37 Certain processing steps require specific attribute fields to be in the input theme s table s _ If they are not found an error message such as that shown below will be issued This may be an indication that the wrong theme has been registered for a given input Most likely however it will indicate that the attributes for a given theme have been improperly edited by the user 1002 Fieldis Tribld not found in theme S035 Comb shp Stor Run all steps in sequence from Step O04 on Processing terminated The operation to be undertaken by clicking on the Execute button will not occur until the error conditions have been corrected The editing performed assists in reducing errors however the user should verify the information entered or selected prior to clicking on the Execute button The processing step for most dialogs will create an output theme or table The name
329. tory H Geomorphologyversiond Test Temps By clicking on the button labeled View Log one can view the actions taken via registration or management Note Refer to the earlier Section entitled Using the Log for a discussion on the log and the dialog providing access to it Clicking on the Done button will return to the Setup Dialog April 2006 Setup Dialog for the Stream Geomorphic Assessment Tools Page 62 Registering Themes As has been discussed in prior sections each theme must be registered prior to its use within the Tools Only those themes which are supplied to or created by the user need to be registered Specifically the following themes must be registered Land Cover Land Use 2002 LcLu as polygons obtained from the VT River Management Section Meander Centerline delineations as polylines as digitized by the user Ortho Photo Boundary as polygons will be pre registered in SGAT template otherwise must be obtained from VCGI HUC 10 Boundary as polygons will be pre registered in SGAT template otherwise must be obtained from lobtained from River Corridor Management RCM Reach Segmentation Points as points as digitized by the user required only if segmentation of reaches is to be performed Soils as polygons obtained from VCGI version updated in 2003 Sub watershed delineations as polygons as digitized by the user Surface Waters as polylines obtained from VCGI Town Boundary as po
330. trol labeled User Note will be located at the bottom of each dialog for the processing steps and data set registration This is a free form text field into which a note can be entered that pertains to the output data set and that will be entered into the system log This field along with the system log should be used to describe any pertinent conditions As an example one may have attempted to run Step 07 and received errors The errors are corrected and Step 07 is run again It would be useful to Know that the second run follows cleaning up certain errors e g a note could be entered describing the type and number of errors corrected This field is also useful for describing the content or variation when Multiple Output Versions of a data set are used Refer to Section entitled Multiple Output Versions The system log is described in the Section entitled Using the Log April 2006 Organization Page 45 Using the Log A log will contain entries for all key activities i e registration of a source theme table selection of user type or application completion of a processing step etc This provides the user with the ability to review the log to determine what steps or activities have been completed and what the results were for various processing steps The log will serve as a critical component with respect to support in the use of the Tools The log as well as any necessary data sets should be forwarded to the supp
331. tst sh Multiple Themes for this input created Select Theme Bil to be used last one created shown first Name of Table containing Data to be Summed Type of Data Being Summarized Area for which Data is being Summarized C Soils C Sub Watersheds Land Cover Land Use Corridors fable NotRegistered W Tables required for LcLu Areas Summed to Reach o negsiere Corridor has not been created or registered Output Table containing Data aggregated to Upstream Watershed Area Gutput Table S73Lc dbf Table will be created upon completion of this Step To be saved in h geomorphologyversion3 D erivdD ata Note for insertion into System Log User Note Done To use this dialog This dialog is specifically tailored to the themes resulting from Step 12 e The theme representing reach points created in Step 06 will be displayed e Select the type of data soils or land cover that is to be summarized e Select the Area for which the data is being summarized sub watersheds or corridors e Enter a comment note in the Note text field to describe any conditions error corrections etc that may aid in understanding the process used in developing the assessment data April 2006 Step 13 Sum Data to Upstream Watershed Area Page 170 Once the above radio buttons corresponding to the above have been selected the remaining elements on the dialog that are required to perform Step 13 will automatically be filled i
332. tton This will clear all pending updates created since the start of the session or the last Save operation April 2006 Part D Step FITOOb Feature Indexing Page 208 16 To save pending updates click on the Save button This will permanently apply the pending updates to the appropriate Point or Polyline impact theme As indicated in Steps 15 and 16 one must save the impacts If you attempt to quit the dialog by clicking on the Done button a check is made to determine whether any changes are pending If there are pending changes an error message is issued warning that they will be lost if you continue Results of Feature indexing For point features the point will be projected onto the nearest surface water polyline The projected point will be entered along with the data entered on the dialog into the FITOOPtImpact shp shape file For polyline features the following is performed 1 The point entered for the downstream point i e the downstream end of the impact being indexed is projected onto the surface water The surface water polyline is broken at that point and the segment located upstream of the point is retained 2 The polylines connecting the downstream point with the upstream point are extracted 3 The point entered for the upstream point i e the upstream end of the impact being indexed is projected onto the surface water The surface water polyline is broken at that point and the segment falling downstream of the
333. tures one must first create a route table This is accomplished via the Setup button on the dialog First an extract of the surface water theme will be made This extract will contain only those polylines for which a value for the tributary identifier attribute field Tribld has been assigned The extract theme will be used in creating a route table for indexing features and for the actual feature indexing procedure Note In the subsequent text within this section any reference to surface waters or to the surface water theme pertains to the extract containing only those polylines with a non blank value for the Tribid attribute field The route table identifies the connectivity between polylines and orders the connectivity for stream tracing In addition the order of the polyline vertices in the surface water theme is altered if necessary to ensure that the order is in the upstream direction i e vertex 0 is at the downstream end of the polyline and vertex n is at the upstream end The purpose is to facilitate rapid transversal of the stream network The extract of the surface water theme and the route table are created by clicking on the Setup button In order to create the route table the entire surface water theme is traced Processing times may be somewhat lengthy 10 to 20 minutes perhaps more in very large watersheds or in watersheds with dense surface waters So have patience and plan for the processing time when this fu
334. uch as the VT Orthophotos 1 5000 USGS Quads 1 24000 or 1 25000 and others etc The scales shown in parentheses provide guidance as to the relative accuracy of the data i e the smaller the number to the right of the colon the more accurate the data should be This documentation field will only be applicable to theme registration Note A free form text field for entering notes This can be a contact name for the data set a condition discovered with the data corrections made etc The above data should be completed for each theme registered It is not essential that the documentation information be entered at the time when the theme is registered One can register the theme and then return to the registration dialog for the given theme to add or to update the documentation information as it becomes available Note All theme registration data is maintained in the system table SysBase Themes dbf Field aliases are also used in identifying the names of fields required to be in the attributes of certain themes During the registration of the theme table specific fields will have to be identified for each of these aliases The following table lists those themes for which fields must be identified ThemeAlias Field _ Description Land Cover LcLu Classification Values in field will identify the Land Cover Land Use Land Use Codes classification code represented by a polygon This field and the values within it is used to rel
335. uence point 14 87 would be assigned a different Tributary Identifier See Figure to right T4 S3 a For example all stream segments pertaining to the Main Stem could be assigned the code of M all segments for the first Tributary could be assigned the code 77 the second Tributary could be assigned the code TZ etc Tributaries which flow into other tributaries can be assigned identifiers in a hierarchical manner For example sub tributaries which flow into a tributary identified as 72 could be assigned identifiers such as 12 0181 T2 01S2 etc Remember however that the tributary 72 must continue through to its terminal segment The figure to the right illustrates this concept Note that T4 continues to the terminal segment and all other subordinate tributaries are assigned different Tributary Identifiers April 2006 Step 04x Assign Tributary Identifiers Manually Page 107 The following is a general outline of one procedure which can be used to assign the identifiers 1 2 10 11 In the resulting dialog enter the tributary identifier to be assigned in the lower box 13 Open the view in which the surface waters from Step 03 was added Make that Surface Water theme resulting from Step 03 active by clicking on it in the Table of Contents frame on the left hand side of the view Click on the Open Theme Table button on the button bar The attribute table for the theme will
336. uld not have been possible Special thanks are given to Staci who made sure that questions and issues were resolved in a timely fashion and who spent many hours testing the software as it was being developed The development effort was team spirited and appreciated by all The approach used to obtain Latitude Longitude coordinates was borrowed from a script View_Lat ave dated June 16 2000 written by Peter Telep of the Vermont Department of Environmental Conservation Waterbury VT Shannon Hill of the River Management Section Christa Alexander of the Vermont Department of Fish and Wildlife and Kristen Underwood of South Mountain Research and Consulting Bristol VT were instrumental participants as technical advisors during the development of Version 1 Shannon also served as a technical advisor during the development of Version 2 April 2006 Introduction Page 3 Trademarks ESRI ArcView Spatial Analyst Arc Info and PC Arc Info are registered trademarks of Environmental Systems Research Institute Inc ESRI Avenue and Dialog Designer are trademarks of Environmental Systems Research Institute Inc Windows Window 98 Windows 2000 Windows Explorer Microsoft Excel and Microsoft Access are trademarks or registered trademarks of Microsoft Inc System Requirements The Stream Geomorphic Assessment Tools Tools were developed using the Avenue programming language available with ArcView The Tools are provided as an ArcView ex
337. ur Pt to be used Surface Waters with Tribld Assigned used for Feature Indexing Created via Setu eaa ene SOSSWFinaltrbldshp Theme containing only surface waters for which the i O Aa E Tributary Identifier Trbld has been assigned is available to perform Feature Indexing To be saved in H GeomorphologyVersion4 DenvdD ata Themes to be Created Modified through Indexing Feature PE Impacts FITOOPtImpact sho w Existing Theme FITOUPtmpact shp for Impacts Point Features will be replaced Poliline Impacts FIT OOLnimpact shp lt Existing Theme FITO0LAlmpact shp for Impacts Polyline Features will be replaced To be saved in H GeomorphologyVersion4 DenvdD ata Note for insertion into System Lo User Note Setup Indes Features To use this dialog e The theme containing surface waters created in Step 05 will be displayed e The theme containing the primary pour point for the watershed created in Step 02 will be displayed e The theme to be created or modified that contains the point impact features that have been indexed will be displayed e The theme to be created or modified that contains the polyline impact features that have been indexed will be displayed e Enter a note to be entered into the system log upon completion of setup processing Starting the Process After the user note has been entered click on the Setup button This will create the route table necessary for indexing features Reme
338. ustrates the Feature Types as defined by the attribute field named Swi for the older surface waters themes Two lakes are shown with a stream flowing through them The values used for the Sw are shown for each segment Network lines ar represented by the value N are M used to connect the inflow and outflow points on the lakes Only the linear stream features represented by the heavy lines blue S and black N should be used for analysis by the Jools extension The user will have to be familiar with the attribute data provided for the older surface waters The following table provides guidelines for extracting data from VCGI surface water coverages VCGIl Attribute Values for Field SWL Code Yes S Streams Note All of the codes may not be present in any given surface water coverage To perform the extraction use the area of the dialog labeled Linear Stream Feature Selection April 2006 Step 02 Extract and Clip the Surface Waters to Primary Watershed Page 87 1 If you are NOT using the 1 5000 VHD and you are using an older version of the surfacewater click on the check box labeled Extract Selected Linear Features Make sure that a check mark is in that box If one already exists clicking in the box removes the check mark and disables the related controls on the dialog Clicking again inserts a check mark and enables the controls 2 Inthe box labeled Feature Field select the fiel
339. utary Identifiers Interactively 96 Step 04b Assign Tributary Identifiers Interactively 101 Step 04x Assign Tributary Identifiers Manually 107 Step 04z Problems Associated with Incorrect Assignment of Tributary Identifiers __ 109 Part B Data Development for Sub Watersheds 111 Step 05 Clip Linear Surface Waters to Sub Watershed Boundaries 112 Step 06 Calculate Reach Points and Reach Point Data 115 Step 07 Calculate Valley Line and Data 125 Step 08 Calculate Channel Width and Stream Data 136 Step 09 Calculate Stream Corridors Buffers 140 Step 09 Using Alternative Stream Corridors Buffers 146 Step 10 Data Entry Review of Reach Point Data 149 Step 10 Calculating Derived Data 153 Step 10 Set Map Documentation Fields 155 Step 10 Export Reach Point Data to dBase Table 157 Part C Soils Land Cover and Density Analysis 159 Step 11 Clip Theme to Boundary 160 Step 12 Summarize and Attach Descriptive Data 163 Step 13 Sum Data to Upstream Watershed Area 170 Step 14 Summarize Area by Field Value Cross Tabulate 175 Step 15 Calculate Densities 183 Part D Reach Segmentation and Feature Indexing 190 Part D Reach Segmentation 191 STEP SEGOO Setup Surface Water Theme 192 STEP SEG01 Segment Reaches 195 April 2006 Page ii Part D Feature Indexing 199 STEP FlT00a Setup for Feature Indexing 201 STEP FITOOb Feature Indexing 206 STEP FIT00c Feature Data Modification Deletion 211 STEP FIT0O1 Feature Segmentation 214 STEP FITO2 Ext
340. vailable at that time Since the release of Version 1 it has been used in the Phase Geomorphic Assessment of several watersheds The experience gained from its use in those efforts has been reflected in the development of Version 2 Version 2 embodies the enhancement of certain functions provided under Phase and includes a number of additional capabilities Among the new capabilities are the following Inclusion of Inflow Points and upstream drainage area for watersheds Stream Corridor development in Accordance with Appendix E of the Phase Handbook Calculation of a Valley Line including length and average width Calculation of channel sinuosity valley confinement and channel and valley slopes Aggregation of data for upstream watershed areas for stream corridors and sub watersheds Coordinates for Reach Points Latitude Longitude and State Plane Ability for the user to provide documentation information on the watershed and reach points User data entry editing and review of Reach Point data Numerous other minor modifications to improve usability 9 A A ooo oo gt In order to implement these additions modifications it was necessary to reorganize the processing steps established in Version 1 Version 3 incorporated the following enhancements and or changes e Significant modification to the user interface that requires themes tables to be registered prior to their use This minimizes the chances of improper selection in a given step
341. ve the theme into your base data folder with a new name Go into SGAT theme registration and unregister your old surface water and register the theme you just created as your surface water Start SGAT over from Step 1 or 2 depending on whether you changed the exterior watershed boundary As shown in the figure below in Step 3 Combine Stream Segments between confluence points under Options select All Fields This will carry along your Trib ID s to the new SO3swcomb shp and you will not have to re assign them April 2006 Step 03 Combine Stream Segments between Confluence Points Page 93 input Theme s Surface Waters 02SWClipped shp Theme for Surface Waters for Watershed to be used Fields and Data to Transfer from Surface Water Theme to Output Theme Options Select Fields i Swid j O All Fields Hold Shift h Ej Tribid C No Fields AEE Surev Select Fields via List Box to Right E Surface Water Theme to be Created anane Existing Theme SO3S W Comb shp for SZW Combined between Jutput Theme 5035WComb shp zi confluence pts will be replaced To be saved in c projects 03 otter creek lewis little otterslemon fairssgat 20055DerivdD ata Note for insertion into System Log User Note Combine Done To use this dialog e The theme representing surface waters clipped to the overall watershed boundary produced in Step 02 will be displayed e Sele
342. ver the main stem or tributary for the geomorphic reach List should include commas separating individual orthophoto identification e g Hinesburg Starksboro etc o HUC 10 List of HUC 10 Watershed Identifiers within which the reach or a part of the reach falls o Notes Location for user to make comments about the reach data concerns problems etc User should document any changes made to reach point data e g Changed valley length to be 5279 instead of 5300 due to error in valley wall theme Maximum length of entry is 128 characters Editing Data Step 10 provides the user with the ability to enter or modify a limited set of data that is associated with a reach point Elevation Channel Width Valley Length Valley Width USGS Maps Orthophotos Towns and Notes or Comments Note Step 10 is the only place where elevation USGS Maps Orthophotos Towns and Notes can be assigned to reach points This data can be entered or edited at any point following Step 06 without concern for the data to be overwritten in another step To edit data select the reach point of interest in the list box labeled Reach ID Then place the cursor in the field to be changed and replace the value shown Continue until all of the changes required have been made All changes made remain as pending changes until the Save button is clicked As a result changes can be made to any number of reach points prior to clicking on the Save button Once the Save
343. vided by clicking on the button labeled Part D Stream Segmentatioin on the Main Dialog Clicking on that button will display the dialog displayed below Part D Reach Segmentation Main Dialog Data Development Functions for Fluvial Erosion Hazard Mappin WARNING Please follow instructons Features and data are modifed in each of the steps To ensure corect data always start with the first enabled step and proceed sequentially Do not re run steps SEGOO Setup Surface Water Theme View Log Done Clicking on the buttons for Steps SEGOO or SEGO7 will display the corresponding dialog box for that step Clicking on the button labeled Done will return you to the Main Dialog April 2006 Part D Reach Segmentation Page 191 STEP SEGOO Setup Surface Water Theme This step creates a surface water theme to be used for reach segmentation The source input theme is the surface water theme resulting from Part B Step 05 This processing step performs the following 1 2 3 Surface water segments that have a non blank value for the Tribld field are extracted from the source theme A temporary MergeField is created using the RchPtld appended to the Tribld A merge operation is performed that joins all surface water segments having the same MergeField value Attribute fields are created updated as follows e ChanlWidth Channel width for the reach as calculated in Part B Step 08 e NumParts Count of th
344. watersheds Step 12 would then be performed on each of the themes resulting from the above combinations Step 13 would be performed f soils and Land Cover Land Use data is to be analyzed for the entire catchment or drainage area above each reach point Then Step 14 would be performed on each of the tables resulting from Step 12 and or Step 13 Step 15 is independent of the other steps and permits one to obtain densities of features that are located within the sub watersheds or stream corridors The densities are calculated on a per Square mile basis e g number of point houses linear footage roads square miles wetlands per square mile Clicking on the Done button will return you to the Main dialog for the Tools extension April 2006 Part C Steps 11 15 Soils Land Cover amp Density Analysis Page 159 Step 11 Clip Theme to Boundary This dialog provides the ability to clip a data theme with a boundary theme The boundary theme is used like a cookie cutter Only those areas of the data theme that fall entirely within or cross the area s represented by the boundary theme will be placed in the output theme Those areas from the data theme that fall outside the boundary theme are clipped off at the boundaries The data themes of particular interest are soils and land cover land use The boundary themes are the stream corridors from Step 09 and the sub watersheds provided by the user Examples of the resultin
345. within ArcView are made to the structure of the table outside of ArcView it may not be useable within ArcView This in turn could result in corruption of the ArcView project which could render it unusable The following figure illustrates a portion of the table produced Numerous fields to the right are omitted Of particular note is that for each Reach Point field RchPtld which is equivalent to a sub watershed or stream corridor only one record is found for each soil mapping unit field MuSym_cor Muid_c This is the result of the summation performed in this step where the areas are summed for the same soil mapping unit within a stream corridor or sub watershed 2 12soilschwdthx dbf lolx WATER LESS THAN 40 ACRES PAARA RAAAAARARO NARAR ARENA ARRARO RRARRARE ARAA RAR ARM KARENA ARNARONARARAREARAAKARSRAPAR ARERR AANARARARARAR ANA AA RAN ANAKARA PRR AKAANANANARAR ANR AA ARANAN ARARNAR encnsresetentiene sstntvectearcreetsscseeeettartsencte cue csttuteccss isttcestertcensterceeertatersstisrectstraresss sieves ARNAN KAN AARNAR ARNAR AARAA AARNARAR NARAR KARARAN ARARNAR AARARAARNARA NNRARKKRARRNARARNARARRARH i RUMNEY FINE SANDY LOAM suaeeaseaeegeasnsneaeay Qheacceuesuseusesauseuaesauaehanseuseuaeesuseaserenseggers Mrnnrnnnnnnnnnnnnnnnnnnnnnnn ANNNNANANNNNNNNNNNANAANANNNNNNNA ANANANANNNNNNNANAAANNAANNNNNTNNNNANANAANANNNNANINAAAAAANNNANAANINAAAAAANNAAANAAINANAAAAANAAAAAAENAAAAANANAAAAANENAAAAANNNAAAAAAENAAAAAANNHAAAANAN
346. xample of a name would be S77LC shp for LcLu within the stream corridors The area units are displayed on this dialog however they cannot be changed April 2006 Step 11 Clip Theme to Boundary Page 160 Part C Step 11 Clip Data Themes to Selected Boundaries Data Theme to be Clipped FIRST Select Type of Data Theme heme Name s00soils shp v Soils C Lelu Theme for Soils to be used Boundary Theme Defining Areas to which Data Theme will be Clipped FIRST Select Area for Boundary Them Theme Name s00subwshed shp Sub Watershed Source Corridors Step 09 Theme for Sub Watersheds to be used Units in which Area will be calculated rea Units sq Mies Theme to be Created Output Theme S11SW shp Theme will be created upon completion of this Step To be saved in h geomorphology wersion3 D eriydD ata Note for insertion into System Log User Note co Starting the process After the required information has been entered on the dialog click on the button labeled Clip Processing may take a few moments depending upon the hardware used After one clicks on the Clip button the following message will be displayed This provides the user with a bail out in the event that the button was inadvertently clicked To continue with the clipping operation click on the Yes button 1025 soils_clip shp Soils will be clipped using S
347. y Regional Planning Commission Adam Lougee Executive Director Contracting for Versions 2 and 3 was provided by the Lamoille County Regional Planning Commission Michele Boomhower Executive Director Contracting for Versions 4 and 4 5 was provided by the Department of Fish amp Wildlife VT Agency of Natural Resources Vermont Center for Geographic Information David Brotzman Executive Director Agency of Natural Resources Technical Advisory Group included Mike Kline Shannon Hill Staci Pomeroy Ty Mack Department of Environmental Conservation Christa Alexander Department of Fish and Wildlife Request for technical assistance training questions and comments should be directed to Shannon Hill 802 747 5066 shannon hill state vt us River Management Section DEC Water Quality Division 103 South Main St Building 10 North Waterbury Vermont 05671 0408 Information on the Stream Geomorphic Assessment process may be obtained from the River Management Section Geomorphic Assessment internet web page at www vtwaterquality org Table of Contents Appendices Introduction Overview History Credits Trademarks System Requirements Restrictions Geographic Limitation Soils Data Requirements ArcView Skills Feedback Format of Material Distributed Format of This Document Contents of Distribution CD General Concepts Setting Up for Using the Tools Installation of the Tools ArcView Extension To unload the Tools extensio
348. y the Channel Length Result is expressed as a percentage e Valley Slope f the reach point and its upstream neighboring reach point have been assigned elevations and the Valley Length is available the Valley Slope will be calculated Valley Slope is the difference in elevation at the upstream end of the valley Upstream Reach Pt and the downstream end of the valley at the reach point divided by the Valley Length Result is expressed as a percentage e Sinuosity f both Valley Length and Channel Length are present Channel Sinuosity will be calculated by dividing the Channel Length by Valley Length e Confinement lf both Valley Width and Channel Width present Valley Confinement will be calculated by dividing the Valley Width by the Channel Width If the value of any required data element is zero the related calculations are not performed This allows one to enter data as it is collected April 2006 Step 10 Data Entry Review of Reach Point Data Page 153 Clicking on the Calc Data button is recommend to insure that all derived data is calculated with the most current values Repeatedly clicking on the button will not adversely affect data e g the derived data slopes sinuosity and confinement will simply be re calculated each time the user clicks on the calculation button When one clicks on the Calc Data button the message shown below will be displayed SGAT Y N 1001 GeoSW Revu lbtCalc Click 1001 Field s ChanlSlop

Download Pdf Manuals

Related Search

Related Contents

Steelseries 3H USB  Guidance for the Labelling of Medical Devices under Section 21 to  FLIP取扱説明書  Manual de usuario - buronacionaldeempleados.com  FORCE-A DUALEX SCIENTIFIC+ polyphenol & chlorophyll  Mode d`emploi pour télécharger sa carte déchetterie  C H 140G S M - Fantini & Cosmi    Stearns YUKATAT B523 User's Manual  M5504 manual de usuario  

Copyright © All rights reserved. Failed to retrieve file