| Braden River - Aerial Topographic Mapping | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49686 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset 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-08-09T17:11:37 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: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(HARN) 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/4152/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4152 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.epsg.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::5703 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: Braden River - Aerial Topographic Mapping alternateTitle: fl2005_swfwmd_bradenriver_m2521_metadata date: (CI_Date) date: 2013-12-12 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49686 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49686 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/dataviewer protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download 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: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (CI_PresentationFormCode) mapDigital abstract: This metadata record describes the ortho & LIDAR mapping of the Braden River area, FL. The mapping consists of LIDAR data collection, contour generation, and production of natural color orthophotography with a 1ft pixel using imagery collected with a Wild RC-30 Aerial Camera. Additionally, this area was collected at a 30-cm GSD using color imagery collected with a Leica ADS-40 Aerial Digital Camera as part of the Sarasota County project area. More information on the ADS-40 imagery collected over Braden River can be found in the metadata for the Sarasota County project. Original contact information: Contact Name: Harold Rempel Contact Org: EarthData International Title: Project Manager Phone: 301-948-8550 Email: metadata@earthdata.com This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The purpose of this mapping project is to create and deliver digital terrain models (DTM), capable of generating one-foot contours and to produce orthophotography at a 200'. credit: Acknowledgement of SWFWMD would be appreciated in products derived from these data. This digital data is produced for the purposes of updating/creating a DFIRM database. Ground control and quality control checkpoints were collected by EarthData Aviations. LiDAR was acquired and processed by Earthdata International. Quality Control testing and assurance was performed by Earthdata International. 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 Jul 01, 2023 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) unknown graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2521/supplemental/SWFWMD_2005_BradenRiver_geo.KMZ fileDescription: This graphic shows the lidar coverage for the 2005 SWFWMD Braden River data set. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Braden River keyword: Florida keyword: Hillsborough County keyword: Sarasota County type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Geographic Names Information System date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Aerial Photography keyword: Bare Earth keyword: Contours keyword: Digital Orthophotography keyword: Ground Control keyword: Point Cloud type: (MD_KeywordTypeCode) theme 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: Cite As: OCM Partners, [Date of Access]: Braden River - Aerial Topographic Mapping [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49686. 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: 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: 49686 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49686.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 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -82.53037 eastBoundLongitude: -82.287044 southBoundLatitude: 27.341756 northBoundLatitude: 27.461523 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Publication Date timePosition: 2005-05-20 supplementalInformation: A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2521/supplemental/SWFWMD_2005_BradenRiver_geo.KMZ return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: All deliverables meet specifications in contract. LAS Files meet ASPRS Classification Standards. date: (unavailable) return to top distributionInfo: (MD_Distribution) 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=2521 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. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2521/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: The generated contours have been produced to be fully compliant with NSSDA accuracy standards for 2' contours. The digital orthophotography meets national mapping accuracy standards for 200 scale product. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: See LiDAR data report.; Quantitative Value: 1.0 meters, Test that produced the value: See LiDAR data report. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The digital elevation model is fully compliant with National Standard for Spatial Data Accuracy (NSSDA) published by the Federal Geographic Data Committee (FGDC) in 1998. The NSSDA uses root-mean-square error (RMSE) to estimate positional accuracy. RMSE is the square root of the average of the set of squared differences between dataset coordinate values and coordinate values from an independent source of higher accuracy for identical points. Accuracy is reported in ground distances at the 95% confidence level. Accuracy reported at the 95% confidence level means that 95% of the positions in the dataset will have an error with respect to true ground position that is equal to or smaller than the reported accuracy value. The reported accuracy value reflects all uncertainties, including those introduced by geodetic control coordinates, compilation, and final computation of ground coordinate values in the product. ; Quantitative Value: 0.65 meters, Test that produced the value: Accuracy calculated to 65 cm RMSEz. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Measure evaluationMethodDescription: Cloud Cover: 0 result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The following software is used for validation of the 1. Aerotriangulation - Photo-T, ISAT 2. DTM data - Z/I Imaging SSK 3. Digital Orthophotography - Z/I Imaging OrthoPro result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Compliance with the accuracy standard was ensured by the placement of GPS ground control prior to the acquisition of aerial photography. The following checks were performed. 1. The ground control and airborne GPS data stream were validated through a fully analytical bundle aerotriangulation adjustment. The residuals of the adjustment met the required standards for accuracy which are 1 part in 10,000 of the flying height for the horizontal position (X and Y) and 1 part in 9,000 or better of the flying height in elevation (Z). 2. The DTM (Digital Terrain Model) data were checked against the project control. The technician visited and confirmed the accuracy of the project mass points during initial compilation. 3. Digital orthophotography was validated through an inspection of edge matching and visual inspection for image quality. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: New ground control was established to control and orient the photography, and included both photo-identifiable features and artificial targets. The ground control network and airborne GPS data was integrated into a rigid network through the completion of a fully analytical bundle aerotriangulation adjustment. 1. The original aerial film was scanned at a resolution of 1,210 DPI. The scans were produced using Z/I Imaging PhotoScan flatbed metric scanners. Each unit has a positional accuracy of 1.5 microns and a radiometric resolution of 1,024 gray levels for each of three color layers. 2. The raster scans were given a preliminary visual check on the scanner workstation to ensure that the raster file size is correct and to verify that the tone and contrast were acceptable. A directory tree structure for the project was established on one of the workstations. This project was then accessed by other workstations through the network. The criteria used for establishment of the directory structure and file naming conventions accessed through the network avoids confusion or errors due to inconsistencies in digital data. The project area was defined using the relevant camera information that was obtained from the USGS camera calibration report for the aerial camera and the date of photography. The raster files were rotated to the correct orientation for mensuration on the softcopy workstation. The rotation of the raster files was necessary to acommodate different flight directions from one strip to the next. The technician verified that the datum and units of measurement for the supplied control were consistent with the project requirements. 3. The photogrammetric technician performed an automatic interior orientation for the frames in the project area. The softcopy systems that were used by the technicians have the ability to set up predefined fiducial templates for the aerial camera(s) used for the project. Using the template that was predefined in the interior orientation setup, the software identified and measured the eight fiducial positions for all the frames. Upon completion, the results were reviewed against the tolerance threshold. Any problems that occurred during the automatic interior orientation would cause the software to reject the frame and identify it as a potential problem. The operator then had the option to measure the fiducials manually. dateTime: DateTime: 2004-10-11T00:00:00 processStep: (LI_ProcessStep) description: 4. The operator launched the point selection routine which automatically selected pass and tie points by an autocorrelation process. The correlation tool that is part of the routine identified the same point of contrast between multiple images in the Von Gruber locations. The interpolation tool can be adjusted by the operator depending on the type of land cover in the triangulation block. Factors that influence the settings include the amount of contrast and the sharpness of features present on the photography. A preliminary adjustment was run to identify pass points that had high residuals. This process was accomplished for each flight line or partial flight line to ensure that the network has sufficient levels of accuracy. The points were visited and the cause for any inaccuracy was identified and rectified. This process also identified any gaps where the point selection routine failed to establish a point. The operator interactively set any missing points. 5. The control and pass point measurement data was run through a final adjustment on the Z/I SSK PhotoT workstations. The PhotoT program created a results file with the RMSE results for all points within the block and their relation to one another. The photogrammetrist performing the adjustments used their experience to determine what course of action to take for any point falling outside specifications. 6. The bundle adjustment was run through the PhotoT software several times. The photogrammetrist increased the accuracy parameters for each subsequent iteration so, when the final adjustment was run, the RMSE for the project met the accuracy of 1 part in 10,000 of the flying height for the horizontal position (X and Y) and 1 part in 9,000 or better of the flying height in elevation (Z). The errors were expressed as a natural ratio of the flying height utilizing a one-sigma (95%) confidence level. 7. The accuracy of the final solution was verified by running the final adjustment, placing no constraints on any quality control points. The RMSE values for these points must fall within the tolerances above for the solution to be acceptable. the adjustment with the RMSE values for each point measured. The .XYZ file contains the adjusted X, Y, Z,coordinates for all the measured points and the .PHT file contains the exterior orientation parameters of each exposure station. dateTime: DateTime: 2004-10-11T00:00:00 processStep: (LI_ProcessStep) description: EarthData has developed a unique method for processing lidar data to identify and remove elevation points falling on vegetation, buildings, and other aboveground structures. The algorithms for filtering data were utilized within EarthData's proprietary software and commercial software written by TerraSolid. This software suite of tools provides efficient processing for small to large-scale, projects and has been incorporated into ISO 9001 compliant production work flows. The following is a step-by-step breakdown of the process. 1. Using the lidar data set provided by EarthData, the technician performs calibrations on the data set. 2. Using the lidar data set provided by EarthData, the technician performed a visual inspection of the data to verify that the flight lines overlap correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the dataset and inspected them where adjacent flight lines overlapped. These overlapping areas were merged and a process which utilizes 3-D Analyst and EarthData's proprietary software was run to detect and color code the differences in elevation values and profiles. The technician reviewed these plots and located the areas that contained systematic errors or distortions that were introduced by the lidar sensor. 3. Systematic distortions highlighted in step 2 were removed and the data was re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from one type of land cover to another. 4. The lidar data for each flight line was trimmed in batch for the removal of the overlap areas between flight lines. The data was checked against a control network to ensure that vertical requirements were maintained. Conversion to the client-specified datum and projections were then completed. The lidar flight line data sets were then segmented into adjoining tiles for batch processing and data management. 5. The initial batch-processing run removed 95% of points falling on vegetation. The algorithm also removed the points that fell on the edge of hard features such as structures, elevated roadways and bridges. 6. The operator interactively processed the data using lidar editing tools. During this final phase the operator generated a TIN based on a desired thematic layers to evaluate the automated classification performed in step 5. This allowed the operator to quickly re-classify points from one layer to another and recreate the TIN surface to see the effects of edits. Geo-referenced images were toggled on or off to aid the operator in identifying problem areas. The data was also examined with an automated profiling tool to aid the operator in the reclassification. 6.The data was separated into a bare-earth DEM. A grid-fill program was used to fill data voids caused by reflective objects such as buildings and vegetation. The final DEM was written to an ASCII XYZ and LAS format. 7. The reflective surface data was also delivered in ASCII XYZ and LAS format. 8. Final TIN files are created and delivered. dateTime: DateTime: 2004-08-10T00:00:00 processStep: (LI_ProcessStep) description: This process describes the method used to compile breaklines to support the lidar digital elevation model data. Around the perimeter of the lidardata set to complete the surface model, breaklines were photogrammetrically derived . The following step-by-step procedures were utilized for breakline development. The breakline file contains three dimensionally accurate line strings describing topographical features. The relationship of lidar points to breaklines will vary depending on the complexity and severity of the terrain. Breaklines were collected where necessary to support the final product. Examples of some such locations include along the edges of roads, stream banks and centerlines, ridges, and other features where the slope of the terrain changes. 1. Using the imagery provided by EarthData Aviations, breakline data was captured in the MicroStation environment, which allowed the photogrammetrist to see graphically where each lidar X, Y, and Z point and any breaklines fall in relation to each other. This unique approach allowed for interactive editing of the breakline by the photogrammetrist. The technician generated a set of temporary contours for the stereo model in the ZI work environment to provide further guidance on the breakline placement. The technician added and/or repositioned breaklines to improve the accuracy as required. Once these processes were completed, the temporary guidance contours were deleted, and the data were passed to the editing department for quality control and formatting. 4. The breakline data set was then put into an ESRI shape file format 5. The 1 foot contours were generated in Microstation (using 2 foot specifications) with an overlay software package called TerraSolid. Within TerraSolid, the module Terramodler was utilized to first create the tin and then a color relief was created to view for any irregularities before the contour generator was run. The contours were checked for accuracy over the DTM and then the Index contours were annotated. At this point the technician identified any areas of heavy tree coverage by collecting obscure shapes. Any contours that were found within these shapes do not meet Map Accuracy Standards and are coded as obscure. The dataset was viewed over the orthos before the final conversion. The contours were then converted to Arc/Info where final QC AMLs were run to verify that no contours were crossing. The contours were delivered in shp format as a merged file. dateTime: DateTime: 2004-12-10T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received zipped files in PNT format. The files contained ASCII LiDAR point cloud data for intensity and elevation measurements. OCM performed the following processing on the data for data storage purposes and Digital Coast provisioning: 1. The data were converted from projected State Plane (Florida West 0902) coordinates to geographic (NAD83) coordinates 2. The data were converted from NAVD88 heights (in feet) to ellipsoid heights using Geoid03 (in meters) 3. The LAS files were run through a program to remove error value based on elevation. 4. The LAS files were run through a ground algorithm to correctly convert "never classified" points to the ground class. 5. Data were zipped to laz format dateTime: DateTime: 2012-08-06T00:00:00 source: (LI_Source) description: Source Contribution: The aerial photographic mission was composed of a total of 237 exposures in 10 North-South oriented flight lines. Photography was obtained at an altitude of 3,960 feet above mean terrain. Aerial photography was exposed in conjunction with airborne GPS; the stationary GPS receiver was positioned over a control point located at the airport. Aerial photography was exposed on natural color negative film using Wild RC-30 camera 5086, with 153.277 mm (6 inch) focal length lens cone number 13112. Photography was exposed on Agfa X-100 film, emulsion number 67663036. | Source Geospatial Form: profile | Type of Source Media: filmstrip scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Braden River Aerial Photography date: (CI_Date) date: 2005-03-08 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2004-03-08 source: (LI_Source) description: Source Contribution: The LIDAR aquisition for Braden River was acquired in two sorties using the Leica ALS40 sensor. The data was acquired at a flying height of 5,000 feet AMT with a scan rate of 26 Hz and a 20 degree field of view. | Source Geospatial Form: profile | Type of Source Media: Fire wire scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: LIDAR Acquisition of Braden River date: (CI_Date) date: 2004-03-04 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2004-02-28 endPosition: 2004-03-04 source: (LI_Source) description: Source Contribution: Kevin Chappell, a Florida PSM, under contract to EarthData International established a total of 17 new combined LIDAR/photo identities established, designated BRAD-01 through BRAD-17. In addition, there were 9 LIDAR check points, designated BRAD-CK-01 through BRAD-QC-10 (there was no BRAD-QC-09). There were six temporary base points, three in the area covered by this project. Points were established prior to aerial imagery acquisition. The points were surveyed using GPS for both vertical and horizontal coordinate values. Ground control references Florida West State Plane NAD83, NAVD88 both in Meters. | Source Geospatial Form: diagram | Type of Source Media: electronic mail system scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Report of Survey of Braden River, FL date: (CI_Date) date: 2006-05-06 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2004-04-05 processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2023-07-01T06:10:54 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |