2007 ARRA Lidar: Lake County, IL
OCM Partners
Data Set
(DS)
| ID: 49759
| Published / External
Created: 2017-11-15
|
Last Modified: 2023-12-07
Project (PRJ) | ID: 49401
ID: 49759
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2007 ARRA Lidar: Lake County, IL |
---|---|
Short Name | il2007_arra_lake_co_m4794_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2015-01-15 |
* » Abstract |
The Classified Point Cloud LAS files consist of 5 different classifications: Unclassified, Ground, Noise, Water and Ignored Ground. Merrick used the Leica ALS50 sensor. Merrick & Company flew a mapping mission in April/May 2007 to capture aerial photography over 539 square miles of Lake County, Illinois. |
* Purpose |
Questions pertaining to this dataset can be forward to the Lake County Department of Information and Technology/GIS Mapping Division in Waukegan, IL at maps@lakecountyil.gov (or KCaldwell@co.lake.il.us) |
Notes |
10403 |
Other Citation Details | |
• Supplemental Information |
A report for this project is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4794/supplemental/il2007_arra_lake_co_m4794_surveyreport.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/4794/supplemental/il2007_arra_lake_co_m4794.kmz |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | Ground |
None | Terrain |
Temporal Keywords
Thesaurus | Keyword |
---|---|
None | 2007 |
* 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 |
LAS 1.2 format (classes 1,2,9,10) |
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 Merrick & Co, USGS, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2015-01-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 | 2015-01-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 | 2015-01-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 | 2015-01-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 | -88.2023 |
---|---|
* » E° Bound | -87.75516 |
* » N° Bound | 42.497153 |
* » S° Bound | 42.155385 |
* » 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-16 |
End | 2007-05-07 |
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=4794 The data set is dynamically generated based on user-specified parameters.; |
• » 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=4794 |
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/4794/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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4794/supplemental/il2007_arra_lake_co_m4794.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the 2007 ARRA lidar project for Lake County, Illinois |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4794/breaklines/index.html |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | Zip |
Description |
Link to the breaklines. |
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 |
See report |
Analytical Accuracy | |
Horizontal Positional Accuracy |
The ortho imagery horizontal positional accuracy and the assurance of that accuracy depend, in part, on the accuracy of the data inputs to the rectification process. These inputs consist of the digital terrain model (DTM), fully digital analytic aerotriangulation (FDAAT) control and methods, the photo source camera calibration, scanner calibration, and aerial photographs. The orthoimagery output from these inputs meet National Map Accuracy Standards (NMAS). Aerial cameras have current certification from the USGS, National Mapping Division, Optical Science Laboratory. Test calibration scans are performed on all source photography scanners.; Quantitative Value: 0.068 meters, Test that produced the value: The horizontal positional accuracy value is derived from a standard aerotriangulation process known as a simultaneous bundle adjustment. Coordinates of ground points are derived from the measured coordinates of image points using mathematical functions. These corrections are made to points distributed over a large area, known as a block. The resulting solution is obtained simultaneously for all points to maintain consistency of all the stereo-models within the block. 0.236 feet RMSE X; 0.212 feet RMSE Y, averaging to 0.224 ft overall. |
Vertical Positional Accuracy |
NSSDA accuracy of 0.59 feet exceeds Fundamental Vertical Accuracy (FVA) requirement of 0.6 feet; Quantitative Value: 0.088 meters, Test that produced the value: RMSE(z) in meters |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
The dataset was reviewed to ensure complete coverage of the project area. |
Conceptual Consistency |
Calibrations of the LIDAR flightline data are performed; this process is known as boresighting. The flightlines are compared to evaluate both their relative and absolute accuracies. |
» 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 |
LiDAR data was collected using Leica ALS50 Phase I sensor. The raw data was verified in MARS software for complete coverage of the project area, and boresighted to align the flightlines. Raw data files were parsed into manageable client-specific tiles. These tiles were then processed through automated filtering that separates the data into different classification groups: unclassified points, ground points, "noise" points and water. The data was next taken into MARS to reclassify the erroneous points that may remain in the LiDAR point cloud after auto-filter. |
Process Date/Time | 2010-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 the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in UTM Zone 5, NAVD88 (orthometric) heights in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from UTM coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in feet using Geoid 03. 3. The LAS data were sorted by latitude and the headers were updated. |
Process Date/Time | 2015-01-10 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 | 49759 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:22+0000 |
Metadata Record Last Modified By | Rebecca Mataosky |
» Metadata Record Last Modified | 2023-12-07 21:32+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 |
---|