Shapefile
Tags
Habitat fragmentation, Coastal, In-stream structures, Streams, Streams, Impediment, Habitat corridors, Habitat connectivity, environment, Anadromous species, Passage assessments, Stream flow, Dams, Salmon, Inventory, Road crossings, Potadromous migrations, Biotic barriers, structure, Central Valley, Passage, California, Barriers (structures), Obstacle, Culvert, Steelhead, inlandWaters, Diversion, Anadromous migrations
The Passage Assessment Database (PAD) is an ongoing inventory of known and potential barriers to anadromous fish in California. It compiles currently available fish passage information from more than two hundred data sources, and allows past and future barrier assessments to be standardized and stored in one place. The inventory is to be used to identify barriers suitable for removal or modification to restore spawning and riparian habitat for salmon and steelhead, and to enhance aquatic and riparian habitat. The PAD is intended to be compatible with a variety of other data sets related to anadromous fish issues. PAD records are saved with geographic location information. Each barrier record is indexed to the 24k high-resolution NHD allowing the user to combine the PAD with other fisheries data tied to the same hydrography.
The Passage Assessment Database (PAD) geospatial file contains locations of known and potential barriers to salmonid migration in California streams with additional information about each record. The PAD is an ongoing map-based inventory of known and potential barriers to anadromous fish in California, compiled and maintained through a cooperative interagency agreement. The PAD compiles currently available fish passage information from many different sources, allows past and future barrier assessments to be standardized and stored in one place, and enables the analysis of cumulative effects of passage barriers in the context of overall watershed health. The database is set up to capture basic information about each potential barrier. It is designed to be flexible. As the database grows, other modules may be added to increase data detail and complexity. For the PAD to be useful as a restoration tool, the data within the PAD need to accurately depict the on-the ground reality of fish passage constraints. This requires the PAD to retrieve new barrier data and updates to existing sites and to have verified and vetted the information it receives. In 2013, new PAD data standards were designed to standardize this process, and refine the data in PAD making the data more robust. The standard is available online at:
https://nrmsecure.dfg.ca.gov/FileHandler.ashx?DocumentID=78802
. The new standards have been implemented for all new records since 2013. In the future, the new standards will be implemented for all existing records. If after reading the metadata, additional details about the PAD project are needed, please visit the CalFish website at
www.calfish.org/PAD
or refer to the PAD Methodology document at
http://nrm.dfg.ca.gov/FileHandler.ashx?DocumentID=19037
. To send comments about data issues, corrections, edits or to map a new barrier location not yet reported in the PAD, please use the PAD Online Data Review Application:
https://map.dfg.ca.gov/pad/
or send an email to: Anne.Elston@wildlife.ca.gov. Preferred citation: California Department of Fish and Wildlife, Passage Assessment Database, November 2016 Version.
Since the inception of the Passage Assessment Database, funding for the compilation of these data have been provided by the California Coastal Conservancy, U.S. Fish and Wildlife Service (USFWS), NOAA Fisheries and the California Department of Fish and Wildlife (CDFW). The CDFW Fisheries Restoration Grant Program is one of the most recent and longest funders of the PAD. The USFWS has recently provided funding for the compilation of miles upstream, etc. Pacific States Marine Fisheries Commission staff manage and compile data into this dataset. Datasets were collected and supplied by multiple agencies and organizations, and the PAD would not be possible without these datasets (see the "Source Citation" element (srccite) for more information). We would like to thank Daniel Wieferich from the United States Geological Service for metadata support. He reviewed and edited the metadata for compliance with the Federal Geographic Data Committee Content Standard for Digital Geospatial Metadata.
The PAD is a database of ongoing inventory of fish passage assessments related to fish passage in California. Since it is an inventory of assessments; the PAD includes information on known and potential barriers, non-barriers, remediated sites, and unscreened diversions which can impede fish passage. Known barriers (that is, total, partial, temporal, total and partial, total and temporal records) should be parsed or queried from the dataset, and reported as the number of barriers in California. Records with “unknown” or “unassessed” passage status, have the potential to block fish passage, and should be reported as potential barriers. Contact the PAD Administrator (Anne.Elston@wildlife.ca.gov), if you have questions about using, reporting or analyzing data in this dataset. The data in the PAD are a reflection of the datasets that have been found to date by PAD staff, not the actual state of fish passage in streams. Refer to "Data Quality" (dataqual) for information regarding data quality and limitations of this dataset. The PAD was intended to track the anadromous fish passage assessments in California; however, over time passage assessments related to non-anadromous species and some passage assessments outside of California have been added to the PAD. Per the current PAD data standards, https://nrmsecure.dfg.ca.gov/FileHandler.ashx?DocumentID=78802, both will be maintained in the dataset but not added to the PAD anymore. Additionally, it should be noted that many fish passage assessments recorded in the PAD are outside of the current species range and within their historical range. National Oceanic and Atmospheric Administration’s (NOAA) Distinct Population Segment boundaries, http://www.westcoast.fisheries.noaa.gov/maps_data/species_population_boundaries.htmlc, along with the PAD, can be used to indicate barriers below major rim dams and within the species current geographic area.
Extent
| West | -124.375158 | East | -114.139589 |
| North | 42.978930 | South | 32.593852 |
| Maximum (zoomed in) | 1:5,000 |
| Minimum (zoomed out) | 1:150,000,000 |
Since the inception of the Passage Assessment Database, funding for the compilation of these data have been provided by the California Coastal Conservancy, U.S. Fish and Wildlife Service (USFWS), NOAA Fisheries and the California Department of Fish and Wildlife (CDFW). The CDFW Fisheries Restoration Grant Program is one of the most recent and longest funders of the PAD. The USFWS has recently provided funding for the compilation of miles upstream, etc. Pacific States Marine Fisheries Commission staff manage and compile data into this dataset. Datasets were collected and supplied by multiple agencies and organizations, and the PAD would not be possible without these datasets (see the "Source Citation" element (srccite) for more information). We would like to thank Daniel Wieferich from the United States Geological Service for metadata support. He reviewed and edited the metadata for compliance with the Federal Geographic Data Committee Content Standard for Digital Geospatial Metadata.
publication date
There are no legal limitations of use associated with this dataset. This PAD geospatial file is a public dataset.
The PAD is a database of ongoing inventory of fish passage assessments related to fish passage in California. Since it is an inventory of assessments; the PAD includes information on known and potential barriers, non-barriers, remediated sites, and unscreened diversions which can impede fish passage. Known barriers (that is, total, partial, temporal, total and partial, total and temporal records) should be parsed or queried from the dataset, and reported as the number of barriers in California. Records with “unknown” or “unassessed” passage status, have the potential to block fish passage, and should be reported as potential barriers. Contact the PAD Administrator (Anne.Elston@wildlife.ca.gov), if you have questions about using, reporting or analyzing data in this dataset. The data in the PAD are a reflection of the datasets that have been found to date by PAD staff, not the actual state of fish passage in streams. Refer to "Data Quality" (dataqual) for information regarding data quality and limitations of this dataset. The PAD was intended to track the anadromous fish passage assessments in California; however, over time passage assessments related to non-anadromous species and some passage assessments outside of California have been added to the PAD. Per the current PAD data standards, https://nrmsecure.dfg.ca.gov/FileHandler.ashx?DocumentID=78802, both will be maintained in the dataset but not added to the PAD anymore. Additionally, it should be noted that many fish passage assessments recorded in the PAD are outside of the current species range and within their historical range. National Oceanic and Atmospheric Administration’s (NOAA) Distinct Population Segment boundaries, http://www.westcoast.fisheries.noaa.gov/maps_data/species_population_boundaries.htmlc, along with the PAD, can be used to indicate barriers below major rim dams and within the species current geographic area.
These data are referenced to the National Hydrography Dataset (1:24,000) flowlines using the COMID field.
The Passage Assessment Database was compiled using information about fish passage from a large number of sources. These datasets used by the PAD were originally created for a number of different purposes, from general stream habitat surveys to rigorous assessments of fish barriers. The quality of the data in the PAD will vary depending on the data source, including different amounts of accuracy of fish passage information, detail and varying degrees of accuracy in location descriptions. See to "Attribute Accuracy" (attraccr), "Horizontal Positional Accuracy" (horizpar) and "Completeness" (complete) reports for more detailed explanations. For a list of data sources, refer to "Online Link" (onlink). Since many datasets overlapped in their geographic range, information about the same barrier could sometimes be found in several different datasets. In most cases, the duplicates were identified during data entry or in subsequent data quality evaluation. However, the dataset may still contain a slight overestimate of the numbers of known and potential barriers.
The PAD strives to keep the data as current and updated as possible, however, there can be a lag between on the ground projects and when that information is entered into the PAD. The data in the PAD are a reflection of the datasets that have been found to date by PAD staff, not the actual state of fish passage in streams. For example, the PAD includes very comprehensive data about passage barriers in some watersheds but not in others. This does not mean that there aren’t many barriers in the other watersheds, but rather that the PAD does not yet include comprehensive barrier data for these watersheds. Many datasets have no assessment of whether the inventoried structures are barriers to fish passage, if and when they were surveyed, and whether the structures are partial, temporal or total barriers. Non-surveyed structures are listed as “unassessed” and may need a formal assessment. Other structures were surveyed for fish passage, but passage status was indeterminate; therefore, many are listed as “unknown” passage status. FishXing can assist with a passage determination for those determined indeterminate at time of survey. Many original datasets are missing other information that should be included in the passage assessment database. For example, many datasets do not have species information indicating which species (and life stage) are blocked by the barrier and the level of blockage (i.e., temporal or total). In some cases, the original datasets include this information, but this information was not added to the PAD.
Since the inception of the PAD in 2002, passage statuses (BarStatus field attributes (i.e., total, temporal, partial)) came from various data sources (from fish passage surveys to professional judgement) and people with varying degrees of fish passage knowledge. For a majority of the PAD records, professional judgement is used as the protocol for determining passage status. In early 2013, new PAD data standards were developed and implemented for new records and the person that made the professional passage status determination began to be tracked. Prior to this, only the name of the agency that made the passage status determination was tracked and because there are many references from the same agency for each PAD record, tracking the person that made the determination was difficult. To deal with the differences in the level of fish passage expertise and the potential for receiving fish passage determinations and assessments by persons with little to no fish passage experience; new PAD data standards were developed in regards to who determines fish passage. The new PAD data standards dictate that if the passage status was not determined by a fish passage professional, the passage status will be listed as unknown until a fish passage professional has confirmed or disputed the sources’ passage assessment. Since 2013, professional fish passage experience from the person that assessed passage at the site if not specified in the assessment report is requested in order to meet this PAD data standard, and is tracked in the database. Prior to 2013, when a barrier had been remediated by adding a fishway or by another modification, the passage status of that PAD record was changed to "not a barrier" unless otherwise specified by the data source. In order to track the success of the fish passage improvement projects and assess whether the site still impedes passage, a new passage status called "remediated, fish presence unconfirmed" was developed and used until such time qualitative (photo) or quantitative (fish counts) data was provided to the PAD to confirm that it is indeed not a barrier to fish passage. The PAD Data Standard is used to ensure the accuracy of the passage status and location attributes for all new records added and updated in the PAD since 2013.
The PAD Data Standard is used to ensure the accuracy of the location attributes in this dataset. Per the data standard, the PAD Administrator verifies with the data source that the coordinates are precise and where not precise, asks for the bank location and distance in feet from the coordinates, and standardizes all PAD locations by tying them to hydrography. All records in this dataset are stored with geographic location information. Each barrier record is indexed to the High-resolution National Hydrography Dataset (NHD) developed by USGS at roughly 1:24,000 scale (24K NHD). The NHD was used to assign a stream address to a PAD record. Using the ‘Locate feature along route’ command in ESRI's ArcGIS 9.3 and later versions, each barrier was assigned a position along the measured stream network by capturing the unique identifier for each line segment and the measure along the segment that represents the barrier location. When aligned to the 24K NHD, points were shifted from the coordinates given in the original dataset to the 24K NHD. For this reason, the locations in PAD may not reflect the actual location of the point, structure or barrier. Original coordinates are kept with the original data set. Additionally, some locations were snapped to the wrong stream and these were not diligently checked. The PAD Data Standard reduces this error for all records added in the PAD since 2013, by verifying that the snapped barriers are on the correct stream and road route/post-mile (if applicable). The stream name in the PAD comes from the source datasets and is generally more accurate than the stream name that the record has been snapped to. Opportunistically, stream names in existing PAD records are compared with the name of the stream that the barrier is snapped to, the source documentation is reviewed and the locations are corrected. Location errors in the entire dataset will need to be identified and corrected in 2015-2016. In some cases, the datasets do not have very precise location information. For example, some stream surveys only mention that there is a barrier or structure within a defined reach of stream, making it impossible to pinpoint the barrier location. Structures described in this way are maintained in GIS as linear geospatial files. For the purposes of creating one point feature spatial file, all linear locations were converted to a single point at the beginning of the linear stream reach. Some datasets describe locations using the distance of the structure from the stream mouth (i.e., river mile) – these were digitized using this measure on the hydrography. Since the 1: 24,000 hydrography may not follow the exact course of the stream and stream measures may not be precise, measured distances along a stream may not reflect reality. This has caused location errors and led to duplicate barrier entries. Errors are minimized by referencing structures to other landmarks whenever possible.
A formal accuracy assessment of the vertical positional information in the data set has either not been conducted, or is not applicable.
4. To assist with coarse filtering of large number of barriers for restoration consideration and to enable the optimization model being developed by the California Fish Passage Forum, additional fields were added to the PAD geospatial file. These fields were derived from tracing the high-resolution National Hydrography Dataset upstream and downstream from a barrier. These fields are periodically updated, with the most recent update on July 30, 2013. The fields include the number of downstream and upstream barriers, the order of the barrier on a stream network (“1” would be the most downstream barrier), and miles upstream and downstream to the next barrier or limit of anadromy, if applicable. Only known barriers were used for the analysis; barriers with unknown passage status, unassessed structures, non-barriers, diversions and sites where remediation occurred but fish presence is unconfirmed were excluded from the analysis. Barriers outside of the NOAA’s Steelhead Distinct Population Segment boundary as of January 2013, and those areas that were determined to be anthropogenically blocked by NOAA, were excluded from this analysis. Many of these derived fields from this analysis do not reside inside of the PAD, but they have been added to this geospatial dataset.
1. Gather fish passage assessment data. Retrieve and request fish passage assessment and fish passage improvement project information from multiple agencies and organizations. Acceptable data formats include geospatial data or other electronic data files, assessment reports, survey and data retrieval forms, personal communication, grant proposals, news clips or websites, etc. Data retrieval includes use of applications (i.e., PAD review application) and data forms, and outreach to multiple organizations including presenting at conferences, conducting training and review sessions and sending direct requests for data through email. The location or Passage ID, structure type, passage status, contact information of the data submitter, information regarding fish passage expertise of the person that determined fish passage status, and a description of the treatment (if applicable) that occurred are required prior to data entry into the PAD. Prior to 2013, some of this information was requested but not required and thus not entered into the PAD. For the most part; location, passage status and structure type were received and entered into the PAD. Protocol used was requested if it was not clear by the reference material provided. Other information not-required by the PAD, is requested by the PAD Administrator in order create a comprehensive record of fish passage constraints to assist restoration practitioners and PAD users. This other information requested includes site/barrier description including size of the structure, velocity issues, fishway presence and status, survey specifics, observation of fish downstream or upstream prior to barrier removal, species and life stage blocked or benefited from treatment, and structure and landowner information.
2. Review fish passage assessment data received and compile data into the PAD. Beginning in 2013, fish passage assessment data received are reviewed and compiled into the PAD following steps i through iii. i. Request fish passage experience from the person that assessed passage at the site if not specified in the assessment report. Use a standard form for retrieving the persons' professional experience in fish passage available online at: https://nrm.dfg.ca.gov/FileHandler.ashx?DocumentID=87996. If the assessment of passage status did not come from a fish passage professional, list the passage status as unknown until a fish passage professional has confirmed or disputed the sources’ passage assessment. ii. Check that the data received includes passage status. A structure or non-structural element (i.e., waterfall, grade, temperature, etc.) will be added to the PAD and listed as ‘unassessed’ passage status if the passage status is unknown and if the barrier is a probable or potential barrier and hasn’t been assessed. For instances where barriers are probable partial or total barriers, this information will be added to the site comments. For a structure or non-structural element that has been assessed for fish passage but passage status was unable to be determined; the passage status will be listed as "unknown". USFS Grey filter category (i.e., indeterminate) is an example of this. For fish passage improvement projects, request qualitative (e.g., photos of fish above the barrier) or quantitative (fish counts above the barrier) evidence that the structure is no longer a barrier to fish passage. Quantitative or qualitative evidence will need to be received by the PAD Administrator prior to changing passage status to ‘not a barrier’. Otherwise, passage status will be listed as ‘remediated, fish presence unconfirmed’. iii. All barriers and diversions will be subject to the Quality Assurance and Quality Control (QAQC) procedures listed below (a-d), to the extent that this is possible. The QAQC procedures include verification of location information and steps for the prevention of duplicate barriers and diversions in the PAD. a) When receiving barrier and diversion information, use ESRI's ArcMap (9.x or later versions) to decide if these are new barriers and diversions that need to be added to the PAD. Look at existing PAD barriers and diversions within proximity of this new site, compare photos, site names, structure owners, passage statuses, passage types and site comments. If it is still difficult to determine if this is a new site, request more information from the source. In many cases, existing barriers in PAD are incorrectly located and can often be off more than several hundred feet. b) Verify with the source that the coordinates are precise (i.e., taken on top of the barrier) and ask for the datum used if not provided. If the latitude/longitude coordinates aren’t precise, ask for the barrier or diversion bank location (looking downstream) and distance in feet from the GPS coordinates. Also, ask why these coordinates aren’t precise. c) When sources send information that have may have duplicate information, send an email back to the source addressing these issues. d) Standardize PAD locations and tie them to hydrography. Refer to the text below for the process and explanation for standardizing locations of PAD records including assumptions the PAD utilizes. The PAD records in this geospatial dataset only include records with geographic location information. Barrier records are indexed to the High-resolution National Hydrography Dataset (NHD) developed by United States Geological Survey at a 1:24,000 or finer scale. The NHD was used to assign a stream address to a PAD record. Using the ‘Locate feature along route’ command in ArcGIS 9.3 and later versions, each barrier was assigned a position along the measured stream network by capturing the unique identifier for each line segment (ComID) and the measure (NHDComMeas) along the segment that represents the barrier location. When the stream is not digitized in the NHD, the PAD record retains the location that was provided by the original data source. In the database, this is tracked (i.e., 24k hydrography not digitized) in a separate field. Since some of the fisheries related datasets in California are tied to the LLID-based routed hydrography of a 1:100,000 scale (rather than the NHD), the PAD is also available in a format compatible with the LLID hydrography. For the purposes of creating one point feature spatial file, all linear locations were converted to a single point at the beginning of the linear stream reach. Downstream ends of linear barriers such as flood control channels, gradients or low-flow sections were digitized as points, based on the assumption that the adult fish swimming upstream will have to deal with the downstream end of a barrier first. The length of the linear barriers can be found in the site comments/notes for each. All geographic data that are received for use in the PAD are saved in their original format as well as in their final standardized format. If there are any problems with the PAD data, it will always be possible to return to the original dataset for a solution. When aligned to the 24K hydrography, points were shifted from the coordinates given in the original dataset to the 24K NHD. For this reason, the locations in PAD may not reflect the actual location of the point, structure or barrier. Beginning in 2013, the streams that the barriers were snapped to were reviewed to see if they match the stream name and road route/post-mile (if applicable) per the original/source dataset, and the locations of the snapped PAD records were moved accordingly. Also, the locations of all new and updated barriers were revised so that they are on top of the barrier or close to the barrier per aerial imagery but still aligned to the 24K hydrography. If there is more than one barrier at the same location and it’s the same barrier type, this will be captured in one PAD ID and the number of barriers will be added to a new field. If the passage statuses differ between these barriers, the lower level passage status will be associated with the PAD ID and the passage statuses of all barriers will be noted in the site comments. For example, if there are two culverts next to one another under the same bridge one that is a total barrier and the other that is a partial barrier, this will be combined into one PAD ID (i.e., one point) and listed as a partial barrier. The site comments will contain the passage status of both culverts.
3. Compile other locational specific information using ArcGIS. Using ESRI's ArcGIS 9.x and later versions, perform spatial joins on PAD records with county and watershed datasets to obtain attributes from these datasets and add them to the PAD.
The PAD has received and retrieved 811 reference documents and datasets that have been used to add and update information in this dataset. The input datasets that have contributed to and gone into the PAD, include spatial data, electronic data files, assessment reports, surveys and data retrieval forms, personal communication, grant proposals, news clips and websites, etc. These datasets have contributed to the fish passage assessment data that is in the PAD.
The date range represents the earliest input dataset to the most recent input dataset that was used to create this dataset.
Table containing attribute information associated with the data set.
Producer defined
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
Feature geometry.
Esri
Coordinates defining the features.
StreamNet database and PAD Unique ID created by the PAD for linking to California records in StreamNet (i.e., BarrierID (700,000 - 799,000)).
StreamNet
Passage Assessment Database internal unique ID.
Passage Assessment Database
Name of a stream the structure is located in.
Passage Assessment Database
Name of a stream the structure is located in.
First order tributary to.
Passage Assessment Database
First order tributary to.
Structure/site name.
Passage Assessment Database
Structure/site name.
Type of instream structure/site.
Passage Assessment Database
Barrier status of the structure/site. Terminology used for the passage status is consistent with Section IX of the California Salmonid Stream Habitat Restoration Manual published by the Department of Fish and Game (Table IX-1, page IX-1).
Passage Assessment Database
Assessment protocol used to inventory or assess the structure/site (DFG Restoration Manual, FishXing Software, Professional Judgement, Caltrans Reconnaissance Protocol, Caltrans Detailed Protocol, Field Survey).
Passage Assessment Database
Agency or individual assessing the structure/site.
Passage Assessment Database
Agency or individual assessing the structure/site.
Date of the barrier inventory/assessment.
Original sources.
Date
Barrier treatment status.
Passage Assessment Database
Year the barrier was removed or remediated.
Original Sources.
Group responsible for treating or removing the barrier. This only includes one responsible party and other organizations involved in treatment of fish passage are listed in the notes field.
Passage Assessment Database
Group responsible for treating or removing the barrier.
Owner of the land.
Passage Assessment Database
Unknown
Subjective notes further describing the structure, based on site conditions observed during the field inventory/assessment.
Original Sources
Unknown
Potential treatment options to remediate the barrier.
Original Sources
Unknown
Federal HUC unit (4th field HUC Unit) , USGS
U.S. Geological Survey
Unknown
County name.
U.S. Geological Survey
Unknown
Hydrologic Region (Calwater 2.2.1).
Calwater 2.2.1
Hydrologic Unit (Calwater 2.2.1).
Calwater 2.2.1
Unknown
Hydrologic Area (Calwater 2.2.1).
Calwater 2.2.1
Unknown
Hydrologic Subarea (Calwater 2.2.1).
Calwater 2.2.1
Unknown
Calwater number (Calwater 2.2.1).
Calwater 2.2.1
Stream reach ID, from indexing to 24k National Hydrography Dataset (NHD).
Passage Assessment Database
Stream reach measure, from indexing to 24k National Hydrography Dataset (NHD).
Passage Assessment Database
CalHydro stream unique ID (100K California Hydrography).
Passage Assessment Database
Unknown
CalHydro stream location address (begft) from snapping to 100K California Hydrography.
Passage Assessment Database
Road route number or road name.
Passage Assessment Database
Unknown
Road post mile number.
Passage Assessment Database
Is the diversion operational? (yes/no)
Passage Assessment Database
Is the diversion mobile? (yes/no)
Passage Assessment Database
The date the record last updated in the PAD. Updates include passage status updates, location revisions and other revisions to the record.
Producer defined
All data sources providing data to the PAD.
Producer defined
Unknown
Web legend category used for the web mapping service: CDFW BIOS. Some of the attributes (i.e., Total Barrier, Partial Barrier, Natural Total Barrier, Natural Partial Barrier, Not a Barrier, Unknown Passage Status) in this field are created by combining the attributes in the barrier status and/or site type fields. Refer to each "Enumerated Domain Value Definition" (attrlabl) listed below for more details.
Producer defined
GCS North American 1983 Longitude.
Passage Assessment Database
GCS North American 1983 Latitude.
Passage Assessment Database
Hyperlink to the photogragh of the site showing the barrier and/or barrier remediation.
Passage Assessment Database
Unknown
Order of a barrier within the stream network of a watershed (e.g. 1 = first downstream barrier). Barriers outside of NOAA's Steelhead DPS boundary (January 2013) and those areas that were determined to be anthropogenically blocked by NOAA (January 2013) were excluded from this analysis. Potential barriers (unknown passage status and unassessed barriers), non-barriers, removed structures, diversions and non-structural barriers were excluded from this analysis. Last calculated on July 2013. Attributes in this field are derived from "Process Step" (procdesc) #4 described above in "Lineage".
Passage Assessment Database
Stream miles upstream to next upstream barrier tracing the NHD stream network. Barriers outside of NOAA's Steelhead DPS boundary (January 2013) and those areas that were determined to be anthropogenically blocked by NOAA (January 2013) were excluded from this analysis. Potential barriers (unknown passage status and unassessed barriers), non-barriers, removed structures, diversions and non-structural barriers were excluded from this analysis. Last calculated on July 2013. Attributes in this field are derived from "Process Step" (procdesc) #4 described above in "Lineage".
Passage Assessment Database
Stream miles upstream to natural limits of anadromy tracing the NHD stream network or to NOAA's Steelhead DPS boundary (January 2013). Potential barriers (unknown passage status and unassessed barriers), non-barriers, removed structures, diversions and non-structural barriers were excluded from this analysis. Last calculated on July 2013. Attributes in this field are derived from "Process Step" (procdesc) #4 described above in "Lineage".
Passage Assessment Database
PAD_ID of the immediate downstream barrier. Barriers outside of NOAA's Steelhead DPS boundary (January 2013) and those areas that were determined to be anthropogenically blocked by NOAA (January 2013) were excluded from this analysis. Potential barriers (unknown passage status and unassessed barriers), non-barriers, removed structures, diversions and non-structural barriers were excluded from this analysis. Last calculated on July 2013. Attributes in this field are derived from "Process Step" (procdesc) #4 described above in "Lineage".
Passage Assessment Database
The number of barriers located downstream. Barriers outside of NOAA's Steelhead DPS boundary (January 2013) and those areas that were determined to be anthropogenically blocked by NOAA (January 2013) were excluded from this analysis. Not calculated for potential barriers (unknown passage status and unassessed barriers), non-barriers, removed structures, diversions and non-structural barriers. Last calculated on July 2013. Attributes in this field are derived from "Process Step" (procdesc) #4 described above in "Lineage".
Passage Assessment Database
The number of barriers located upstream. Barriers outside of NOAA's Steelhead DPS boundary (January 2013) and those areas that were determined to be anthropogenically blocked by NOAA (January 2013) were excluded from this analysis. Not calculated for potential barriers (unknown passage status and unassessed barriers), non-barriers, removed structures, diversions and non-structural barriers. Last calculated on July 2013.
Passage Assessment Database
The entity and attribute information provided here describes the tabular data associated with the data set. Please review the detailed descriptions that are provided (the individual attribute descriptions) for information on the values that appear as fields/table entries of the data set.
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.
The Passage Assessment Database (PAD) geospatial file contains locations of known and potential barriers to salmonid migration in California streams with additional information about each record. The PAD is an ongoing map-based inventory of known and potential barriers to anadromous fish in California, compiled and maintained through a cooperative interagency agreement. The PAD compiles currently available fish passage information from many different sources, allows past and future barrier assessments to be standardized and stored in one place, and enables the analysis of cumulative effects of passage barriers in the context of overall watershed health. The database is set up to capture basic information about each potential barrier. It is designed to be flexible. As the database grows, other modules may be added to increase data detail and complexity. For the PAD to be useful as a restoration tool, the data within the PAD need to accurately depict the on-the ground reality of fish passage constraints. This requires the PAD to retrieve new barrier data and updates to existing sites and to have verified and vetted the information it receives. In 2013, new PAD data standards were designed to standardize this process, and refine the data in PAD making the data more robust. The standard is available online at: https://nrmsecure.dfg.ca.gov/FileHandler.ashx?DocumentID=78802. The new standards have been implemented for all new records since 2013. In the future, the new standards will be implemented for all existing records. If after reading the metadata, additional details about the PAD project are needed, please visit the CalFish website at www.calfish.org/PADor refer to the PAD Methodology document at http://nrm.dfg.ca.gov/FileHandler.ashx?DocumentID=19037. To send comments about data issues, corrections, edits or to map a new barrier location not yet reported in the PAD, please use the PAD Online Data Review Application: https://map.dfg.ca.gov/pad/or send an email to: Anne.Elston@wildlife.ca.gov. Preferred citation: California Department of Fish and Wildlife, Passage Assessment Database, November 2016 Version.
The Passage Assessment Database (PAD) is an ongoing inventory of known and potential barriers to anadromous fish in California. It compiles currently available fish passage information from more than two hundred data sources, and allows past and future barrier assessments to be standardized and stored in one place. The inventory is to be used to identify barriers suitable for removal or modification to restore spawning and riparian habitat for salmon and steelhead, and to enhance aquatic and riparian habitat. The PAD is intended to be compatible with a variety of other data sets related to anadromous fish issues. PAD records are saved with geographic location information. Each barrier record is indexed to the 24k high-resolution NHD allowing the user to combine the PAD with other fisheries data tied to the same hydrography.
publication date
None
The PAD is a database of ongoing inventory of fish passage assessments related to fish passage in California. Since it is an inventory of assessments; the PAD includes information on known and potential barriers, non-barriers, remediated sites, and unscreened diversions which can impede fish passage. Known barriers (that is, total, partial, temporal, total and partial, total and temporal records) should be parsed or queried from the dataset, and reported as the number of barriers in California. Records with “unknown” or “unassessed” passage status, have the potential to block fish passage, and should be reported as potential barriers. Contact the PAD Administrator (Anne.Elston@wildlife.ca.gov), if you have questions about using, reporting or analyzing data in this dataset. The data in the PAD are a reflection of the datasets that have been found to date by PAD staff, not the actual state of fish passage in streams. Refer to "Data Quality" (dataqual) for information regarding data quality and limitations of this dataset. The PAD was intended to track the anadromous fish passage assessments in California; however, over time passage assessments related to non-anadromous species and some passage assessments outside of California have been added to the PAD. Per the current PAD data standards, https://nrmsecure.dfg.ca.gov/FileHandler.ashx?DocumentID=78802, both will be maintained in the dataset but not added to the PAD anymore. Additionally, it should be noted that many fish passage assessments recorded in the PAD are outside of the current species range and within their historical range. National Oceanic and Atmospheric Administration’s (NOAA) Distinct Population Segment boundaries, http://www.westcoast.fisheries.noaa.gov/maps_data/species_population_boundaries.htmlc, along with the PAD, can be used to indicate barriers below major rim dams and within the species current geographic area.
Since the inception of the Passage Assessment Database, funding for the compilation of these data have been provided by the California Coastal Conservancy, U.S. Fish and Wildlife Service (USFWS), NOAA Fisheries and the California Department of Fish and Wildlife (CDFW). The CDFW Fisheries Restoration Grant Program is one of the most recent and longest funders of the PAD. The USFWS has recently provided funding for the compilation of miles upstream, etc. Pacific States Marine Fisheries Commission staff manage and compile data into this dataset. Datasets were collected and supplied by multiple agencies and organizations, and the PAD would not be possible without these datasets (see the "Source Citation" element (srccite) for more information). We would like to thank Daniel Wieferich from the United States Geological Service for metadata support. He reviewed and edited the metadata for compliance with the Federal Geographic Data Committee Content Standard for Digital Geospatial Metadata.
Since the inception of the PAD in 2002, passage statuses (BarStatus field attributes (i.e., total, temporal, partial)) came from various data sources (from fish passage surveys to professional judgement) and people with varying degrees of fish passage knowledge. For a majority of the PAD records, professional judgement is used as the protocol for determining passage status. In early 2013, new PAD data standards were developed and implemented for new records and the person that made the professional passage status determination began to be tracked. Prior to this, only the name of the agency that made the passage status determination was tracked and because there are many references from the same agency for each PAD record, tracking the person that made the determination was difficult. To deal with the differences in the level of fish passage expertise and the potential for receiving fish passage determinations and assessments by persons with little to no fish passage experience; new PAD data standards were developed in regards to who determines fish passage. The new PAD data standards dictate that if the passage status was not determined by a fish passage professional, the passage status will be listed as unknown until a fish passage professional has confirmed or disputed the sources’ passage assessment. Since 2013, professional fish passage experience from the person that assessed passage at the site if not specified in the assessment report is requested in order to meet this PAD data standard, and is tracked in the database. Prior to 2013, when a barrier had been remediated by adding a fishway or by another modification, the passage status of that PAD record was changed to "not a barrier" unless otherwise specified by the data source. In order to track the success of the fish passage improvement projects and assess whether the site still impedes passage, a new passage status called "remediated, fish presence unconfirmed" was developed and used until such time qualitative (photo) or quantitative (fish counts) data was provided to the PAD to confirm that it is indeed not a barrier to fish passage. The PAD Data Standard is used to ensure the accuracy of the passage status and location attributes for all new records added and updated in the PAD since 2013.
The Passage Assessment Database was compiled using information about fish passage from a large number of sources. These datasets used by the PAD were originally created for a number of different purposes, from general stream habitat surveys to rigorous assessments of fish barriers. The quality of the data in the PAD will vary depending on the data source, including different amounts of accuracy of fish passage information, detail and varying degrees of accuracy in location descriptions. See to "Attribute Accuracy" (attraccr), "Horizontal Positional Accuracy" (horizpar) and "Completeness" (complete) reports for more detailed explanations. For a list of data sources, refer to "Online Link" (onlink). Since many datasets overlapped in their geographic range, information about the same barrier could sometimes be found in several different datasets. In most cases, the duplicates were identified during data entry or in subsequent data quality evaluation. However, the dataset may still contain a slight overestimate of the numbers of known and potential barriers.
The PAD strives to keep the data as current and updated as possible, however, there can be a lag between on the ground projects and when that information is entered into the PAD. The data in the PAD are a reflection of the datasets that have been found to date by PAD staff, not the actual state of fish passage in streams. For example, the PAD includes very comprehensive data about passage barriers in some watersheds but not in others. This does not mean that there aren’t many barriers in the other watersheds, but rather that the PAD does not yet include comprehensive barrier data for these watersheds. Many datasets have no assessment of whether the inventoried structures are barriers to fish passage, if and when they were surveyed, and whether the structures are partial, temporal or total barriers. Non-surveyed structures are listed as “unassessed” and may need a formal assessment. Other structures were surveyed for fish passage, but passage status was indeterminate; therefore, many are listed as “unknown” passage status. FishXing can assist with a passage determination for those determined indeterminate at time of survey. Many original datasets are missing other information that should be included in the passage assessment database. For example, many datasets do not have species information indicating which species (and life stage) are blocked by the barrier and the level of blockage (i.e., temporal or total). In some cases, the original datasets include this information, but this information was not added to the PAD.
The PAD Data Standard is used to ensure the accuracy of the location attributes in this dataset. Per the data standard, the PAD Administrator verifies with the data source that the coordinates are precise and where not precise, asks for the bank location and distance in feet from the coordinates, and standardizes all PAD locations by tying them to hydrography. All records in this dataset are stored with geographic location information. Each barrier record is indexed to the High-resolution National Hydrography Dataset (NHD) developed by USGS at roughly 1:24,000 scale (24K NHD). The NHD was used to assign a stream address to a PAD record. Using the ‘Locate feature along route’ command in ESRI's ArcGIS 9.3 and later versions, each barrier was assigned a position along the measured stream network by capturing the unique identifier for each line segment and the measure along the segment that represents the barrier location. When aligned to the 24K NHD, points were shifted from the coordinates given in the original dataset to the 24K NHD. For this reason, the locations in PAD may not reflect the actual location of the point, structure or barrier. Original coordinates are kept with the original data set. Additionally, some locations were snapped to the wrong stream and these were not diligently checked. The PAD Data Standard reduces this error for all records added in the PAD since 2013, by verifying that the snapped barriers are on the correct stream and road route/post-mile (if applicable). The stream name in the PAD comes from the source datasets and is generally more accurate than the stream name that the record has been snapped to. Opportunistically, stream names in existing PAD records are compared with the name of the stream that the barrier is snapped to, the source documentation is reviewed and the locations are corrected. Location errors in the entire dataset will need to be identified and corrected in 2015-2016. In some cases, the datasets do not have very precise location information. For example, some stream surveys only mention that there is a barrier or structure within a defined reach of stream, making it impossible to pinpoint the barrier location. Structures described in this way are maintained in GIS as linear geospatial files. For the purposes of creating one point feature spatial file, all linear locations were converted to a single point at the beginning of the linear stream reach. Some datasets describe locations using the distance of the structure from the stream mouth (i.e., river mile) – these were digitized using this measure on the hydrography. Since the 1: 24,000 hydrography may not follow the exact course of the stream and stream measures may not be precise, measured distances along a stream may not reflect reality. This has caused location errors and led to duplicate barrier entries. Errors are minimized by referencing structures to other landmarks whenever possible.
A formal accuracy assessment of the vertical positional information in the data set has either not been conducted, or is not applicable.
The PAD has received and retrieved 811 reference documents and datasets that have been used to add and update information in this dataset. The input datasets that have contributed to and gone into the PAD, include spatial data, electronic data files, assessment reports, surveys and data retrieval forms, personal communication, grant proposals, news clips and websites, etc. These datasets have contributed to the fish passage assessment data that is in the PAD.
1. Gather fish passage assessment data. Retrieve and request fish passage assessment and fish passage improvement project information from multiple agencies and organizations. Acceptable data formats include geospatial data or other electronic data files, assessment reports, survey and data retrieval forms, personal communication, grant proposals, news clips or websites, etc. Data retrieval includes use of applications (i.e., PAD review application) and data forms, and outreach to multiple organizations including presenting at conferences, conducting training and review sessions and sending direct requests for data through email. The location or Passage ID, structure type, passage status, contact information of the data submitter, information regarding fish passage expertise of the person that determined fish passage status, and a description of the treatment (if applicable) that occurred are required prior to data entry into the PAD. Prior to 2013, some of this information was requested but not required and thus not entered into the PAD. For the most part; location, passage status and structure type were received and entered into the PAD. Protocol used was requested if it was not clear by the reference material provided. Other information not-required by the PAD, is requested by the PAD Administrator in order create a comprehensive record of fish passage constraints to assist restoration practitioners and PAD users. This other information requested includes site/barrier description including size of the structure, velocity issues, fishway presence and status, survey specifics, observation of fish downstream or upstream prior to barrier removal, species and life stage blocked or benefited from treatment, and structure and landowner information.
2. Review fish passage assessment data received and compile data into the PAD. Beginning in 2013, fish passage assessment data received are reviewed and compiled into the PAD following steps i through iii. i. Request fish passage experience from the person that assessed passage at the site if not specified in the assessment report. Use a standard form for retrieving the persons' professional experience in fish passage available online at: https://nrm.dfg.ca.gov/FileHandler.ashx?DocumentID=87996. If the assessment of passage status did not come from a fish passage professional, list the passage status as unknown until a fish passage professional has confirmed or disputed the sources’ passage assessment. ii. Check that the data received includes passage status. A structure or non-structural element (i.e., waterfall, grade, temperature, etc.) will be added to the PAD and listed as ‘unassessed’ passage status if the passage status is unknown and if the barrier is a probable or potential barrier and hasn’t been assessed. For instances where barriers are probable partial or total barriers, this information will be added to the site comments. For a structure or non-structural element that has been assessed for fish passage but passage status was unable to be determined; the passage status will be listed as "unknown". USFS Grey filter category (i.e., indeterminate) is an example of this. For fish passage improvement projects, request qualitative (e.g., photos of fish above the barrier) or quantitative (fish counts above the barrier) evidence that the structure is no longer a barrier to fish passage. Quantitative or qualitative evidence will need to be received by the PAD Administrator prior to changing passage status to ‘not a barrier’. Otherwise, passage status will be listed as ‘remediated, fish presence unconfirmed’. iii. All barriers and diversions will be subject to the Quality Assurance and Quality Control (QAQC) procedures listed below (a-d), to the extent that this is possible. The QAQC procedures include verification of location information and steps for the prevention of duplicate barriers and diversions in the PAD. a) When receiving barrier and diversion information, use ESRI's ArcMap (9.x or later versions) to decide if these are new barriers and diversions that need to be added to the PAD. Look at existing PAD barriers and diversions within proximity of this new site, compare photos, site names, structure owners, passage statuses, passage types and site comments. If it is still difficult to determine if this is a new site, request more information from the source. In many cases, existing barriers in PAD are incorrectly located and can often be off more than several hundred feet. b) Verify with the source that the coordinates are precise (i.e., taken on top of the barrier) and ask for the datum used if not provided. If the latitude/longitude coordinates aren’t precise, ask for the barrier or diversion bank location (looking downstream) and distance in feet from the GPS coordinates. Also, ask why these coordinates aren’t precise. c) When sources send information that have may have duplicate information, send an email back to the source addressing these issues. d) Standardize PAD locations and tie them to hydrography. Refer to the text below for the process and explanation for standardizing locations of PAD records including assumptions the PAD utilizes. The PAD records in this geospatial dataset only include records with geographic location information. Barrier records are indexed to the High-resolution National Hydrography Dataset (NHD) developed by United States Geological Survey at a 1:24,000 or finer scale. The NHD was used to assign a stream address to a PAD record. Using the ‘Locate feature along route’ command in ArcGIS 9.3 and later versions, each barrier was assigned a position along the measured stream network by capturing the unique identifier for each line segment (ComID) and the measure (NHDComMeas) along the segment that represents the barrier location. When the stream is not digitized in the NHD, the PAD record retains the location that was provided by the original data source. In the database, this is tracked (i.e., 24k hydrography not digitized) in a separate field. Since some of the fisheries related datasets in California are tied to the LLID-based routed hydrography of a 1:100,000 scale (rather than the NHD), the PAD is also available in a format compatible with the LLID hydrography. For the purposes of creating one point feature spatial file, all linear locations were converted to a single point at the beginning of the linear stream reach. Downstream ends of linear barriers such as flood control channels, gradients or low-flow sections were digitized as points, based on the assumption that the adult fish swimming upstream will have to deal with the downstream end of a barrier first. The length of the linear barriers can be found in the site comments/notes for each. All geographic data that are received for use in the PAD are saved in their original format as well as in their final standardized format. If there are any problems with the PAD data, it will always be possible to return to the original dataset for a solution. When aligned to the 24K hydrography, points were shifted from the coordinates given in the original dataset to the 24K NHD. For this reason, the locations in PAD may not reflect the actual location of the point, structure or barrier. Beginning in 2013, the streams that the barriers were snapped to were reviewed to see if they match the stream name and road route/post-mile (if applicable) per the original/source dataset, and the locations of the snapped PAD records were moved accordingly. Also, the locations of all new and updated barriers were revised so that they are on top of the barrier or close to the barrier per aerial imagery but still aligned to the 24K hydrography. If there is more than one barrier at the same location and it’s the same barrier type, this will be captured in one PAD ID and the number of barriers will be added to a new field. If the passage statuses differ between these barriers, the lower level passage status will be associated with the PAD ID and the passage statuses of all barriers will be noted in the site comments. For example, if there are two culverts next to one another under the same bridge one that is a total barrier and the other that is a partial barrier, this will be combined into one PAD ID (i.e., one point) and listed as a partial barrier. The site comments will contain the passage status of both culverts.
3. Compile other locational specific information using ArcGIS. Using ESRI's ArcGIS 9.x and later versions, perform spatial joins on PAD records with county and watershed datasets to obtain attributes from these datasets and add them to the PAD.
4. To assist with coarse filtering of large number of barriers for restoration consideration and to enable the optimization model being developed by the California Fish Passage Forum, additional fields were added to the PAD geospatial file. These fields were derived from tracing the high-resolution National Hydrography Dataset upstream and downstream from a barrier. These fields are periodically updated, with the most recent update on July 30, 2013. The fields include the number of downstream and upstream barriers, the order of the barrier on a stream network (“1” would be the most downstream barrier), and miles upstream and downstream to the next barrier or limit of anadromy, if applicable. Only known barriers were used for the analysis; barriers with unknown passage status, unassessed structures, non-barriers, diversions and sites where remediation occurred but fish presence is unconfirmed were excluded from the analysis. Barriers outside of the NOAA’s Steelhead Distinct Population Segment boundary as of January 2013, and those areas that were determined to be anthropogenically blocked by NOAA, were excluded from this analysis. Many of these derived fields from this analysis do not reside inside of the PAD, but they have been added to this geospatial dataset.
The entity and attribute information provided here describes the tabular data associated with the data set. Please review the detailed descriptions that are provided (the individual attribute descriptions) for information on the values that appear as fields/table entries of the data set.
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.
There are no legal limitations of use associated with this dataset. This PAD geospatial file is a public dataset.