| 2017 SWFWMD Lidar DEM: Hillsborough County, FL | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:66859 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: 2022-03-21T18:07:21 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: EPSG::6360 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: EPSG::6443 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2017 SWFWMD Lidar DEM: Hillsborough County, FL alternateTitle: fl2017_hills_dem_m9457_metadata date: (CI_Date) date: 2017 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2019-04-26 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 66859 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/66859 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://coast.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: NOAA's Office for Coastal Management (OCM) website description: Information on the NOAA Office for Coastal Management (OCM) function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://watermatters.sharefile.com/share/view/s8c9019e00fd243908654e733a6b2016c/fo8aa188-f8b9-4341-b2da-78817608948c protocol: WWW:LINK-1.0-http--link name: SWFWMD Data Distribution Site description: Link to the Southwest Florida Water Management District (SWFWMD) data distribution site. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/raster5/elevation/FL_Hills_DEM_2017_9457/supplemental/Hillsborough_County_Topographic_Lidar_Final_Report_20190611.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/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: Dewberry collected 1200 square miles of lidar data in Hillsborough County, Florida. The nominal pulse spacing for this project was 1 point every 0.25 meters or a nominal pulse density of 16 points per square meter. Dewberrry used proprietary procedures to classify the LAS according to project specifications: 1-Unclassified, 2-Ground, 6-Building Rooftops, 7-Low Noise, 9-Water, 17- Bridge Decks, 18-High Noise. Geometrically unreliable points, ground points within 2 feet of breaklines, and ground points within 3 feet of buiding rooftops have been identified with the Withheld Flag. Overage points have been identified with the Overlap Flag. The lidar data were combined with 3D breaklines compiled by Dewberry to create hydro-enforced bare-earth DEMs. The data were tiled according to the Florida Statewide Lidar Index tiling scheme with each tile covering an area of 5,000 feet by 5,000 ft. purpose: The DEMs model the bare-earth surface and are enforced with the 3D breaklines created for this project. credit: Dewberry 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://coast.noaa.gov/htdata/raster5/elevation/FL_Hills_DEM_2017_9457/supplemental/fl2017_hills_dem_m9457.kmz fileDescription: Link to the dataset footprint. fileType: KML graphicOverview: (MD_BrowseGraphic) fileName: https://coast.noaa.gov/htdata/raster5/elevation/FL_Hills_DEM_2017_9457/breaklines/ fileDescription: Link to the hydro breaklines. fileType: Zip descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > DIGITAL ELEVATION/TERRAIN MODEL (DEM) 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) 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) 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) descriptiveKeywords: (MD_Keywords) keyword: AIRCRAFT type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Hillsborough County type: (MD_KeywordTypeCode) place descriptiveKeywords: (MD_Keywords) keyword: DEMs - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Cite As: OCM Partners, [Date of Access]: 2017 SWFWMD Lidar DEM: Hillsborough County, FL [Data Date Range], https://www.fisheries.noaa.gov/inport/item/66859. 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) accessConstraints: (MD_RestrictionCode) otherRestrictions useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | 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. | Distribution Liability: Translation of files to formats other than those described here is the sole responsibility of individuals downloading these 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: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 66859 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/66859.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) grid language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: Microsoft Windows 7 Enterprise Service Pack 1; ESRI ArcCatalog 10.3. extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -82.655501 eastBoundLongitude: -82.049932 southBoundLatitude: 27.633443 northBoundLatitude: 28.185092 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2017-01-31 endPosition: 2017-03-04 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: GeoTIFF version: (missing) 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=9457/details/9457 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, map projection, file format, etc. A new metadata will be produced to reflect your request using this record as a base. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/raster5/elevation/FL_Hills_DEM_2017_9457 protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in the original coordinate system. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The DEMs are derived from the source lidar and 3D breaklines created from the lidar. Horizontal accuracy is not performed on the DEMs or breaklines. Only checkpoints photo-identifiable in the intensity imagery can be used to test the horizontal accuracy of the lidar. Photo-identifiable checkpoints in intensity imagery typically include checkpoints located at the ends of paint stripes on concrete or asphalt surfaces or checkpoints located at 90 degree corners of different reflectivity, e.g. a sidewalk corner adjoining a grass surface. The xy coordinates of checkpoints, as defined in the intensity imagery, are compared to surveyed xy coordinates for each photo-identifiable checkpoint. These differences are used to compute the tested horizontal accuracy of the lidar. As not all projects contain photo-identifiable checkpoints, the horizontal accuracy of the lidar cannot always be tested. Lidar systems are calibrated during installation of the system and then again for every project acquired. Typical calibrations include cross flights that capture features from multiple directions that allow adjustments to be performed so that the captured features are consistent between all swaths and cross flights from all directions. This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 1.35 ft (41 cm) RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 3.28 ft (100 cm) at a 95% confidence level. Eleven (11) checkpoints were photo-identifiable but do not produce a statistically significant tested horizontal accuracy value. Using this small sample set of photo-identifiable checkpoints, positional accuracy of this dataset was found to be RMSEx = 1.09 ft (33.2 cm) and RMSEy = 0.70 ft (21.3 cm) which equates to +/- 2.23 ft (68 cm) at 95% confidence level. While not statistically significant, the results of the small sample set of checkpoints are within the produced to meet horizontal accuracy result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The DEMs are derived from the source lidar and 3D breaklines created from the lidar. The DEMs are created using controlled and tested methods to limit the amount of error introduced during DEM production so that any differences identified between the source lidar and final DEMs can be attributed to interpolation differences. DEMs are created by averaging several lidar points within each pixel which may result in slightly different elevation values at a given location when compared to the source LAS, which is tested by comparing survey checkpoints to a triangulated irregular network (TIN) that is created from the lidar ground points. TINs do not average several lidar points together but interpolate (linearly) between two or three points to derive an elevation value. The vertical accuracy of the final bare earth DEMs was tested by Dewberry with 178 independent checkpoints. The same checkpoints that were used to test the source lidar data were used to validate the vertical accuracy of the final DEM products. The survey checkpoints are evenly distributed throughout the project area and are located in areas of non-vegetated terrain (147 checkpoints), including bare earth, open terrain, and urban terrain, and vegetated terrain (31 checkpoints), including forest, brush, tall weeds, crops, and high grass. The vertical accuracy is tested by extracting the elevation of the pixel that contains the x/y coordinates of the checkpoint and comparing these DEM elevations to the surveyed elevations. All checkpoints located in non-vegetated terrain were used to compute the Non-vegetated Vertical Accuracy (NVA). Project specifications required a NVA of 0.64 ft (19.6 cm) at the 95% confidence level based on RMSEz (0.33 ft/10 cm) x 1.9600. All checkpoints located in vegetated terrain were used to compute the Vegetated Vertical Accuracy (VVA). Project specifications required a VVA of 0.96 ft (29.4 cm) based on the 95th percentile. This DEM dataset was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 0.33 ft (10 cm) RMSEz Vertical Accuracy Class. Actual NVA accuracy was found to be RMSEz =0.12 ft (3.6 cm), equating to +/- 0.23 ft (7.0 cm) at 95% confidence level. This DEM dataset was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 0.33 ft (10 cm) RMSEz Vertical Accuracy Class. Actual VVA accuracy was found to be +/- 0.50 ft (15.2 cm) at the 95th percentile. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: A visual qualitative assessment was performed to ensure data completeness and bare earth data refinement. No void or missing data. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data covers the project tiling scheme. result: (missing) lineage: (LI_Lineage) statement: The NOAA Office for Coastal Management (OCM) downloaded the DEM .img file from the Southwest Florida Water Management District (SWFWMD). processStep: (LI_ProcessStep) description: Class 2, ground, lidar points are exported from the LAS files into an Arc Geodatabase (GDB) in multipoint format. The 3D breaklines, water bodies, hydrographic features, and islands are imported into the same GDB. 2D building footprints are buffered by 3 feet and the highest ground elevation within the buffered footprint is applied to the entire footprint. The 3D building footprints are then imported into the same GDB as the multipoints and other 3D breaklines. An ESRI Terrain is generated from these inputs. The surface type of each input is as follows: Ground Multipoint: Masspoints Water bodies: Hard Replace Hydrographic feature : Hard Line Islands : Hard Line Building Footprint: Hard Replace The ESRI Terrain is converted to a raster. The raster is created using linear interpolation with a 2.5 foot cell size. The DEM is reviewed with hillshades in both ArcGIS and Global Mapper. Hillshades allow the analyst to view the DEMs in 3D and to more efficiently locate and identify potential issues. Analysts review the DEM for missed lidar classification issues, incorrect breakline elevations, incorrect hydro-flattening or hydro-enforcement, and artifacts that are introduced during the raster creation process. The corrected and final DEM is clipped to individual tiles. Dewberry uses a proprietary tool that clips the DEM to each tile located within the final Tile Grid, names the clipped DEM to the Tile Grid Cell name, and verifies that final extents are correct. All individual tiles are loaded into Global Mapper for the last review. During this last review, an analsyt checks to ensure full, complete coverage, no issues along tile boundaries, tiles seamlessly edge-match, and that there are no remaining processing artifacts in the dataset. dateTime: DateTime: 2019-04-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) downloaded 1 raster DEM file in .img format from the Southwest Florida Water Management District (SWFWMD). The data were in Florida State Plane West NAD83(2011), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. The bare earth raster file was at a 2.5 feet grid spacing. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used internal an script to assign the EPSG codes (Horizontal EPSG: 6443 and Vertical EPSG: 6360) and convert the .img file to GeoTiff format. 2. Copied the file to https. processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: The 3D breaklines were used to enforce elevations along hydrographic features, water bodies, islands, and building footprints were used to cause water to flow around buildings in the bare-earth DEMs. scaleDenominator: (MD_RepresentativeFraction) denominator: 2000 sourceCitation: (CI_Citation) title: 3D Breaklines date: (CI_Date) date: 2019-04-26 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Dewberry role: (inapplicable) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2017-01-31 endPosition: 2017-03-28 source: (LI_Source) description: Source Contribution: Class 2, ground, was used from the tiled lidar to create the bare-earth DEM masspoints. scaleDenominator: (MD_RepresentativeFraction) denominator: 2000 sourceCitation: (CI_Citation) title: Tiled Lidar date: (CI_Date) date: 2019-04-26 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Dewberry role: (inapplicable) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2017-01-31 endPosition: 2017-03-28 | |