spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
contentInfo
distributionInfo
dataQualityInfo

2013 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Tulalip Partnership
 (MI_Metadata)
    fileIdentifier:  gov.noaa.nmfs.inport:50174
    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:38
    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 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Tulalip Partnership
            alternateTitle:  wa2013_pslc_tulalip_m2614_metadata
            date:  (CI_Date)
                date:  2014-01-14
                dateType:  (CI_DateTypeCode) publication
            identifier:  (MD_Identifier)
                authority:  (CI_Citation)
                    title:  NOAA/NMFS/EDM
                    date: (inapplicable)
                code:
                  Anchor:  InPort Catalog ID 50174
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName: (inapplicable)
                contactInfo:  (CI_Contact)
                    onlineResource:  (CI_OnlineResource)
                        linkage: https://www.fisheries.noaa.gov/inport/item/50174
                        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:  In October 2012, WSI (Watershed Sciences, Inc.) was contracted by the Puget Sound LiDAR Consortium (PSLC)to collect Light Detection and Ranging (LiDAR) data on a 5-year cycle for sites in Washington. The Tulalipsite in northwestern Washington is one of these sites. Unclassified (1), Ground (2) and Snow (14). This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data.
        purpose:  Provide high resolution terrain elevation and land cover elevation data. Data were collected to aidin assessing stream and forest habitat.
        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 inlocal, 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/2614/supplemental/wa2013_pslc_tulalip_m2614.KMZ
            fileDescription:  This graphic shows the 2013 lidar coverage for the Tulalip Partnership lidar collection.
            fileType:  kmz
        descriptiveKeywords:  (MD_Keywords)
            keyword:  LAZ
            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]: 2013 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Tulalip Partnership [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50174.
        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 datamay no longer represent actual surface conditions. Users should not use this data for critical applications without a fullawareness 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 responsibilityof Watershed Sciences, PSLC, 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:  50174
                citedResponsibleParty:  (CI_ResponsibleParty)
                    organisationName: (inapplicable)
                    contactInfo:  (CI_Contact)
                        onlineResource:  (CI_OnlineResource)
                            linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50174.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:  -123.5796125
                eastBoundLongitude:  -122.9079181
                southBoundLatitude:  47.7515734
                northBoundLatitude:  48.4311248
        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/2614/supplemental/wa2013_pslc_tulalip_m2614.KMZ Reports explaining collection and quality assurance is available at:https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2614/supplemental/wa2013_pslc_tulalip_m2614_lidarreport.pdf
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=2614
                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/2614/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_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Horizontal Positional Accuracy
            evaluationMethodDescription:  Horizontal positional accuracy for LiDAR is dependent upon the quality ofthe GPS/INS solution, sensor calibration and ground conditions at the time of data capture.The standard system results for horizontal accuracy are less than 1 meter.Not reported, assumed as 1.0 m. Laser horizontal errors are a function of flight altitudeabove ground (i.e., +/- 1/3000th AGL flight altitude). Relative errors for the position mustbe less than 1.5 cm horizontal and 2.0 cm vertical in order to be accepted.; Quantitative Value: 1.0 meters, Test that produced the value: See Lidar report.
            result: (missing)
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy
            evaluationMethodDescription:  Upon the LiDAR data's arrival to the office, WSI processing staff initiates a suite ofautomated and manual techniques to process the data into the requested deliverables.Processing tasks include GPS control computations, smoothed best estimate trajectory(SBET) calculations, kinematic corrections, calculation of laser point position,calibration for optimal relative and absolute accuracy, and classification ofground and non-ground points.; Quantitative Value: 0.054 meters, Test that produced the value: Vertical absolute accuracy was primarily assessed from RTK ground check point (GCP)data collected on open, bare earth surfaces with level slope (less than 20 degrees).Fundamental Vertical Accuracy (FVA) reporting is designed to meet guidelinespresented in the National Standard for Spatial Data Accuracy (FGDC, 1998). FVAcompares known RTK ground survey check points to the triangulated ground surfacegenerated by the LiDAR points. FVA is a measure of the accuracy of LiDAR point datain open areas where the LiDAR system has a "very high probability" of measuring theground surface and is evaluated at the 95% confidence interval (1.96 sigma).Vertical accuracy was calculated at 2-sigma to 0.178 ft (5.4 cm).
            result: (missing)
        report:  (DQ_CompletenessCommission)
            nameOfMeasure:  Completeness Report
            evaluationMethodDescription:  LiDAR data has been collected and processed for all areas within the project study area.
            result: (missing)
        report:  (DQ_ConceptualConsistency)
            nameOfMeasure:  Conceptual Consistency
            evaluationMethodDescription:  The accuracy of the LiDAR data collection can be described in terms of absolute accuracy (the consistency ofthe data with external data sources) and relative accuracy (the consistency of the dataset with itself). SeeAppendix A in the lidar report for further information on sources of error and operational measures used toimprove relative accuracy.
            result: (missing)
        lineage:  (LI_Lineage)
            statement: (missing)
            processStep:  (LI_ProcessStep)
                description:  Planning.In preparation for data collection, WSI reviewed the project area using Google Earth,and flightlines were developed using a combination of specialized software. Carefulplanning by acquisition staff entailed adapting the pulse rate, flight altitude, scanangle, and ground speed to ensure complete coverage of the study area at thetarget point density of 11.43 points per square meter (ground points only were calculated at0.83 points per square meter). Efforts are taken to optimize flight paths by minimizingflight times while meeting all accuracy specifications.Factors such as satellite constellation availability and weather windows mustbe considered during the planning stage. Any weather hazards or conditions affectingthe flight were continuously monitored due to their potential impact on the dailysuccess of airborne and ground operations. In addition, a variety of logisticalconsiderations required review including private property access, potential airspace restrictions, and availability of company resources (both staff andequipment).Special care was taken to acquire the tidal flats at low tide wherepossible.
            processStep:  (LI_ProcessStep)
                description:  LiDAR Processing Steps:1. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPSand static ground GPS data.Software - Waypoint GPS v.8.3 Trimble Business Center v.3.00 Geographic Calculator 20132. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processedaircraft position with attitude data. Sensor head position and attitude are calculatedthroughout the survey. The SBET data are used extensively for laser point processing.Software - IPAS TC v.3.13. Calculate laser point position by associating SBET position to each laser point returntime, scan angle, intensity, etc. Create raw laser point cloud data for the entire surveyin *.las (ASPRS v. 1.2) format. Data are converted to orthometric elevations (NAVD88) byapplying a Geoid12 correction.Software - ALS Post Processing Software v.2.744. Import raw laser points into manageable blocks (less than 500 MB) to perform manualrelative accuracy calibration and filter erroneous points. Ground points are thenclassified for individual flight lines (to be used for relative accuracy testingand calibration).Software - TerraScan v.13.0085. 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 andresults are applied to all points in a flight line. Every flight line is used forrelative accuracy calibration.Software - TerraMatch v.13.0026. Classify resulting data to ground and other client designated ASPRSclassifications (Table 7). Assess statistical absolute accuracy via direct comparisonsof ground classified points to ground RTK survey data.Software - TerraScan v.13.008 TerraModeler v.13.0027. Generate bare earth models as triangulated surfaces. Highest hit models were createdas a surface expression of all classified points (excluding the noise and withheldclasses). All surface models were exported as ESRI grids at a 3-foot pixel resolution.Software - TerraScan v.13.008 ArcMap v. 10.1 TerraModeler v.13.002
            processStep:  (LI_ProcessStep)
                description:  The NOAA Office for Coastal Management (OCM) downloaded topographic files in LAZ format from PSLC's website.The files contained lidar easting, northing, elevation, intensity, return number, class, scan angleand GPS time measurements. Entiat data were received in Washington State Plane North, 4601 (feet) andreferenced to NAVD88 (feet).OCM performed the following processing for data storage and Digital Coast provisioning purposes:1. The All-Return LAZ files were cleared of variable lengths records.2. The All-Return LAZ files were converted from a Projected Coordinate System (State Plane 4601)to a Geographic Coordinate system (NAD83).3. The All-Return LAZ files were converted from NAVD88 to ellipsoidal heights using Geoid03.
                dateTime:
                  DateTime:  2014-01-14T00: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-01T06:31:29
                processor:  (CI_ResponsibleParty)
                    individualName:  NOAA Office for Coastal Management
                    contactInfo:  (CI_Contact)
                        address:  (CI_Address)
                            electronicMailAddress:  coastal.info@noaa.gov
                    role:  (CI_RoleCode) processor