View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components
|2006 Federal Emergency Management Agency (FEMA) Topographic Lidar: Bristol and Plymouth Counties, MassachusettsspatialRepresentationInfo|
language: eng; USA
characterSet: (MD_CharacterSetCode) utf8
hierarchyLevel: (MD_ScopeCode) dataset
contact: Mike Sutherland(author) (CI_ResponsibleParty)
role: (CI_RoleCode) author
metadataStandardName: ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded Data
metadataStandardVersion: ISO 19115-2:2009(E)
return to top
geometricObjectType: (MD_GeometricObjectTypeCode) point
return to top
return to top
return to top
title: 2006 Federal Emergency Management Agency (FEMA) Topographic Lidar: Bristol and Plymouth Counties, Massachusetts
dateType: (CI_DateTypeCode) publication
citedResponsibleParty: NOAA CSC (originator)
citedResponsibleParty: FEMA (originator)
organisationName: Massachusetts Office of Geographic Information (MASSGIS)
role: (CI_RoleCode) originator
citedResponsibleParty: NOAA CSC (publisher) (CI_ResponsibleParty)
role: (CI_RoleCode) publisher
presentationForm: (CI_PresentationFormCode) imageDigital
abstract: FEMA Contract No. EME-2003-CO-0340 FEMA Task Order T018 Sanborn Map Company furnished the collection and processing, and development of Lidar and contours using photogrammetry to support the FEMA mapping requirements for a total of 142 square miles in coastal areas in Plymouth and Bristol Counties in Massachusetts. The 142 square miles includes the communities of Westport, Dartmouth, New Bedford, Fairhaven, Mattapoisett, Marion, and Wareham. The project area was defined using a buffered shapefile with limits along the coastline. The project area included a portion of both counties. All lidar data was acquired during November 2006 by Sanborn. Orthophotography used to create 2D breaklines was produced in 2005 by MassGIS as part of its statewide orthophoto program. All lidar data that was acquired was produced in accordance with FEMA specifications (Source: FEMA Guidelines and Specifications, Appendix N, Section N.1.2). Lidar Acquisition Parametes: Average Altitude: 1,200 Meters AGL Airspeed: ~120 Knots Scan Frequency: 36 Hertz Scan Width Half Angle: 16 Degrees Pulse Rate: 50000 Hertz The data being distributed through the NOAA Digital Coast are Gridded Bare-Earth LAS files.
purpose: The LIDAR derived data sets, including the first and last returns, a Gridded DEM, TIN file, 2' contours in ESRI geodatbase format and masspoint and Breakline files were developed to support Camp Dresser and McKee's continued development of updated Digital Flood Insurance Rate Maps and flood insurance studies for coastal areas in Massachusetts. Contours are based on bare earth LIDAR and breaklines digitized from 2D orthophotography (subsequently draped over the 3D LIDAR points) (Source: FEMA Guidelines and Specs, Appendix N). Coastal shoreline areas were set a 0.00 elevation to cartographically represent contours.
status: (MD_ProgressCode) completed
organisationName: Federal Emergency Management Agency, Region I
positionName: Flood Insurance and Mitigation Division
deliveryPoint: 99 High Street, 6th Floor
role: (CI_RoleCode) pointOfContact
maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded
fileDescription: This kmz file shows the extent of coverage for the 2006 FEMA Bristol and Plymouth counties, MA lidar data set.
keyword: Land Surface
keyword: Digital Terrain Model
keyword: Elevation Data
keyword: Flow vectors
type: (MD_KeywordTypeCode) theme
title: FEMA NFIP Topic Category
keyword: Bristol County
keyword: Plymouth County
type: (MD_KeywordTypeCode) place
resourceConstraints: Lidar Use Limitation
resourceConstraints: NOAA Legal Statement
title: Lidar Final Report
positionName: Citation URL
name: Lidar Final Report
function: (CI_OnLineFunctionCode) information
associationType: (DS_AssociationTypeCode) crossReference
spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector
language: eng; USA
topicCategory: (MD_TopicCategoryCode) elevation
return to top
distributorContact: NOAA CSC(distributor) (CI_ResponsibleParty)
role: (CI_RoleCode) distributor
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.
distributorContact: Mike Sutherland
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 top
level: (MD_ScopeCode) dataset
nameOfMeasure: Vertical Positional Accuracy Report
evaluationMethodDescription: The lidar data was evaluated using a collection of 11 GPS surveyed checkpoints. The category classes of bare earth, low grass and urban were used. For the Bristol checkpoints, the RMSEz is 14.7 centimeters. This area yielded much better results than the project requirement of 18.5 centimeters RMSEz. The vertial accuracy of the source data meet or exceed vertical National Map Accuracy Standards for 2-foot contour mapping. Please set the Project Report located in the supplemental information section above for more details.
nameOfMeasure: Vertical Positional Accuracy
measureDescription: This value reflects the data's tested Vertical Root Mean Squared Error (RMSEz) at 95% confidence interval (RMSEz @ 95% confidence = RMSEz x 1.9600) as defined by the Federal NSSDA (National Spatial Standard for Data Accuracy). Units in meters.
evaluationMethodDescription: Terrain data are derived datasets that aid automated hydrologic and hydraulic analyses, the flood hazard area boundary delineations, and quality control.
measureDescription: Sanborn used proprietary algorithms to remove features and artifacts in the first and last return data that did not reflect true ground elevations. New aerial stereo photography was flown, and aerial triangulated to allow production of breakline ehnacement of the Bare earth DEM and to hydrologically enforce contours and elevation data through the compilation of drainage breaklines.
description: Using an Optech Light Detection and Ranging (LiDAR) system, flight lines were planned for standard density 1.4 meter GSD. The Flight plan for the project includes the following specifications to fully meet the project requirements - single pass density of approximately 2.0 square meters per sample * Swath width 728 meters * Flight altitude 1000 meters * flight line spacing -589 meters with 125 meters overlap *Scan Frequency- 35 Hz *Scan Angle- 20 degrees * Aircraft ground speed -- 140 knots * System Calibration pre and post mission * Two GPS base stations within 30 KM. Multiple returns were recorded for each laser pulse along with an intensity value for each return. The data are calibrated for geographic referencing. Points are further processed, using TerraSolid? software, to classify return values. The first and last return data is filtered to remove the vegetation and above ground manmade features to yield a ground surface. The bare earth elevation data was draped over the existing orthophotos. Breaklines for hydrographic features, bridges, culverts and major roadways were captured in 2D. Elevations were associated to the breaklines by draping onto the Lidar data. The DTM was then used to produce a TIN. The TIN was used to generate 2-ft contours.
description: The NOAA Coastal Services Center (CSC) received topographic files in ASCII format. The files contained lidar elevation measurements. 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 feet. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The ASCII files were converted to LAS V1.2 using LASTools' txt2las. 2. The topographic las file '8002645' was found to be corrupt and removed from the data set. 3. All points in the topographic las files were converted to Class 2 (Ground) using LASTools' las2las. 4. The topographic las files were found to contain noise, those points were manually reclassified to Class 7 (Noise) using Merrick MARS7. 5. All additional VLRs in the topographic las files' header used by MARS7 were removed using LASTools' las2las. 6. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03. 7. The topographic las files were converted from a Projected Coordinate System (MA SP 2001) to a Geographic Coordinate System (NAD83). 8. The topographic las files' horizontal units were converted from feet to decimal degrees. 9. The topographic las files' vertical units were converted from feet to meters. 10. The data were converted to LAZ format.
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.
processor: Mike Sutherland (processor) (CI_ResponsibleParty)
role: (CI_RoleCode) processor
return to top
maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) annually
maintenanceNote: 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-12-06T16:44:54.725-05:00