Data Management Plan
GUID: gov.noaa.nmfs.inport:40077 | Published / External
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
These data were collected by the SHOALS-1000T(Scanning Hydrographic Operational Airborne Lidar Survey)system which consists of an airborne laser transmitter/receiver with a 1kHz. bathymetric laser and a10 kHz topographic laser. The system was operated from a Beechcraft King Air 90aircraft. Data were collected with the bathymetric laser while flying at altitudes of about 400 meters and a groundspeed of about 124 knots. The topographic laser data was collected at altitudes of about 700 m and a groundspeed of 150 kts. One KGPS base stations was used during processing of the dataset. The SHOALS system includes a ground-based data processing system for calculating accurate horizontal position and water depth / elevation. LIDAR is an acronym for LIght Detection And Ranging. The system operates by emitting a pulse of light that travels from an airborne platform to the water surface where a small portion of the laser energy is backscattered to the airborne receiver. The remaining energy at the water\x92s surface propagates through the water column and reflects off the sea bottom and back to the airborne detector. The time difference between the surface return and the bottom return corresponds to water depth. The maximum depth the system is able to sense is related to the complex interaction of radiance of bottom material, incident sunangle and intensity, and the type and quantity of organics or sediments in the water column. As a rule-of-thumb, the SHOALS 1000 system is capable of sensing bottom to depths equal to two or three times the Secchi depth. Topographic elevations are gridded in this dataset.
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.
4. Resources
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):
Process Steps:
- 2005-05-20 00:00:00 - The SHOALS airborne system acquires a tremendous volume of raw data during a single mission. The lidar data are unique and require a specialized Ground Control System (GCS) for survey planning and post-processing. The GCS main functions1) import airborne data stored on removable hard drives;2) perform quality control checks on initial depths and horizontal positions;3) provide display and edit capabilities;4) calculate depth and position (XYZ) values for each sounding; and5) output final positions and depths for each sounding. The GCS possesses an automated capability to post-process the data to obtain corrected depth and horizontal positions within the specified system accuracies. This is accomplished by accurately identifying the surface and bottom returns from the airborne data. Depths are determined by computing the time difference between the arrival of the surface and bottom returns. Corrections are computed and applied for depth biases associated with light propagation, water level fluctuations, and various inherent system characteristics. Surface waves are modeled and removed so that depths can be referenced to a common mean water surface. Applying tidal corrections and/or KGPS corrections then produces a depth referenced to a known datum. A manual processing capability also allows evaluation of anomalous data by providing display and edit functions of sounding data and system parameters. Digital photos collected once per second (and easily viewed during editing) permit visual scrutiny of the area to aid the hydrographer in deciding whether to exclude suspect data from further processing. Output from the GCS is a digital data set of XYZ(positions/depths) for each laser sounding that is compatible with most GIS and other contouring and mapping systems.
- 2006-04-01 00:00:00 - Both positional information and project control for the LIDAR survey were supplied by the KGPS in the ellipsoidal datum of NAD83.For ease of merging the data set with existing multibeam sounding data, survey instructions required the data to be projected during post-processing and delivered in the UTM Zone 10 projection. The Geoid99 height model was used to convert the vertical datum from the ellipsoidal 3-D datum of NAD83 to the orthometric vertical datum NAVD88. But to accurately merge the LIDAR data with existing multibeam sounding data, the data sets must obviously be in the same vertical reference frame (Milbert 2002).Since the multibeam sounding data were referenced to an averaged tidally-derived vertical datum (MLLW) and the LIDAR data were referenced to an orthometric vertical datum (NAVD88) based on Mean Sea Level (MSL), a VDatum model (Spargo et. al 2006)was used to vertically transform the LIDAR data to MLLW for compatibility and comparison with the multibeam sounding data. The VDatum model relates the NAVD88 to MLLW by using a grid, or zone, of tide model comparisons with known leveled tide benchmark stations to better account for the spatial variability of tidal dynamics over a given area (Milbert 2002;Spargo et. al 2006). The VDatum model that was used is available for download athttp://chartmaker.ncd.noaa.gov/csdl/vdatum_projectsWA.htm.
(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.
Missing/invalid information:
- 1.7. Data collection method(s)
- 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.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.
None
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.