| 2013 City and Borough of Juneau, Alaska Lidar | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49628 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: 2023-02-21T18:41:16 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 5279631270 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: EPSG::6318 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: EPSG::5866 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2013 City and Borough of Juneau, Alaska Lidar alternateTitle: ak2013_cbj_juneau_m4813_metadata date: (CI_Date) date: 2015-03-10 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49628 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49628 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/mllw/4813/supplemental/ak2013_cbj_juneau_m4813_surveyreport.pdf protocol: WWW:LINK-1.0-http--link name: Project report description: Project report from the lidar contractor function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: This dataset is LiDAR point cloud data, which encompasses a 100 meter buffer around the Juneau,AK study area, approximately 121,313 acres. Dataset Description: This dataset consists of 1273 .LAS files delineated in 750 x 750 m tiles and named as specified by the client. Each .LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. LAS points contain RGB values from orthoimagery mosaics. Normalized intensity values are represented in the intensity field in this version of the point cloud. Ground Conditions: LiDAR acquisition of near shore areas was prioritized to coincide with the lowest tides possible, within constraints of daily local weather patterns. Leaf-off, no snow conditions were targeted in all other areas given the diverse terrain represented in the study area. The LAZ files have vertical georeferencing using the EPSG 5866 code for mean lower low water. However, this code is for depth while the data is in height. There was no appropriate code for MLLW height at the time. purpose: Data was collected to aid CBJ in assessing the topographic and geophysical properties of the study area to support municipal planning, habitat assessments, and general development in the region. The LiDAR point cloud data were used to create classified LiDAR LAS files, normalized intensity images, 3D breaklines, bare earth DEM, bare earth hydro-flattened DEM, High Hit DSM, Vegetation height model, bridge footprints, 0.5m contours, and a mean high water contour. Data were also used to rectify 4-band orthophotos. The contract for this project was funded by the Coastal Impact Assistance Program through the Alaska Department of Commerce, Community, and Economic Development as part of Grant # 10-CIAP-0009, titled 'Habitat Mapping and Analysis Project.' All processing was completed by WSI. In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. TINing the points produces large triangles and hence the elevations may be less accurate within such areas. Elevation values for open water surfaces are derived from waters edge breaklines. Triangles were created across water surfaces by interpolating from the nearest breakline elevation points. RandM Engineering Inc. (Mark A. Johnson - AKPLS#7570) provided the Mean Lower Low Water (MLLW) elevation adjustment for all monuments used for the project. These MLLW elevations were determined by running level loops from tidal benchmarks with published MLLW elevations to each monument. Differences between the orthometric elevations of each monument on Geoid 12A and the MLLW elevations can be found in Appendix B of the Juneau LiDAR data report. The average MLLW adjustment was approximately 1.045m with a standard deviation of 0.066m. As a result of being calibrated using the ellipsoidal MLLW elevations instead of the normal ellipsoidal elevations, the LiDAR data was adjusted to the MLLW vertical datum. 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) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/mllw/4813/supplemental/ak2013_cbj_juneau_m4813.kmz fileDescription: This graphic shows the lidar coverage for the 2013 lidar project covering Juneau County, Alaska. fileType: kmz descriptiveKeywords: (MD_Keywords) 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 type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 14.9 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 City and Borough of Juneau, Alaska Lidar [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49628. 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: No restrictions apply to this data. | Use Constraints: In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. TINing the points produces large triangles and hence the elevations may be less accurate within such areas. Elevation values for open water surfaces are derived from waters edge breaklines. Triangles were created across water surfaces by interpolating from the nearest breakline elevation points. RandM Engineering Inc. (Mark A. Johnson - AKPLS#7570) provided the Mean Lower Low Water (MLLW) elevation adjustment for all monuments used for the project. These MLLW elevations were determined by running level loops from tidal benchmarks with published MLLW elevations to each monument. Differences between the orthometric elevations of each monument on Geoid 12A and the MLLW elevations can be found in Appendix B of the Juneau LiDAR data report. The average MLLW adjustment was approximately 1.045m with a standard deviation of 0.066m. As a result of being calibrated using the ellipsoidal MLLW elevations instead of the normal ellipsoidal elevations, the LiDAR data was adjusted to the MLLW vertical datum. 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 RandM Engineering Inc., Watershed Sciences Inc (Quantum Spatial), Alaska DGGS, 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: 49628 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49628.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: -135.155767 eastBoundLongitude: -133.665411 southBoundLatitude: 58.043303 northBoundLatitude: 58.895525 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2013-05-08 endPosition: 2013-06-11 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) distributionFormat: (MD_Format) name: Zip version: (missing) distributionFormat: (MD_Format) name: LAZ version: (missing) distributionFormat: (MD_Format) name: EPT 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=4813 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/mllw/4813/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/mllw/4813/ept.json protocol: WWW:LINK-1.0-http--link name: ept.json description: Data in Entwine Point Tile format suitable for streaming. 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 cumulative orthophoto horizontal accuracy (RMSE) for the Juneau Priority Area 1 was 0.55 feet (0.17 meters) measured by ground control points and 0.30 feet (0.09 meters) measured by air targets, meeting our accuracy standard of < 3 pixels (0.45 meters); Quantitative Value: 0.17 meters, Test that produced the value: The cumulative orthophoto horizontal accuracy (RMSE) for the Juneau Priority Area 1 was 0.55 feet (0.17 meters) measured by ground control points and 0.30 feet (0.09 meters) measured by air targets, meeting our accuracy standard of < 3 pixels (0.45 meters) result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Specifications for this project require that the FVA be 24.5 cm or better AccuracyZ at 95 percent confidence level.; Quantitative Value: 0.059 meters, Test that produced the value: 5.9 cm meters AccuracyZ at 95 percent Confidence Interval. Accuracy was assessed using 3095 ground survey RTK (real time kinematic) points. ; Quantitative Value: 0.072 meters, Test that produced the value: Bare Earth SVA; Quantitative Value: 0.236 meters, Test that produced the value: Brush SVA; Quantitative Value: 0.122 meters, Test that produced the value: Deciduous Forest SVA; Quantitative Value: 0.127 meters, Test that produced the value: Evergreen Forest SVA; Quantitative Value: 0.131 meters, Test that produced the value: Short Grass SVA; Quantitative Value: 0.106 meters, Test that produced the value: Wetland Grass SVA result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: LAS files include all data points collected. No points have been removed or excluded. Shaded relief images have been visually inspected for data errors such as pits, border artifacts, and shifting. LiDAR flight lines have been examined to ensure consistent elevation values across overlapping flight lines. The raw point cloud is of good quality and data passes Fundamental Vertical Accuracy specifications. Please see the LiDAR data report for a discussion of the statistics related to this dataset. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data cover the entire area specified for this project. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: LiDAR Pre-Processing: 1. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data. Sensor head position and attitude are calculated throughout the survey. The SBET data are used extensively for laser point processing. 4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.2) format. Data are converted to orthometric elevations (NAVD88) by applying a Geoid12a correction. 5. Import raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter erroneous points. Ground points are then classified for individual flight lines (to be used for relative accuracy testing and calibration). 6. Using ground classified points per each flight line, the relative accuracy is tested. Automated line-to-line calibrations are then performed for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calibrations are calculated on ground classified points from paired flight lines and results are applied to all points in a flight line. Every flight line is used for relative accuracy calibration. 7. Assess statistical absolute accuracy via direct comparisons to ground RTK survey data. dateTime: DateTime: 2013-09-30T00:00:00 processStep: (LI_ProcessStep) description: LiDAR Post-Processing: 1. Classify data to ground and other client designated classifications using proprietary classification algorithms. 2. Manually QC data classification 3. Normalize Intensity Values for receiver auto gain control, atmospheric effects, and angle of incidence. 4.Apply RGB values from orthophotos to points. dateTime: DateTime: 2013-09-30T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in UTM Zone 5, mean lower low water heights in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from UTM coordinates to geographic coordinates. 2. Duplicate points were removed dateTime: DateTime: 2022-09-13T00:00:00 processor: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |