Data Management Plan
DMP Template v2.0.1 (2015-01-01)Please provide the following information, and submit to the NOAA DM Plan Repository.
Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
Critical habitat includes the stream channels within the designated stream reaches, and includes a lateral extent as defined by the ordinary high-water line (33 CFR 329.11). In areas where the ordinary high-water line has not been defined, the lateral extent will be defined by the bankfull elevation. Bankfull elevation is the level at which water begins to leave the channel and move into the floodplain and is reached at a discharge which generally has a recurrence interval of 1 to 2 years on the annual flood series. Critical habitat in estuaries is defined by the perimeter of the water body as displayed on standard 1:24,000 scale topographic maps or the elevation of extreme high water, whichever is greater.See the final rule (70 FR 52488) for descriptions of areas excluded from this critical habitat designation. Economic exclusions were clipped out of the data. Military areas ineligible for designation due to qualifying Integrated Natural Resources Management Plans (INRMPs) and excluded due to national security impacts were not clipped out of the data.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
- 2005-08-15 00:00:00 - Data creation process 2005. sc_steelhead_ch_06_2005.shp Stream segments were identified and assigned attributes by Southwest Region (SWR) biologists using 1:100,000 hydrography data and other basemap information on hard copy maps. SWR biologists divided the routed hydrography into stream segments using the best available information to represent local steelhead distribution and habitat. The segments' upper and lower extents were manually marked onto the basemaps by the biologists. This information was then visually interpreted from the paper maps and entered into a digital format using the "Route Tools" extension provided by CDFG. The resulting event table was then used with the CDFG routed hydrography as the route reference to create routed events based on the biologists' segment determinations. The table containing the accompanying segment attribute information was joined using 'GIS_Link' as the related field, and the shapefile 'CH_SC_Steelhead' was created from the routed events. To minimize errors that may have occurred during the process, the completed digital file was compared against the marked maps for consistency. The biologists also reviewed the completed digital file to ensure attribute information was associated with the correct stream segments. Biologists rated each Calwater (California Watershed Map) Hydrologic Sub-area (HSA) based on occupancy and habitat quanitity and quality information found in the steelhead distribution shapefile (CH_SC_Steelhead). These biological ratings were compared against economic values given to each HSA. Based on whether selected criteria were met, an HSA was determined to be included or excluded from critical habitat. All stream segments were then coded to reflect their HSA's designation. The only exceptions to this occured when a stream segment was valued as a migration corridor (the segment would be included as critical habitat even if the HSA was excluded) or if there were other overriding biological considerations. Those segments coded as critical habitat were then extracted from the distribution shapfile and placed in the resulting 'SC_Steelhead_Proposed_Critical_habitat' file. Public comments were received following draft publication of the critical habitat proposed rule in December 2004. These comments were incorporated into the data set and the final critical habitat file 'SC_Steelhead_CH_06_2005' was created. Data layers from the following were used during this process: California Geospatial Information Data Library, State Coastal Conservancy, California Department of Forestry, US Geological Survey
- 2019-07-17 00:00:00 - sc_steelhead_ch_06_2005.shp (California_Teale_Albers_NAD83) geographic transformation not necessary, unprojected -> STSCA_ch.shp (GCS_North_American_1983 wkid 4269). Geometry was not edited, attributes were not edited, metadata was edited.
- 2021-04-26 00:00:00 - The 2019 version STSCA_ch.shp (GCS_North_American_1983 wkid 4269) was converted into the standardized feature class Steelhead_SouthernCaliforniaDPS_20050902 (GCS_WGS_84 wkid 4326) using the National Critical Habitat Geodatabase processing protocol. During standardization, geometry was not edited. Attributes were edited. Metadata was edited and populated using the final rule/CFR and the source sc_steelhead_ch_06_2005.shp (California_Teale_Albers_NAD83). Migrated fields: "STREAM" into "UNIT" (edited stream/river names to standardize text; the names in the original source file did not match the names in the final rule; generally entire drainages were named the same, populated names using NHD name where possible, deleted if unnamed), SPAWNHAB (value = yes) + REARHAB (value = yes) + MIGRAHAB (value = yes) into "NOTES" (values = spawning, rearing, migration) Dropped fields: FID, EVENTID, LLID, BEGFT, ENDFT, COMMENTS, GIS_LINK, ESU, BASIN, PRESENCE, QUALSPWN, QUALREAR, QUALMIGR, ESTUAHAB, QUALESTU
(describe or provide URL of description):
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
- 1.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the data
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.2. Data storage facility prior to being sent to an archive facility
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.