Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:64733 | 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: These are Digital Elevation Model (DEM) data for Franklin, Lewis, Madison, Oneida, Onondaga, Oswego, and St. Lawrence Counties, New York as part of the required deliverables for the New York 2016 Lidar project. Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 1-meter hydro-flattened raster DEM.
Geographic Extent: Seven counties in New York, covering approximately 4,474 total square miles. 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 68 independent accuracy checkpoints, 43 in Bare Earth and Urban landcovers (43 NVA points), 25 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 5948 DEM files (4597 files for the East Zone AOI and 1351 files for the Central Zone AOI) from the New York State GIS site. The data were downloaded from these URLs: ftp://ftp.gis.ny.gov/elevation/DEM/FEMA_FranklinStLawrence2016/ and ftp://ftp.gis.ny.gov/elevation/DEM/FEMA_OneidaSubbasin2016/. The data were processed to the Data Access Viewer (DAV) and http. In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from and the breaklines 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 DEM data were downloaded from the New York State GIS 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:
- 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. The data for counties in the East Zone AOI were developed based on a horizontal projection/datum of NAD83 (2011), State Plane New York East Zone, meters and vertical datum of NAVD88 (GEOID12B), meters. The data for counties in the Central Zone AOI were developed based on a horizontal projection/datum of NAD83 (2011), State Plane New York Central Zone, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as flightline-extent unclassified LAS swaths, as processed classified LAS 1.4 files formatted to 5948 (4597 files for the East Zone AOI and 1351 files for the Central Zone AOI) 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.
- 2017-01-01 00:00:00 - Hydro-Flattened Raster DEM Processing: Class 2 (Ground) lidar points in conjunction with the hydro breaklines were used to create a 1 meter hydro-flattened raster DEM. Using automated scripting routines within ArcMap, an ERDAS Imagine .IMG file was created for each tile. Each surface is reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface.
- 2021-06-04 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 5948 (4597 files for the East Zone AOI and 1351 files for the Central Zone AOI) digital elevation model (DEM) files in img format from the NY State GIS ftp site (ftp://ftp.gis.ny.gov/elevation/DEM/FEMA_FranklinStLawrence2016/ and ftp://ftp.gis.ny.gov/elevation/DEM/FEMA_OneidaSubbasin2016/) . The bare earth raster files were at a 1 m grid spacing. The data were in NY State Plane East (Franklin and St. Lawrence) and NY State Plane Central (Oneida Subbasin) NAD83 (2011), meters coordinates and NAVD88 (Geoid 12B) elevations in meters. OCM assigned the appropriate EPSG codes (Horiz - 6534 (Oneida Subbasin) and 6536 (Franklin and St.Lawrence), Vert - 5703) and copied the raster files to https for Digital Coast storage and provisioning purposes.
(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
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(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.us-east-1.amazonaws.com/dem/NY_Franklin_StLawr_DEM_2017_9315/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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.