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
For Oneida County, NY, there were two types of elevation datasets. The first type is LiDAR and the second one is Auto-correlation DEM. Auto-correlation DEM data was developed wherever LiDAR data was not available. LiDAR data was made available to this project through two different initiatives. The first set of LiDAR data was made available through HMTAP-1650 project, which consisted of area of 3 miles buffers around Mohawk River. Though data was available for the whole length of Mohawk, only data that pertained to the county was used for this project.The second set of LiDAR data was made available for DFIRM. DFIRM data was delivered at two different times. The first delivery done in 2008 (covers middle part of the county) and the second delivery done in 2009 (covers a small area in the west, around Oneida lake). As the two coverages did not have issues dealing with overlaps, they were used as they are. For the auto correlated data, in an effort to provide an alternative to the collection of LiDAR data and utilization of the National Elevation Dataset (NED), Dewberry has tested the methodology for the generation of a photogrammetrically derived surface model appropriate for Hydrologic and Hydraulic modeling and conforming to FEMA standards.The autocorrelated surface was generated using imagery from the 2003 New York statewide collection along with the Aerial Triangulation (AT) solution provided with the source imagery. The surface was subsequently edited through manual processes and improved with breaklines in order to meet ASPRS Class 1 accuracy requirements for 4 foot contour mapping.The final terrain is named as Oneida_Terrain.gdb. Please check the image from the PDF report in the General folder of the MIP submitted data.
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.
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):
- 2008-01-01 00:00:00 - For the Oneida Co. LIDAR data -Using Sanborn's Leica ALS50(Sno 49) LiDAR system,12 flight lines of standard density (1.4 meter ground sample distance) data were collected over areas in Oneida Co, NY(approx 20 sq miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. For the autocorrelated data Manual Editing of surface posts using the interactive terrain editing (ITE) tools in Socet Set. The Manual editing was performed against the stereo imagery.Source used is Raw Scanned Imagery, AT, Initial Auto-Correlated Surface in ascii xyz format. Source production - Final Auto-Correlated surface in ASCII xyz format. Then the Stereo Imagery and Final Auto-Correlated Surface were used to identify areas where breaklines where necessary to support 4' contours; Source used - Raw Scanned Imagery, AT, Final Auto-Correlated Surface; source production - Breaklines. The next step was Using the final Auto-Correlated Surface posts and the Breaklines as source material the data was imported into an ArcGIS File Geodatabase and a terrain was generated; Source used -Final Auto-Correlated Surface in ASCII xyz format, Breaklines; Source production - Terrain Dataset.For the HMTAP data a manual visualization process was performed. This includes creating pseudo image products such as 3dmodels. By creating multiple images and using overlay techniques, potential errors can be found.
- 2016-06-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received topographic LAS files as part of a delivery of FEMA projects in various states which have not been made available to the public with any other federal agency. The files contained lidar easting, northing, elevation, as well as ancillary collection attributes. The data were received in UTM 18 in meters and were vertically referenced to NAVD88 using the Geoid03 model. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were converted from feet to meters, removing erroneous elevations. 2. The LAS files were converted from orthometric (NAVD88) heights to ellipsoidal heights using the Geoid03 model. 3. The LAS files were converted from a projected coordinates to Geographic Coordinates in decimal degree. 4. Files were retiled to have more homogeniety across the project.
(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.
- 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.
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.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
This data can be obtained on-line at the following URL:
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.