Data Management Plan
GUID: gov.noaa.nmfs.inport:49673 | 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
This Light Detection and Ranging (LiDAR) LAS dataset is a topographic survey conducted for a coalition of GIS practitioners,
including the Florida Division of Emergency Management (FDEM), Florida Water Management Districts, Florida Fish and Wildlife
Conservation Commission, Florida Department of Environmental Protection, Army Corps of Engineers Jacksonville District, and
other state and federal agencies. The goal for this project is to use the LiDAR data as new elevation inputs for updated SLOSH
data grids. The ultimate result is the update of the Regional Hurricane Evacuation Studies (RHES) for the state. The State of Florida
Division of Emergency Management LiDAR Survey was collected under the guidance of a Professional Mapper/Surveyor.
Data were collected for 255 square miles in the eastern portion of Indian River County, Florida from August 24 - 28, 2007.
This is a classified lidar data set. The data are classified: 1 = Unclassified, 2 = Ground (Bare Earth), 7 = Noise, 9 = Water
and 12 = Overlap. The data was collected at a maximum post spacing of 4 feet in unobscured areas for random point data.
Original contact information:
Contact Org: Florida DEM
Phone: 850-413-9907
Email: gis@dca.state.fl.us
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:
- 2009-01-05 00:00:00 - LiDAR was collected within portions of Indian River County. System Parameters/Flight Plan: The LiDAR system acquisition parameters were developed based on a maximum average ground sample distance of 4 feet. Two Leica ALS50 sensors were used for acquisition. Acquisition specifications for the two sensors were as follows: Sensor 19 Field of View (full angle) - 29 degrees Nominal flight altitude (AMSL) - 3999.30 feet Airspeed - 54.02 meters/sec Laser pulse rate - 75,000 Hz Nominal swath width (on ground) - 2068.58 feet Maximum cross track point spacing - 3.91 feet Maximum along track point spacing - 3.94 feet Average point spacing - 2.21 feet Flight line spacing - 1544.95 feet Side overlap - 25.31%. Sensor 59 Field of View (full angle) - 29 degrees Nominal flight altitude (AMSL) - 3999.30 feet Airspeed - 60.70 meters/sec Laser pulse rate - 84,400 Hz Nominal swath width (on ground) - 2068.58 feet Maximum cross track point spacing - 3.94 feet Maximum along track point spacing - 3.91 feet Average point spacing - 2.21 feet Flight line spacing - 1413.72 feet Side overlap - 31.66%. LiDAR System Calibration: Prior to the LiDAR acquisition, the system underwent a calibration to verify the operational accuracy and misalignment angles. Boresight calibrations were performed for each LiDAR system at the beginning and end of each flight mission. LiDAR Data Acquisition: LiDAR data acquisition only occurred when the sky was sufficiently clear of clouds, smoke, and atmospheric haze. The LiDAR data was processed immediately after the acquisition to verify the coverage had no voids. GPS/Inertial Measurement Unit (IMU) Post Processing: The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. LiDAR Processing and Classification: The LiDAR data was post processed and verified to be consistent with the project requirements in terms of post spacing and absence of artifacts. The point cloud underwent classification to determine bare-earth points (class 2), noise points (class 7), water returns (class 9), and unclassified data (class 1). Class 12 contains LiDAR points removed from the overlap region between adjacent flight lines.
- 2010-06-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received files in LAS format. The files contained LiDAR intensity and elevation measurements. OCM performed the following processing on the data to make it available within Digital Coast: 1. The data were converted from State Plane Florida East coordinates to geographic coordinates. 2. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03. 3. The LAS header fields were sorted by latitude and updated.
(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.6. Type(s) of data
- 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/539/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;
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.