Data Management Plan
GUID: gov.noaa.nmfs.inport:49764 | 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
Acquisition of Light Detection and Ranging (LiDAR) elevation data was for the Hurricane and Storm Damage Risk Reduction System (HSDRRS). In February 2012,
USACE, Contracting Division contracted with The Atlantic Group to provide acquisition of Light Detection and Ranging (LiDAR) elevation data in the Hurricane and Storm Damage Risk Reduction System, St. Charles, Jefferson, Orleans, St. Bernard and Plaquemines Parishes, LA. This data will be used to support interior drainage modeling. LiDAR data should be collected to fully capture the total interior of the HSDRRS, including floodwalls, structures, and levees, and 200 feet outside of the HSDRRS to water's edge as appropriate. The project shall include capture of LiDAR data and the creation of digital elevation models derived from the LiDAR. The project area is approximately 418.4 sq. miles, including a 200' buffer. The purpose of the survey is to obtain measurements of the bare ground surface, as well as top surface feature elevation data for providing geometry input to USACE hydrodynamic and other numerical models as well as for performing economic related assessments.
Upon receipt of data, the NOAA Office for Coastal Management (OCM) noted that many areas have lidar points over water that are classified as ground. This was mainly seen in lidar points over Lake Pontchartrain. In these areas, those points were reclassified from ground (2) to unclassified (1). In other areas, however, the user should be aware that points over water may be classified as ground.
In addition to the lidar point data, bare earth Digital Elevation Models (DEMs), at a 2 ft grid spacing, created from the lidar point data are also available. These data are available for download here: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6352
Breaklines created from the lidar are also available for download in shp format at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/6350/breaklines
The DEM and breakline products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA, OCM or its partners.
Original contact information:
Contact Name: Patrick Robinson
Contact Org: Atlantic Group
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):
- 2012-01-01 00:00:00 - The ABGPS, IMU, and raw Optech LiDAR data are integrated into the Optech post processor software. The resultant file is in a LAS binary file format. The LAS file version 1.2 format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the geodetic coordinates referenced to the NAD83 horizontal datum and NAVD88 2004.65 vertical datum.
- 2012-01-01 00:00:00 - The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters is applied as appropriate for the production of bare earth digital terrain models (dtms). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as define by the LAS 1.2 specification. The data was classified as follows: Class 1 = Unclassified. This class includes all non-ground classified points. Class 2 = Ground. Class 7 = Low Points. Class 9 = water. Class 12 = Overlap.
- 2012-01-01 00:00:00 - Conversion from Geodetic coordinates NAD83 into Louisiana state plane zone 1702 using NAD83 and conversion from ellipsoid heights (meters) into orthometric heights using NAVD88 (US Survey Foot). Files are orthogonally tiled based to a 1500m x 1500m extent, and labeled with a "Tile_ID" attribute.
- 2017-08-15 00:00:00 - The NOAA Office for Coastal Management (OCM) received 525 files in las 1.2 format. LAS files from the 2004.65 folder were processed. The files contained lidar intensity and elevation measurements for the USACE HSDRRS project area. The data were in LA State Plane, Zone 1702 (NAD83 2007) coordinates and in NAVD88 elevations in feet. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The data were converted from las to laz format. 2. Spaces in the filenames were converted to underscores. 3. The LAStools software scripts lasinfo and lasvalidate were run on the las files to check for errors. 4. The data were converted from GPS seconds of the week to adjusted GPS time. 5. In 46 files, reclassified points that were over Lake Pontchartrain from ground (2) to unclassified (1). 6. Reclassified outlier elevation points (greater than 2000 ft and less than -100 ft) to noise (7). 7. Internal OCM scripts were run to convert the files from LA State Plane Zone 1702 coordinates to geographic coordinates and to convert from NAVD88 elevations in feet to ellipsoid elevations in meters using Geoid09. 8. Internal OCM scripts were run on the las files to assign the geokeys, to sort the data by gps time and zip the data to database and to http.
(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.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.
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.
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6350;
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.