Data Management Plan
GUID: gov.noaa.nmfs.inport:51633 | 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
This Light Detection and Ranging (LiDAR) dataset is a survey of the Pocomoke and Atlantic Coastal Watersheds in Maryland. The project area consists of approximately 500 square miles. The project design of the LiDAR data acquisition was developed to support a nominal post spacing of 0.70 meter. Fugro EarthData, Inc. acquired 151 flight lines in eight lifts on February 6, 7, 9, 13, 15, and 16, 2011; in tidal areas, data was collected within 2 hours (before or after) of mean low tide. The data was divided into 1500 by 1500 meter cells that serve as the tiling scheme. LiDAR data collection was performed with a Piper Navajo twin engine aircraft, utilizing a Leica ALS60 MPiA sensor, collecting multiple return x, y, and z as well as intensity data. LiDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. This data of the Pocomoke and Atlantic Coastal Watersheds in Maryland, was collected at sufficient resolution to provide a nominal point spacing of 0.70 meter for collected points. Up to 4 returns were recorded for each pulse in addition to an intensity value.
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):
Original acquisition and processing of lidar data was completed by Fugro EarthData, Inc. and delivered to NRCS and Maryland. NOAA OCM obtained the data from Maryland iMAP and modified for ingest into the Digital Coast system.
- 2011-06-27 00:00:00 - Fugro EarthData utilized commercial software as well as proprietary software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain features were filtered out, the data was either run through a different filter or was corrected during the manual filtering process. Interactive editing was then completed in 3D visualization software which also provides manual and automatic point classification tools. Vegetation and artifacts remaining after automatic data post-processing were reclassified manually through interactive editing. The hard edges of ground features that were automatically filtered out during the automatic filtering process were brought back into ground class during manual editing. Auto-filtering routines were utilized as much as possible within fenced areas during interactive editing for efficiency. The technician reviewed the LiDAR points with color shaded TINs for anomalies in ground class during interactive filtering. Upon the completion of peer review and finalization of bare earth filtering, the classified LiDAR point cloud work tiles went through a water classification routine. Upon the completion of finalization of the classified LiDAR point cloud work tiles, the tiles were reprojected to NAD83 (HARN), UTM zone 18 north, meters; NAVD88, meters, using GEOID09 and cut to the approved tile layout in LAS format.
- 2011-06-24 00:00:00 - The hydrographic features were collected as vector linework using classified LiDAR datasets, intensity images, shaded-relief TIN surfaces, and contours. These features were classified as Inland Ponds and Lakes, Inland Streams and Rivers (single line), Inland Streams and Rivers (double line), Non-Tidal Boundary Waters, and Tidal Waters. After initial collection, linework was then checked for the following topological and attribution rules: non-bank lines must be digitized from an uphill to downhill direction, lines must be attributed with the correct feature code, dangles must exist only at the upstream headwater end of streams and at the downstream outfall, line intersections must be at nodes, non-bankline features must form a dendritic collection network, lakes that have a digitized inflow path must have a centerline as well, lakes that have a digitized outflow path but do not have a digitized inflow path should not have a centerline, isolated ponds that are not part of the drainage network should not have centerlines; lake and stream banklines must form closed polygons, single streams should not fall within bankline polygons and lake and stream connector lines should not fall outside of bankline polygons. Hydro features were collected as vector linework using LiDAR and its derived products listed above. This linework is initially 2D, meaning that it does not have elevation values assigned to individual line vertices. Vertex elevation values were assigned using a distance weighted distribution of LiDAR points closest to each vertex. After the initial 'drape', the linework elevation values were further adjusted based on the following rules: lake feature vertices were re-assigned (flattened) to lowest draped vertex value; lake connector line vertices were re-assigned (flattened) to lowest draped vertex value of the surrounding lake bankline, single stream and stream connector line vertices were adjusted so that subsequent vertices are lower than previous ones based on line direction, and double stream bankline vertices were re-assigned based on the vertices of the closest adjusted double stream connector line. After assignment of 3D values, the stream network is checked to ensure the following does not exist: large differences between initial drape and adjusted elevation values, elevation differences between nodes, and elevation values flowing in an 'uphill' direction. Data was provided to the terrain department for hydro-enforcement of the DEM.
- 2017-10-16 00:00:00 - NOAA OCM downloaded the data from Maryland iMAP as zip files by Block. (Citation: Lidar data from Maryland iMAP)
- 2018-02-26 00:00:00 - Lidar data were changed from NAVD88 (Geoid09) vertical coordinates to ellipsoid heights using the GEOID09 grids. The class scheme was not described in the original metadata, but research on the related data for the Worcester coastal area suggests class 10 is ignored ground near breaklines and class 11 is withheld. Examination of the data supports that hypothesis. Data were then ingested into the Digital Coast Data Access Viewer system for distribution.
(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.
- 2.4. Point of Contact Email
- 3.1. Responsible Party for Data Management
- 5.2. Quality control procedures employed
- 7.4. Approximate delay between data collection and dissemination
- 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.
Access via online tool
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.