Data Management Plan
GUID: gov.noaa.nmfs.inport:64745 | 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
Product: These lidar data are processed classified LAS 1.4 files, formatted to 4,597 (Franklin and St. Lawrence) and1351 (Oneida Sub-Basin) individual 1,500-meter x 1,500-meter tiles; used to create intensity images, 3D breaklines, hydro-flattened DEMs, and contours as necessary.
Geographic Extent: Seven counties in New York. East Zone AOI is Franklin and St. Lawrence Counties, Central Zone AOI is Lewis, Madison, Oneida, Onondaga, and Oswego Counties.
Dataset Description: New York FEMA 2016 QL2 Lidar project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2. Lidar data was delivered as flightline-extent unclassified LAS swaths, as processed classified LAS 1.4 files formatted to 4,597 individual 1,500-meter x 1,500-meter tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 1,500-meter x 1,500-meter schema. Continuous breaklines were produced in Esri file geodatabase format. Contours with a 1-foot interval were produced in Esri file geodatabase format, tiled to the same 1,500-meter x 1,500-meter schema.
Ground Conditions: Lidar was collected in winter/spring of 2016/2017, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Quantum Spatial, Inc. established a total of 76 ground control points that were used to calibrate the lidar to known ground locations established throughout the New York East Zone (Franklin and St. Lawrence Counties) project area. An additional 71 independent accuracy checkpoints, 71 in Bare Earth and Urban landcovers (59 NVA points), 59 in Forested, Brushland/Trees, and Tall Weeds/Crops categories (59 VVA points), were used to assess the vertical accuracy of the data. Quantum Spatial, Inc. established a total of 30 ground control points that were used to calibrate the lidar to known ground locations established throughout the New York Central Zone (Lewis, Madison, Oneida, Onondaga, and Oswego Counties) project area. An additional 64 independent accuracy checkpoints, 41 in Bare Earth and Urban landcovers (41NVA points), 23 in Forested, Brushland/Trees, and Tall Weeds/Crops categories (25 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
The NOAA Office for Coastal Management (OCM) downloaded the 4597 las files from the New York State GIS site. The data for Frankin and St. Lawrence Counties were downloaded from this URL: ftp://ftp.gis.ny.gov/elevation/LIDAR/FEMA_FranklinStLawrence2016/. The data for the Oneida Sub-Basin area (1351 laz files) were downloaded from the USGS ftp site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_NY_FEMA_R2_B1_2016_LAS_2018/laz/. The data were processed to the Data Access Viewer (DAV) and https. In addition to these lidar point data, the hydro breaklines and the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link provided in the URL section of this metadata record.
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:
Data were collected and processed by Quantum Spatial, Inc. for FEMA. The data were downloaded from the New York State GIS ftp site and the USGS ftp site by the NOAA Office for Coastal Management (OCM) where the data were processed to make it available for custom download from the Data Access Viewer (DAV) and bulk download from https.
Process Steps:
- 2017-01-01 00:00:00 - LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper us used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Quantum Spatial, Inc. proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.
- 2021-06-09 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 4597 las files from ftp://ftp.gis.ny.gov/elevation/LIDAR/FEMA_FranklinStLawrence2016/. The data were in NY State Plane East (NAD83 2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water,10 - Ignored Ground, 17 - Bridge Decks. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 10, 17. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The las files were converted from las format to laz format using laszip. 2. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 3. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model b. Convert the laz files from NY State Plane East (NAD83 2011), meters coordinates to geographic coordinates c. Filter points outside the elevation range of 0 to 2000 meters d. Filter points outside the geographic range of the bounding coordinates of -76, 44, -73, 46 degrees e. Assign the geokeys, sort the data by gps time and zip the data to database and to http.
- 2021-06-28 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 1351 laz files from ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_NY_FEMA_R2_B1_2016_LAS_2018/laz/. These files make up the Oneida Sub-Basin portion (Central Zone) of the data set. The data were in NY State Plane Central (NAD83 2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water,10 - Ignored Ground, 17 - Bridge Decks. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 10, 17. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model b. Convert the laz files from NY State Plane Central (NAD83 2011), meters coordinates to geographic coordinates c. Filter points outside the elevation range of 0 to 1000 meters d. Filter points outside the geographic range of the bounding coordinates of -76.5, 42.5, -75, 44 degrees e. Remove parts of the USGS file names for conciseness, maintaining the integral parts of the file name. f. Assign the geokeys, 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.
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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9321/index.html
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.