2004 Connecticut Coastline Lidar Mapping
Office for Coastal Management
Data Set
(DS)
| ID: 48168
| Published / External
Created: 2017-11-14
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 37231
ID: 48168
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2004 Connecticut Coastline Lidar Mapping |
---|---|
Short Name | ct2004_m20_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2006-08-14 |
* » Abstract |
LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. Using a combination of laser rangefinding, GPS positioning and inertial measurement technologies; LIDAR instruments are able to make highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures and vegetation. This data was collected at submeter resolution to provide nominal 1m spacing of collected points. Two returns were recorded for each pulse in addition to an intensity value. Original contact information: Contact Org: NOAA Office for Coastal Management Phone: 843-740-1202 Email: coastal.info@noaa.gov |
* Purpose |
LIDAR data is used for 3D visualization, elevation based analysis and for feature extraction. |
Notes |
10191 |
Other Citation Details | |
• Supplemental Information |
Reflective surface data represents the DEM created by laser energy reflected from the first surface encountered by the laser pulse. Some energy may continue beyond this initial surface to be reflected by a subsequent surface as represented by the Last Return data. Intensity information is captured from the Reflective Surface pulse and indicates the relative energy returned to the sensor as compared to the energy transmitted. The Intensity image is not calibrated or normalized but indicates differences in energy absorption due to the interaction of the surface materials with laser energy at the wavelength transmitted by the sensor. Points are classified as on ground surface or not on ground surface to support creation of a bare earth model from the data. Open water is classified as not bare ground. The 2004 Connecticut Lidar Data Validation Report may be viewed at https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/20/supplemental/index.html |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > TOPOGRAPHICAL RELIEF MAPS |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > SEAFLOOR TOPOGRAPHY |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
None | Beach |
None | Erosion |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > CONNECTICUT |
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 | None Planned |
Maintenance Note | |
» Data Presentation Form | |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn for the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. |
Data Set Credit | This data set was developed for the NOAA OCM by Woolpert. |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2006-08-14 |
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 | 2006-08-14 |
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 | 2006-08-14 |
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 | 2006-08-14 |
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 | -72.908092 |
---|---|
* » E° Bound | -72.279933 |
* » N° Bound | 41.45389 |
* » S° Bound | 41.240042 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2004-10-08 |
End | |
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 |
US DOD |
Security Handling Description |
Information Unclassified with release control provided by NOAA/Office for Coastal Management |
• Data Access Policy | |
» Data Access Procedure |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer.; |
• » 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=20 |
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/20/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 | |
---|---|
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 |
Horizontal accuracy can be characterized by the rule of thumb of 1/2000th of flying height or roughly 0.5 meters for this collect. Spot checks in the field routinely are measured at 1/4000th of flying height but are not formally characterized. |
Vertical Positional Accuracy |
The vertical accuracy was tested following the National Standards for Spatial Data Accuracy. Based on a total of 22 points the average error between the bare earth LiDAR coverage and the control was 0.002 m with a root mean square error (RMSE) of 0.057 m. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure |
Cloud Cover: Unknown |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
LIDAR raster data is visually inspected for completeness to ensure that any gaps between flight lines or loss of signal represents less than 5% of required collection area. Areas of open water where loss of LIDAR signal is common are corrected to the best estimate of water level at time of collection. LIDAR is self-illuminating and has minimal cloud penetration capability. Water vapor in steam plumes or particulates in smoke may cause reflection of LIDAR signals and loss of elevation information beneath these plumes. Glass structures and roofs may appear transparent to the LIDAR signal and therefore may not register on the reflective surface. Some asphalt formulations have been shown to absorb topographic LIDAR wavelength energy resulting in "pitting" of roof surfaces using this material. |
Conceptual Consistency |
All LAS formatted LIDAR data are validated using commercial GIS software to ensure proper formatting and loading before delivery. This validation procedure ensures that data on delivery media is in correct physical format and is readable. |
» 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 | Collection System Calibration |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Minimizes horizontal error caused by IMU mis-alignment by checking over known range and by comparing positional results from adjacent flight lines to compute error adjustment function. | Type of Source Media: Validation Report |
Citation Title | LiDAR data collection |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2004-10-08 |
Extent End Date/Time | |
Scale Denominator | 3000 |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Raw spatial elevation information | Type of Source Media: DVD-ROM |
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 |
Data Collection: Using a LH Systems ALS50 Light Detection and Ranging (LiDAR) system, 41 flight lines of high density (submeter ground sample distance) data were collected over areas in coastal Connecticut (approximately 300 square kilometers). Two returns were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in one (1) mission on October 8, 2004. Three (3) airborne global positioning system (GPS) base stations were used to support the LiDAR data acquisition: Moriches 1 continuously operating reference station (CORS) ARP, NGS point P36, and one station Woolpert located using static GPS positioning methods, Madison CP. In addition, twenty-two control points were surveyed through fast-static GPS methods to support the final accuracy analysis and tied into the National Geodetic Survey (NGS) points Moriches CORS and P36. |
Process Date/Time | 2004-10-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Airborne GPS Processing: Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The overlap between flight lines was removed to provide a homogeneous coverage, and the coverage was classified to extract a bare earth digital elevation model (DEM). Airborne GPS is differentially processed using the GrafNAV V4.10 software by Waypoint Consulting of Calgary, Alberta, Canada. The PDOP and distance separation is as follows: P36: Maximum PDOP = 3.58 (maximum) Average Distance Separation: 17 km Madison CP: Maximum PDOP = 3.58 (maximum) Average Distance Separation: 19 km IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia. The classification and quality control (QC) of LiDAR data is carried out using a combination of proprietary software and TerraScan software by Terrasolid Limited of Helsinki, Finland. Two (2) coverages were delivered in the LAS file format: bare-earth and above ground features. |
Process Date/Time | 2004-11-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
IMU data Processing: IMU data provides information concerning roll, pitch and yaw of collection platform during collection event. IMU information allows the pulse vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly positioned on the elevation model surface. IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. |
Process Date/Time | 2004-11-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
Reflective Surface Generation: The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia. |
Process Date/Time | 2004-11-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
LIDAR Point Classification The classification and quality control (QC) of LiDAR data is carried out using a combination of proprietary software and TerraScan software by Terrasolid Limited of Helsinki, Finland. |
Process Date/Time | 2004-12-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 6 |
---|---|
» Description |
Output LAS Files Random LIDAR points maintained in UTM coordinate system converted to Geographic projection with units of Decimal Degrees |
Process Date/Time | 2005-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 7 |
---|---|
» Description |
Transfer to delivery media: Data is transferred from hard-disk to DVD delivery media using a Primera Bravo DVD/CDROM disc publishing hardware. |
Process Date/Time | 2005-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 8 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received files in LAS format. The files contained LiDAR intensity and elevation measurements. OCM performed the following processing on the data to make it available within the LiDAR Data Retrieval Tool (LDART): 1. The las files were converted from State Plane coordinates to Geographic coordinates. 2. The las header fields were sorted by latitude and updated. |
Process Date/Time | 2006-09-27 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 9 |
---|---|
» Description |
For data management purposes, the Office for Coastal Management (OCM) converted the data from NAVD88 heights to ellipsoid heights using Geoid 03. |
Process Date/Time | 2008-01-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 | 48168 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-14 14:19+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 | OCM |
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 |
---|