Data Management Plan
GUID: gov.noaa.nmfs.inport:69998 | 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
These lidar data were processed as classified LAS 1.4 files, formatted to individual 500 m x 500 m tiles; used to create breaklines and hydro-flattened DEMs.
Geographic Extent:
West AOI (Jefferson and Lewis Counties) covering approximately 626 square miles.
East AOI (Columbia, Rensselaer, Saratoga, Warren, and Washington Counties) covering approximately 2,548 square miles.
Dataset Description: This data project was undertaken in 2018 and 2019. This project called for the flight planning, collection, and processing of point cloud products. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. These data were created based on a horizontal projection/datum of NAD83 (2011), Universal Transverse Mercator, meters and vertical datum of NAVD88 (GEOID12B), meters. These LiDAR data were delivered as processed classified LAS 1.4 files compressed to LAZ files.
Ground Conditions: Lidar was collected in 2018 and 2019 in full leaf out conditions. Because of this, a "produced to meet" statement is not provided for Vegetated Vertical Accuracy (VVA).
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.
East AOI (Columbia, Rensselaer, Saratoga, Warren, and Washington Counties)
W: -76.11, E: -75.23, N: 44.3, S: 43.48West AOI (Jefferson and Lewis Counties)
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:
- 2020-01-01 00:00:00 - LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed and edited using TIN visualization and profiles to ensure correct classification on the Class 2 (Ground) points as well as the other classifications required by NCEM. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization in a 3D environment for all rivers equal to or larger than 100 feet in width and all closed water bodies equal to or greater than 2 acres. Island equal or greater than 1 acre are mapped are included. All ground (Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were classified to water (Class 9) A buffer of 1 foot was also used around each hydro-flattened feature to classify ground (Class 2) points within the buffer to breakline proximity (Class 10). All Lake Pond Island and Double Line Drain Island features were reviewed and checked to ensure that the ground (Class 2) points were reclassified to the correct classification after the automated classification was completed. Overlap data was not processed as Geiger mode LiDAR is flown at a 55 percent overlap with a Palmer scanner. All data was manually reviewed and any remaining artifacts in the ground (Class 2) removed.
- The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) file that was 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. This is the AWS URL being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NY_HudsonRiverRegion_1_2020/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/NY_HudsonRiverRegion_2020_A20/NY_HudsonRiverRegion_1_2020/LAZ/
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.