| 2017 Lidar DEM: City of Palm Coast, FL | identificationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:52734 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: 2023-07-03T11:48:47 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2017 Lidar DEM: City of Palm Coast, FL alternateTitle: fl2017_palmcoast_dem_m8535_metadata.xml date: (CI_Date) date: 2017-10 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 52734 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/52734 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://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8501 protocol: WWW:LINK-1.0-http--link name: Citation URL description: Link to custom download the lidar point data from which these raster Digital Elevation Model (DEM) data were created. 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/geoid12b/8501/supplemental/fl2017_palmcoast_m8501_lidar_report.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. 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/geoid12b/8501/breaklines/ protocol: WWW:LINK-1.0-http--link name: Citation URL description: Link to download the breakline data. 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: Digital Aerial Solutions LLC collected 185.5 square miles in the City of Palm Coast in Florida. The nominal pulse spacing for this project was 1 point every 0.35 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity, 17- Overpasses and Bridges, 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 FDEM statewide tiling scheme with each tile covering an area of 5,000 ft by 5,000 ft. A total of 161 LAS tiles and 161 DEM tiles were produced for the entire project. The NOAA Office for Coastal Management (OCM) received 161 DEM files from the City of Palm Coast, FL. OCM processed the data to be available on the Digital Coast 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, are also available. These data are available for custom download at the link provided in the URL section of this metadata record. Breakline data are also available. These data are are available for download at the link provided in the URL section of this metadata record. 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. purpose: The purpose of this lidar data was to produce high accuracy 3D elevation products, including tiled lidar in LAS 1.4 format, 3D breaklines, and 2.5 foot cell size hydro flattened Digital Elevation Models (DEMs). All products follow and comply with USGS Lidar Base Specification Version 1.2. credit: St. Johns River Water Management District 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/geoid12b/8501/supplemental/fl2017_palmcoast_m8501.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML 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: 12.3 descriptiveKeywords: (MD_Keywords) 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: 12.3 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: 14.9 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane keyword: DEM > Digital Elevation Model type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 14.9 descriptiveKeywords: (MD_Keywords) keyword: DEM keyword: DTM type: (MD_KeywordTypeCode) theme 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 Lidar DEM: City of Palm Coast, FL [Data Date Range], https://www.fisheries.noaa.gov/inport/item/52734. 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: This data was produced for the St. Johns River Water Management District according to specific project requirements. This information is provided "as is". Further documentation of this data can be obtained by contacting: St. Johns River Water Management District, 4049 Reid Street, P.O. Box 1429, Palatka, Fl 32178-1429. Telephone (386) 329-4500. 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: 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: 52734 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/52734.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 language: eng; US topicCategory: (MD_TopicCategoryCode) oceans environmentDescription: Microsoft Windows 7 Enterprise Service Pack 1; ESRI ArcCatalog 10.4.1 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -81.381478 eastBoundLongitude: -81.14499762 southBoundLatitude: 29.40842538 northBoundLatitude: 29.65638572 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2017-03-28 endPosition: 2017-03-29 supplementalInformation: A complete description of this dataset is available in the Final Project Report submitted to St. Johns River Water Management District. A link to this report is provided in the URL section of this metadata record. return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip 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=8535 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/raster2/elevation/FL_Palm_Coast_DEM_2017_8535 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: 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. 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. Lidar vendors calibrate their lidar systems 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. 1.81 ft (55.1 cm) at 95% confidence level 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 (1 meter) at a 95% confidence level. Four (4) 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 = 0.67 ft (20.4 cm) and RMSEy = 0.80 ft (24.4 cm) which equates to +/- 1.81 ft (55.1 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 36 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 (26 checkpoints), including bare earth, open terrain, and urban terrain, and vegetated terrain (10 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. NVA = 0.28 ft (8.5 cm) at 95% confidence level VVA = 0.35 ft (10.7 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 NVA accuracy was found to be RMSEz =0.14 ft (4.2 cm), equating to +/- 0.28 ft (8.5 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.35 ft (10.7 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 full tiles. No void or missing data exists. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data covers the project boundary. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Data for St. Johns River Water Management District QL2 Lidar Project was acquired by Digital Aerial Solutions LLC. The project area included approximately 185.5 contiguous square miles or 480.44 square kilometers for the City of Palm Coast in Florida. Lidar sensor data were collected with the Leica ALS80 HP lidar system. The data was delivered in NAD83(2011) State Plane Florida East, U.S. Survey Feet and NAVD88 (Geoid12B), U.S. Survey Feet. 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. 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. dateTime: DateTime: 2017-03-01T00:00:00 processStep: (LI_ProcessStep) description: 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 (5,000 ft x 5,000 ft). The tiled data is then opened in Terrascan where Dewberry identifies edge of flight line points that may be geometrically unusable with the withheld bit. These points are separated from the main point cloud so that they are not used in the ground algorithms. Overage points are then identified with the overlap bit. 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. A final QC is performed on the data. 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) dateTime: DateTime: 2017-06-01T00:00:00 processStep: (LI_ProcessStep) description: Dewberry used GeoCue software to produce intensity imagery and raster stereo models from the source lidar for use in lidargrammetry techniques. Dewberry then produced full point cloud intensity imagery, bare earth ground models, density models, and slope models. These files were ingested into eCognition software, segmented into polygons, and training samples were created to identify water. eCognition used the training samples and defined parameters to identify water segments throughout the project area. Water segments were then reviewed for completeness, separated into project defined feature classes, merged, and smoothed. Elevations derived from a bare earth lidar terrain were applied to each feature for 3D attribution. The delineation of lakes and ponds and tidal waters, or other water bodies at a constant elevation, was achieved using eCognition software. Lidargrammetry was used to monotonically collect streams and rivers, or features that have gradient 3D elevations. All breaklines were collected according to specifications for the project. dateTime: DateTime: 2017-06-01T00:00:00 processStep: (LI_ProcessStep) description: Dewberry digitzed 2D bridge deck polygons from the intensity imagery and used these polygons to classify bridge deck points in the LAS to class 17. As some bridges are hard to identify in intensity imagery, Dewberry then used ESRI software to generate bare earth elevation rasters. Bare earth elevation rasters do not contain bridges. As bridges are removed from bare earth DEMs but DEMs are continuous surfaces, the area between bridge abutments must be interpolated. The rasters are reviewed to ensure all locations where the interpolation in a DEM indicates a bridge have been collected in the 2D bridge deck polygons. dateTime: DateTime: 2017-09-01T00:00:00 processStep: (LI_ProcessStep) description: The bridge deck polygons are loaded into Terrascan software. Lidar points and surface models created from ground lidar points are reviewed and 3D bridge breaklines are compiled in Terrascan. Typically, two breaklines are compiled for each bridge deck-one breakline along the ground of each abutment. The bridge breaklines are placed perpendicular to the bridge deck and extend just beyond the extents of the bridge deck. Extending the bridge breaklines beyond the extent of the bridge deck allows the compiler to use ground elevations from the ground lidar data for each endpoint of the breakline. dateTime: DateTime: 2017-10-01T00:00:00 processStep: (LI_ProcessStep) description: Breaklines are reviewed against lidar intensity imagery to verify completeness of capture. All breaklines are then compared to ESRI terrains created from ground only points prior to water classification. The horizontal placement of breaklines is compared to terrain features and the breakline elevations are compared to lidar elevations to ensure all breaklines match the lidar within acceptable tolerances. Some deviation is expected between hydrographic breakline and lidar elevations due to monotonicity, connectivity, and flattening rules that are enforced on the hydrographic breaklines. Once completeness, horizontal placement, and vertical variance is reviewed, all breaklines are reviewed for topological consistency and data integrity using a combination of ESRI Data Reviewer tools and proprietary tools. Corrections are performed within the QC workflow and re-validated. dateTime: DateTime: 2017-09-01T00:00:00 processStep: (LI_ProcessStep) description: Class 2, ground, and Class 8, model key points, lidar points are exported from the LAS files into an Arc Geodatabase (GDB) in multipoint format. The 3D breaklines, Inland Lakes and Ponds and Streams and Tidal are imported into the same GDB. An ESRI Terrain is generated from these inputs. The surface type of each input is as follows: Ground Multipoint: Masspoints Inland Lakes and Ponds: Hard Replace Streams and Rivers : Hard Line Tidal : Hard Replace dateTime: DateTime: 2017-09-01T00:00:00 processStep: (LI_ProcessStep) description: 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, and artifacts that are introduced during the raster creation process. dateTime: DateTime: 2017-10-01T00:00:00 processStep: (LI_ProcessStep) description: 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: 2017-10-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received 161 DEM files from the City of Palm Coast, Florida. The data were in FL State Plane East (NAD83 2011) coordinates and NAVD88 (Geoid12B) elevations in feet. The bare earth hydro-flattened raster files were at a 2.5 ft grid spacing. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: Converted the raster files from img format to cloud optimized geotiffs dateTime: DateTime: 2023-07-03T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: Originator date: (missing) | |