spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
contentInfo
distributionInfo
dataQualityInfo

2012 USGS-FEMA Lidar: Virginia Northern Counties (South)
 (MI_Metadata)
    fileIdentifier:  gov.noaa.nmfs.inport:50130
    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-03-29T00:00:00
    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:  2012 USGS-FEMA Lidar: Virginia Northern Counties (South)
            alternateTitle:  va2012_usgs_fema_northernco_S_m4729_metadata
            date:  (CI_Date)
                date:  2015-01-12
                dateType:  (CI_DateTypeCode) publication
            identifier:  (MD_Identifier)
                authority:  (CI_Citation)
                    title:  NOAA/NMFS/EDM
                    date: (inapplicable)
                code:
                  Anchor:  InPort Catalog ID 50130
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName: (inapplicable)
                contactInfo:  (CI_Contact)
                    onlineResource:  (CI_OnlineResource)
                        linkage: https://www.fisheries.noaa.gov/inport/item/50130
                        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/geoid18/4729/supplemental/va2012_usgs_fema_northernco_S_m4729_surveyreport.pdf
                        protocol:  WWW:LINK-1.0-http--link
                        name:  survey report
                        description:  Survey report from the lidar contractor.
                        function:  (CI_OnLineFunctionCode) download
                role: (inapplicable)
            presentationForm: (unknown)
        abstract:  Dewberry collected LiDAR for ~3,341 square miles in various Virginia Counties, a part of Worcester County, and Hoopers Island. The acquisition was performed by Terrapoint. This metadata covers the LiDAR produced for the Virginia Counties North project area. The nominal pulse spacing for this project is 1.6 ft (0.5 meters). This project was collected with a sensor which collects intensity values for each discrete pulse extracted from the waveform. GPS Week Time, Intensity, Flightline and echo number attributes were provided for each LiDAR point. Dewberry used proprietary procedures to classify the LAS according to contract specifications: 1-Unclassified, 2-Ground, 7-Noise, 9-Water, 10-Ignored Ground due to breakline proximity, and 11-Withheld (Reclassed to 15). Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro flattened DEMs for the 2,140 tiles (5000 ft x 5000 ft) that cover the project area. This collection has been divided into 2 parts (North and South), due to a portion of the data being collected in two zones: Virginia State Plane North 4501 and Virginia State Plane South 4502. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data.
        purpose:  The purpose of this LiDAR data was to produce high accuracy 3D elevation products, including tiled LiDAR in LAS 1.2 format, 3D breaklines, and a 2.5 ft cell size hydro flattened Digital Elevation Models (DEM).
        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/4729/supplemental/va2012_usgs_fema_northernco_S_m4729.kmz
            fileDescription:  This graphic shows the coverage of the 2012 USGS-FEMA Virginia Northern Counties (South) lidar collection.
            fileType:  kmz
        descriptiveKeywords:  (MD_Keywords)
            keyword:  2012
            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]: 2012 USGS-FEMA Lidar: Virginia Northern Counties (South) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50130.
        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 USGS, FEMA, Dewberry, 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:  50130
                citedResponsibleParty:  (CI_ResponsibleParty)
                    organisationName: (inapplicable)
                    contactInfo:  (CI_Contact)
                        onlineResource:  (CI_OnlineResource)
                            linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50130.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:  -77.713172
                eastBoundLongitude:  -76.506493
                southBoundLatitude:  37.746085
                northBoundLatitude:  38.944008
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    description:   | Currentness: Ground Condition
                    beginPosition:  2011-04-19
                    endPosition:  2012-02-10
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)
        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=4729
                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/4729/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:  Lidar source compiled to meet 1.0 m horizontal RMSE.; Quantitative Value: 1.0 meters, Test that produced the value: Dewberry does not perform independent horizontal accuracy testing on the LiDAR. LiDAR vendors perform calibrations on the LiDAR sensor and compare data to adjoing flight lines to ensure LiDAR meets the 3.28 ft horizontal accuracy standard at the 95% confidence level. Please see the final project report for more details.
            result: (missing)
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy
            evaluationMethodDescription:  The breaklines are derived from the source LiDAR. Vertical Accuracy is not tested on the breaklines. The vertical accuracy of the LiDAR was tested by Dewberry with 66 independently collected checkpoints. The survey checkpoints are distributed throughout the project area. These 66 checkpoints contain 21 open terrain points, 24 crops/weeds points, and 21 forested points. The 66 checkpoints were used to compute the Fundamental Vertical Accuracy (FVA) and the Consolidated Vertical Accuracy (CVA). Project specifications required a FVA of 0.60 feet for open terrain and a CVA of 1.195 feet. Appendix A, Guidance for Aerial Mapping and Surveying, to FEMAs Guidelines and Specifications for Flood Hazard Mapping Partners requires a minimum of 60 test points -- 20 each in a minimum of three land cover categories representative of the floodplain. FEMAs Procedure Memorandum No. 61 - Standards for Lidar and Other High Quality Digital Topography -- specifies that the positional accuracy of LiDAR shall be in accordance with ASPRS/NDEP standards for accuracy testing as well as the USGS Lidar Guidelines and Base Specifications, v13. All of these standards and guidelines require testing for Fundamental Vertical Accuracy (FVA), Supplemental Vertical Accuracy (SVA), and Consolidated Vertical Accuracy (CVA), using a minimum of 20 checkpoints each in a minimum of three land cover categories for a minimum total of 60 QA/QC checkpoints.; Quantitative Value: 0.082 meters, Test that produced the value: The NSSDA RMSEZ is 0.082 m in open terrain which meets project specifications of 0.091 m. The fundamental vertical accuracy is 0.165 m which meets project specifications of 0.183 m. The consolidated vertical accuracy is 0.250 m which meets project specifications of 0.364 m.
            result: (missing)
        report:  (DQ_CompletenessCommission)
            nameOfMeasure:  Completeness Report
            evaluationMethodDescription:  A visual qualitative assessment was performed to ensure data completeness and bare earth data cleanliness. No void or missing data, the bare earth surface is of good quality and data passes vertical accuracy specifications.
            result: (missing)
        report:  (DQ_ConceptualConsistency)
            nameOfMeasure:  Conceptual Consistency
            evaluationMethodDescription:  Data covers the tile scheme provided for the project area.
            result: (missing)
        lineage:  (LI_Lineage)
            statement: (missing)
            processStep:  (LI_ProcessStep)
                description:  - Establishment of survey points to support the LiDAR data collection. two existing published NGS stations (HV5411, GV1969) were observed in a GPS control network and used to establish one new points for the primary control for this site. 1110305, 1110306 was observed and used to control all flight missions and static ground surveys. The following are the final coordinates of the control points used for this project: SurveyBlock, Station, Latitude(D M S Hem), Longitude(D M S Hem), H-Ell(m), H-MSL(m) Counties Middle,1110305/Log0503d/HANO, N 37 42 26.28275, W-77 26 13.13327, 28.5836, 61.4241 Counties Middle,1110306/Log0505t/KENT, N 37 30 06.65193, W-77 07 33.81068, -0.137, 33.4957
                dateTime:
                  DateTime:  2011-04-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  - Airborne acquisition of Lidar Terrapoint used one Optech ALTM 3100EA system to collect the data. The Optech System was configured in the following method: Aircraft Speed 150 knots Data Acquisition Height 950 m AGL Swath Width 691.54 m Distance between Flight Lines 311.2 m Overlap 55 % Scanner Field Of View 22 +/- degrees (+/-2 degrees flagged as withheld) Pulse Repetition Rate 70 KHz Scan Frequency 40 Hz Number of Returns per Pulse 4 Discrete returns Beam Divergence 0.3 mRad Flight Line Length shorter than 70km Base Station Distance shorter than 40km Resultant Raw Point Density ~2 pt/m2 with overlap Aircraft platforms were used in the collection of this project: A Piper Navajo aircraft was used to conduct the aerial survey. The Navaho is a fixed wing aircraft that have an endurance of approximately 5 hours. -GPS-IMU: High accuracy IMU (200Hz) and GPS information (1Hz) concerning the attitude and position of the sensor were acquired at the same time as the Laser data. Ground based GPS stations also acquired consecutive GPS information for the duration of the flights. A combination of Sokkia GSR 2600 and NovAtel DL-4+ dual-frequency GPS receivers were used to support the airborne operations of this survey. - Flights and Flight Lines The area is covered by several missions, a mission is defined as the block of acquisition between aircraft take-off and landing flown under good meteorological and GPS conditions, and each mission includes multiple flightlines. Number Of Missions: 10 List Of Missions: o211126a o211127c o211130a o511122a o511122b o511124a o511125a o511126a o511127b o511129a Number Of Flight Lines: 144
                dateTime:
                  DateTime:  2011-04-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  - Airborne GPS Kinematic processing Airborne GPS kinematic data was processed on-site using GrafNav kinematic On-The-Fly (OTF) software. Flights were flown with a minimum of 6 satellites in view (13o above the horizon) and with a PDOP of better than 4. Distances from base station to aircraft were kept to a maximum of 40 km, to ensure a strong OTF (On-The-Fly) solution. For all flights, the GPS data can be classified as excellent, with GPS residuals of 3cm average but no larger than 10 cm being recorded. The Geoid09 geoid model, published by the NGS, was used to transform all ellipsoidal heights to orthometric.
                dateTime:
                  DateTime:  2011-04-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  - Generation and Calibration of laser points Laser data points are generated using Optechs software Dashmap. Those software combine the raw laser range and angle data file with the finalized GPS/IMU trajectory information. Each mission is evaluated in Terrasolids Terramatch software to correct any residual roll pitch heading misalignments, if necessary those values are to the data. The resulting point cloud is projected into the desired coordinate system and created in LAS format. One file per swath, files bigger than 2Gb split in 2. On a project level, a coverage check is carried out to ensure no slivers are present.
                dateTime:
                  DateTime:  2011-05-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  - Mission to mission adjustments of Lidar data All missions are validated and adjusted against the adjoining missions for relative vertical biases and collected GPS static and kinematic ground truthing points for absolute vertical accuracy purposes.
                dateTime:
                  DateTime:  2011-06-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  -Deliverable Product Generation Raw Lidar point are projected were reprojected from UTM zone 18 to the delivery projection State Plane Virginia, US Survey Feet. *Raw Calibrated LIDAR Point Cloud Raw LiDAR point cloud, was provided in the following formats/parameters: - LAS V1.2, point record format 1, Adjusted GPS time, georeferencing information populated in header - The following fields are included in the LAS file: 1. Adjusted GPS time reported to the nearest microsecond 2. Flight line ID 3. Easting (reported to the nearest 0.01ft) 4. Northing (reported to the nearest 0.01ft) 5. Elevation (reported to the nearest 0.01ft) 6. intensity 7. Echo number 8. Classification 9. Scan angle 10. Edge of scan 11. Scan direction - Full swaths, all collected points delivered (except discarded flightline) - The Withheld bit flags the last 2 degrees of the swath (Additional areas are classified with the withheld in areas where wind or vegetation affected the quality of the data long the edge of the flight line. The classification of the additional withheld areas does not affect the density of the data.) - 1 file per swath, 1 swath per file (except when swath had to be divided in section for size or calibration)
                dateTime:
                  DateTime:  2011-07-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  Dewberry utilizes a variety of software suites for inventory management, classification, and data processing. All LiDAR related processes begin by importing the data into the GeoCue task management software. GeoCue allows the data to retain its delivered tiling scheme (5000 ft by 5000 ft). The tiled data is then opened in Terrascan where Dewberry uses proprietary ground classification routines to remove any non-ground points and generate an accurate ground surface. The ground routine consists of three main parameters (building size, iteration angle, and iteration distance); by adjusting these parameters and running several iterations of this routine an initial ground surface is developed. The building size parameter sets a roaming window size. Each tile is loaded with neighboring points from adjacent tiles and the routine classifies the data section by section based on this roaming window size. The second most important parameter is the maximum terrain angle, which sets the highest allowed terrain angle within the model. Once the ground routine has been completed a manual quality control routine is done using hillshades, cross-sections, and profiles within the Terrasolid software suite. After this QC step, a peer review and supervisor manual inspection is completed on a percentage of the classified tiles based on the project size and variability of the terrain. After the ground classification corrections were completed, the dataset was processed through a water classification routine that utilizes breaklines compiled by Dewberry to automatically classify hydrographic features. The water classification routine selects ground points within the breakline polygons and automatically classifies them as class 9, water. During this water classification routine, points which are in close proximity (2 ft) to the hydrographic features are moved to class 10, an ignored ground. In addition to classes 1, 2, 8, 9, and 10, the project allows for a Class 7, noise points. This class was only used if needed when points could manually be identified as low/high points. Dewberry also used Class 11 - Withheld points. The fully classified dataset is then processed through Dewberrys comprehensive quality control program. The data was classified as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 7= Noise Class 8= Model Key Points Class 9 = Water Class 10= Ignored Ground Class 11= Withheld The LAS header information was verified to contain the following: Class (Integer) GPS Week Time (0.0001 seconds) Easting (0.01 ft) Northing (0.01 ft) Elevation (0.01 ft) Echo Number (Integer 1 to 4) Echo (Integer 1 to 4) Intensity (8 bit integer) Flight Line (Integer) Scan Angle (Integer degree)
                dateTime:
                  DateTime:  2011-09-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  Dewberry used GeoCue software to develop raster stereo models from the LiDAR intensity. The raster resolution was 1ft.
                dateTime:
                  DateTime:  2011-09-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  LiDAR intensity stereopairs were viewed in 3-D stereo using Socet Set for ArcGIS softcopy photogrammetric software. The breaklines are collected directly into an ArcGIS file geodatabase to ensure correct topology. The LiDARgrammetry was performed under the direct supervision of an ASPRS Certified Photogrammetrist. The breaklines were stereo-compiled in accordance with the Data Dictionary. The data dictionary defines Tidal Waters as the land and water interface at the time of LiDAR acquisition of tidally influenced bodies of water. There is no minimum area requirement. Tidal variations over the course of a collection or between different collections will result in discontinuities along shorelines. This is considered normal and these anomalies should be retained. Variations in water surface elevation resulting in tidal variations during a collection should NOT be removed or adjusted, as this would require either the removal of valid, measured ground points or the introduction of unmeasured ground into the DEM. The USGS priority is on the ground surface, and accepts there may be occasional, unavoidable irregularities in water surface. Breaklines must be captured at or just below the elevations of the immediately surrounding terain. Under no circumstances should a feature be elevated above the surrounding LiDAR points. If it can be reasonably determined where the edge of water most probably falls, beneath the dock or pier, then the edge of water will be collected at the elevation of the water where it can be directly measured. If there is a clearly-indicated headwall or bulkhead adjacent to the dock or pier and it is evident that the waterline is most probably adjacent to the headwall or bulkhead, then the water line will follow the headwall or bulkhead at the elevation of the water where it can be directly measured. If there is no clear indication of the location of the waters edge beneath the dock or pier, then the edge of water will follow the outer edge of the dock or pier as it is adjacent to the water, at the measured elevation of the water. Breaklines shall snap and merge seamlessly with linear hydrographic features.
                dateTime:
                  DateTime:  2011-09-01T00:00:00
            processStep:  (LI_ProcessStep)
                description:  The NOAA Office for Coastal Management (OCM) received the topographic lidar files in LAS format from USGS-FEMA. The files contained lidar easting, northing, elevation, intensity, return number, etc. The data was received in both Virginia State Plane North 4501 and Virginia State Plane South 4502. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The project was subdivided into 2 projects according to projection (Virginia State Plane North and Virginia State Plane South) 2. The files were reviewed and erroneous elevations were removed. 3. Class 11 points (witheld) were reclassified to Class 15. 4. Data were converted to geographic coordinates and ellipsoid heights in meters.
                dateTime:
                  DateTime:  2014-09-24T00: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
            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:  2022-04-01T06:17:18
                processor:  (CI_ResponsibleParty)
                    individualName:  NOAA Office for Coastal Management
                    contactInfo:  (CI_Contact)
                        address:  (CI_Address)
                            electronicMailAddress:  coastal.info@noaa.gov
                    role:  (CI_RoleCode) processor