This documentation file was generated on 2019-05-01 by Myrica McCune ------------------- # GENERAL INFORMATION ------------------- 1. Title of Dataset Willamette River Floodplain 100 Meter Slices Framework Geospatial Data 2. Creator Information Name: Hulse, David Institution: University of Oregon College, School or Department: Institute for a Sustainable Environment Address: 5247 University of Oregon, Eugene, OR 97403-5247 Role: PI Name: Enright, Chris Institution: University of Oregon College, School or Department: Institute for a Sustainable Environment Address: 5247 University of Oregon, Eugene, OR 97403-5247 Email: cenright@uoregon.edu Role: Research Associate Name: Branscomb, Allan Institution: University of Oregon College, School or Department: Institute for a Sustainable Environment Address: 5247 University of Oregon, Eugene, OR 97403-5247 Email: allanb@uoregon.edu Role: Research Assistant 3. Contact Information Name: Enright, Chris Institution: University of Oregon College, School or Department: Institute for a Sustainable Environment Address: 5247 University of Oregon, Eugene, OR 97403-5247 Email: cenright@uoregon.edu Role: Research Associate ------------------- CONTEXTUAL INFORMATION ------------------- 1. Abstract for the dataset The Slices Framework is intended for use in making decisions about conservation and restoration in the Willamette River floodplain. It makes use of distinct spatial units for tracking change in the floodplain. The first of these units are 1 kilometer long slices drawn at right angles to the floodplain, first put forward in the Willamette River Basin Planning Atlas (Ch. 8 pp. 131-147 in Hulse, Gregory and Baker 2002). The second of these units are 100m subdivisions of the original 1 km slices, with ten 100m slices in each 1 km slice. Together, they cover the entire pragmatic floodplain of the Willamette River. We define the pragmatic floodplain as the zone subject to periodic flooding that is bounded by significant infrastructure (e.g. highways, residential areas, etc.) This geospatial dataset contains the slice spatial and attribute data reporting amounts of key processes and patterns by slice and how they vary over time. 2. Context of the research project that this dataset was collected for. This framework is intended to support the assessment, planning, and monitoring of conservation and restoration activities within the Willamette River floodplain. These activities may include reconnecting historical channels that have been blocked and allowing the river to flood certain locations from which it is now normally excluded. Since restoration activities that would require disruption of significant constructed assets, roads, residential and commercial areas, and others, are infeasible, the spatial extent of this framework is narrower, primarily in the section between Eugene and Albany, than the historical floodplain. We provide access to four types of information, each of which uses the slices as a reporting unit for processes and patterns that are critical to native ecosystem function. These four types of information are: 1) a series of 20 pdf maps showing slice boundaries and slice numbers superimposed on contemporary air photographs; 2) an Excel spreadsheet that reports amounts of key processes and patterns by slice and how they vary over time; 3) a digital map in both ArcGIS geodatabase and shapefile formats. 4] this metadata as a pdf. Using the slices framework consists of finding the portion of the floodplain (i.e. north, middle, or south) in which you are interested, and opening the relevant pdfs, spreadsheet or ArcGIS file that best suits your purposes. The pdfs are a series of 20 layered maps, each combining an air photo with taxlot boundaries, major road names and 1 km and 100 m slice boundaries and numbers and thematic map layers. Together, they cover the entire pragmatic floodplain of the Willamette River. 3. Date of data collection: 2017-06-01 4. Geographic location of data collection: Bounding Box: Latitude North: 45.618656 Latitude South: 44.014635 Longitude West: -123.303439 Longitude East: -122.581036 Hydrologic Unit Code: 1709 5. Funding sources that supported the collection of the data: Project funded by the Meyer Memorial Trust and the Oregon Watershed Enhancement Board -------------------------- SHARING/ACCESS INFORMATION -------------------------- 1. Licenses/restrictions placed on the data: This work is licensed under a CC BY-NC license (Attribution-NonCommercial) 2. Links to publications related to the dataset: D. Hulse, S. Gregory. 2004. Integrating resilience into floodplain restoration. Journal of Urban Ecology. Special Issue on Large-Scale Ecosystem Studies: Emerging trends in urban and regional ecology, vol. 7, pp. 295-314. https://oe.oregonexplorer.info/externalcontent/willamette_slices/fldpln_rstr2004.pdf D. Hulse, S. Gregory, J. Baker. (Eds). 2002. Willamette River Basin Planning Atlas: Trajectories of environmental and ecological change. (2nd edition), Oregon State University Press, Corvallis, Oregon 97333. p. 180. The Atlas is freely available online as PDF documents. http://www.fsl.orst.edu/pnwerc/wrb/Atlas_web_compressed/PDFtoc.html 3. Links to other publicly accessible locations of the data: https://oregonexplorer.info/slices 4. Recommended citation for the data: Hulse, D., Enright, C., & Branscomb, A. (2019). Willamette River Floodplain 100 Meter Slices Framework Geospatial Data (Version 1) [Data set]. University of Oregon. Institute for a Sustainable Environment. https://doi.org/10.7267/5712MC568 5. Dataset Digital Object Identifier (DOI) 10.7267/5712mc568 6. Limitations to reuse The 2-year flood inundation data are not intended for floodplain management or regulatory purposes. -------------------------- VERSIONING AND PROVENANCE -------------------------- 1. Last modification date 2017-06-01 2. Was data derived from another source? Yes. Pacific Northwest Ecosystem Research Consortium Willamette River historic floodplain "slices" (http://oregonstate.edu/dept/pnw-erc/) -------------------------- METHODOLOGICAL INFORMATION -------------------------- Description of methods used for collection/generation of data: 1. Construction of 100 m slices The 100 meter polygons are designed to be regular spatial subdivisions of a preexisting map that subdivided the Willamette River historic floodplain into 1 kilometer spatial reporting units called "slices" developed by the Pacific Northwest Ecosystem Research Consortium http://oregonstate.edu/dept/pnw-erc/ . The 1 km slices were created by a combination of automated and manual steps that relied on a series of scripts written in the ArcInfo command language AML. The principal script in this suite is called segment.aml, originally developed by John Gabriel at Alsea Geospatial, Inc. in 1999, and modified for use in creating this 100 m slice coverage. Primary inputs to the script are the name of a line coverage representing the principal axis of the River's mainstem and parameters defining the interval to be used in locating points along the axis and the length of lines subsequently to be drawn by the script at right angles to the axis through each of the points. The axis coverage NUAXIS was provided by the Department of Fisheries and Wildlife at Oregon State University. Prior to creating the 100 m slices map, we created a 1 km slices map and ensured that its lines were spatially coincident with those in SLICES_v21. Subsequent to the development of the 100 m slices coverage, a revised 1 km slices coverage, called V21E was created that, primarily for the reach south of Albany, reduced the width of the floodplain from the historic area of inundation to the narrower "pragmatic" floodplain defined as the area for which the 100 m slice spatial reporting units are intended to be used. The output of the segment script is a series of arcs intersecting the main stem centerline at 100 m intervals. Manual edits and assigning of slice numbers Manual editing was required after the AML created the 100 m arc coverage. Where the centerline was predominantly north to south (for example, slices 8101 - 10010), the AML created arcs were evenly spaced and aligned as expected. Where the centerline contained a vertex to accommodate variations in the shape of the river (for example, slices 6401 - 7310), the 100 m arcs created by the AML were spaced and aligned in ways that were inconsistent with our nesting of 100 m slices within 1 km slices. Manual edits were done where required to correct spacing and to distribute arcs where there is a change in channel orientation. The primary guideline was to have each set of ten 100 m slices nested within its 1 km slice, i.e. the northern boundary of 100 m slice 8301 is coincident with the northern boundary of 1 km slice 83 and the southern boundary of slice 8310 is coincident with the southern boundary of 1 km slice 83. The 100 m arc coverage was converted to a geodatabase feature for manual edits in ArcMap. The 1km coverage was used as a background for editing to align 100 m slices and adjust spacing. A 100 m parallel spacing is not possible in locations where the channel changes orientation over a short distance (for example slices 3501 - 3510, 4601 - 4610). In these locations each set of ten 100 m slices was connected to a common vertex defined by its bounding 1 km slice. Where the common vertex occurs depends on the change in orientation (at 1 km slice 35 it is to the west, at 1 km slice 71 it is to the south, at 1 km slice 124 it is to the east). Where the bounding 1 km slice met at a vertex on the boundary (for example 1 km slices 72 and 112), the 100 m arcs were snapped to this same vertex. Where the 1 km slices did not have a common vertex at the boundary (for example 1 km slices 71, 73, 122), the 1 km boundary arcs were extended to create a common vertex outside of the boundary. The 100 m slice arcs were snapped to this newly created common vertex and then extended past the boundary on the opposite side. To create the 100 m polygons, the arc coverage was clipped to the boundary polygon and then appended to the boundary polygon. The assigning of 100 m slice numbers used the 1 km slice numbers as a starting place. For each 100 m slice nested within a 1 km slice, the identification begins with the 1 km slice number and is followed by 1 - 10 (1 is northernmost, 10 is southernmost). For example, the 100 m slices within 1 km slice 35 are 3501 - 3510. The assignment of 100 m slice numbers was accomplished with a combination of GIS operations (point on polygon overlay, joinitem) and manual inspection and editing. Where a slice is not contiguous (for example slice 22701 which has 3 polygons), the same slice number identifies all polygons of that slice. 2. Ecological attributes 2a. Channel complexity measures (Attributes: CHLEN10, CHLEN50, CHLEN50, CHAREA10) The Pacific Northwest Ecosystem Research Consortium PNW-ERC) http://oregonstate.edu/dept/pnw-erc/ quantified channel complexity in the Willamette River floodplain using two measurements, area of river channel, and length of river channel, using a 1 km slice spatial reporting framework for ca. 1850 "historical" and ca. 1995 "current" conditions. Based on this approach we report channel length and area of wetted features, within the pragmatic floodplain for ca. 2010 conditions and for ca. 2050 future conditions based on the PNW-ERC Conservation 2050 scenario, using the 100 m slice spatial reporting framework of this shape file, S100_wm_v4. Additional detail concerning the development of these measures can be found in the section of the Technical Details Channel Complexity page at the Slices Web site: https://oregonexplorer.info/slices. 2b. Two-year Inundation (Attribute: FLD_2YR) Two-year floodplain inundation identifies areas of predicted inundation associated with a regulated 2-year flood event. Depth represents depth of water, in feet, above the topographic surface captured during LiDAR acquisition and does not necessarily reflect true water depth. These data were created by River Design Group, Inc. (RDG) to be used as a tool in identifying restoration opportunities on the Willamette River and are not intended for floodplain management or regulatory purposes. The data were delivered by RDG on July 7, 2012 and are used here with permission of RDG. Additional detail concerning the procedures used to produce the values for Two Year Flood Inundation can be found in the Technical Details 2 Year Flood ca. 2010 section of the Slices Web site: https://oregonexplorer.info/slices . 2c. Floodplain forest measures (Attributes: FPF2010, FPF2050, PBF2010, PBF2010KM) Floodplain Forest ca. 2010 is reported in acres for each 100 m slice in the field FPF2010. The representation of floodplain forest in the 100 m SLICES is derived from multiple datasets and two sources with different underlying spatial grains. In slices 1 – 7907, the primary data source is Landsat satellite data at a 30 m spatial grain. In slices 7908 – 22907, the representation was processed at a 6ft. grain using 2011 NAIP imagery and ca. 2009 LiDAR data. Additional detail concerning the procedures used to produce the values for Floodplain forest can be found in the Technical Details Floodplain Forest document. 2d. Percent bank forested measures (Attributes: PB2010, PBF2010KM) Percent Bank Forested ca. 2010 is reported for each 100 m slice and also for each 1 km slice. In the GIS data, Percent Bank Forested is reported in the field PBF2010 for the 100 m slices and the field PBF2010KM for the 1 km slices. Percent Bank Forested ca. 2010 is calculated per 100 m slice to be the area of floodplain forest within 120 feet (one site potential tree height) of the low water bank divided by the total area within 120 feet of the bank. For each 1 km slice, the Percent Bank Forested is calculated to be the area of floodplain forest within 120 feet of the low water bank divided by the total area within 120 feet of the bank. Additional detail concerning the procedures used to produce the values for Percent Bank Forested can be found in the Technical Details percent Bank Forested document. 2e. Cold water Refuges (Attribute: CLDO_2015) Cold water refuges are reported for the 100 m slices. The value of 1 indicates that between 2011 and 2016 at least one data point collected in the corresponding 100 m slice met the definition of cold water refuge (explained below). The value of zero means that data collected in that 100 m slice did not meet the definition of cold water OR that no data were collected in that 100 m slice. Cold water refuges in the Willamette River occur in sloughs and side channels, where subsurface water emerges and exchanges slowly with the mainstem river. Cold water refuges are defined here as locations where, in the months of July and August, the slough or side channel temperature is 2 degrees C colder than the daily maximum temperature of the associated mainstem Willamette River and the concentration of dissolved oxygen is 4.0 mg/L or greater. The 4.0 mg/L value represents a concentration at which native fish can survive but this should not be confused with optimal dissolved oxygen for native fish. Additional detail concerning the procedures used to produce the values for Cold Water Refuges can be found in the Technical Details Cold Water Refuges document. 2f. Juvenile Spring Chinook Habitat measures (Attributes: JCRES2010, JCCON2010) Two attributes are associated with juvenile Spring Chinook habitat, JCRES_2010 reports the number of acres in each 100 m slice identified for restoration, and the attribute JCCON_2010 reports the number of acres in each 100 m slice identified for conservation. Additional detail concerning the procedures used to produce the values for Cold Water Refuges can be found the Technical Details/Juvenile Chinook document. 2g. Native fish measures (Attributes: PCNAT2010, SABUN2010 ) The attribute field PCNAT2010 reports the percentage of native fish out of all fish captured in each 1 km slice (i.e. the value 93 represents 93 percent native fish). Salmonid abundance, the number of Salmonids captured in each 1 km slice is reported in the GIS attribute field SABUN2010. The percent native and salmonid abundance are reported in the first 100m slice (lowest number, ending in 01) for the entire associated 1 km slice. For example, salmonid abundance in 100 m slice number 21601 is 51; the value of 51 reports the number of salmonids captured in 1 km slice 216 (100 m slices 21601 - 21610). Additional detail concerning the procedures used to produce the values for Native fish can be found in the Technical Details Native fish document. --------------------- DATA & FILE OVERVIEW --------------------- 1. File List A. Shapefile component files Short description: Shapefile containing spatial features and attributes 1. s100_wm_v4.dbf 2. s100_wm_v4.CPG 3. s100_wm_v4.shp 4. s100_wm_v4.shx 5. s100_wm_v4.sbn 6. s100_wm_v4.sbx 7. s100_wm_v4.prj B. Filename: s100_wm_v4.mdb Short description: Geodatabase containing spatial features and attributes C. Filename: s100_wm_v4.xml Short description: Metadata document in the Federal Geographic Data Committee Content Standard For Digital Geospatial Metadata (FGDC CSDGM) format. See more about FGDC CSDGM: https://www.fgdc.gov/metadata/csdgm-standard 2. Relationship between files: The shapefile and geodatabase contain the same features and attributes. The .xml document describes both the shapefile and geodatabase. ----------------------------------------- TABULAR DATA-SPECIFIC INFORMATION FOR: s100_wm_v4.shp and s100_wm_v4.mdb ----------------------------------------- 1. Number of variables: 18 2. Number of cases/rows: 2602 3. Variable List 1. Name: JF Description: This field is used in the management of attributes obtained from external data sources. 2. Name: FP_KM Description: Beginning from the confluence of the Columbia River, segments of floodplain 1 km apart are identified by sequential numbering. 3. Name: FP_100m Description: 100 m slices are enumerated in the north to south, upstream direction. 4. Name: FP_KM01 Description: Beginning from the confluence of the Columbia River, segments of floodplain 1 km apart are identified by sequential numbering. 5. Name: CHLEN10 Description: The ca. 2010 centerline length in meters of wetted features connected to the Willamette River mainstem. 6. Name: CHLEN50 Description: The ca. 2050 centerline length in meters of wetted features connected to the Willamette River mainstem under the PNW-ERC's Conservation 2050 scenario. 7. Name: CHAREA10 Description: The ca. 2010 area in square meters of wetted features within the pragmatic floodplain. 8. Name: CHAREA50 Description: The ca. 2050 area in square meters of wetted areas within the pragmatic floodplain under the PNW-ERC's Conservation 2050 scenario. 9. Name: FPF2010 Description: Floodplain forest area in acres derived from land use land cover classes from a ca. 2000 land use land cover. representation. 10. Name: FPF2050 Description: Floodplain forest area in acres derived from land use land cover classes from PNW-ERC's 2050 Conservation scenario land use land cover in slices 1 - 7901 at 30 m grain, and ca. 2010 6 ft Landuse-Landcover in slices 7902 - 22902. 11. Name: PBF2010 Description: Percent Bank Forested ca. 2010 is reported for each 100 m slice. 12. Name: PBF2010KM Description: Percent Bank Forested ca. 2010 is reported for each 1 km slice. 13. Name: FLD_2YR Description: Area in acres of predicted inundation associated with a regulated 2-year flood. 14. Name: CLDO_2015 Description: Locations of cold water in side channels and alcoves. The value of 1 indicates that between 2011 and 2016 at least one data point collected in the corresponding 100 m slice met the definition of cold water refuge. The value of zero means that data collected in that 100 m slice did not meet the definition of cold water OR that no data were collected in that 100 m slice. 15. Name: JCRES2010 Description: Number of acres in each 100 m slice identified for restoration. 16. Name: JCCON2010 Description: Number of acres in each 100 m slice identified for conservation. 17. Name: PCNAT2010 Description: Of all fish captured in each 1 km slice, PCNAT2010 reports the percentage that are native fish. 18. Name: SABUN2010 Description: Number of Salmonids captured in each 1 km slice.