Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:64728 | 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
Product: Calibrated LiDAR version 1.4 .las tiles, classified for subsequent derivatives.
Geographic Extent: New York, Bronx, Kings, Queens, and Richmond Counties in New York plus an additional 100 m buffer.
Dataset Description: In May 2017, Quantum Spatial (QSI) was contracted by Applied Geographics (AppGeo) to collect topographic and topobathymetric Light Detection and Ranging (LiDAR) data for the City of New York (NYC). QSI collected and processed traditional (near infrared wavelength, Leica ALS80 sensor) LiDAR over the topographic AOI, and spliced together NIR and bathymetric LiDAR (green wavelength, Riegl VQ-880-G sensor) for the topobathymetric AOI. LiDAR point data are delivered in 2,500 X 2,500 ft tiles.
Ground Conditions: Topographic LiDAR was collected in May 2017 with approximately 50% leaf-off conditions. Bathymetric data was collected in July 2017 during low tide time windows. Ground control data were used to geospatially correct the LiDAR point cloud and used to perform quality assurance checks on the final products. In addition, Continuously Operating Reference Stations (CORS) from the New York State Spatial Reference Network (NYSNet) were used to geospatially correct the aircraft positional coordinate data and as base stations for GSP collection. All ground survey work to support the topobathymetric LiDAR acquisition was conducted during the NIR LiDAR collection window. Land cover class check points were also collected throughout the study area to evaluate vertical accuracy.
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 the New York City Department of Information Technology and Telecommunications. The data were retrieved from the New York State GIS FTP website [ address: ftp://ftp.gis.ny.gov/elevation/LIDAR/NYC_TopoBathymetric2017/ ] 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:
- 2018-01-01 00:00:00 - The following outlines the processing of the point cloud data: 1. Flightlines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Laser point return coordinates were computed using Waypoint Inertial Explorer and Leica Cloudpro software based on independent data from the LiDAR system, IMU, and aircraft. 3. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate. 4. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment. 5. Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and intensities. Specifically, refinement in the combination of system pitch, roll, and yaw offset parameters optimize internal consistency. 6. Noise (e.g., pits and birds) was filtered using post-processing software, based on known elevation ranges and included the removal of any cycle slips. 7. Using TerraScan and Microstation, ground classifications utilized custom settings appropriate to the study area. 8. The corrected and filtered return points were compared to the ground survey points collected to verify the vertical accuracy. (Citation: Lidar Data)
- 2021-06-02 00:00:00 - The NOAA Office for Coastal Management (OCM) retrieved 1,894 lidar point cloud files in laz format from the New York State GIS website. The files contained lidar elevation and intensity measurements. The data were in NAD83 (2011) State Plane New York Long Island (FIPS 3104) in US Feet, and NAVD88 (Geoid12B) elevations in feet. The data were classified as: 1-Unclassified, 2-Ground, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, 17 - Bridge Decks, 25 - Subway stairwells, 40 - Bathymetric Bottom, 41 - Green Near Water Surface, 45 - Water Column. OCM reclassified 25 - Subway Stairwells to 76 to better conform to ASPRS standards, and otherwise processed all classifications of points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12B model, to convert from NY State Plane Long Island (NAD83 2011), US feet coordinates to geographic coordinates, to convert vertical elevations from feet to meters, 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.
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/9306/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 or 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.