Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:49831 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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 airborne LiDAR terrain mapping data was acquired in the spring of 2001. The data were collected for the floodplain mapping program for the state of North Carolina. The data were collected for the state in three phases: 1, 2, and 3. This metadata record describes that data that were in phase 1 of collection and fall within the Cape Fear and Lumber River Basins in central and eastern North Carolina. This area consists of 30 counties which are listed below in the Place Keywords field.
The data were received by the NOAA Office for Coastal Management from the U.S. Geological Survey (USGS) Center for Lidar Coordination and Knowledge (CLICK). For data storage and Digital Coast provisioning purposes, the OCM converted the data to geographic coordinates and ellipsoid (Geoid99) elevations. The data are unclassified.
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:
- 2002-05-31 00:00:00 - Production Narrative: Data collected were processed to determine that valid GPS values were achieved on all flights. The flight data was processed using proprietary automated algorithms that calculate the x, y, and z value of each point by combining GPS position of the aircraft, IMU attitude of the aircraft, range of the laser pulse, and scan angle of the laser scanner. Resulting data from each flight line was then compared to crossing and bordering flight lines to identify any residual pitch, roll or yaw errors. Data were also compared to calibration flights over airports in or adjacent to the Cape Fear and Lumber River Basins. Data were then edited in TerraModel by comparing contour lines, shaded relief models (hillshading) and points clouds within tiles and from one tile to the next. Finally, the data were compared to available ground survey data prior to submitting to the State for QAQC checks.
- 2008-01-01 00:00:00 - Lidar points were supplied to the USGS EROS Center. Points received in a file format other than LAS were converted to LAS, if the data contained adequate attribute information to create a valid LAS file and without the loss of any original attribute information. The points have been re-tiled into a standard Quarter-Quad, or Quarter-Quarter-Quad, scheme for publication on the CLICK website. The data remain in the Coordinate Reference System in which they were received. No alteration of any sort, of either the geometry or attribute values or structure has been performed.
- 2023-10-03 00:00:00 - The lidar point data were originally received by the NOAA Office for Coastal Management from the USGS Center for Lidar Coordination and Knowledge (CLICK) in las format in 2012. In 2023, some of the tiles were found to be missing data. The data were reacquired from the USGS legacy data web site, no longer in a quarter quad related tile scheme. The data were reprocessed for the Digital Coast. 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. 2. The data were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid99. 3. The data were compressed in the cloud optimized point cloud version of LAZ. (Citation: Point cloud files)
(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/1399/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=1399
;
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.