2006 Federal Emergency Management Agency (FEMA) Topographic Lidar: Bristol and Plymouth Counties, Massachusetts
OCM Partners
Data Set
(DS)
| ID: 49770
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49770
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2006 Federal Emergency Management Agency (FEMA) Topographic Lidar: Bristol and Plymouth Counties, Massachusetts |
---|---|
Short Name | ma2006_fema_bristolplymouth_m2602_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2013-11 |
* » 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. |
Notes |
10414 |
Other Citation Details | |
• Supplemental Information |
A complete description of this dataset is available in the project report submitted to FEMA Region 1 by CDM: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2602/supplemental/ma2006_fema_bristolplymouth.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2602/supplemental/ma2006_fema_bristolplymouth.KMZ |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
FEMA NFIP Topic Category | Breaklines |
FEMA NFIP Topic Category | Contours |
FEMA NFIP Topic Category | DEM |
FEMA NFIP Topic Category | Digital Terrain Model |
FEMA NFIP Topic Category | Elevation Data |
FEMA NFIP Topic Category | Flow vectors |
FEMA NFIP Topic Category | Land Surface |
FEMA NFIP Topic Category | LIDAR |
FEMA NFIP Topic Category | Relief |
FEMA NFIP Topic Category | Slope |
FEMA NFIP Topic Category | Topography |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Office for Coastal Management |
---|---|
• » City | Charleston |
• » State/Province | SC |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | |
• Maintenance Frequency | As Needed |
Maintenance Note | |
» Data Presentation Form | las |
• Entity Attribute Overview |
LiDAR points in LAZ format (ASPRS Class 2,7) |
Entity Attribute Detail Citation |
none |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of FEMA, Sanborn, CDM, MASSGIS, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2013-11 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2013-11 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2013-11 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2013-11 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -71.136354 |
---|---|
* » E° Bound | -70.588933 |
* » N° Bound | 41.795113 |
* » S° Bound | 41.47402 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2006-11-10 |
End | 2006-11-26 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2602 ; |
• » Data Access Constraints |
None |
• Data 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2602 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2602/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2602/supplemental/ma2006_fema_bristolplymouth.KMZ |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the communities of Westport, Dartmouth, New Bedford, Fairhaven, Mattapoisett, Marion, and Wareham. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | 2016-05-23 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-11-14 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details. |
Activity Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | 2018-03-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload to move data access links to Distribution Info. |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy | |
Vertical Positional Accuracy |
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. ; Quantitative Value: 0.294 meters, Test that produced the value: 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. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
Terrain data are derived datasets that aid automated hydrologic and hydraulic analyses, the flood hazard area boundary delineations, and quality control. |
Conceptual Consistency |
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. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» 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. |
Process Date/Time | 2006-12-31 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) 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. OCM 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. |
Process Date/Time | 2013-11-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 49770 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:22+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2022-08-09 17:11+0000 |
Metadata Record Published | 2022-03-16 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|