Data Management Plan
GUID: gov.noaa.nmfs.inport:49821 | 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
The project entails the acquisition and processing of LiDAR for approximately 1,265 square miles covering areas of Madison and Eastern Yazoo Counties. Collect and deliver high-density elevation point data derived from multiple-return light detection and ranging (LiDAR) measurements for use in supporting topographic analysis, including applications such as flood plain mapping. Hydro enforced breaklines were collected within the identified Special Flood Hazard Area for Madison County, MS including an additional 221sq. miles in the heavily developed areas in Madison County, and 112 sq. miles in a buffered area along the Big Black River in Yazoo County, MS. The data will be delivered as LiDAR Bare Earth within the areas designated in areas of Madison and Eastern Yazoo Counties to aid in visual interpretation of Flood Basin elevations and for addition to the MDEM elevation dataset. Also included in the delivery was LiDAR Intensity data in Tiff format. The intensity values are a measure of the return signal strength. It measures the peak amplitude of return pulses as they are reflected back from the target to the detector of the LiDAR system. These intensity images are a very useful tool to clients and can be used as a substitute for orthophotos. All data will comply with mapping guidelines and specifications as stated in the FEMA Procedure Memorandum No.61.
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):
Process Steps:
- 2012-01-01 00:00:00 - The flight path will be planned as a series of parallel flight lines with cross flight lines for the purposes of quality control. In addition, the flight plan will include flight line distances of 45 kilometers or less and zigzag flight line collection as a result of the inherent IMU drift associated with IMU systems. A digital flight line layout using OPTECH ALTM NAV flight design software for direct integration into the aircraft flight navigation system was created and used.
- LiDAR Sensor Calibration and LiDAR Processing. LIDAR calibrations are performed to determine and eliminate systematic bias that may occur within the hardware of the ALTM system. The systematic bias that are corrected involve scale, roll, and pitch. In addition to the calibration process regarding sensor installation, for every mission, the runway is kinematically surveyed by making three passes. The LiDAR system is flown at right angles over the runway several times and residuals are generated from the processed data.
- Breaklines were captured within the identified SFHA for Madison County, MS, including a buffered 112 sq. mile area along the Big Black River in Yazoo County, MS. The breaklines are significant hydrological features that are appropriate to support the future development of 2-foot contours meeting a 1.19-foot absolute vertical accuracy at the 95% confidence level. Horizontal accuracy is computed using the formula RMSE (z) x 1.7308: 1-inch = 100 feet equivalent (Accuracy = 2.2 feet or 0.67 meters) as defined by the ASPRS Guidelines: Accuracy Reporting for topographic Data. This guideline implements the National Standard for Spatial Data Accuracy (NSSDA) for testing of topographic data.
- Digital Elevation Models (DEMs) are generated in spatial software and have a final cell size of 4 feet. Each DEM is a 32-bit floating point GeoTiff.
- 2013-09-16 00:00:00 - The NOAA Office for Coastal Management (OCM) received topographic files in .laz format from the Mississippi Department of Environmental Quality (MDEQ). The files contained lidar elevation measurements. The data were received in Mississippi State Plane West 2300, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic laz files were converted from a Projected Coordinate System (Mississippi State Plane West 2300) to a Geographic Coordinate system (NAD 83). 2. The topographic laz files' horizontal units were converted from feet to decimal degrees. 3. The topographic laz files were cleaned of error points above 492 ft and below 114 ft. 4. The topographic laz files' were converted from NAVD88 elevations to NAD83 ellipsoidal elevations using Geoid03 5. Classification 11 was moved to classification 12 due to OCM system requirements (class 11 is reserved for bathymetric points, though these points are overlap points, Class 12).
(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.amazonaws.com/laz/geoid18/2561/index.html
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:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2561
;
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.