(MI_Metadata)fileIdentifier: gov.noaa.csc.maps:wa2004_pslc_piercecounty_m2532language: eng; USAcharacterSet: (MD_CharacterSetCode) utf8hierarchyLevel: (MD_ScopeCode) datasetcontact: (CI_ResponsibleParty)individualName: Mike SutherlandorganisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 303-497-6120facsimile: 303-497-6513address: (CI_Address)deliveryPoint: NOAA/NESDIS/NGDC E/GC1 325 Broadwaycity: BoulderadministrativeArea: COpostalCode: 80305-3328country: USAelectronicMailAddress: mike.sutherland@noaa.govhoursOfService: 7:30am-5:00pm Mountainrole: (CI_RoleCode) authordateStamp: 2013-10-17metadataStandardName: ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded DatametadataStandardVersion: ISO 19115-2:2009(E)return to topspatialRepresentationInfo: (MD_VectorSpatialRepresentation)geometricObjects: (MD_GeometricObjects)geometricObjectType: (MD_GeometricObjectTypeCode) pointreturn to topreferenceSystemInfo: (MD_ReferenceSystem)referenceSystemIdentifier: (RS_Identifier)authority: (CI_Citation)title: North American Datum 1983alternateTitle: NAD83date: (CI_Date)date: 2007-01-19dateType: (CI_DateTypeCode) revisioncitedResponsibleParty: (CI_ResponsibleParty)organisationName: contactInfo: (CI_Contact)onlineResource: (CI_OnlineResource)linkage: http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269name: NAD83description: Link to Geographic Markup Language (GML) description of reference system.function: (CI_OnLineFunctionCode) informationrole: (CI_RoleCode) resourceProvidercitedResponsibleParty: (CI_ResponsibleParty)organisationName: European Petroleum Survey GroupcontactInfo: (CI_Contact)onlineResource: (CI_OnlineResource)linkage: http://www.epsg-registry.org/name: European Petroleum Survey Group Geodetic Parameter Registrydescription: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations.function: (CI_OnLineFunctionCode) searchrole: (CI_RoleCode) publishercode: urn:ogc:def:crs:EPSG::4269return to topreferenceSystemInfo: (MD_ReferenceSystem)referenceSystemIdentifier: (RS_Identifier)code: Ellipsoid in MeterscodeSpace: Local Vertical Referencereturn to topidentificationInfo: (MD_DataIdentification)citation: (CI_Citation)title: 2004 Puget Sound Lidar Consortium (PSLC) Topographic Bare-Earth Lidar: Pierce County, WAdate: (CI_Date)date: 2013-08-01dateType: (CI_DateTypeCode) publicationcitedResponsibleParty: (CI_ResponsibleParty)organisationName: DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 843-740-1200address: (CI_Address)deliveryPoint: 2234 South Hobson Ave.city: CharlestonadministrativeArea: SCpostalCode: 29405-2413electronicMailAddress: coastal.info@noaa.govonlineResource: (CI_OnlineResource)linkage: http://coast.noaa.govrole: (CI_RoleCode) originatorcitedResponsibleParty: (CI_ResponsibleParty)individualName: Diana MartinezorganisationName: Puget Sound Lidar Consortium (PSLC)positionName: Senior GIS Analyst, Puget Sound Regional CouncilcontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 206-971-3052address: (CI_Address)deliveryPoint: 1011 Western Avenue, Suite 500city: SeattleadministrativeArea: WApostalCode: 98104-1035country: USAelectronicMailAddress: dmartinez@psrc.orgrole: (CI_RoleCode) originatorcitedResponsibleParty: (CI_ResponsibleParty)organisationName: DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 843-740-1200address: (CI_Address)deliveryPoint: 2234 South Hobson Ave.city: CharlestonadministrativeArea: SCpostalCode: 29405-2413electronicMailAddress: coastal.info@noaa.govonlineResource: (CI_OnlineResource)linkage: http://coast.noaa.govrole: (CI_RoleCode) publisherpresentationForm: (CI_PresentationFormCode) imageDigitalabstract: Terrapoint surveyed and created this data for the Puget Sound LiDAR Consortium under contract. The project area covers approximately 814 square miles of western Pierce County. A majority of the data was collected between January 21st and March 08, 2004. Two small areas were reflown during spring 2005.purpose: The LiDAR bare earth ASCII files can be used to create DEM and also to extract topographic data in software that does not support raster data. This high accuracy data can be used at scales up to 1:12000 (1 inch = 1,000 feet). The LiDAR bare earth 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.status: (MD_ProgressCode) completedpointOfContact: (CI_ResponsibleParty)individualName: Diana MartinezorganisationName: Puget Sound Lidar Consortium (PSLC)positionName: Senior GIS Analyst, Puget Sound Regional CouncilcontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 206-971-3052address: (CI_Address)deliveryPoint: 1011 Western Avenue, Suite 500city: SeattleadministrativeArea: WApostalCode: 98104-1035country: USAelectronicMailAddress: dmartinez@psrc.orgrole: (CI_RoleCode) pointOfContactresourceMaintenance: (MD_MaintenanceInformation)maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeededgraphicOverview: (MD_BrowseGraphic)fileName: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/wa/pslc2004/wa2004_pslc_piercecountybe_footprint.kmzfileDescription: This kmz file shows the extent of coverage for the 2004 PSLC Pierce County, WA lidar data set.fileType: kmzdescriptiveKeywords: (MD_Keywords)keyword: Topography/Bathymetrykeyword: Elevationkeyword: Modelkeyword: LiDARkeyword: LASkeyword: Remote Sensingkeyword: Bare Earthkeyword: ground surfacetype: (MD_KeywordTypeCode) themethesaurusName: (CI_Citation)title: nonedate: descriptiveKeywords: (MD_Keywords)keyword: USkeyword: Washingtonkeyword: Pierce Countytype: (MD_KeywordTypeCode) placethesaurusName: (CI_Citation)title: Nonedate: resourceConstraints: (MD_Constraints)useLimitation: These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.resourceConstraints: (MD_LegalConstraints)useLimitation: While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty.spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vectorlanguage: eng; USAtopicCategory: (MD_TopicCategoryCode) elevationextent: (EX_Extent)geographicElement: (EX_GeographicBoundingBox)westBoundLongitude: -122.696132eastBoundLongitude: -121.910870southBoundLatitude: 46.743235northBoundLatitude: 47.321118temporalElement: (EX_TemporalExtent)extent: TimePeriod: beginPosition: 2004-01-24endPosition: 2004-03-08return to topdistributionInfo: (MD_Distribution)distributionFormat: (MD_Format)name: LAZversion: distributor: (MD_Distributor)distributorContact: (CI_ResponsibleParty)organisationName: DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 843-740-1200address: (CI_Address)deliveryPoint: 2234 South Hobson Ave.city: CharlestonadministrativeArea: SCpostalCode: 29405-2413electronicMailAddress: coastal.info@noaa.govonlineResource: (CI_OnlineResource)linkage: http://coast.noaa.govrole: (CI_RoleCode) distributordistributionOrderProcess: (MD_StandardOrderProcess)orderingInstructions: The National Geophysical Data Center serves as the archive for this LIDAR data. NGDC should only be contacted for this data if it cannot be obtained from
NOAA Coastal Services Center.distributor: (MD_Distributor)distributorContact: (CI_ResponsibleParty)individualName: Mike SutherlandorganisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 303-497-6120facsimile: 303-497-6513address: (CI_Address)deliveryPoint: NOAA/NESDIS/NGDC E/GC1 325 Broadwaycity: BoulderadministrativeArea: COpostalCode: 80305-3328country: USAelectronicMailAddress: mike.sutherland@noaa.govhoursOfService: 7:30am-5:00pm Mountainrole: (CI_RoleCode) distributordistributionOrderProcess: (MD_StandardOrderProcess)orderingInstructions: The National Geophysical Data Center serves as the archive for this LIDAR dataset. NGDC should only be contacted for the data if it cannot be obtained from
NOAA Coastal Services Center.return to topdataQualityInfo: (DQ_DataQuality)scope: (DQ_Scope)level: (MD_ScopeCode) datasetreport: (DQ_AbsoluteExternalPositionalAccuracy)nameOfMeasure: Horizontal Positional Accuracy ReportevaluationMethodDescription: Not applicable for pure elevation data: every XY error has an associated Z error.result: report: (DQ_AbsoluteExternalPositionalAccuracy)nameOfMeasure: Vertical Positional Accuracy ReportevaluationMethodDescription: 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.result: report: (DQ_AbsoluteExternalPositionalAccuracy)nameOfMeasure: Vertical Positional AccuracymeasureDescription: 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: (DQ_QuantitativeResult)valueUnit: BaseUnit: identifier: metersunitsSystem: value: Record: 0.30report: (DQ_CompletenessCommission)evaluationMethodDescription: Elevation data has been collected for all areas inside project boundaries.result: report: (DQ_ConceptualConsistency)measureDescription: 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 gap 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: lineage: (LI_Lineage)processStep: (LE_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.dateTime: DateTime: 2004-01-01T00:00:00processStep: (LE_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 GEOID99dateTime: DateTime: 2004-01-01T00:00:00processStep: (LE_ProcessStep)description: Post-processing. Return points were then classified semi-automatically as ground (and water), not-ground (vegetation and structures) and blunder. For 2000 and 2001 data, the despike virtual deforestation algorithm described by Haugerud and Harding (2001) was used. After 2001, TerraPoint shifted to Terrascan software, which includes additional classification algorithms, allows for greater intervention by a human operator, and generally produces better bare-earth surface models.dateTime: DateTime: 2004-01-01T00:00:00processStep: (LE_ProcessStep)description: ASCII file generation The X,Y,Z values of the ground returns were exported into ASCII files. These were divided into USGS quarter quads (3.25 minute by 3.25 minute).dateTime: DateTime: 2004-01-01T00:00:00processStep: (LE_ProcessStep)description: Breakng down ASCII files TerraPoint shipped data in USGS quarter-quads (3.25 minute by 3.25 minute). To reduce the file size and make them more user friendly, each quarter quad files was further broken down into 25 smaller tiles.dateTime: DateTime: 2004-01-01T00:00:00processStep: (LE_ProcessStep)description: The NOAA Coastal Services Center (CSC) received topographic files in ASCII .txt format. The files contained lidar elevation measurements only. 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. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The parsed ASCII .txt files were converted to LAS version 1.2 using LAStools' txt2las tool. 2. The topographic las files' classifications off all points were changed from Class 0 (Never Classified) to Class 2 (Ground). 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 (NAD 83). 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. 7. The data were converted to LAZ format.dateTime: DateTime: 2013-08-01T00:00:00processor: (CI_ResponsibleParty)organisationName: DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 843-740-1200address: (CI_Address)deliveryPoint: 2234 South Hobson Ave.city: CharlestonadministrativeArea: SCpostalCode: 29405-2413electronicMailAddress: coastal.info@noaa.govonlineResource: (CI_OnlineResource)linkage: http://coast.noaa.govrole: (CI_RoleCode) processorprocessStep: (LE_ProcessStep)description: The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently
being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format.
The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of
LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to
the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.dateTime: DateTime: 2013-10-17T00:00:00processor: (CI_ResponsibleParty)individualName: Mike SutherlandorganisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of CommercecontactInfo: (CI_Contact)phone: (CI_Telephone)voice: 303-497-6120facsimile: 303-497-6513address: (CI_Address)deliveryPoint: NOAA/NESDIS/NGDC E/GC1 325 Broadwaycity: BoulderadministrativeArea: COpostalCode: 80305-3328country: USAelectronicMailAddress: mike.sutherland@noaa.govhoursOfService: 7:30am-5:00pm Mountainrole: (CI_RoleCode) processorreturn to topmetadataMaintenance: (MD_MaintenanceInformation)maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) annuallydateOfNextUpdate: 2014-10-17maintenanceNote: This metadata was automatically generated from the FGDC Content Standards for Digital Geospatial Metadata standard (version FGDC-STD-001-1998) using the 2013-01-04 version of the FGDC RSE to ISO 19115-2 for LiDAR transform.maintenanceNote: Translated from FGDC 2013-10-17T11:36:49.568-06:00