| 2001-2002 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Island County and Northeast Jefferson County, Washington | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50139 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:39 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: 2001-2002 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Island County and Northeast Jefferson County, Washington alternateTitle: wa2002_pslc_island_jefferson_m1453_metadata date: (CI_Date) date: 2013-02 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50139 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50139 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: TerraPoint surveyed and created this data for the Puget Sound LiDAR Consortium under contract. The area surveyed is approximately 525 square miles and covers all of Island County, WA and the Northeast portion of Jefferson County, WA. All data was collected during ideal conditions (leaf-off). The LAS files were derived from all returns ASCII files contain the X,Y,Z values of all the LiDAR returns collected during the survey mission. The GPS time, scan angle and return numbers of each point were preserved in the conversion from ASCII to LAS. The LAS files were classified into the following ASPRS classes: (1) Unclassified (2) Bare Earth. Ground and water points are included in Class 2 (Bare Earth). Futher details are available in the Process Steps below. No ancillary data, such as intensity, is available for this data. Initially this dataset was flown in 2001 with a 30% overlap between flight lines which did not meet specifications. The dataset was reflown in 2002 with a 50% overlap between flight lines as the rest of the PSLC data. The data is broken down into USGS quarter quads and then into 25 tiles within each quarter quad. Due to the overlap the nominal point spacing of the dataset is 1.0 meter. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The LAS files can be used to create DEMs and also to extract topographic data in software that does not support raster data. Other surface features can also be extracted with custom applications. This high accuracy data can be used at scales up to 1:12000 (1 inch = 1,000 feet). LiDAR data has a wide range of uses such as earthquake hazard studies, hydrologic modeling, forestry, coastal engineering, roadway and pipeline engineering, flood plain mapping, wetland studies, geologic studies and a variety of analytical and cartographic projects. credit: Please credit the Puget Sound LiDAR Consortium (PSLC) for these data. The PSLC is supported by the Puget Sound Regional Council, the National Aeronautical and Space Administration (NASA), the United States Geological Survey (USGS) and numerous partners in local, state, and tribal government. 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) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1453/supplemental/pslc2001_island_jefferson_wa_footprint.kmz fileDescription: This graphic shows the lidar coverage for Island County and NE Jefferson County in Washington. fileType: kmz 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]: 2001-2002 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Island County and Northeast Jefferson County, Washington [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50139. 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. 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 Terrapoint, PSLC, NASA, 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: 50139 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50139.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: -122.959139 eastBoundLongitude: -122.34735 southBoundLatitude: 47.892561 northBoundLatitude: 48.434366 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2001-01-09 endPosition: 2002-03-23 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/1453/supplemental/pslc2001_island_jefferson_wa_footprint.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=1453 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/1453/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: Elevations are recorded in floating-point meters and the vertical datum is ellipsoidal (GEOID99). There are no other attribute tables. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Not applicable for pure elevation data: every XY error has an associated Z error. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Puget Sound Lidar Consortium evaluates vertical accuracy with two measures: internal consistency and conformance with independent ground control points. Internal Consistency: Data are split into swaths (separate flightlines), a separate surface is constructed for each flightline, and where surfaces overlap one is subtracted from another. Where both surfaces are planar, this produces a robust measure of the repeatability, or internal consistency, of the survey. The average error calculated by this means, robustly determined from a very large sample, should be a lower bound on the true error of the survey as it doesn't include errors deriving from a number of sources including: 1) inaccurately located base station(s), 2) long-period GPS error, 3) errors in classification of points as ground and not-ground (post-processing), 4) some errors related to interpolation from scattered points to a continous surface (surface generation). Conformance with independent ground control points: Bare-earth surface models are compared to independently-surveyed ground control points (GCPs) where such GCPs are available. The purpose of the ground control evaluation is to assess that the bare earth DEMs meet the vertical accuracy specification in the PSLC contract with TerraPoint: "The accuracy specification in the contract between the Puget Sound LiDAR Consortium and TerraPoint is based on a required Root Mean Square Error (RMSE) 'Bare Earth' vertical accuracy of 30 cm for flat areas in the complete data set. This is the required result if all data points in flat areas were evaluated. Because only a small sample of points is evaluated, the required RMSE for the sample set is adjusted downward per the following equation from the FEMA LiDAR specification (adjusted from the 15 cm RMSE in the FEMA specification to 30 cm to accommodate the dense vegetation cover in the Pacific Northwest)." During this step, the bare earth DEMs were compared with existing survey benchmarks. The differences between the LiDAR bare earth DEMs and the survey points are calculated and the final results are first summarized in a graph that illustrates how the dataset behaves as whole. The graph illustrates how close the DEM elevation values were to the ground control points. The individual results were aggregated and used in the RMSE calculations. The results of the RMSE calculations are the measure that makes the data acceptable for this particular specification in the contract. ; Quantitative Value: 0.30 meters, Test that produced the value: Root mean square Z error in open, near-horizontal areas, as specified by contract. Our assessment suggests that all data meet this standard. Accuracy may be significantly less in steep areas and under heavy forest canopy. Accuracy appears to be significantly better for data acquired in early 2003 and afterward, to which in-situ calibration has been applied. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Elevation data has been collected for all areas inside project boundaries. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Puget Sound Lidar Consortium evaluates logical consistency of high-resolution lidar elevation data with three tests: examination of file names, file formats, and mean and extreme values within each file; internal consistency of measured Z values in areas where survey swaths overlap; and visual inspection of shaded-relief images calculated from bare-earth models. File names, formats, and values: All file naming convention and file formats are check for consistency. Internal Consistency Analysis: This analysis calculates and displays the internal consistency of tiled multi-swath (many-epoch) LiDAR data. The input for this analysis is the All-return ASCII data, but it only uses the first returns. The data is divided into swaths, or flightlines, and they are compared with each other. Since the contract specifications require 50% sidelaps, it means that all areas should have been flown twice. The results of this analysis is to verify that the data was generally flown to obtain the 50% sidelaps, that there are no gaps between flightlines and also that overlapping flightlines are consistent in elevation values. Visual inspection of shaded-relief images: During the visual inspection, hillshades are derived from the bare earth DEMs. The hillshades are examined for any obvious data errors such as blunders, border artifacts, gaps between data quads, no-data gaps between flight lines, hillscarps, land shifting due to GPS time errors, etc. The data is examined a scale range of 1:4000 to 1:6000. During this process we also compare the data to existing natural features such as lakes and rivers and also to existing infrastructure such as roads. Orthophotos area also used during this phase to confirm data errors. If any of these data errors are found, they are reported to TerraPoint for correction. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Acquisition. Lidar data were collected in leaf-off conditions (approximately 1 November - 1 April) from a fixed-wing aircraft flying at a nominal height of 1,000 meters above ground surface. Aircraft position was monitored by differential GPS, using a ground station tied into the local geodetic framework. Aircraft orientation was monitored by an inertial measurement unit. Scan angle and distance to target were measured with a scanning laser rangefinder. Scanning was via a rotating 12-facet pyramidal mirror; the laser was pulsed at 30+ KHz, and for most missions the laser was defocussed to illuminate a 0.9m-diameter spot on the ground. The rangefinder recorded up to 4 returns per pulse. Flying height and airspeed were chosen to result in on-ground pulse spacing of about 1.5 m in the along-swath and across-swath directions. Most areas were covered by two swaths, resulting in a nominal pulse density of about 1 per square meter. processStep: (LI_ProcessStep) description: Processing. GPS, IMU, and rangefinder data were processed to obtain XYZ coordinates of surveyed points. For data acquired after January 2003 (NW Snohomish, Mt Rainier, Darrington, and central Pierce projects), survey data from areas of swath overlap were analysed to obtain best-fit in-situ calibration parameters that minimize misfit between overlapping swaths. This reduces vertical inconsistency between overlappoing swaths by about one-half. Heights were translated from ellipsoidal to orthometric (NAVD88) datums via GEOID99 processStep: (LI_ProcessStep) description: ASCII file generation All Point returns with all their attributes were directly exported into ASCII files. These were first divided into USGS quarter quads (3.25 minute by 3.25 minute) and then in 25 tiles per quarter quad. processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received topographic files in ASCII .TXT format. The files contained lidar elevation measurements. The data were received in Washington State Plane North Zone 4601, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid99 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The ASCII .TXT files were converted to LAS version 1.2 using LAStools' txt2las tool. 2. Bare earth points were classified using LAStools' lasground tool. 3. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid99. 4. The topographic las files were converted from a Projected Coordinate System (WA SP North) to a Geographic Coordinate system (GCS). 5. The topographic las files' vertical units were converted from feet to meters. 6. The topographic las files' horizontal units were converted from feet to decimal degrees. dateTime: DateTime: 2013-02-01T00: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-07-01T05:59:05 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |