| 2021 Miami-Dade ITD Lidar: Miami-Dade County, FL | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:76028 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2025-06-02T17:18:22 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 1543279465 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) / UTM zone 17N date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/6346/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6346 version: 6.18.3 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2021 Miami-Dade ITD Lidar: Miami-Dade County, FL alternateTitle: fl2021_miami_dade_m10338_metadata date: (CI_Date) date: 2021 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2022 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 76028 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/76028 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/10338/ept.json protocol: WWW:LINK-1.0-http--link name: Entwine Point Tile (EPT) description: Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10338/supplemental/2021_LiDAR_gdb.zip protocol: WWW:LINK-1.0-http--link name: Breaklines description: Link to the breaklines, overpasses, bridges, QAQC points, and ground control points. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10338/supplemental/2021_ITD_SMR_Report.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to the lidar report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/10338/ept.json protocol: WWW:LINK-1.0-http--link name: Potree 3D View description: Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/ protocol: WWW:LINK-1.0-http--link name: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) description: The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: GPI Geospatial Inc., operating under the authority of Miami-Dade County Aviation Department, as per contract number E15-MDAD-01, has been tasked by Miami-Dade County's Information Technology Department (ITD) to provide LiDAR data for 615 square miles, including the classification of the data and the creation of hydro-flattened Digital Elevation Model (DEM). GPI Geospatial has created a file geodatabase named 2021_Lidar.gdb. The project deliverables included fully compliant LAS v1.4 with georeferenced information included in LAS header. The LAS files have 16-bit intensity values with GPS times recorded as Adjusted GPS Time, at a precision sufficient to allow unique timestamps for each return. The LiDAR classification followed the ASPRS Standards LIDAR Point Classes: 1 = Unclassified; 2 = Ground (or Bare Earth); 3 = Low Vegetation 0 -5ft; 4 = Medium Vegetation 5-25ft; 5 = High Vegetation 25-above; 6 = Building; 7 = Low Point (noise); 8 = Model Key-point (mass point); 9 = Water; 17 = Bridges; 18 = High Noise; 20 = Ignored Ground. Mass points deliverable LAS v1.4 with georeferenced information included in LAS header. The mass point files have 16-bit intensity values with GPS times recorded as Adjusted GPS Time, at a precision sufficient to allow unique timestamps for each return. The LAS files and mass points were tiled, without overlap, following FDOR tiling grid with 16 sub-tiles provided by Miami Dade County's Information Technology Department (ITD). The Miami-Dade County Information Technology Department (ITD) provided the NOAA Office for Coastal Management (OCM) with a copy of the las point data to make the data available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from AWS S3. This metadata record describes that data. This data set contains point cloud data(' in LAZ (compressed LAS) format', ''). The data may have been reprojected or otherwise modified from the original data in an automated process. Disregard projection information in this abstract and refer to the spatial reference section. purpose: GPI Geospatial, operating under the authority of Miami-Dade County Aviation Department, as per contract number E15-MDAD-01, has been tasked by Miami Dade County's Information Technology Department (ITD) to provide LiDAR data for 615 square miles, including the classification of the data and the creation of hydro-flattened Digital Elevation Model (DEM). GPI Geospatial has created a file geodatabase named 2021_Lidar.gdb credit: Miami-Dade County Information Technology Department (ITD) The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed 2025-06-02 at https://coast.noaa.gov/dataviewer. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10338/supplemental/fl2021_miami_dade_m10338.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION keyword: EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) edition: 17.0 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > FLORIDA keyword: VERTICAL LOCATION > LAND SURFACE type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) edition: 20.8 descriptiveKeywords: (MD_Keywords) keyword: LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) edition: 17.2 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 17.2 descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-02 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2021 Miami-Dade ITD Lidar: Miami-Dade County, FL [Data Date Range], https://www.fisheries.noaa.gov/inport/item/76028. resourceConstraints: (MD_Constraints) useLimitation: NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) license otherConstraints: Anchor: Universal (CC0 1.0) Public Domain Dedication To the extent possible under law, the U.S. Government has waived all copyright and related or neighboring rights to this dataset. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-02 from the NOAA system. Access Constraints: None resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-02 from the NOAA system. Use Constraints: Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. The data was collected under the supervision of a Florida licensed Surveyor and Mapper in compliance with Florida Statute 472.000. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-02 from the NOAA system. Distribution Liability: Translation of files to formats other than those described here is the sole responsibility of individuals downloading the data. Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: 2021 Miami-Dade ITD Lidar DEM: Miami-Dade County, FL date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 76039 associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 76028 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/76028.pdf protocol: WWW:LINK-1.0-http--link name: NOAA Data Management Plan (DMP) description: NOAA Data Management Plan for this record on InPort. function: (CI_OnLineFunctionCode) information role: (inapplicable) associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: Microsoft Windows 10 pro; Esri ArcGIS 10.6.1.9270 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -80.85965 eastBoundLongitude: -80.117 southBoundLatitude: 25.39015 northBoundLatitude: 25.98084 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2021-04-07 endPosition: 2021-04-09 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2021-04-16 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2021-06-10 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: (inapplicable) version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAS/LAZ - LASer version: (missing) fileDecompressionTechnique: LAZ distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10338/details/10338 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10338/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, UTM Zone 17 NAD83(2011) meters coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: The LiDAR data was registered to ground control established by GPI Geospatial Inc. in 2021 for the collection of LiDAR and Orthophotography of that year. This control is adequate to support the accuracy specifications identified for this project. The surveyor's report documents and certify the procedures and accuracies of the horizontal and vertical control, aircraft positioning systems, and system calibration procedures used in this LiDAR mapping project. The horizontal and vertical control is based on direct ties to National Geodetic Survey (NGS) control stations, National Spatial Reference System (NSRS). The horizontal control references the North American Datum of 1983/2011 current published datum (NAD_1983_2011_StatePlane_Florida_East_FIPS_0901_Feet). The vertical control references the NAVD88 using Geoid 18 to perform computations from ellipsoidal heights to orthometric heights. The vertical accuracy of the newly-established ground control is within one third of the specified LiDAR Fundamental Vertical Accuracy. All surveying and mapping performed for this project meets or exceeds FEMA Flood Hazard Mapping Program, Guidelines and Specifications for Flood Hazard Mapping Partners, Appendix A, Section A.5 Ground Control, and Section A.6 Ground Surveys and as superseded by Procedure Memorandum No.61 Standards for LiDAR and Other High Quality Digital Topography, 27 September 2010. GPI Geospatial Inc. collected the data at 20 points per square meter. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 2.2 feet RMSEx / RMSEy Horizontal Accuracy Class, which equates to Positional Horizontal Accuracy = +/- 3.8 feet (1.15 m) at a 95% confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: LAS Swath Non-Vegetated Vertical Accuracy (NVA) Tested 0.31 Feet (9.4 cm) Non-vegetated vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using 0.157 Feet (4.8 cm) (RMSEz) x 1.96000 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines and tested against the TIN using LiDAR ground points against 76 NVA points. LAS Swath Vegetated Vertical Accuracy (VVA) Tested 0.191 Feet (5.8 cm) at the 95th percentile reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines and tested against the TIN using LiDAR ground points against 35 VVA points. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Data set has been visually inspected. All data produced strives to meet National Mapping Accuracy Standards (NMAS). result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: See vendor's report result: (missing) lineage: (LI_Lineage) statement: The NOAA Office for Coastal Management (OCM) received 10,904 LAS files from the Miami-Dade County Information Technology Department (ITD). processStep: (LI_ProcessStep) description: The project was divided in two phases: Collection and classification of LiDAR data; and creation of 5-foot and 2-foot cell spaced hydro flattened mosaic DEM of the project area. The LiDAR data was collected utilizing a Riegl VQ-1560ii 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 3,592 kHg, resulting in an average of 28 points per square meter single swath. Three areas needed reflight's due to clouds and building shadows the flight height was lowered to get under the cloud celling in these areas. These areas were collected at 2,500 feet agl at 120 knots at a pulse rate repetition of 4,000kHg. These lines were collected at 50.6 points per square meter single swath. The sensor used a 60-degree field of view. The project was flown to have 30 percent overlap between swaths for original flight plan and 60% for the 2,500 foot altitude. The Global Positioning System (GPS) data were processed using Applanix POSPac Mapping Suite version 8.4 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 Geoid 18. 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 (or Bare Earth); 3 = low vegetation 0 - 5 ft; 4 = med veg 5 - 25 ft; 5 = high veg 25 - above; 6 = building; 7 = low point (noise); 9 = water; 17 = bridges; 18 = high noise; 20 = ignored ground. 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. Breaklines were digitized from the LiDAR data in ArcMap dateTime: DateTime: 2021-07-06T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received 10,904 LAS files from the Miami-Dade County Information Technology Department (ITD). The files were in Florida State Plane East NAD83(2011), US feet coordinates and the elevations were in NAVD88 (GEOID18) feet. The LAS files contain 11 classifications: 1 = unclassified; 2 = ground (or Bare Earth); 3 = low vegetation 0 - 5 ft; 4 = med veg 5 - 25 ft; 5 = high veg 25 ft and higher; 6 = building; 7 = low point (noise); 9 = water; 17 = bridges; 18 = high noise; 20 = ignored ground. OCM processed the 1, 2, 3, 4, 5, 6, 7, 9, 17, 18, and 20 point classes to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The data were converted to laz format using laszip 2. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 3. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the GEOID18 model b. Convert from FL State Plane East Zone 0901 (NAD83 2011), US survey foot coordinates to geographic coordinates c. Convert from vertical units of feet to meters d. Filter points outside the elevation range of -100 to 2000 feet e. Assign the geokeys, to sort the data by gps time and zip the data to database and to AWS S3. dateTime: DateTime: 2025-05-29T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: LAS Files date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Miami-Dade County Information Technology Department (ITD) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.miamidade.gov/global/technology/home.page protocol: WWW:LINK-1.0-http--link name: Miami-Dade County Information Technology Department (ITD) description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) originator processStep: (LI_ProcessStep) description: The dataset has been mosaiced, reprojected, and clipped as needed from the original input files using PDAL and GDAL commands. dateTime: DateTime: 2025-06-02 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |