Data Management Plan
GUID: gov.noaa.nmfs.inport:72980 | 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
The Project data set consists of the Classified Point Cloud. The geographical extent of this dataset extends to the LA_Catahoula_Concordia_2017_D17 D3 boundary, approximately 5,160 square miles. The parishes included in this dataset are: Catahoula, Concordia, Avoyelles, Pointe Coupee, St. Martin, and portions of St. Landry, Lafayette, Acadia, Iberia, and Vermillion.
Ground Conditions: water at normal levels; no unusual inundation; no snow; leaf off. How the Withheld Points are Identified: Withheld (ignore) points were identified in the files using the standard LAS Withheld bit.
This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services. The following are the USGS EPT files being accessed:
LA_Catahoula_Concordia_1 (D1, Work Unit 74197)
LA_Catahoula_Concordia_2 (D2, Work Unit 208932)
LA_Catahoula_Concordia_3 (D3, Work Unit 211679)
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):
Lineage Statement:
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tiles (EPT) hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.
Process Steps:
- 2018-03-23 00:00:00 - Aerial LiDAR Acquisition: LiDAR acquisition was done using Hardy-Anders Field Nachez Admas County Airport(KHEZ) as the base airports. DAS used two dedicated GPS base station located at the respected airports to support the aerial LiDAR acquisition. DAS used Leica's Terrian Mapper LiDAR Sensor (SN90524) for the acquisition.
- 2019-05-22 00:00:00 - LiDAR Data Processing: Inertial Explorer 8.9 software was used to compute inertial solution file (*.sol) for each mission using ground GPS base station. The resulting solution was checked to ensure a minimum accuracy of +/- 0.05m, combined separation, for horizontal and vertical positions. Inertial Explorer methodology integrates Inertial Navigation Solution by processing the GPS data and Inertial Measurement Unit (IMU). The software applies the reference lever arms for the GPS and IMU during the process to determine the trajectory (position and orientation) of the LiDAR sensor during the acquisition mission. Inertial Explorer generated graphical results was reviewed to ensure that the IMU data was healthy. These results are found in Appendix D. Raw LiDAR sensor ranging data and the final solution sensor trajectory (*.sol), from Inertial Explorer, were processed in Leica’s Cloud Pro software to produce LiDAR point cloud swath for each flight line in LAS version 1.4 file format. Quality control of the swath point cloud was performed to validate proper functioning of the sensor system, full coverage of the project area and point density of the LiDAR data. Swath point clouds were assigned unique file source identification. The data was found to be complete and consistent with the sensor calibration parameters.
- 2020-07-22 00:00:00 - LiDAR Calibration:HxMap is the common workflow platform for Leica airborne sensors. The processing workflow involves; Ingest, Block Creation, LiDAR Matching, Quality Assurance (QA) and Product Generation. LiDAR is processed in HxMap by generating point clouds from raw sensor data during the Ingest step. Noise filtering, sensor installation calibration and atmospheric condition parameters are also applied during the ingest process. Once all data is processed through ingest, they are assembled into a block for LiDAR Matching. The LiDAR Matching step resolves LiDAR registration errors which remain in the point clouds after sensor and installation calibration parameters are applied in the ingest step. QA tool is run on the Block after LiDAR Matching to verify quality of results. QA results are reviewed to ensure that, 95% of patches less thand 5cm for Vertical Scan Direction and Vertical Line Separation. Ground control points are also included to assess absolute accuracy for the point cloud data. LiDAR products are finally generated in the Product Generation step as LAS swaths (LAS 1.4). Vertical (Z) shift (calculated from QA step) is also applied during the product generation.
- Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and no changes were made to the vertical (NAVD88 GEOID12B meters).
- 2024-06-14 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tiles (EPT) that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. These are the AWS URLs being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/LA_Catahoula_Concordia_1_2017/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/LA_Catahoula_Concordia_2_2017/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/LA_Catahoula_Concordia_3_2017/ept.json
(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)
- 3.1. Responsible Party for Data Management
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/LA_Catahoula_Concordia_2017_D17/
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk and custom downloads.
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
Data is backed up to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.