2013 USACE Topographic Lidar: Rio Puerto Nuevo (PR)
OCM Partners
Data Set
(DS)
| ID: 49954
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49954
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2013 USACE Topographic Lidar: Rio Puerto Nuevo (PR) |
---|---|
Short Name | pr2013_usace_gsj_pn_rdlp_m4711_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2014-12-22 |
* » Abstract |
This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. The NAD83/2011 geodetic products were delivered as individual LAS files representing the geographic extent of each uniquely identified and acquired flight line or lift. USACE regularly uses digital topographic information to support regulatory, land management and acquisition, planning, engineering and habitat restoration projects. The data were classified into 4 classifications; (1) unclassified, (2) ground, (9) water,and (12) overlap points. The full study area of approximately 404 square km was processed. The tiles are 1,000 x 1,000m in size and Final deliverables were provided as geographic coordinates referenced to the North American Datum of 1983/2011 Realization (NAD83/2011) and as projected coordinates referenced to the State Plane Coordinate System, Puerto Rico Virgin Islands FIPS Zone 5200, NAD83/2011, vertical PRVD02 orthometric height. Upon arrival to NOAA's Office for Coastal Management the data were converted from State Plane to geographic and from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 12a. Original project title was "2013 Greater San Juan, Puerto Nuevo, Rio de la Plata". |
* Purpose |
The purpose of the project is to provide the United States Army Corps of Engineers with updated digital topgraphic information covering the Rio Puerto Nuevo basin of the greater San Juan, Puerto Rico metropolitan area. The Corps regularly uses digital topographic information to support regulatory, land management and acquisition, planning, engineering and habitat restoration projects. The data may also become available to local, state and other federal agencies for their specific management and analysis needs. |
Notes |
10598 |
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/4711/supplemental/pr2013_usace_gsj_pn_rdlp_m4711.kmz A report for this dataset is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4711/supplemental/pr2013_usace_gsj_pn_rdlp_m4711_surveyreport.pdf |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
CoRIS Discovery Thesaurus | Geographic Information > LiDAR |
CoRIS Theme Thesaurus | EARTH SCIENCE > Land Surface > Topography> Terrain Elevation |
None | usace |
Temporal Keywords
Thesaurus | Keyword |
---|---|
None | 2011 |
None | February |
* Spatial Keywords
Thesaurus | Keyword |
---|---|
CoRIS Place Thesaurus | COUNTRY/TERRITORY > United States of America > Puerto Rico > Puerto Rico (18N066W0000) |
CoRIS Place Thesaurus | OCEAN BASIN > Atlantic Ocean > Caribbean Sea /North Atlantic Ocean > Puerto Rico > Puerto Rico (18N066W0000) |
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 |
Lidar points in LAZ format (Classes 1,2,9,12) |
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 USACE, Precision Aerial Reconnaissance, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2014-12-22 |
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 | 2014-12-22 |
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 | 2014-12-22 |
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 | 2014-12-22 |
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 | -66.159 |
---|---|
* » E° Bound | -66.026 |
* » N° Bound | 18.484 |
* » S° Bound | 18.348 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2013-10-27 |
End | 2013-11-03 |
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? | |
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=4711; |
• » 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=4711 |
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/4711/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 | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4711/supplemental/pr2013_usace_gsj_pn_rdlp_m4711.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the coverage of the 2013 USACE Puerto Rico lidar collection. |
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 | 2017-01-05 |
---|---|
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 |
These data are not attributed. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Expected horizontal accuracy for the Leica ALS70-cm sensor, as determined from system studies and other methods, is 1/5500th of the flight height, which, in the instance of this particular project was 3,800-feet AGL (1250m), giving a horizontal tolerance of less than 0.691 US survey feet (0.211 m).; Quantitative Value: 0.211 meters, Test that produced the value: 21.1 cm |
Vertical Positional Accuracy |
The Fundamental Vertical Accuracy (FVA) of the dataset was determined using check points located only in open, non-vegetated terrain where there is a very high probability that the sensor will have detected the ground surface. For this project, one of the ground cover classes (OLG) was used in addition to vertical control (VC) to calculate the fundamental vertical accuracy. The vertical control points were not a ground cover classification, but were captured to be used in the calibration and editing of the data. The fundamental accuracy is calculated at the 95-percent confidence level as a function of RMSEz and is specified at a higher level of accuracy than other land cover categories. The FVA is calculated using the same formula as Accuracyz.; Quantitative Value: 0.06 meters, Test that produced the value: 6.0 cm RMSEz |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
This data set covers the spatial extent of topographic lidar data obtained during this survey. |
Conceptual Consistency |
Data covers the tile scheme provided for the area and was verified for correct topology. Hydro connectivity, monotonicity and vertical consistency of the breaklines was validated. |
» 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 |
All flights for the project were accomplished with a single-engine Cessna 206 which provided an ideal, stable aerial base for LiDAR acquisition. This platform has relatively fast cruise speeds that are beneficial for project mobilization and demobilization while maintaining relatively slow stall speeds which can prove ideal for collection of a high-density, consistent data posting. IPAS-TC software was used to compute Inertial SOL file to process the final LiDAR LAS files. The method works by integrating Inertial Navigation Solution by processing IMU data and the simultaneously collected GPS data from SPAN System (Position and Orientation System/Airborne Vehicle) along with observables of locally positioned GPS base station on the ground. It computes a carrier phase GPS solution and then blends it with inertial data. This project's data was processed in strip form, meaning each flight line was processed independently. Processing the lines individually provides the data analyst with the ability to QC the overlap between lines. Each strip was imported into a project using TerraScan (Terrasolid, Ltd.) By creating a project the various flight lines are combined while breaking the dataset as a whole into manageable pieces. This process also converts the dataset from Geographic Coordinate System (NAD 83, 2011) to NAD83, 2011 Puerto State Plane. The ellipsoid height values will be converted to PRVD02, Meters, orthometric values using Geoid 12A, provided by National Geodetic Survey (NGS). Breaklines are collected manually, based on the LiDAR surface model in TerraModeler version 013. The classification of points as either water or ground is determined based on a combination of factors in the data: point density, voids in data returns, and flatness of the surface, and intensity value. Auxiliary information, such as the imagery provided by USACE, as well as ESRI's Hydro layer is used as an additional aid in decision making. |
Process Date/Time | 2014-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Survey check points were collected in the following two areas: Rio de la Plata (West Area) and Puerto Nuevo Project (East Area). Spread across each area 15-20 survey check points for each of the following classes were collected. The five classes were: DESCRIPTION - FEATURE CODE a. Open/Low Grass - OLG b. Tall Grass/Crops - TGC c. Brush/Low Trees - BLT d. Forest - FOR e. Wetlands - WET Overall, 201 points were collected as described in the table below (This tables includes landscape class points, but does not include the additional points collected for vertical and horizontal control). The additional points and accuracy calculations are provided in the accuracy assessment portion of this report. The two landscape classes with dense tall grass vegetation (Brush/low trees and Tall Grass/Crops) tested at higher than the target accuracy. Based on the thick vegetation, the LIDAR points that got to the ground in these areas were minimal, and aggressive filtering and manual edits were required in order to remove the dense vegetation from the ground point classification. As a result, the ground points in these areas were sometimes tens to hundreds of meters apart. The distance of the ground points in these locations resulted in a triangulatedtest surface that may not represent the small terrain variations around the control survey points. Although a particular LiDAR point cannot be tested, accuracy statements can be made about the performance of the ABGPS, IMU and LiDAR sensors. The ABGPS data are quality controlled by solutions from base stations. On this project, these solutions all agreed to better than 5 cm horizontally. The IMU sensor combines the post-processed GPS data with the raw inertial data to produce a best estimate of trajectory. Automated quality control checks will not allow the IMU solution to be of a lower accuracy than the provided input from the GPS solution. The altitude of the ALS70-CM sensor (S/N 7169) on this project was 1250-meters AGL providing a spot size of 29 cm in diameter. Each return is located somewhere within the spot on the ground, meaning the location of the point is located within 14.5 cm of the center of the spot. |
Process Date/Time | 2014-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received the files in laz format from USACE . The files contained lidar elevation and intensity measurements. The data were in State Plane, 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. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 12a. 3. The LAS data were sorted by latitude and the headers were updated. |
Process Date/Time | 2014-10-20 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 | 49954 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:23+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 |
---|