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 limits cover 615 square miles of Miami-Dade County. The project was divided into two phases: Collection and classification of LiDAR data and creation of 5-foot cell spaced hydro enforced mosaic DEM of the project area.
The lidar point, DEM, and breakline data were provided to the Office for Coastal Management (OCM) by the Miami-Dade County Information Technology Department (OTD) for inclusion in the Data Access Viewer (DAV).
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 links 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.
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):
Bare-earth 5-foot DEM as 32-bit floating point raster format in ARCGIS GRID Raster format in compliance with USGS LIDAR Base Specifications such as: georeferencing information, delivered without overlap and with no edge artifacts or mismatched, “NODATA” value for void areas, bridges removed from the surface, etc.
- 2018-01-01 00:00:00 - The project was divided in two phases: Collection and classification of LiDAR data and creation of 5-foot cell spaced hydro enforced mosaic DEM of the project area. The LiDAR data was collected utilizing a Riegl VQ-1560i in a Cessna 206 from an approximate altitude of 4,200 feet above ground level, at an approximate ground speed of 110 knots at a pulse rate repetition of 2000 kHg, resulting in an average of 15.2 points per square meter single swath and 20 plus with the 55% overlap. To get under the cloud celling some flight lines were collected at 2,000 feet agl at 110 knots. These lines were collected at 29.12 points per square meter single swath. The sensor used a 60-degree field of view. The project was flown to have 55 percent overlap between swaths. The Global Positioning System (GPS) data were processed using Applanix POSPac Mapping Suite version 8.3 using Smart Base method and single base methods. A fixed bias carrier phase solution was computed in forward and reverse directions. The LiDAR collection took place when Positional Dilution of Precision (PDOP) was at or below 3. Occasionally, the PDOP rose slightly above 3. This had no effect on the data. The GPS trajectory was combined with the IMU data using the Applanix POSPac software. The resulting Smoothed Best Estimate of Trajectory (SBET) was exported and used in Riegl RiProcess software to compute the laser mass point positions in Northing, Easting, and Elevations coordinates. The raw laser data were merged with the SBET using Riegl RiProcess software. The data set was processed using RiProcess, RiAnalyze, and RiWorld software where each flight line was processed to a point cloud. The data was adjusted flight line to flight line using Riegl’s Scan Data Adjustment tool to ensure a proper relative calibration match between flight lines. Each flight was checked for project coverage, data gaps between overlapping flight lines, point density and then exported in LAS 1.4 format. The entire project was collected without gaps. The LAS files were projected to the NAD_1983_2011_StatePlane_Florida_East_FIPS_0901_Feet and North American Vertical Datum of 1988 (NAVD88). Ellipsoidal heights were converted to orthometric heights using the current Geiod12B. The LAS files were imported to TerraSolid, LTD TerraScan software to be classified to bare earth ground and later feature coded to USGS specifications. The LAS files contain 12 classifications: 1 = unclassified; 2 = ground; 3 = low veg; 4 = med veg; 5 = high veg; 6 = building; 7 = noise points; 9 = water; 10 = buffered ground points surrounding breaklines; 12 = overlap; 17 = overpass and bridges; 18 = high noise. The LiDAR data was run through an automated ground and building classification using terrascan software. A manual check of the building classification was done. The vegetation heights were assigned by an automated process after the bare-earth and buildings were classified. No manual classification of the vegetation class was performed on this data set. Breaklines were digitized from the LiDAR data in Microstation and elevations were assigned using LP360 and ArcGIS. The double line linear hydrographic features were hydro-enforced with downhill constraints to model correct flow patterns. Water bodies were hydro-flattened to ensure uniform elevation across the feature. DEMs were created using QCoherent LP360 software. The bare-earth LAS data was loaded into the software along with the tile layout and hydro shapefile collected from the LAS data set. DEMS were produced at a 5ft cell size and hydro-flattened. To QC the DEMs, Global Mapper was used to check for completeness of the tiles and that the hydro features were flattened and represented correct elevations. Once the QC was complete the files were exported out of ArcGIS to create Arc DEM. COLLECTION DATES: 4/25/18, 4/26/18, 4/29/18, 4/30/18, 5/01/18, 6/05/18, 6/06/18, 6/22/18, 12/05/18 173 flight lines of data were collected.
- 2021-03-24 00:00:00 - The NOAA Office for Coastal Management (OCM) received 1file in esri ArcGrid format from the Miami-Dade County Information Technology Department (ITD). The bare earth raster file was at a 5 ft grid spacing. The data were in FL State Plane, Zone 0901, NAD83(2011), US survey foot coordinates and NAVD88 (GEOID12B) elevations in feet. OCM converted the file from esri ArcGrid format to Geotiff format and the file was assigned the EPSG codes of 6438 (horizontal) and 8228 (vertical) and then copied to https for Digital Coast storage and provisioning purposes using an internal OCM script.
(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.
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.