20201123 11485200 1.0 FGDC CSDGM Metadata FALSE River_Segments 202047.778700 736622.739200 4470530.164800 4822761.295800 1 002 0.000 Projected GCS_North_American_1983 Linear Unit: Meter (1.000000) NAD_1983_UTM_Zone_15N <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS[&quot;NAD_1983_UTM_Zone_15N&quot;,GEOGCS[&quot;GCS_North_American_1983&quot;,DATUM[&quot;D_North_American_1983&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433]],PROJECTION[&quot;Transverse_Mercator&quot;],PARAMETER[&quot;False_Easting&quot;,500000.0],PARAMETER[&quot;False_Northing&quot;,0.0],PARAMETER[&quot;Central_Meridian&quot;,-93.0],PARAMETER[&quot;Scale_Factor&quot;,0.9996],PARAMETER[&quot;Latitude_Of_Origin&quot;,0.0],UNIT[&quot;Meter&quot;,1.0],AUTHORITY[&quot;EPSG&quot;,26915]],VERTCS[&quot;NAVD_1988&quot;,VDATUM[&quot;North_American_Vertical_Datum_1988&quot;],PARAMETER[&quot;Vertical_Shift&quot;,0.0],PARAMETER[&quot;Direction&quot;,1.0],UNIT[&quot;Meter&quot;,1.0],AUTHORITY[&quot;EPSG&quot;,5703]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>-9998100</YOrigin><XYScale>450445547.3910538</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>26915</WKID><LatestWKID>26915</LatestWKID><VCSWKID>5703</VCSWKID><LatestVCSWKID>5703</LatestVCSWKID></ProjectedCoordinateSystem> 20220509 11130500 20220509 11130500 NAP 150000000 5000 River_Segments Table containing attribute information associated with the data set. Producer defined Feature Class 0 FID FID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Name Name of Stream FEMA, USGS Name of the Stream or River. Name String 150 0 0 Shape Feature geometry. Esri Coordinates defining the features. Shape Geometry 0 0 0 NHDCODE NHDCODE Double 19 0 0 NHD Code. USGS Stream_Typ Stream_Typ String 5 0 0 NHDDesc NHDDesc String 254 0 0 NHD Description USGS Slope Slope Single 13 0 0 Stream Slope Producer Strm_order Strm_order Integer 5 5 0 Stream Order Producer Sinuosity Sinuosity Single 13 0 0 Stream Sinuosity Producer OBJECTID Internal feature number. Esri Sequential unique whole numbers that are automatically generated. OBJECTID Integer 10 10 0 Shape_Leng Shape_Leng Double 19 0 0 Segment Segment String 100 0 0 Length_MI Length_MI Single 13 0 0 SEG_NO SEG_NO Integer 5 5 0 As other checking was being completed, the linework was also split at various key locations to determine the character of the streamline. Classifications were given to the streamlines as they were split. These classifications were developed in line with the NHDs FTYPE field and were: 1. Stream or River – regular stream or river segment. 2. Culvert or under bridge - road culvert or bridge (manmade structure) on DEM. 3. Artificial Path - ponds or reservoirs, also connects SSC to WSC. (see below) 4. Connector - connection from artificial path to stream, use for earth dam. 5. Municipality Supplied Pipeline Infrastructure - municipality supplied info. (see below) 6. Drainage Extension - drawn to correct flow. (see below) 7. DFIRM Extension – when inundation on effective FIRM but not in the initial linework. (see below) 8. NULL Value – Used to connect stream segments where definition was temporarily lost. (see below) Artificial Path (continued) - In addition to its “normal” usage (routing flow through ponds/reservoirs and connecting SSC to WSC), it could be said that is has a third area of usage (though it’s basically just a subtle variation of usage for waterbodies)used in wetland areas where there is no significant channel definition or an obvious “waterbody” (with visible standing water), however, there appears to be some presence of wetland vegetation, so flow through the area is attributed as artificial path (it’s just a little bit drier-type of artificial path). The basic standard followed for differences in these stream segments attribution were: 1.Really wet, standing water = artificial path. 2.Somewhatf wet, with unique signs like subtle depressions, moisture-loving vegetation = artificial path. 3.Not wet at all (or maybe just a tiny bit damp) and not much of any definition in DEM = NULL value. Municipality Supplied Pipeline Infrastructure (continued) - A clear flow path on LiDAR was often lacking in larger, older metropolitan areas in the state as well due to storm sewer projects. In the case of larger older municipalities, an effort was made to obtain any data the municipality might have showing the course of storm sewers. While not used for flood plain mapping, this information was used to connect the network when it was interrupted by development to ensure flow accumulations and the flow path followed were as accurate as possible. In some cases the storm sewer network was evident through photography so the city was not contacted. Areas of new development could be captured by referencing aerial photography from predevelopment years. Cities supplying data for this effort were: Burlington, Cedar Rapids, Coralville, Davenport, Des Moines, Dubuque, Iowa City, Johnston, Keokuk, Muscatine, Sioux City, Waterloo. As this was a project to supply streamline data for flood plain mapping, consideration was taken in capturing areas where effective flood determinations existed regardless of whether or not the area met the criteria of 1sq mile flow accumulation (FEMA spec) or a flow path shown on the LiDAR-derived DEM. Drainage Extension (continued) - Drawn in to correct flow. Always added to upstream end of stream segments. Directs flow that is significantly misrouted due to large road embankment (or other obstruction), where there was not already a proper stream/culvert line drawn through culvert in road embankment (criteria for digitizing a proper stream was not fulfilled). DFIRM Extensions (continued) - were incorporated into the linework to capture these instances in order to ensure consideration of existing effective Special Flood Hazard Areas (SFHA). These may not represent a stream, in these cases they most likely were areas that experienced a flooding event in the past and were requested to be included on a Flood Insurance Rate Map (FIRM) for risk awareness by community officials. NULL Value (continued) - Disappearing streams, or the lack of a clear flow path in the LiDAR surface, caused problems in creating a stream network as there was nothing to guide streamline collection. In order to connect the network and ensure flow a segment with NULL value was added. As best as possible, these approximated where overland flow occurred using various years of aerial photography to show where water went during high and low water events. The entity and attribute information was generated by the individual and/or agency identified as the originator of the data set. Please review the rest of the metadata record for additional details and information. dataset Iowa DNR NRGIS Librarian 319-335-1353 309B Trowbridge Hall Iowa City IA IA casey.kohrt@dnr.iowa.gov 2018-05-09 ArcGIS Metadata 1.0 Iowa Department of Natural Resources 319-335-1353 502 East 9th St. Des Moines IA 50309 casey.kohrt@dnr.iowa.gov Vector Digital Data Set (Polyline) zip ArcGIS 10x Shapefile 0.000 Stream Centerlines of the State of Iowa 2016-01-06T00:00:00 Iowa Department of Natural Resources Iowa Flood Center Small stream centerlines were developed for a dual purpose. The first was to be used to create hydrography for the Iowa DNR's statewide floodplain mapping project in accordance with the Rebuild Iowa Advisory Commission’s 120-Day report to the Governor in November of 2008. The second was to be used to conflate data from the National Hydrography Dataset (NHD) to a more accurate resolution stream network in order to be consistent with the already existing NHD framework. For this reason streams start at 24 acres of flow accumulation where there is a visible channel in the surface of a Digital Elevation Model (DEM) based on the State of Iowa’s LiDAR collection. This linework was the basis for creating hydrologically corrected DEMs that were used to determine the one square mile starting point for modeling flood plains, per FEMA standards and specifications. The linework has been collected using the State of Iowa’s Statewide LiDAR product as the main determination for flow as this surface was used when carrying out Iowa’s Statewide Flood Plain Mapping Project. In cases where LiDAR was insufficient for capture, aerial photography from various years for the State of Iowa was referenced. The NRCSs Eight-Digit Hydrologic Unit boundaries (HUC8) is the Federal Emergency Management Agencies (FEMA) specified unit of study for flood plain mapping designations. Rather than studying by county, FEMA realized that more accurate products resulted from considering an entire HUC8 and gave a more complete look at what contributed/minimized flood damage. Therefore all data was initially compiled into HUC8s, then further compiled into this statewide dataset. This digital, geographically referenced data set was developed by the Iowa Department of Natural Resources to carry out agency responsibilities related to management, protection, and development of Iowa's natural resources. Chris Kahle Iowa Department of Natural Resources 319-335-2068 ckahle@dnr.iowa.gov GNIS 2015-01-31 https://ofmpub.epa.gov/sor_internet/registry/termreg/searchandretrieve/taxonomies/search.do?search=&searchString=&taxonomyName=WBT%20-%20Geographic%20Locations Web Taxonomy - Geographic Locations Iowa Unrestricted License Unrestricted License https://creativecommons.org/publicdomain/zero/1.0/ There are no Use Limitations for this dataset Version 6.2 (Build 9200) ; Esri ArcGIS 10.9.1.28388 true -96.68527 -90.072193 40.332153 43.557807 0.000000 0.000000 ground condition 2007-01-01T00:00:00 2015-01-01T00:00:00 0.000000 0.000000 Iowa Department of Natural Resources 319-335-1353 502 East 9th St. Des Moines IA 50309 casey.kohrt@dnr.iowa.gov [From Metadata Record] Iowa Department of Natural Resources Iowa DNR NRGIS Librarian 319-335-1353 309B Trowbridge Hall Iowa City IA IA casey.kohrt@dnr.iowa.gov [From Metadata Record] Iowa DNR Iowa DNR NRGIS Librarian 319-335-1353 309B Trowbridge Hall Iowa City IA IA casey.kohrt@dnr.iowa.gov [From Metadata Record] Iowa DNR Geospatial Administrator Iowa DNR 309 Trowbridge Hall Iowa City Iowa 52242 casey.kohrt@dnr.iowa.gov 1 -96.685270 -90.072193 43.557807 40.332153 0.000000 0.000000 Last metadata review date: 20160104 There are no access constraints. There are no use constraints. Data set is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details. As reported in the process steps. Next was to determine when WSC began. WSC were collected by NRCS Eight-Digit Hydrologic Unit boundaries (HUC8) and are defined for this project as consistently shown as 7m wide or greater on the LiDAR (does not go between 7m and narrower). When a watercourse became 7m or wider it was treated differently and small stream digitization was not collected for these reaches. WSC were captured using an entirely different process. Initially capture was done by hand. A methodology was developed where slopes (from LiDAR) were used to determine areas where the percent slope was 20 or greater, these areas were extracted. ESRIs Raster to line was performed on the extracted areas to get rough top of bank (TOB) and edge of water (EOW) lines. These lines were then hand edited to detail the TOB and EOW for a stream for usage in floodplain modeling data capture. The EOW lines were also used to generate Wide Stream centerlines by running ESRIs collapse dual lines to centerline tool. The Centerlines were smoothed and edited to make it more visually aesthetic. As other checking was being completed, the linework was also split at various key locations to determine the character of the streamline. Classifications were given to the streamlines as they were split. These classifications were developed in line with the NHDs FTYPE field and were: 1. Stream or River – regular stream or river segment. 2. Culvert or under bridge - road culvert or bridge (manmade structure) on DEM. 3. Artificial Path - ponds or reservoirs, also connects SSC to WSC. (see below) 4. Connector - connection from artificial path to stream, use for earth dam. 5. Municipality Supplied Pipeline Infrastructure - municipality supplied info. (see below) 6. Drainage Extension - drawn to correct flow. (see below) 7. DFIRM Extension – when inundation on effective FIRM but not in the initial linework. (see below) 8. NULL Value – Used to connect stream segments where definition was temporarily lost. (see below) Artificial Path (continued) - In addition to its “normal” usage (routing flow through ponds/reservoirs and connecting SSC to WSC), it could be said that is has a third area of usage (though it’s basically just a subtle variation of usage for waterbodies)used in wetland areas where there is no significant channel definition or an obvious “waterbody” (with visible standing water), however, there appears to be some presence of wetland vegetation, so flow through the area is attributed as artificial path (it’s just a little bit drier-type of artificial path). The basic standard followed for differences in these stream segments attribution were: 1.Really wet, standing water = artificial path. 2.Somewhatf wet, with unique signs like subtle depressions, moisture-loving vegetation = artificial path. 3.Not wet at all (or maybe just a tiny bit damp) and not much of any definition in DEM = NULL value. Municipality Supplied Pipeline Infrastructure (continued) - A clear flow path on LiDAR was often lacking in larger, older metropolitan areas in the state as well due to storm sewer projects. In the case of larger older municipalities, an effort was made to obtain any data the municipality might have showing the course of storm sewers. While not used for flood plain mapping, this information was used to connect the network when it was interrupted by development to ensure flow accumulations and the flow path followed were as accurate as possible. In some cases the storm sewer network was evident through photography so the city was not contacted. Areas of new development could be captured by referencing aerial photography from predevelopment years. Cities supplying data for this effort were: Burlington, Cedar Rapids, Coralville, Davenport, Des Moines, Dubuque, Iowa City, Johnston, Keokuk, Muscatine, Sioux City, Waterloo. As this was a project to supply streamline data for flood plain mapping, consideration was taken in capturing areas where effective flood determinations existed regardless of whether or not the area met the criteria of 1sq mile flow accumulation (FEMA spec) or a flow path shown on the LiDAR-derived DEM. Drainage Extension (continued) - Drawn in to correct flow. Always added to upstream end of stream segments. Directs flow that is significantly misrouted due to large road embankment (or other obstruction), where there was not already a proper stream/culvert line drawn through culvert in road embankment (criteria for digitizing a proper stream was not fulfilled). DFIRM Extensions (continued) - were incorporated into the linework to capture these instances in order to ensure consideration of existing effective Special Flood Hazard Areas (SFHA). These may not represent a stream, in these cases they most likely were areas that experienced a flooding event in the past and were requested to be included on a Flood Insurance Rate Map (FIRM) for risk awareness by community officials. NULL Value (continued) - Disappearing streams, or the lack of a clear flow path in the LiDAR surface, caused problems in creating a stream network as there was nothing to guide streamline collection. In order to connect the network and ensure flow a segment with NULL value was added. As best as possible, these approximated where overland flow occurred using various years of aerial photography to show where water went during high and low water events. Names were attributed to the streamline network using Modeled Stream Centerlines from the modeling effort for Statewide Floodplains. These models required naming for logical storage and directory structure for each HUC8 and were typically only for segments of streams draining more than 1sqmi. Names were also used for development of Flood Insurance Rate Map (FIRM) datasets. Only streams with a proper name (not reach codes or unnamed streams) had their attribution transferred to the 24acre linework. A hierarchy for the datasets referenced was followed to determine a stream name. In order of weight, these were: Effective FIRM, NHD Name, USGS TopoBureau of Geographic Names. The effective FIRMs had priority due to this project being related to floodplain mapping, names should match between versions of FIRMs for a county. In most cases sources agreed; however, there were times when the names disagreed or were incorrect in one source or another. When sources disagreed, the name that was shared by most sources was used. The Mississippi and Missouri river segments were not modeled; therefore, there was no effort in the modeling preparation process to collect centerlines. Centerlines for these were added to the overall dataset by heads up digitizing using the NHD as a guide to create connectivity. Attribution is identical to the STREAM_TYPE values for these rivers to offer consistency. The named (modeled stream centerlines) data was spatially joined to the 24 acre streamline network by HUC8. Segments that did not spatially join were added and attributed to make sure of connectivity. Also, since the named streams were only typically to the extent of 1sq mile of drainage, the NAME attribute needed to be added to the upstream segments of the network where named streams existed. The hydrological streamline network was created using the State of Iowa’s Statewide LiDAR product as the main determination for flow as this surface was used when carrying out Iowa’s Statewide Flood Plain Mapping Project. In cases where LiDAR was insufficient for capture, aerial photography from various years for the State of Iowa was referenced. In order to create the 24 acre linework, two classifications of streams were distinguished: Small Stream Centerlines (SCC) and Wide Stream Centerlines (WSC). Depending on this distinction, collection was performed in different ways detailed below. Next, the WSC and SCC were combined to create a HUC8 wide stream network. After determining the SSC start points and stop points, collection could begin. Work was performed to collect stream networks by NRCS Twelve-Digit Hydrologic Unit boundaries (HUC 12) area designations in order to more easily process and collect data. Initially streams were hand digitized, while we worked on developing an automated process to get linework from the LiDAR DEMs, as manual digitization was tedious. Ultimately, a code (Gelder Code) was used to get initial linework for creating a HUC12 wide stream network. Water surfaces can be very TIN-y, and this method looked for pits and connected low points when obstacles in the water surface occurred. Run against the LiDAR, this code used NHD linework to determine initial flow networks by filling in pits and punching in holes where needed on the DEM to make flow happen. The output from this was then smoothed to remove some of the roughness of the resulting linework. Editing was also performed when the code output was incorrect and strayed from the streambed in order to assure the linework was accurate. There were cases where the conditions were met for a defined stream (24 acre FAC, scar on DEM) that were not captured by the code as it was dependent on the NHD linework which might not have features for the area. In these cases, hand digitization was performed. Editing for both WSC and SCC was performed in the same way after initial collection of each. Linework was checked to make sure the lines were drawn in a downstream direction and linework around confluences were logical in flow (lines didn’t meet perpendicular or going upstream) as this interfered with ArcHydro when processing the final product later for flood plain mapping needs. After editing, splitting and attributing SSC and WSC the data was thoroughly reviewed for QAQC in order to assure the accuracy of the product. The individual HUC12 networks and WSCs then needed to be joined together in order to create a HUC8-wide stream network. WSC were first split into individual HUC8 designation areas. Then joining began by connecting all HUC12s that did not have WSC to consider. Where WSC existed in a HUC12 or throughout a HUC8, connections were made by adding a segment to the terminus of a HUC12 or any stream entering a Wide Stream area; this was attributed as an artificial path as per NHD standards. Connections were made with the same criteria used above for confluences assuring the lines were drawn in a downstream direction and linework around confluences were logical in flow (lines didn’t meet perpendicular or going upstream). Source information used in support of the development of the data set. 2010 Two Foot Pixel, Color Infrared Orthophotography Mosaic of Iowa Source Input 26 2010-09-10T00:00:00 Iowa Department of Natural Resources Source information used in support of the development of the data set. 2013 National Agriculture Imagery Program (NAIP) Ortho Imagery of Iowa Source Input 30 2013-09-12T00:00:00 USDA-FSA Aerial Photography Field Office Source information used in support of the development of the data set. 1960's Digital Orthorectified Image of Iowa, in MrSid Format Source Input 15 2012-01-01T00:00:00 Iowa Department of Natural Resources Source information used in support of the development of the data set. State and County boundaries of the state of Iowa Source Input 1 1990-11-01T00:00:00 James D. Giglierano and Madhukar Mohan Source information used in support of the development of the data set. 2010 National Agriculture Imagry Program (NAIP) Aerial Photography of Iowa Source Input 28 2010-09-29T00:00:00 USDA-FSA Aerial Photography Field Office Source information used in support of the development of the data set. Statewide Top of Bank/Edge of Water dataset, derived from 1m LiDAR Source Input 9 Iowa Department of Natural Resources Source information used in support of the development of the data set. 2005 National Agriculture Imagery Program (NAIP) Aerial Photography of Iowa in MrSid Format Source Input 21 2005-09-11T00:00:00 USDA-FSA Aerial Photography Field Office Source information used in support of the development of the data set. Digital 1-meter Color-Infrared County Orthophoto Mosaics of Iowa in MrSID format Source Input 19 Iowa 2002 Digital Orthophoto Update Project Source information used in support of the development of the data set. Incorporated Citiy Boundaries in Iowa in 2010, as Derived from the Census Places Dataset Source Input 6 2010-01-01T00:00:00 U.S. Department of Commerce, U.S. Census Bureau, Geography Division Source information used in support of the development of the data set. National Hydrography Dataset, Flowlines with Hydrologic Significance in Iowa Source Input 8 U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency, USDA Forest Service, and other Federal, State and local partners (see dataset specific metadata under Data_Set_Credit for details) Source information used in support of the development of the data set. Conservation and Recreation Lands with Public Access in the State of Iowa Source Input 5 2006-04-20T00:00:00 Iowa Geological Survey of the Iowa Department of Natural Resources Source information used in support of the development of the data set. 2008 National Agriculture Imagery Program (NAIP) Aerial Photography Mosaic of Iowa Source Input 24 2008-10-21T00:00:00 USDA-FSA Aerial Photography Field Office Source information used in support of the development of the data set. 1980's Digital Orthorectified Image of Iowa, in MrSid Format Source Input 17 2011-01-01T00:00:00 Iowa Department of Natural Resources Source information used in support of the development of the data set. 1930's Digital Orthorectified Image of Iowa, in MrSid Format Source Input 13 2006-01-01T00:00:00 Iowa Department of Natural Resources Source information used in support of the development of the data set. 2007 National Agriculture Imagery Program (NAIP) Aerial Photography Mosaic of Iowa Source Input 23 2007-10-03T00:00:00 USDA-FSA Aerial Photography Field Office Source information used in support of the development of the data set. Effective Flood Insurance Rate Maps (FIRMs) Source Input 12 Federal Emergency Management Agency Source information used in support of the development of the data set. 1970's Digital Orthorectified Image of Iowa, in MrSid Format Source Input 16 2012-01-01T00:00:00 Iowa Department of Natural Resources Source information used in support of the development of the data set. 2006 National Agriculture Imagery Program (NAIP) Aerial Photography of Iowa Source Input 22 2006-11-06T00:00:00 USDA-FSA Aerial Photography Field Office Source information used in support of the development of the data set. Watershed Boundary Dataset, Eight-Digit Hydrologic Units (Sub-Basins) of Iowa Source Input 2 2008-01-01T00:00:00 NRCS-Iowa, Des Moines, Iowa and EPA Region 5, Chicago, Illinois. Source information used in support of the development of the data set. 2009 National Agriculture Imagery Program (NAIP) Aerial Photography Mosaic of Iowa Source Input 25 2009-10-30T00:00:00 USDA-FSA Aerial Photography Field Office Source information used in support of the development of the data set. The Iowa LiDAR Project - Block Data Consisting of One Meter Digital Elevation Models (DEM) and Hillshades of the Bare Earth, First Return, and Last Return and an Intestity Rasters Derived from LiDAR LAS Files Source Input 7 Iowa Department of Natural Resources Source information used in support of the development of the data set. 2010 Two Foot Pixel, Color Orthophotography Mosaic of Iowa Source Input 27 2010-09-10T00:00:00 Iowa Department of Natural Resources Source information used in support of the development of the data set. 1950's Digital Orthorectified Image of Iowa, in MrSid Format Source Input 14 2009-01-01T00:00:00 Iowa Department of Natural Resources Source information used in support of the development of the data set. 2011 National Agriculture Imagery Program (NAIP)Four-Band Aerial Photography of Iowa Source Input 29 2011-08-18T00:00:00 USDA-FSA Aerial Photography Field Office Source information used in support of the development of the data set. Gelder Code used to derive raw linework for editing and attribution Source Input 11 Brian Gelder Source information used in support of the development of the data set. 1990's Digital Orthorectified Image of Iowa, in MrSid Format Source Input 18 2006-01-01T00:00:00 Iowa Department of Natural Resources Source information used in support of the development of the data set. Digital Raster Graphic Mosaic of Iowa Source Input 10 2002-01-01T00:00:00 U.S. Department of Agriculture, Natural Resources Conservation Service Source information used in support of the development of the data set. Watershed Boundary Dataset, Twelve-Digit Hydrologic Units (Sub-Watersheds) with Hydrologic Relevance in Iowa Source Input 3 2008-01-01T00:00:00 NRCS-Iowa, Des Moines, Iowa and EPA Region 5, Chicago, Illinois. Source information used in support of the development of the data set. National Wetland Inventory of Iowa Source Input 4 2009-06-03T00:00:00 Iowa Department of Natural Resources, US Fish and Wildlife Service Source information used in support of the development of the data set. 2004 National Agriculture Imagery Program (NAIP) Aerial Photography of Iowa in MrSid Format Source Input 20 2004-10-25T00:00:00 USDA-FSA Aerial Photography Field Office Method to create stream order from stream centerline data: Must have only the centerline and not any braids or splitting around islands. All confluences must be snapped and have a node at the confluence. Create an integer field called “Dissolve” and populate it with the value “1”. Perform the following steps until you have reached the outlet of the watershed. 1. Perform “Unsplit Line” on the centerline coverage using the Dissolve field to dissolve on to create “Dissolve_1”. 2. Perform “Feature Vertices To Points” using the Dissolve_1 coverage as input and Dangle as the point type to create “Dangle_1”. 3. Perform “Select by Location” on “Dissolve_1” that Intersect with “Dangle_1”. Then unselect the segment that is the outlet for the watershed and export the remaining selected features as “Order_1”. 4. Switch selection on “Dissolve_1” and export the selected segments as “Dissolve_1b”. 5. Perform “Unsplit Line” on “Dissolve_1b” using Dissolve field to dissolve on to create “Dissolve_2”. 6. Repeat process starting at Step 2. Calvin Wolter, Iowa DNR, March 28, 2016 2016-03-28T00:00:00 Process to calculate stream sinuosity Separate stream segments by Stream Order and MLRA. Within each MLRA and Stream Order group, survey subset of segments to determine mean channel width and standard deviation. For streams with Top of Bank coverage convert the vertices to points, run a Distance command on the stream segments and transfer the distance value to the points. Use the mean value of those points plus one standard deviation to calculate 30 times the channel width to determine length of stream segment needed for performing stream sinuosity calculation. For each MLRA and Stream Order subset split segments into the appropriate length as determined previously. Perform Feature Vertices to Point command on stream lines using the Both ends option to create point coverage. Use Add XY Coordinates command to point coverage to add X and Y coordinates fields with values. Perform Spatial Join between stream coverage and point coverage selecting points that intersect streams and summarized using minimum and maximum values for attributes to create new line coverage. Add a straight distance field to new line coverage and calculate using following equation: Sqr((([Min_Point_X] – [Max_Point_X])*([Min_Point_X] – [Max_Point_X])) + (([Min_Point_Y] – [Max_Point_Y]) * ([Min_Point_Y] – [Max_Point_Y]))) Create Sinuosity field and calculate using Length/Straight Length Calvin Wolter, Iowa DNR March 30, 2016 2016-03-30T00:00:00 0 EPSG 6.11(3.0.1) Simple FALSE 0 FALSE TRUE 25CCD6E7-4B4B-4DF2-882A-4BC8BB478AAF