Data Management Plan
GUID: gov.noaa.nmfs.inport:49832 | 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
Airborne LIDAR terrain mapping data acquired January through March 2003. Point data (XYZ) in ASCII format. Horizontal datum NAD83(1995) North Carolina State Plane feet. Vertical datum NAVD88 US Survey Feet. These data may represent a single geographic tile of a larger, county/sub-county data set. As such, the map extent indicated in the Spatial_Domain element is representative of the larger data set and not an individual tile. The data are organized in 10,000 ft x 10,000 ft tiles using the NC Bureau of Land Records Management (LRMP) standards. Specific information about individual data tiles is included in the data delivery index. LAS tiles were received at NOAA OCM.
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:
- 2003-12-22 00:00:00 - All data collection flights were initialized and finalized during periods of GPS Position Dilution of Precision greater than 4. GPS data quality was evaluated post-flight to ensure sufficient quality for LIDAR data requirements and integration. GPS base maximum allowable distance between stations was established such that no more than a 50 mile radius occurred between occupations. Swath width of terrain covered in a single flightline at an altitude of 10,000 feet AMT was approximately 3,173 meters. Field of View for the Leica GeoSystems Aeroscan system used was 55 degrees project wide, or approximately 27.5 degrees from nadir with a maximum of 5 returns collected for each pulse. Nominal post spacing for finalized Bare Earth product was 2 meters. An average of 10-20 rapid static GPS survey collected ground control points were established per base airport project wide to detect and correct horizontal and vertical bias. Typically, 3 or more flightlines of LIDAR returns were collected for each airport lift, one of which being bi-directional for use in optimizing instrument boresight angles to account for aircraft pitch, yaw and roll. All post process collection quality assurance is achieved aided by airport cross and bi-directional flightlines, entire lift cross flightlines, and the use of surveyed ground control points.
- 2003-12-22 00:00:00 - - Checking for coverage and anomalies - Airport calibration - Production flightline calibration - Removal of blunders
- 2003-12-22 00:00:00 - Tiling, Automated filtering for point classification, Manual editing to classify points, Quality control
- 2006-04-26 00:00:00 - The methods used to develop these data for the North Carolina Floodplain Mapping Program are documented in LIDAR Bare Earth Mass Points and Breaklines Technical Document.
- 2016-02-26 00:00:00 - The lidar point data were received by the NOAA Office for Coastal Management from USGS CLICK. The data were LAS format, horizontal datum NAD83 North Carolina State Plane (3200) feet, vertical datum NAVD88 US Survey Feet and contained elevation, intensity measurements and classifications. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from State Plane coordinates to geographic coordinates in decimal degrees. 2. The data were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03.
(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.6. Type(s) of 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.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.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5010/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5010;
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.