2008 FEMA Lidar: South Oneida County (NY)
OCM Partners
Data Set
(DS)
| ID: 49885
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49885
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2008 FEMA Lidar: South Oneida County (NY) |
---|---|
Short Name | ny2008_fema_south_oneida_m5044_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2016-06-15 |
* » Abstract |
For Oneida County, NY, there were two types of elevation datasets. The first type is LiDAR and the second one is Auto-correlation DEM. Auto-correlation DEM data was developed wherever LiDAR data was not available. LiDAR data was made available to this project through two different initiatives. The first set of LiDAR data was made available through HMTAP-1650 project, which consisted of area of 3 miles buffers around Mohawk River. Though data was available for the whole length of Mohawk, only data that pertained to the county was used for this project.The second set of LiDAR data was made available for DFIRM. DFIRM data was delivered at two different times. The first delivery done in 2008 (covers middle part of the county) and the second delivery done in 2009 (covers a small area in the west, around Oneida lake). As the two coverages did not have issues dealing with overlaps, they were used as they are. For the auto correlated data, in an effort to provide an alternative to the collection of LiDAR data and utilization of the National Elevation Dataset (NED), Dewberry has tested the methodology for the generation of a photogrammetrically derived surface model appropriate for Hydrologic and Hydraulic modeling and conforming to FEMA standards.The autocorrelated surface was generated using imagery from the 2003 New York statewide collection along with the Aerial Triangulation (AT) solution provided with the source imagery. The surface was subsequently edited through manual processes and improved with breaklines in order to meet ASPRS Class 1 accuracy requirements for 4 foot contour mapping.The final terrain is named as Oneida_Terrain.gdb. Please check the image from the PDF report in the General folder of the MIP submitted data. |
* Purpose |
Terrain data is used to represent the topography of a watershed and/or floodplain environment and to extract useful information for hydraulic and hydrologic models. (Source: FEMA Guidelines and Specs, Appendix N). |
Notes |
10529 |
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/5044/supplemental/ny2008_fema_oneida_south_m5044.kmz The project report of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5044/supplemental/ny2008_fema_oneida_south_m5044_lidarreport.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.0 format ASPRS cassfication scheme (1 = undefined; 2 = ground) contains the following fields of information: Class, GPS WeekTime, Easting, Northing, Elevation, Echo, Number, Echo, Intensity, Flightline |
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, NYSDEC, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2016-06-15 |
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-15 |
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-15 |
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-15 |
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 | -75.891796 |
---|---|
* » E° Bound | -75.061561 |
* » N° Bound | 43.319044 |
* » S° Bound | 42.919916 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2007-04-30 |
End | 2007-05-11 |
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=5044; |
• » Data Access Constraints |
None |
• Data Use Constraints |
The data depicts the elevations at time of survey and are accurate only for that time. Exercise professional judgement in using this data. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5044 |
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/5044/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/5044/supplemental/ny2008_fema_oneida_south_m5044.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the 2008 FEMA project spanning Oneida County, NY. |
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-10-25 |
---|---|
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 vertical accuracy is in compliance with the National Standard for Spatial Data Accuracy (NSSDA) RMSE estimation of elevation data in support of 2ft. contour mapping products as it is referenced in the FEMA guidelines for flood hazard mapping, appendix A (see Cross References). The Sanborn Map Company has performed a data accuracy validation and found this data to be in compliance.Additionaly, The New York State Department of Environmental Conservation performed a ground control analysis of the Oneida LiDAR data using ground control checkpoints in several land cover classes and found the resultant RMSE in the exposed ground class to be within the contract specifications of 0.185 meters.For the auto correlated data, data were compiled to meet ASPRS Class 1 accuracy requirements for 4 ft contour mapping. the vetical accuracy value is 1.18 meters. For HMTAP the elevation meets the accuracy required for this project (accuracy equivalent to 2 ft contours according to FEMA Guidelines and Specifications for Flood Hazard Mapping. Partners).; Quantitative Value: 0.185 meters, Test that produced the value: For the Oneida County Lidar data - Vertical error associated with this LiDAR data is a function of several factors including acquisition practices, height of the sensor above terrain, point spacing, diameter of the pulse footprint, network control station coordinates, kinematic GPS solutions, IMU calibration and post-processing functions.; Quantitative Value: 1.18 meters, Test that produced the value: For the autocorrelated data the resultant RMSE of this check was 1.18 meters; Quantitative Value: 0.60 meters, Test that produced the value: For the auto correlated data, when verifified against the control points identified by NY DOT the absolute accuracy of the surface model is 1.18 m RMSE. However, extensive evaluation was performed against the stereo imagery from which the surface was created and a relative accuracy of .39 m RMSE was achieved. Therefore the majority of the error present in the absolute accuracy is attributable to the error that is inherent in the AT solution for the source imagery.For HMTAP both methods(NDEP and RMSE)were utilised for vertical accuracy testing, LiDAR data over all three river basins(Susquehanna, Delaware and Mohawk) meets and exceeds all specifications. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
Complete |
Conceptual Consistency |
The 2009 Oneida County LiDAR data has met all quality checks in terms of relative accuracy, absolute accuracy, coverage and point and file format. The relative accuracy of the LiDAR data refers to how well the data set matches within itself. That is to say, adjacent LiDAR scans are in alignment with each other with no vertical or horizontal shifts caused by improper calibration and/or georeferencing. The absolute elevation has been validated by both Sanborn and NYS DEC.This was done by comparing the LiDAR ground surface against known ground control points. The data file format and point attribution is in compliance with the LAS version 1.1 specifications (see ASPRS LAS1.1 cross reference).The auto correlated data covers the mapping boundary provided for the Oneida County Auto-Correlation area. All files delivered were verified and tested to ensure they open and are positioned properly.The overall final Oneida correlated surface is free of artifacts caused by trees and buildings. Some minor artifacts from editing that do not negatively impact the the elevation of the final surface remain. For the HMTAP data Overall the data exhibit excellent detail and meet both the absolute and relative accuracy. The level of cleanliness for a bare-earth terrain is of the highest quality and no major anomalies were found. |
» 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 |
For the Oneida Co. LIDAR data -Using Sanborn's Leica ALS50(Sno 49) LiDAR system,12 flight lines of standard density (1.4 meter ground sample distance) data were collected over areas in Oneida Co, NY(approx 20 sq miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. For the autocorrelated data Manual Editing of surface posts using the interactive terrain editing (ITE) tools in Socet Set. The Manual editing was performed against the stereo imagery.Source used is Raw Scanned Imagery, AT, Initial Auto-Correlated Surface in ascii xyz format. Source production - Final Auto-Correlated surface in ASCII xyz format. Then the Stereo Imagery and Final Auto-Correlated Surface were used to identify areas where breaklines where necessary to support 4' contours; Source used - Raw Scanned Imagery, AT, Final Auto-Correlated Surface; source production - Breaklines. The next step was Using the final Auto-Correlated Surface posts and the Breaklines as source material the data was imported into an ArcGIS File Geodatabase and a terrain was generated; Source used -Final Auto-Correlated Surface in ASCII xyz format, Breaklines; Source production - Terrain Dataset.For the HMTAP data a manual visualization process was performed. This includes creating pseudo image products such as 3dmodels. By creating multiple images and using overlay techniques, potential errors can be found. |
Process Date/Time | 2008-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received topographic LAS files as part of a delivery of FEMA projects in various states which have not been made available to the public with any other federal agency. The files contained lidar easting, northing, elevation, as well as ancillary collection attributes. The data were received in UTM 18 in meters and were vertically referenced to NAVD88 using the Geoid03 model. 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 Geoid03 model. 3. The LAS files were converted from a projected coordinates to Geographic Coordinates in decimal degree. 4. Files were retiled to have more homogeniety across the project. |
Process Date/Time | 2016-06-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 | 49885 |
---|---|
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 |
---|