| 2013 Suwannee River Water Management District Lidar: Bell (FL) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49708 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(2011) 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/6318/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6318 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: 2013 Suwannee River Water Management District Lidar: Bell (FL) alternateTitle: fl2013_srwmd_bell_m4892_metadata date: (CI_Date) date: 2015-06 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49708 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49708 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: (unknown) abstract: The Light Detection and Ranging (LiDAR) dataset is a survey of Suwannee River G13PD00141 1.0 Meter LiDAR Survey Area 4, Classified Point Cloud, in north-central Florida and encompasses 160 square miles. The LiDAR point cloud was flown at a nominal post spacing of 1.0 meters for unobscured areas. The LiDAR data and derivative products produced are in compliance with the U.S. Geological Survey National Geospatial Program Guidelines and Base Specifications, Version 1. The flight lines were acquired by Digital Aerial Solutions, LLC. between Feb. 04, 2013 and Feb. 15, 2013. Derivative products from the aerial acquisition include: Raw point cloud data in LAS v1.2, classified point cloud data in LAS v1.2, bare earth surface tiles (raster DEM ESRI float GRID format), bare earth surface DEMs mosaic (raster DEM MrSID format), control points, project report, and FGDC compliant XML metadata. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The purpose of collecting this LIDAR data to improve the SRWMD district-wide elevation data set for mapping, spatial analysis, and other SRWMD tasks and applications. This LIDAR data is replacing the digital USGS Topographic 7.5 Minute Map 5 foot contours that SRWMD have relied on for over 20 years. In addition the SRWMD wants to cooperate with Federal and State agencies to meet accepted LIDAR standards in order to produce the highest quality and consistent data possible. In addition, SRWMD collected this LIDAR data as part of a district, state, and national goal to have complete 100 percent LIDAR data coverage of the entire State of Florida. And last the SRWMD wants these data to become part of the USGS National Elevation Data program (NED) and NOAA Digital Coast for public use and distribution. 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/4892/supplemental/fl2013_srwmd_bell_m4892.kmz fileDescription: This graphic shows the lidar coverage for the 2013 extent of the project in Bell, Florida. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Bell keyword: Florida keyword: United States type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Country date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Surface keyword: Terrain type: (MD_KeywordTypeCode) theme descriptiveKeywords: (MD_Keywords) keyword: 2013 keyword: Fall type: (MD_KeywordTypeCode) temporal 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]: 2013 Suwannee River Water Management District Lidar: Bell (FL) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49708. 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: The data depicts the elevations at time of survey and are accurate only for that time. Exercise professional judgment in using this data. 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. These data depict the heights at the time of the survey and are only accurate for that time. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Digital Aerial Solutions, SRWMD, USGS, 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: 49708 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49708.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.920759 eastBoundLongitude: -82.650581 southBoundLatitude: 29.67788 northBoundLatitude: 29.923541 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2013-02-16 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2013-02-17 supplementalInformation: The final survey report for this project is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4892/supplemental/fl2013_srwmd_bell_m4892_surveyreport.pdf A lidar report for this project is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4892/supplemental/fl2013_srwmd_bell_m4892_lidarreport.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4892/supplemental/fl2013_srwmd_bell_m4892.kmz return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: none 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=4892 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/4892/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: There is not a systematic method of testing when testing horizontal accuracy in LiDAR. The horizontal accuracy is checked by collecting building corners during the survey. Lines are then digitized representing the building outline and the differences are measure from each individual survey point to the corner of the building outline. Stats are calculated to ensure horizontal tolerances are met. These measurements resulted in an RMSE of .42 meters and equals a .73 meter horizontal accuracy at the 95 % confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: There is not a systematic method of testing when testing horizontal accuracy in LiDAR. However this is tested during calibration of the sensor and is rechecked during the comparing of parallel and perpendicular flight lines. Additionally the horizontal accuracy is checked by collecting building corners during the survey. Lines are then digitized representing the building outline and the differences are measure from each individual survey point to the corner of the building outline. Stats are calculated to ensure horizontal tolerances are met. These measurements resulted in an RMSE of .42 meters and equals a .73 meter horizontal accuracy at the 95 % confidence level. Accuracy defined by NSSDA at the 95 % confidence level would be multiplier by 1.7308 times the RMSE.; Quantitative Value: 0.42 meters, Test that produced the value: 42 cm RMSE result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Lidar accuracy in a various conditions; Quantitative Value: 0.228 meters, Test that produced the value: Classifed point cloud tested 22.8 cm (0.75 ft.) supplemental vertical accuracy (SVA) at the 95th percentile in Forested catagories. Tested against the TIN.; Quantitative Value: 0.209 meters, Test that produced the value: Classifed point cloud tested 20.9 cm (0.68 ft.) consolidated vertical accuracy (CVA) at the 95th percentile in all categories of data. Tested against the TIN.; Quantitative Value: 0.248 meters, Test that produced the value: Classifed point cloud tested 24.8 cm (0.81 ft.) supplemental vertical accuracy (SVA) at the 95th percentile in Brush Land catagories. Tested against the TIN. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Measure evaluationMethodDescription: Cloud Cover: 0 result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Ground Truth data was collected of the major land cover classes dispersed within the area of interest. 30 points were collected in each of the classes if the land cover was more then 10% of the AOI. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: The GPS survey was tied into the Trimble VRS Now Network located in Florida. The Trimble VRS Now network is a network of continuously operating GPS reference stations that provides Real Time Kinematic (RTK) capabilities within a Real Time Network (RTN). This allows corrections to be applied to the points as they are being collected, eliminating the need for an adjustment. Several existing control monuments listed in the NSRS database were used as checks within the Trimble VRS Now Network. This confirmed network accuracies were being met during the field survey as well as providing a redundancy check on the Trimble VRSnetwork. The Specified local network accuracy of 5cm at the 95% confidence level was met or exceeded. Data analysis was accomplished by comparing ground truth checkpoints with LIDAR points from the edited data set, which were within 3.3 feet horizontally from the ground truth points. Based on the number of returns and the density of points in this project, it was not necessary to compare to anything further away than 3.3 feet horizontally from the ground truth points. Note that the edited LIDAR points are simply a subset of the raw LIDAR points. The points that fell above the ground surface on vegetation canopies, buildings, or other obstructions were removed from the data set. Comparisons were also made between the survey points and the LIDAR derived terrain surface. These comparisons provide an additional verification of the LIDAR data against the survey data. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: The ABGPS, inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the sensor and the IMU monitors the orientation. During the aerial survey, laser pulses reflected from features on the ground surface are detected by the receiver optics and collected by the data logger. GPS locations are based on data collected by receivers on the aircraft and base stations on the ground. The ground base stations are placed no more than 40 km radius from the flight survey area. dateTime: DateTime: 2013-01-22T00:00:00 processStep: (LI_ProcessStep) description: The ABGPS, IMU, and raw scans are integrated using proprietary software developed by Leica and delivered with the Leica System. The resultant file is in a LAS binary file format. The LAS version 1.2 file format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return number, intensity value, xyz, etc.). The LiDAR mass points were processed in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as defined by the LAS 1.2 specification. The datasets were divided into a 1500m by 1500m tiling scheme, based on the US Naitional Grid. The tiles are contiguous, do not overlap, and are suitable for seamless topographic data mosaics that include no "no data" areas. The names of the tiles include numeric column and row designations and all files utilize the LAS file extension dateTime: DateTime: 2013-02-15T00:00:00 processStep: (LI_ProcessStep) description: The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters are applied as appropriate for the production of bare earth digital elevation models (DEMs). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. dateTime: DateTime: 2013-02-21T00:00:00 processStep: (LI_ProcessStep) description: Filtered and edited data are subjected to rigorous QA/QC. A series of quantitative and visual procedures are employed to validate the accuracy and consistency of the filtered and edited data. Ground control is established by DAS and GPS-derived ground control points (GCPs) in various areas of dominant and prescribed land cover. These points are coded according to land cover, surface material, and ground control suitability. A suitable number of points are selected for calculation of a statistically significant accuracy assessment, as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error, and adequate sample size. Accuracy validation and evaluation is accomplished using proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial Data Accuracy (NSSDA), according to Federal Geographic Data Committee (FGDC) specifications. dateTime: DateTime: 2013-06-25T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the files in las format from SRWMD. The files contained lidar elevation and intensity measurements. The data were in State Plane Zone 903, NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from State Plane coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 09. 3. The LAS data were sorted by latitude and the headers were updated. 4. Duplicate points and erroneous elevations were removed. 5. Class 11 were reclassed to Class 15. dateTime: DateTime: 2015-06-10T00:00:00 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-08-01T05:43:25 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |