50051
2004 USACE Puerto Rico Lidar
usace2004_puertorico_m560_metadata
Data Set
Published / External
49401
Lidar - partner (no harvest)
Project
Completed
2007
This record describes Light Detection and Ranging (Lidar) data acquired for the island of Puerto Rico. The data were acquired for
USACE, St. Louis District by 3001, Inc., between January 10 and February 8, 2004. The mission was flown at a density sufficient to support
a maximum final post spacing of 6 feet for unobscured areas. The Puerto Rico LiDAR Survey was collected under the guidance of a
Professional Mapper/Surveyor.
Original contact information:
Contact Org: 3001, Inc.
Title: LiDAR Department
Phone: (985) 661- 3001
Email: lidar@3001inc.com
The Puerto Rico LiDAR dataset will support the creation of Federal Emergency Management Agency (FEMA) Flood Insurance Rate Maps (FIRM) and an
integrated ground and surface water model.
10695
The Puerto Rico data provided by the NOAA Office for Coastal Management via the Digital Coast Data Access Viewer has been reviewed by Center staff as well
as other outside parties. The data, as processed and provided by the OCM, have some noted quality issues and some potential accuracy problems. The
OCM has not done any further accuracy assessment, but we have received some feedback from other organizations about accuracy and datum issues. Please
note that the geoid grids for Puerto Rico, themselves, have a varying level of accuracy. The data is being provided as a 'best available' data set,
but should be used with a level of caution.
The Lidar QA/QC Quantitative and Qualitative Assessment Report for this data set may be viewed at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/560/supplemental/lidarqaqcreport_puertorico_final.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/560/supplemental/2004_USACE_Puerto_Rico_Lidar.kmz
Theme
ISO 19115 Topic Category
elevation
Office for Coastal Management
Charleston
SC
Data Set
None Planned
Any conclusions drawn from the analysis of this information are not the responsibility of the Office for Coastal Management
or its partners.
50249
LAS
LAS
Published / External
Completed
Lidar point cloud LAS 1.0 format | Description Source: "ASPRS LAS 1.0 Format Standard, May, 9, 2003"
Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.
Data Steward
2007
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Distributor
2007
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Metadata Contact
2007
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Point of Contact
2007
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Ground Condition
-67.271346
-65.204146
18.515932
17.913132
Range
2004-01-10
2004-02-08
Yes
Unclassified
None
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. Acknowledgement of
USACE, St. Louis District would be appreciated in products derived from these data.
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=560
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/560/index.html
Bulk Download
Simple download of data files.
https://coast.noaa.gov
Online Resource
https://coast.noaa.gov/dataviewer
Online Resource
2017-01-05
Date that the source FGDC record was last modified.
2017-11-14
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.
2018-02-08
Partial upload of Positional Accuracy fields only.
2018-03-13
Partial upload to move data access links to Distribution Info.
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722
The accuracy assessment was performed using a standard method to compute the root mean square error (RMSE) based on a comparison of ground
control points (GCP) and filtered LiDAR data points. Filtered LiDAR data has had vegetation and cultural features removed and by analysis
represents bare-earth elevations. Testing was performed prior to gridding of the filtered LiDAR data points and construction of the
Intergraph .dtm file format. The RMSE figure was used to compute the vertical National Standard for Spatial Data Accuracy (NSSDA). Ground control
was established by 3001, Inc. A spatial proximity analysis was used to select edited LiDAR data points contiguous to the relevant GCPs. A search
radius decision rule is applied with consideration of terrain complexity, cumulative error and adequate sample size. Cumulative error results from
the errors inherent in the various sources of horizontal measurement. These sources include the airborne GPS, GCPs and the uncertainty of the
accuracy of the LiDAR data points. This accuracy is achieved prior to the sub-sampling that occurs through integration with the inertial
measurement unit (IMU) positions that are recorded. It is unclear at this time whether the initial accuracy is maintained. The horizontal accuracy
of the GCPs is estimated to be in the range of approximately 1 to 1.6 feet. Finally, sample size was considered. The specification for the National
Standard for Spatial Data Accuracy is a minimum of 20 points to conduct a statistically significant accuracy evaluation (Minnesota Planning, 1999,
Positional Accuracy Handbook, Minnesota Planning Land Management Information Center, St. Paul, Minnesota., p.3). Most statistical texts indicate
that a minimum of 30 sample points provide a reasonable Approximation of a normal distribution. The intent of the NSSDA is to reflect the geographic
area of interest and the distribution of error in the data set (Federal Geographic Data Committee, 1998, Geospatial National Standard for Spatial
Data Accuracy, Federal Geographic Data Committee Secretariat, Reston, Virginia, p.3-4). Additional steps were taken to ensure the vertical accuracy
of the LiDAR data including: Step 1: Precision Bore sighting (Check Edge-matching) Step 2: Compare the LiDAR data to the Field Survey
(Field survey is to FEMA specifications and more stringent internal specifications) Step 3: Automated Filtering Step 4: Manual Editing (Quality
Control) Step 5: 3-D digitizing and Photogrammetric Compilation of hydrographic breaklines.
; Quantitative Value: 11.90 meters, Test that produced the value:
Based upon the result of vertical accuracy testing conducted by 3001, Inc., vertical accuracy at the 95% confidence level (Accuracyz) is computed
by the formula RMSEz x 1.9600. The overall vertical accuracy of the Puerto Rico Lidar dataset is 11.90 cm, based upon an RMSEz of 6.07 cm.
These values were derived from a comparison of Lidar data points that fell within a 1 m horizontal radius of 20 established ground control points.
They represent the overall vertical accuracy in all surface types surveyed, which include ashphalt, dirt and mowed grass.
At the end of each flight, the Lidar data was processed to check for complete coverage and to verify that there were no voids in data coverage.
Unknown
Puerto Rico LiDAR Survey
2007-01-01
Range
2004-01-10
2004-02-08
The Puerto Rico LiDAR Survey was acquired for USACE, St. Louis District and processed by 3001, Inc. | Source Geospatial Form: vector digital data | Type of Source Media: online
1
The ABGPS, inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the
sensor and the IMU monitors the orientation. During the aerial survey laser pulses reflected from features on the ground surface are detected by
the receiver optics and collected by the data logger. GPS locations are based on data collection receivers on the aircraft and base stations on the
ground. The ground base stations are placed no more than 35 km radius from the flight survey area.
2007-01-01T00:00:00
2
The ABGPS, IMU, and raw scans are integrated using proprietary software developed by the Leica Geosystems and delivered with the Leica ALS50
System. The resultant file is in a LAS binary file format. The LAS file version 1.0 format can easily transferred from one file format to another.
It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are
produced in the State Plane Puerto Rico FIPS 5200 coordinate system, with units in feet and referenced to the NAD83 horizontal datum and NAVD88
vertical datum.
2007-01-01T00:00:00
3
The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters
is applied as appropriate for the production of bare-earth digital terrain models (DTMs). Interactive editing methods are applied to those areas
where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant
filters. These same feature extraction filters are used to produce elevation height surfaces.
2007-01-01T00:00:00
4
Filtered and edited data are subjected to rigorous QA/QC according to the 3001 Inc. Quality Control Plan and procedures. Very briefly, a series
of quantitative and visual procedures are employed to validate the accuracy and consistency of the filtered and edited data. Ground control is
established by 3001, Inc. and GPS-derived ground control points (GCPs) points in various areas of dominant and prescribed land cover. These points
are coded according to landcover, surface material and ground control suitability. A suitable number of points are selected for calculation of a
statistically significant accuracy assessment as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity
analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied
with consideration of terrain complexity, cumulative error and adequate sample size. Accuracy validation and evaluation is accomplished using
proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial
Data Accuracy (NSSDA) according the Federal Geographic Data Committee (FGDC) specifications.
2007-01-01T00:00:00
5
The LiDAR mass points were delivered in ASPRS LAS 1.0 format. The header file for each dataset is complete as defined by the LAS 1.0 specification.
The LAS files do not include overlap. The delivered tiles are suitable for seamless topographic data mosaics that include no "no data" areas. The
names of the tiles are left padded with zeros as required to achieve a five character length and all files utilize the LAS file extension.
2007-01-01T00:00:00
6
The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained Lidar elevation and intensity measurements.
The data were in projected in Puerto Rico State Plane Coordinates (FIPS 5200/NAD83), and referenced to the orthometric datum of NAVD88 utilizing
Geoid 99. Both planar and vertical units were measured in feet. OCM performed the following processing to the data to make it available
within the Digital Coast:
1. The data were converted from State Plane Coordinates (NAD83; ft) to UTM coordinates (Zone 20/NAD83; m).
2. The vertical units of the data were converted from NAVD88 (ft) to NAVD88 (m).
3. The data were re-tiled using MARS software.
4. The data were reclassified such that all classifications were set to Class 0.
5. The data were filtered to Bare Earth (Class 2) and Unclassified (Class 1) using an automated process in LASEdit.
6. The data were converted from UTM coordinates (Zone 20/NAD83) to geographic coordinates (NAD83) and ellipsoidal elevations (GRS80) using Geoid 99.
7. The LAS data were sorted by latitude and the headers were updated.
2010-12-07T00:00:00
50249
Entity
LAS
gov.noaa.nmfs.inport:50051
Anne Ball
2017-11-15T15:23:59
SysAdmin InPortAdmin
2022-08-09T17:11:37
2022-03-16
OCM Partners
OCMP
1002
Public
No
2022-03-16
1 Year
2023-03-16