2011 FEMA Lidar: Chemung Watershed (NY) (AOI 2)
OCM Partners
Data Set
(DS)
| ID: 49887
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49887
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2011 FEMA Lidar: Chemung Watershed (NY) (AOI 2) |
---|---|
Short Name | ny2011_fema_chemung_m5029_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2016-06-16 |
* » Abstract |
LiDAR data was acquired by Tuck Mapping Solutions, Inc. (TMSI) for the Chemung Watershed and broken down into two AOIs based on the level of processing performed on the dataset. AOI-1 covers approximately 709 square miles, which is the full extent of the acquisition boundary plus a 100-meter buffer around the perimeter of this boundary. AOI-1 was delivered as full-swath, calibrated, and boresighted flight lines in LAS format. A subset of AOI-1, delineated by a buffer around the major stream networks, covers approximately 308 square miles. RAMPP will make the following products available to FEMA by uploading the digital data to the MIP, where applicable, or via hard drives. The deliverables for this Technical Support Data Notebook (TSDN) submittal include written certification that the topographic data development meets minimum Federal Emergency Management Agency (FEMA) standards and specifications. In cases where data do not meet the required standards and specifications, an explanation is included. Additionally, the related metadata file has been uploaded to the Mapping Information Platform (MIP). Deliverables will include raw point clouds and classified point clouds (see report for details), hydro-lines, low confidence polygons, qa/qc report, survey report and a summary report. Classifications include ASPRS Class 1,2,7,9,11. Acquisition AOI-2 fulfills this dataset (see Page 3 of the Final Topographic Data Developmental Report). |
* Purpose |
The following is the Risk Assessment, Mapping, and Planning Partners (RAMPP) Scope of Work for Task Order HSFEHQ-10-J-0006 for Chemung Watershed, NY. RAMPP acquired and processed LiDAR data to support flood hazard data updates based on the FEMA ordering Sheet, dated June 29, 2010. The acquired elevation data complies with the FEMA Procedures Memorandum: Standards for LiDAR and other High Quality Elevation Data (version dated July 19, 2010). RAMPP will be responsible for full turnkey implementation of the elevation collection, processing and post processing of the LiDAR data, checkpoint surveys, quality assurance and quality control (QA/QC). Upon completion of topographic data collection and processing, RAMPP will submit a detailed description of the data available and include the source input files used in a TSDN report document and upload the digital data to the MIP where applicable. Additionally, RAMPP will submit a hard drive to the FEMA Engineering Library with all the LiDAR data and the appropriate reports and documents. |
Notes |
10531 |
Other Citation Details | |
• Supplemental Information |
A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5029/supplemental/ny2011_fema_chemung_watershed_m5029.kmz The lidar report of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5029/supplemental/ny2011_fema_chemung_watershed_m5029_lidarreport.pdf The survey report of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5029/supplemental/ny2011_fema_chemung_watershed_m5029_surveyreport.pdf The quality report of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5029/supplemental/ny2011_fema_chemung_watershed_m5029_qualityreport.pdf |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | Land Surface |
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 | None Planned |
Maintenance Note | |
» Data Presentation Form | las |
• Entity Attribute Overview |
LiDAR point data in LAS 1.2 format |
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 Tuck Mapping Solutions, Inc, FEMA, RAMPP, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2016-06-16 |
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 | 2016-06-16 |
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 | 2016-06-16 |
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 | 2016-06-16 |
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 | -77.547053 |
---|---|
* » E° Bound | -76.958932 |
* » N° Bound | 42.586629 |
* » S° Bound | 42.028889 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2011-04-30 |
End | 2011-05-10 |
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=5029; |
• » 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. Acknowledgement of FEMA would be appreciated in products derived from these data. This digital data is produced for the purposes of updating/creating a DFIRM database. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5029 |
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/5029/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 |
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/5029/supplemental/ny2011_fema_chemung_watershed_m5029.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the 2011 FEMA Chemung Watershed AOI-2 project in New York state. |
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-06-14 |
---|---|
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 |
Compiled to meet 3 foot horizontal accuracy at the 95 percent confidence level (near 1.0 m). Ground control stations are expected to have local network accuracy at the 95% accuracy level of 2 cm horizontally and vertically. |
Vertical Positional Accuracy |
RMSE of 0.100 m (FVA of 19.6 cm); Quantitative Value: 0.100 meters, Test that produced the value: Fundamental Vertical Accuracy (FVA) in open terrain was tested on AOI-2. Checkpoints in the Open Terrain land cover category were tested against the first return LiDAR points in open terrain across the entire acquisition area. FVA is reported at the 95% confidence level, which is computed as the root mean square error of the checkpoint elevations (RMSEz) x 1.9600. The maximum tolerance was 1.25 meters RMSE x 1.9600; the resulting fundamental vertical accuracy tolerance was 0.196 meters (page 20 of the Quality Report). |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
Complete |
Conceptual Consistency |
All LiDAR files delivered were verified and tested to ensure they open and are positioned properly. |
» 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 |
Acquisition LiDAR data was acquired by Tuck Mapping Solutions, Inc. (TMSI) for the Chemung Watershed and broken down into two AOIs based on the level of processing performed on the dataset. AOI-1 covers approximately 709 square miles, which is the full extent of the acquisition boundary plus a 100-meter buffer around the perimeter of this boundary. AOI-1 was delivered as full-swath, calibrated, and boresighted flight lines in LAS format. A subset of AOI-1, delineated by a buffer around the major stream networks, covers approximately 308 square miles. This dataset (AOI-2) was processed by TMSI to classify bare-earth ground points and hydro features and was delivered as a tiled, classified, point cloud in LAS format using the following classification scheme: Class 1 - Processed but unclassified Class 2 - Bare-earth ground Class 7 - Low points and noise Class 9 - Water Class 11 - Withheld |
Process Date/Time | 2011-05-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Processing Processing of the LiDAR data begins with refinement of the initial boresight alignment parameter in the ALS Processor configuration file (.reg) delivered with the raw data. For projects that have more than one lift, the boresight for each lift has to be completed individually because it may differ slightly from lift to lift. Lift boresighting is accomplished using the tri-directional calibration flight lines over the project area. One calibration flight line is flown bi-directionally overlapping a project flight line within the lift. This bi-directional calibration will also be used as a parallel flight line with the adjacent flight line. There is a cross flight line collected perpendicular to both. All three lines along with the parallel project flight line are examined to ensure that they agree, within expected system tolerances, in the overlapping areas. The two bi-directional flight lines are used to diagnose Roll and Pitch. The two parallel flight lines are used to diagnose and correct Heading error. The two perpendicularly overlapping flight lines are used to examine Variable Scan Angle error. To begin lift boresight, the raw LiDAR data of the calibration flight lines will be processed with the initial boresight parameters determined from the LiDAR Sensor Calibration. Once the boresighting is done for the calibration flight lines, the adjusted settings will be applied to the complete lift and checked for consistency. For a well-maintained LiDAR system, functioning correctly under normal operating conditions, actual boresight angles can be considered constant throughout a single mission. Therefore, once the boresight angles have been adjusted based on the calibration flight lines, the same corrections can be applied to the entire lift. Under optimal circumstances, the boresight parameters determined for the calibration flight lines should be the same for all flight lines in the lift, but residual errors can occur. To correct for this, all of the overlaps between flight lines (side lap) and intersections of the project cross flight lines should be examined for internal consistency. If the results of the boresights start showing drift in the middle of the lift or the misalignment between flight lines starts exceeding project accuracy specifications, boresight parameters need to be adjusted to correct these errors. Once boresight adjustments are completed for each individual lift, the technician checks and corrects the vertical misalignment of all the flight lines and also the matching between data and ground truth. This process includes calculating the zbias value for each flight line so that all flight lines are vertically aligned and the entire data set match to the ground control points within the project specified accuracy range. The technician will run a final vertical accuracy check after the z correction. The result will be analyzed against the project specified accuracy to verify it meets the requirement. |
Process Date/Time | 2011-07-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Quality Risk Assessment, Mapping, and Planning Partners (RAMPP) performed a limited review of the Chemung Watershed, New York dataset. 100% of the data was checked for completeness and 5% of the data was visually examined at the micro level for qualitative issues according to the scope of work. A vertical accuracy assessment was performed on the first return points in the Level 1-processed dataset (AOI-1) and the full point cloud in the Level 2-processed dataset (AOI-2). No major completeness or quality issues were identified. Both datasets meet the Federal Emergency Management Agency's (FEMA) vertical accuracy specifications. Based on the limited qualitative and vertical accuracy assessments conducted by RAMPP on the data delivered, the Chemung Watershed, NY delivery meets the applicable project specifications as set forth by the IDIQ Subcontract # HSFEHQ-09-D- 0369-U005, Task Order HSFEHQ-10-J-0006, revised September 3, 2010. |
Process Date/Time | 2011-07-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received AOI 2 of the Chemung Watershed project boundary. The dataset included topographic LAS files as part of a FEMA data delivery. The files contained lidar easting, northing, elevation, as well as ancillary collection attributes. The data were received in UTM 18 (meters) and were vertically referenced to NAVD88 using the "latest" geoid, which was assumed to be the Geoid09 model due to the provided collection dates (as GPS times were usable for this determination). OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were converted from feet to meters, removing erroneous elevations. 2. The LAS files were converted from orthometric (NAVD88) heights to ellipsoidal heights using the Geoid09 model but remaining in meters. 3. The LAS files were converted from a Projected Coordinate System to a Geographic Coordinate system with decimal degree units. |
Process Date/Time | 2016-06-14 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 | 49887 |
---|---|
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 |
---|