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
Aerial Cartographics of America Inc. (ACA) collected 1,535 square miles in the Florida counties of Osceola, Polk and Orange. The nominal pulse spacing for this project was 1 point every 0.5 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 0-Never Classified, 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity, 17- Bridge Decks, 18-High Noise. Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro flattened DEMs for the project area. The data was formatted according to the tile naming convention as stated in the project SOW with each tile covering an area of 2,500 feet by 2,500 ft. A total of 7,292 LAS and DEM tiles were produced for the entire project.
The NOAA Office for Coastal Management (OCM) downloaded the laz files from this USGS site ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_FL_Osceola_2015_LAS_2017/ and processed the data to the Data Access Viewer (DAV) and to https. The total number of files downloaded and processed was 7292.
The hydro breaklines were also downloaded and are available at the link provided in the URL section of this metadata record. Please note that these products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM.
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):
- 2016-05-01 00:00:00 - Data for the Osceola County Florida QL2 LiDAR project was acquired by Aerial Cartographics of America Inc. (ACA). The project area included approximately 1535 contiguous square miles or 2470 square kilometers for the counties of Osceola, Polk and Orange in Florida. LiDAR sensor data were collected with the Riegl LMS-Q680i LiDAR system. The data was delivered in the State Plane coordinate system, feet, Florida East, horizontal datum NAD83 (2011), vertical datum NAVD88, Geoid 12B. Deliverables for the project included a raw (unclassified) calibrated LiDAR point cloud, survey control, and a final acquisition/calibration report. The calibration process considered all errors inherent with the equipment including errors in GPS, IMU, and sensor specific parameters. Adjustments were made to achieve a flight line to flight line data match (relative calibration) and subsequently adjusted to control for absolute accuracy. Process steps to achieve this are as follows: Rigorous LiDAR calibration: all sources of error such as the sensor's ranging and torsion parameters, atmospheric variables, GPS conditions, and IMU offsets were analyzed and removed to the highest level possible. This method addresses all errors, both vertical and horizontal in nature. Ranging, atmospheric variables, and GPS conditions affect the vertical position of the surface, whereas IMU offsets and torsion parameters affect the data horizontally. The horizontal accuracy is proven through repeatability: when the position of features remains constant no matter what direction the plane was flying and no matter where the feature is positioned within the swath, relative horizontal accuracy is achieved. Absolute horizontal accuracy is achieved through the use of differential GPS with base lines shorter than 25 miles. The base station is set at a temporary monument that is 'tied-in' to the CORS network. The same position is used for every lift, ensuring that any errors in its position will affect all data equally and can therefore be removed equally. Vertical accuracy is achieved through the adjustment to ground control survey points within the finished product. Although the base station has absolute vertical accuracy, adjustments to sensor parameters introduces vertical error that must be normalized in the final (mean) adjustment. A copy of the final calibrated swaths are maintained in LAS format 1.2 for production utilizing Terrascan software. A second, identical version of final calibrated swaths are converted from v1.2 to v1.4 using GeoCue software. The withheld and overlap bits are set and all headers, appropriate point data records, and variable length records, including spatial reference information, are updated in GeoCue software and then verified using proprietary Dewberry tools.
- 2016-05-01 00:00:00 - Dewberry utilizes a variety of software suites for inventory management, classification, and data processing. All LiDAR related processes begin by importing the data into the GeoCue task management software. The swath data is tiled according to project specifications (2,500 ft x 2,500 ft). The tiled data is then opened in Terrascan where Dewberry classifies edge of flight line points that may be geometrically unusable to a separate class. These points are separated from the main point cloud so that they are not used in the ground algorithms. Dewberry then uses proprietary ground classification routines to remove any non-ground points and generate an accurate ground surface. The ground routine consists of three main parameters (building size, iteration angle, and iteration distance); by adjusting these parameters and running several iterations of this routine an initial ground surface is developed. The building size parameter sets a roaming window size. Each tile is loaded with neighboring points from adjacent tiles and the routine classifies the data section by section based on this roaming window size. The second most important parameter is the maximum terrain angle, which sets the highest allowed terrain angle within the model. As part of the ground routine, low noise points are classified to class 7 and high noise points are classified to class 18. Once the ground routine has been completed, bridge decks are classified to class 17 using bridge breaklines compiled by Dewberry. A manual quality control routine is then performed using hillshades, cross-sections, and profiles within the Terrasolid software suite. After this QC step, a peer review is performed on all tiles and a supervisor manual inspection is completed on a percentage of the classified tiles based on the project size and variability of the terrain. After the ground classification and bridge deck corrections are completed, the dataset is processed through a water classification routine that utilizes breaklines compiled by Dewberry to automatically classify hydrographic features. The water classification routine selects ground points within the breakline polygons and automatically classifies them as class 9, water. During this water classification routine, points that are within 1x NPS or less of the hydrographic features are moved to class 10, an ignored ground due to breakline proximity. Overage points are then identified in Terrascan and GeoCue is used to set the overlap bit for the overage points and the withheld bit is set on the withheld points previously identified in Terrascan before the ground classification routine was performed. A final QC is performed on the data. The LAS files are then converted from v1.2 to v1.4 using GeoCue software. At this time, all headers, appropriate point data records, and variable length records, including spatial reference information, are updated in GeoCue software and then verified using proprietary Dewberry tools. The data was classified as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 7 = Low Noise Class 9 = Water Class 10 = Ignored Ground due to breakline proximity Class 17 = Bridge Decks Class 18 = High Noise The LAS header information was verified to contain the following: Class (Integer) Adjusted GPS Time (0.0001 seconds) Easting (0.003 m) Northing (0.003 m) Elevation (0.003 m) Echo Number (Integer) Echo (Integer) Intensity (16 bit integer) Flight Line (Integer) Scan Angle (degree)
- 2020-08-10 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded the laz files from this USGS site:ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_FL_Osceola_2015_LAS_2017/ These files were processed to the Data Access Viewer (DAV) and https. The total number of files downloaded and processed was 7292. The data were in FL State Plane East (0901) (NAD83 2011), US survey feet coordinates 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, 18 - High Noise. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 10, 17, 18. 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. A small number of points were classified as 6, 14, and 255. These points were not defined in the project metadata or report. They remain in the data set, but are not listed as available classes for download. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert from FL State Plane East (0901) (NAD83 2011) coordinates in US survey feet, to geographic coordinates, to convert from vertical units of feet to meters, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.
- 2022-09-21 00:00:00 - NOAA Office for Coastal Management found that all of the points that were not marked as withheld were marked as overlap. This made the overlap bit flag of no use and potentially detrimental to processes that drop points with the overlap flag. The overlap bit flag was removed from all points using the las2las program with the -set_overlap _flag 0 argument.
(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
- 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.
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.
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
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.