| 2006 URS Corporation Bare Earth Topographic Lidar: Shawsheen River, Massachusetts | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49771 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:36 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: 2006 URS Corporation Bare Earth Topographic Lidar: Shawsheen River, Massachusetts alternateTitle: ma2006_urs_shawsheen_m2576_metadata date: (CI_Date) date: 2013-10 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49771 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49771 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: URS Corporation contracted EarthData International to aquire topographic elevation data for 82 square miles in Essex and Middlesex Counties, Massachusetts during 2006. Products generated include lidar point clouds, 3D hydro breaklines, and lidar bare-earth elevation models in LAS format using lidar collected with a Leica ALS-50 Aerial Lidar Sensor. Lidar Sensor Specifications: Sensor: Leica ALS-50 Aerial Lidar Sensor (s/n ALS036) Airspeed: ~ 130 knots Laser Pulse Rate: 38,000 Hz Field of View: 35 Degrees Scan Rate: 20 Hz Average Swath Width: 1537 meters Nominal Post Spacing 3 meters This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The purpose of these data is to provide elevation data capable of supporting generation of two foot contours and defining target drainage channel geometry. credit: Please credit URS Corporation and EarthData International for all products derived from this data. 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/2576/supplemental/ma2006_urs_shawsheen_footprint.KMZ fileDescription: This graphic shows the lidar coverage for Essex and Middlesex Counties, Massachusetts. 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]: 2006 URS Corporation Bare Earth Topographic Lidar: Shawsheen River, Massachusetts [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49771. 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 URS Corporation, EarthData International, 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: 49771 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49771.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: -71.308999 eastBoundLongitude: -71.122943 southBoundLatitude: 42.443801 northBoundLatitude: 42.725917 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2006-12-16 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/2576/supplemental/ma2006_urs_shawsheen_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=2576 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/2576/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: 1. The bare-earth points have a Fundamental Vertical Accuracy of 1.2 ft. (36.3 cm) or better at the 95% confidence level in open terrain, after correction of systematic errors, computed by multiplying the RMSEz by 1.9600. This is equivalent to a vertical RMSE of 0.6 ft. (18.5 cm) or less in open terrain, equivalent to 2 foot contours that satisfy National Map Accuracy Standards. 2. In all land cover categories combined, the bare-earth dataset has a Consolidated Vertical Accuracy of 1.6 ft. (49.0 cm) or better at the 95% confidence level, computed by the 95th percentile method of endorsement by the National Digital Elevation Program. 3. The horizontal accuracy meets or exceeds 5.68 ft. (1 meter) or less. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The lidar data fully comply with FEMA guidance as published in Appendix A, April 2003. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Terrasurv performed a geodetic control survey in support of LIDAR mapping. The bare-earth points have a Fundamental Vertical Accuracy of 1.2 ft. (36.3 cm) or better at the 95% confidence level in open terrain, after correction of systematic errors, computed by multiplying the RMSEz by 1.9600. This is equivalent to a vertical RMSE of 0.6 ft. (18.5 cm) or less in open terrain, equivalent to 2 foot contours that satisfy National Map Accuracy Standards. In all land cover categories combined, the bare-earth dataset has a Consolidated Vertical Accuracy of 1.6 ft. (49.0 cm) or better at the 95% confidence level, computed by the 95th percentile method of endorsement by the National Digital Elevation Program. The vertical accuracy of the lidar data fully complies with FEMA guidance as published in Appendix A, April 2003 and National Standard for Spatial Accuracy (NSSDA). ; Quantitative Value: 0.185 meters, Test that produced the value: Tested Vertical Root Mean Square Error (RMSEz) in open area. Units in meters. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Two checks for completeness were performed: 1. EarthData's proprietary software, Checkedb, for verification agianst ground survey points. 2. Terrascan, for verification of automated and manual editing and final QC of products. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Compliance with the accuracy standard was ensured by the placement of GPS ground control prior to the acquisition of lidar data. The following checks were performed. 1. The ground control and airborne GPS data stream were validated through a fully analytical boresight adjustment. 2. The DTM (Digital Terrain Model) data were checked against the project control. 3. Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Terrasurv was tasked to perform a geodetic control survey in support of LIDAR mapping of the Shawsheen river area in Essex and Middlesex Counties, Massachusetts. The Global Positioning System (GPS) was used in a static differential mode to measure the interstation vectors of the network. The National Spatial Reference System (NSRS) was used to provide control for the network. Continuously Operating Reference Station WMTS was used, along with two ground stations of the NSRS. Two Trimble dual frequency receivers were used on day 361 of 2006. A base receiver was set up near on C 35, at the Lawrence Municipal Airport. This point was also used by the flight crew during the aerial data acquisition phase. The two northerly LIDAR points (SR-1 and SR-5) were surveyed using this station as a base. The other three LIDAR stations, and benchmark V 34, were surveyed using the CORS as a base. The horizontal datum was the North American Datum of 1983, 1996 adjustment (NAD 1983 1996), and the vertical datum was the North American Vertical Datum of 1988 (NAVD 1988) Geoid03. dateTime: DateTime: 2006-12-27T00:00:00 processStep: (LI_ProcessStep) description: URS contracted EarthData International, Inc. (EarthData) to collect and deliver high quality topographic elevation point data derived from multiple return, light detection and ranging (Lidar) measurements for an area of interest totaling approximately 82 square miles in Essex and Middlesex Counties, Massachusetts. Data was collected at a nominal three meter (3) meter post spacing between points at an altitude of 2438 meters (8,000 feet) above mean terrain. This data was used to produce a bare-earth surface model and hydro-enforced breaklines for the project. The aerial acquisition was conducted on 16 December, 2006 using and aircraft (tail number N2636P). Lidar data was captured using an ALS-50 Lidar system, s/n ALS036, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. dateTime: DateTime: 2006-12-16T00:00:00 processStep: (LI_ProcessStep) description: EarthData has developed a unique method for processing lidar data to identify and remove elevation points falling on vegetation, buildings, and other aboveground structures. The algorithms for filtering data were utilized within EarthData's proprietary software and commercial software written by TerraSolid. This software suite of tools provides efficient processing for small to large-scale, projects and has been incorporated into ISO 9001 compliant production work flows. The following is a step-by-step breakdown of the process. 1. Using the lidar data set provided by EarthData, the technician performs calibrations on the data set. 2. Using the lidar data set provided by EarthData, the technician performed a visual inspection of the data to verify that the flight lines overlap correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the data set and inspected them where adjacent flight lines overlapped. These overlapping areas were merged and a process which utilizes 3-D Analyst and EarthData's proprietary software was run to detect and color code the differences in elevation values and profiles. The technician reviewed these plots and located the areas that contained systematic errors or distortions that were introduced by the lidar sensor. 3. Systematic distortions highlighted in step 2 were removed and the data was re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from one type of land cover to another. 4. The lidar data for each flight line was trimmed in batch for the removal of the overlap areas between flight lines. The data was checked against a control network to ensure that vertical requirements were maintained. Conversion to the client-specified datum and projections were then completed. The lidar flight line data sets were then segmented into adjoining tiles for batch processing and data management. 5. The initial batch-processing run removed 95% of points falling on vegetation. The algorithm also removed the points that fell on the edge of hard features such as structures, elevated roadways and bridges. 6. The operator interactively processed the data using lidar editing tools. During this final phase the operator generated a TIN based on a desired thematic layers to evaluate the automated classification performed in step 5. This allowed the operator to quickly re-classify points from one layer to another and recreate the TIN surface to see the effects of edits. Geo-referenced images were toggled on or off to aid the operator in identifying problem areas. The data was also examined with an automated profiling tool to aid the operator in the reclassification. 7. The point cloud data were delivered in LAS format. dateTime: DateTime: 2007-02-28T00:00:00 processStep: (LI_ProcessStep) description: 3-D breaklines were created for the creation of a completely new hydrology dataset specifically tailored to meets the needs of the users of terrain data. 1) Breaklines were generated for all streams draining greater than approximately 1 square mile. 2) Two-dimensional lines defining the centerline and banks of those streams were manually digitized into Microstation format from the available 2002 source digital aerial imagery using lidar hillshades as an ancillary reference. 3) Breaklines were collected, unbroken through closed water bodies and culverts, as well as under roads, railroads, and bridges, in order to maintain proper stream network connectivity. 4) The entire breakline dataset was checked to ensure integrity of the linework with respect to topologic structure, connectivity, and positive downhill stream flow. 5) Single line streams were collected with the following criteria: Any area of drainage that did not meet the criteria to be collected as a double banked stream or closed water body. 6) Double-banked streams were collected with the Any area of drainage that was at least 40 feet wide for a distance of greater than 540 feet, and excluding closed water bodies. Double banked streams were delivered as linear features. 7) Artificial path lines were collected as the center line for all double banked streams and closed water bodies. Artificial paths were also created for closed water bodies where no flow path was delineated coming into or leaving the water body, and/or where the closed water body existed as the origin source of a flow path. 8) Artificial paths that are drawn in the two instances above go through the center of the water body and stop halfway through it. Artificial paths were only drawn for water bodies that fell on a streamline. 9) Any islands found within water bodies were collected in instances where trees were visible on them (indicating that these are permanent features). These islands were delivered as separate polyline features if present. 10) Any and all closed water bodies were collected, regardless of size, excluding such features as swimming pools, for the entire project area. 11) Water bodies were delivered as polygon features. 12) Single line streams, double banked streams, artificial paths and closed water bodies have unique attribution such that one feature type can be easily distinguished from another. 13) Linework was delivered in ESRI shape file format. 14) The 3D Hydro Breaklines were developed for the sole purpose of supporting flood mapping and should not be used to generate contours dateTime: DateTime: 2007-02-28T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received topographic files las V1.1 format. The files contained lidar elevation measurements, Class 2 Points, return information, scan angle, intensity values and GPS Week Time. The data were received in Massachusetts State Plane Mainland Zone 2001, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid03 model. The vertical units of the data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The GPS Week Time was converted to Adjusted Standard GPS Time. 2. The las files were changed from V 1.1 to V 1.2. 3. The las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03. 4. The las files were converted from a Projected Coordinate System (MA SP Mainland) to a Geographic Coordinate System (NAD83). 5. The las files' horizontal units were converted from meters to decimal degrees. dateTime: DateTime: 2013-10-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-01T06:23:11 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |