FEMA RiskMAP Atlantic, Ocean, and Monmouth, NJ Area of Interest (AOI)
OCM Partners
Data Set
(DS)
| ID: 49860
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49860
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | FEMA RiskMAP Atlantic, Ocean, and Monmouth, NJ Area of Interest (AOI) |
---|---|
Short Name | nj2010_arra_3counties_m4868_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2015-03-30 |
* » Abstract |
Lidar data was acquired over a 1613 square mile area of interest over Atlantic, Ocean, and Monmouth Counties, New Jersey. The lidar data had a nominal point spacing no greater than 1m with a side lap that did not exceed 60%. The lidar data was flown, under went boresight calibration, was processed and then converted to the final deliverable datum and projection provided as NAD83/2007 New Jersey State Plane Coordinate System in US Survey Feet. The vertical datum was North American Vertical Datum 1988 (NAVD88). |
* Purpose |
Topographic elevation data utilizing airborne lidar in support of the floodplain mapping program and other potential uses. |
Notes |
10504 |
Other Citation Details | |
• Supplemental Information |
A report for this project is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4868/supplemental/nj2010_arra_3counties_m4868_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/4868/supplemental/nj2010_arra_3counties_m4868.kmz |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
Temporal Keywords
Thesaurus | Keyword |
---|---|
None | 2011 |
None | February |
* 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 |
LAS 1.2 format (classes 1,2,7,9,11) |
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 Fugro Earth Data Inc, RAMPP, FEMA, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2015-03-30 |
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-03-30 |
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-03-30 |
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-03-30 |
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 | -74.9863883835 |
---|---|
* » E° Bound | -73.9899530565 |
* » N° Bound | 40.2509146284 |
* » S° Bound | 39.288191083 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2011-02-15 |
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 | |
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=4868 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=4868 |
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/4868/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/4868/supplemental/nj2010_arra_3counties_m4868.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the 2011 New Jersey ARRA Lidar Collection for Atlantic, Monmouth, and Ocean Counties. |
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 |
The following methods are used to assure lidar accuracy. 1. Use of IMU and ground control network utilizing GPS techniques. 2. Use of airborne GPS in conjunction with the acquisition of lidar. 3. Measurement of quality control ground survey points within the finished product. The boresight of the lidar was processed against the ground control for the New Jersey AOI which consisted of 37 lidar ground survey points and 2 airborne GPS (ABGPS) base stations at the operation airport. The horizontal datum for the control was the North American Datum of 1983/2007 adjustment (NAD83/2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). The Geoid09 model was used to transform the ellipsoidal heights to GPS derived orthometric heights. ABGPS data was collected during the acquisition mission for each flight line. During the data acquisition the Positional Dilution of Precision (PDOP) for the ABGPS was monitored. The control points were measured by technicians using Terrascan and Fugro EarthData proprietary software and applied to the boresight solution for the project lines. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Horizontal accuracy will meet or exceed 0.6 m RMSEr; Quantitative Value: 0.60 meters, Test that produced the value: Horizontal accuracy will meet or exceed 0.6 m RMSEr |
Vertical Positional Accuracy |
Vertical elevations will meet or exceed 18.5 cm RMSEz; Quantitative Value: 0.054 meters, Test that produced the value: Vertical accuracy tested at FVA=0.35 ft (10.7 cm). RMSEz = 5.4 cm |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
The bare earth surface will contain voids where insufficient energy was reflected from the surface to generate a valid return from the terrain. Voids in the bare earth surface tend to occur in heavily vegetated areas, water bodies, and beneath buildings, motor vehicles, bridges etc. Fresh or wet asphalt, wet sand and certain types of vegetation can also cause voids or anomalous elevations. |
Conceptual Consistency |
Compliance with the accuracy standard was ensured by the collection of GPS ground control during the acquisition of aerial lidar and the establishment of a GPS base station operation airport. The following checks were performed. 1. The ground control and airborne GPS data stream were validated through a fully analytical boresight adjustment. 2. The lidar elevation data were checked against the project control. 3. Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). |
» 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 |
TerraSurv under contract to Fugro EarthData, Inc. successfully established ground control for the New Jersey AOI. A total of 37 ground control points in the New Jersey AOI were acquired. GPS was used to establish the control network. The horizontal datum was the North American Datum of 1983, 2007 adjustment (NAD83/2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). |
Process Date/Time | 2010-04-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
The Fugro EarthData, Inc. acquisition team collected ALS60 derived lidar over the Atlantic, Ocean, and Monmouth AOI in the State of New Jersey with a 1m, nominal post spacing using a Piper Navajo Chieftain aircraft tailnumber N76JN. The collection for the entire project area was accomplished on April 1st, 2nd, 3rd, 4th, 5th, 6th, 7th, and 10th. Coastal areas where only collected at low tide. The collection was performed using a Leica ALS60 MPiA lidar system, serial number ALS142, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. This project required 14 lifts of flight lines to be collected. The lines were flown at an average of 8,700 feet above mean terrain using a maximum pulse rate frequency of 89,900 Hz. The sensor had a 40 degree FOV and a swath width of 1929 meters. |
Process Date/Time | 2010-04-10 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
1. Lidar, GPS, and IMU data was processed together using lidar processing software. 2. The lidar data set for each flight line was checked for project area coverage and lidar post spacing was checked to ensure it meets project specifications. 3. The lidar collected at the calibration area and project area were used to correct the rotational, atmospheric, and vertical elevation differences that are inherent to lidar data. 4. Intensity rasters were generated to verify that intensity was recorded for each lidar point. 5. Lidar data was transformed to the specified project coordinate system. 6. By utilizing the ground survey data collected at the calibration site and project area, the lidar data was vertically biased to the ground. 7. Comparisons between the biased lidar data and ground survey data within the project area were evaluated and a final RMSEz value was generated to ensure the data meets project specifications. 8. Lidar data in overlap areas of project flight lines were trimmed and data from all swaths were merged into a single data set. 9. The data set was trimmed to the digital project boundary including an additional buffer zone of 100 meters. 10. The resulting data set is referred to as the raw lidar data. |
Process Date/Time | 2010-06-15 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
1. The raw lidar data was processed through a minimum block mean algorithm, and points were classified as either bare earth or non-bare earth. 2. User developed "macros" that factor mean terrain angle and height from the ground were used to determine bare earth point classification. 3. The next phase of the surfacing process was a 2D edit procedure that ensures the accuracy of the automated feature classification. 4. Editors used a combination of imagery, intensity of the lidar reflection, profiles and tin-editing software to assess points. 5. The lidar data was filtered, as necessary, using a quadric error metric to remove redundant points. This method leaves points where there is a change in the slope of surfaces (road ditches) and eliminates points from evenly sloped terrain (flat field) where the points do not affect the surface. 6. The algorithms for filtering data were utilized within Fugro EarthData proprietary software and commercial software written by TerraSolid. 7. The flight line overlap points were merged back into filtered data set for delivery product. 8. The point cloud data were delivered tiled in LAS 1.2 format; class 1 - unclassified, class 2 - ground, class 7 - low point (noise), class 11 - overlap. |
Process Date/Time | 2010-08-20 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» 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 State Plane Zone 2900, NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from State Plane coordinates to geographic coordinates. 2. Erroneous elevations were removed. 3. The data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in meters using Geoid 09. 4. The LAS data were sorted by latitude and the headers were updated. |
Process Date/Time | 2015-03-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 | 49860 |
---|---|
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 |
---|