Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:70012 | 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
Classified Point Cloud -- USGS task order 140G0219F0277 required Winter 2019/Spring 2020 LiDAR surveys to be collected over 20,320 square miles covering part or all of 60 counties in Georgia and 5 counties in Alabama in support of the USGS 3DEP Program. Aerial LiDAR data for this task order was planned, acquired, processed, and produced at an aggregate nominal pulse spacing (ANPS) of less than or equal to 0.71 meters and in compliance with USGS National Geospatial Program LiDAR Base Specification version 1.3. Classes include: 1 - Unclassified, 2 - Ground, 3 - Low Vegetation (0.5 - 5 ft), 4 - Medium Vegetation (5 - 20 ft), 5 - High Vegetation (greater than 20 ft), 6 - Buildings, 7 - Low Noise, 9 - Water Surface, 17 - Bridge Decks, 18 - High Noise, 20- Ignored Ground (Breakline Proximity), 22 - Temporal Exclusion
Block 1 (Work Unit 183176) - covers approximately 4273 square miles
Counties included:
Baldwin, Bibb (partial), Franklin, Gwinnett, Hancock, Hart, Jasper (partial), Jones (partial), Madison, Morgan (partial), Newton (partial), Oconee, Oglethorpe, Putnam, Stephens, Walton (partial)
Block 2 (Work Unit 183296) - covers approximately 3057 square miles
Counties included:
Chatahoochee (partial), Crisp (partial), Dooly (partial), Harris, Houston (partial), Lee, Macon (partial), Marion (partial), Schley (partial), Stewart (partial), Sumter (partial), Taylor (partial), Terrell (partial), Webster
Block 3 (Work Unit 217457) - covers approximately 6360 square miles
Counties included:
Baker (partial), Barbour, (partial), Brooks (partial), Calhoun, Clay (partial), Colquitt (partial), Cook, Crisp (partial), Dougherty, Early (partial), Grady (partial), Henry, (AL, partial), Houston, (partial), Lee, Lowndes, Mitchell (partial), Randolph (partial), Sumter (partial), Terrell, Thomas (partial), Tift, Turner (partial), Worth
Block 4 (Work Unit 223562) - covers approximately 2497 square miles
Counties included:
Baker (partial), Decatur, Early (partial), Geneva (partial), Grady (partial), Henry (AL, partial), Houston (partial), Miller, Mitchell (partial), Seminole
Block 5 (Work Unit 231249) - covers approximately 2391 square miles
Counties included:
Bibb (partial), Butts, Clayton, Fayette (partial), Henry (GA), Jasper (partial), Jones (partial), Monroe, Morgan (partial), Newton (partial), Spalding (partial), Walton (partial),
Block 6 (Work Unit 300006) - covers approximately 1634 square miles
Counties included:
Carroll, Coweta, Douglas, Fayette (partial), Heard, Spalding (partial)
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.
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.
Block 6
W: -85.72, E: -83.63, N: 32.9, S: 31.9Block 2
W: -84.51, E: -83.47, N: 33.7, S: 32.65Block 5
W: -85.95, E: -84.21, N: 31.29, S: 30.68Block 4
W: -85.43, E: -83, N: 31.93, S: 30.6Block 3
W: -84.29, E: -82.72, N: 34.71, S: 32.82Block 1
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 Tile (EPT) files 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:
- 2019-12-31 00:00:00 - Aircraft and Sensor Information and Flight Plan Execution -- Atlantic operated a PACDV (N750DV) outfitted with an Optech Galaxy Prime LiDAR system during the collection of the project area. Atlantic acquired passes of the AOI as a series of perpendicular and/or adjacent flight-lines executed in flight missions conducted between December 2019 and June 2020. Onboard differential Global Navigation Satellite System (GNSS) unit(s) recorded sample aircraft positions at 2 hertz (Hz) or more frequency. LiDAR data was only acquired when a minimum of six (6) satellites were in view. Twenty-three (23) Continuously Operating Reference Stations (CORS) were used to control the LiDAR acquisition for the defined project area.
- 2020-05-11 00:00:00 - Ground Control Survey -- Ground survey points were collected in support of this project, including LiDAR Control Points (LCP), Non-vegetated Vertical Accuracy (NVA) and Vegetated Vertical Accuracy (VVA). Point cloud data accuracy was tested against a Triangulated Irregular Network (TIN) constructed from LiDAR points in clear and open areas. A clear and open area can be characterized with respect to topographic and ground cover variation such that a minimum of five (5) times the Nominal Pulse Spacing (NPS) exists with less than 1/3 of the RMSEZ deviation from a low-slope plane. Slopes that exceed ten (10) percent were avoided. Each land cover type representing ten (10) percent or more of the total project area were tested and reported with a VVA. In land cover categories other than dense urban areas, the tested points did not have obstructions forty-five (45) degrees above the horizon to ensure a satisfactory TIN surface. The VVA value is provided as a target. It is understood that in areas of dense vegetation, swamps, or extremely difficult terrain, this value may be exceeded. The NVA value is a requirement that must be met, regardless of any allowed “busts†in the VVA(s) for individual land cover types within the project. Checkpoints for each assessment (NVA and VVA) are required to be well-distributed throughout the land cover type, for the entire project area.
- 2021-01-14 00:00:00 - LiDAR Point Cloud Generation -- Atlantic used Leica software products to download the IPAS ABGNSS/IMU data and raw laser scan files from the airborne system. Waypoint Inertial Explorer is used to extract the raw IPAS ABGNSS/IMU data, which is further processed in combination with controlled base stations to provide the final Smoothed Best Estimate Trajectory (SBET) for each mission. The SBETs are combined with the raw laser scan files to export the LiDAR ASCII Standard (*.las) formatted swath point clouds.
- 2021-05-28 00:00:00 - LiDAR Calibration -- Using a combination of GeoCue, TerraScan and TerraMatch; overlapping swath point clouds are corrected for any orientation or linear deviations to obtain the best fit swath-to-swath calibration. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project missions, was reduced to ≤2cm. A final analysis of the calibrated lidar is performed using a TerraMatch tie line report for an overall statistical model of the project area. Individual control point assessments for this project can be found in Section VI of the report. Upon completion of the data calibration, a complete set of elevation difference intensity rasters (dZ Orthos) are produced. A user-defined color ramp is applied depicting the offsets between overlapping swaths based on project specifications. The dZ orthos provide an opportunity to review the data calibration in a qualitative manner. Atlantic assigns green to all offset values that fall below the required RMSDz requirement of the project. A yellow color is assigned for offsets that fall between the RMSDz value and 1.5x of that value. Finally, red values are assigned to all values that fall beyond 1.5x of the RMSDz requirements of the project.
- 2022-05-12 00:00:00 - LiDAR Classification -- Multiple automated filtering routines are applied to the calibrated LiDAR point cloud identifying and extracting bare-earth and above ground features. GeoCue, TerraScan, and TerraModeler software was used for the initial batch processing, visual inspection and any manual editing of the LiDAR point clouds. Atlantic utilized collected breakline data to perform classification for class 9 (Water).
- 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 elevations in NAVD88 (GEOID12B).
- 2023-05-26 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files 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/GA_Central_1_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/GA_Central_2_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/GA_Central_3_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/GA_Central_4_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/GA_Central_5_2018/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/GA_Central_6_2018/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/GA_Central_2018_B19/
https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/GA_Central_2019_B19/
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 tape and 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.