49785
2008 City of Baltimore Lidar
md2008_baltimorecity_m1199_metadata
Data Set
Published / External
49401
Lidar - partner (no harvest)
Project
Completed
2012-07
In the spring of 2008, the City of Baltimore expressed an interest to upgrade the City GIS Database with mapping quality airborne LiDAR data.
The City of Baltimore currently had in place a contract for mapping GIS/services with the KCI/Sanborn Joint Venture Partnership, L.L.C. under
Project 1051. The City of Baltimore issued Change Order #1 on on Project 1051 for the LiDAR acquisition and processing. KCI/Sanborn acquired
the LiDAR data over the City of Baltimore (approximately 90 square miles) during one long mission on 15 April 2008.
A Leica Airborne Airborne Laser Scanner Model ALS 50 was used in a Sanborn Aero Commander 500B (Registration N6172X) to acquire the data. The
airborne mission was flown 15 April 2008. The LiDAR system acquired calibration data the same day by conducting flight passes over a known
ground surface before and the LiDAR mission. During final data processing, the calibration parameters were used in the final post-processing
software.
The acquired LiDAR data were processed to obtain the following deliverables:
-DEMs of first and last returns and bare earth (all point data)
-LAS format data in a tile grid provided by the City/KCI
-Gridded DEM in ESRI format (Arc Binary Grid -Arc/INFO Lattice ) produced from Bare Earth Mass Points in 1-meter resolution (Grid size)
-Associated FGDC compliant metadata in XML format
The project specifications called for the LiDAR survey to comply with industry standard FEMA guidelines for accuracy. The FEMA requirement for
this type of mapping calls for vertical errors not to exceed 0.185 meter (0.61 feet) RMSE when compared with ground check points over open
flat terrain and 0.370 meter (1.22 feet) for other types of terrain. This accuracy requirement was comfortably met with comparing LiDAR
derived elevations against 50 ground control check points provided by KCI Technologies. These control points were photo control points used
as part of the photogrammetric mapping project and independent LiDAR checkpoints surveyed by KCI and Mercado after the data was delivered. The
RMSE error observed was 0.058 meter (0.189 feet) over all 50 check points.
Original contact information:
Contact Name: Josh Nimetz
Contact Org: KCI/Sanborn Joint Venture Partnership, L.L.C. (hereafter referred to as KCI/Sanborn)
Title: LiDAR Production Manager
Phone: 719-264-5513
Email: jnimetz@sanborn.com
This LIDAR operation was designed to provide a high density set of masspoints within the defined areas. The data sets are suitable for the
development of contours for use in hydraulic/hydrologic model development, and for assessing environmental impacts. Typical uses for the
dataset include FEMA Flood Map Modernization, DFIRM map updates, watershed delineation and other hydro studies per FEMA specifications, as well
as general use by the City of Baltimore.
10429
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1199/supplemental/2008_City_of_Baltimore_Lidar.kmz
A detailed description of this dataset can be found in the Final Project Report, found here:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1199/supplemental/2008_City_of_Baltimore_Lidar_QA_Report.pdf
Theme
ISO 19115 Topic Category
elevation
Theme
Drainage Area
Temporal
2008
Temporal
April
Office for Coastal Management
Charleston
SC
Data Set
As Needed
Any conclusions drawn from the analysis of this information are not the responsibility of the Office for Coastal Management
or its partners.
Data Steward
2012-07
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
2012-07
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
2012-07
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
2012-07
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
-76.713701
-76.526548
39.372703
39.195787
Discrete
2008-04-15
Yes
Unclassified
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer;
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. These data depict the heights at the time of the survey and are only accurate for that time.
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1199
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/1199/index.html
Bulk Download
Simple download of data files.
https://coast.noaa.gov
Online Resource
https://coast.noaa.gov/dataviewer
Online Resource
2016-05-23
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 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.0.1770
The project specifications called for the LiDAR survey to comply with industry standard FEMA guidelines for
horizontal accuracy.
; Quantitative Value: 1.0 meters, Test that produced the value: Assumed to meet FEMA specifications for horizontal accuracy.
The FEMA requirements call for vertical errors not to exceed 0.185 meter (0.61 feet) RMSE when compared
with ground check points over open flat terrain.
; Quantitative Value: 0.058 meters, Test that produced the value:
The LiDAR derived elevations for this project compared against 50 ground control check points
showed the RMSE error observed was 0.058 meters.
None provided
All LAS formatted LiDAR data are validated to ensure that data on delivery media is in correct physical format
and is readable and correctly georeferenced and projected. Note that LiDAR intensity is not calibrated or normalized.
1
Using a Leica Geosystems ALS50 Light Detection And Ranging (LiDAR) system, 29 flight lines of an average density of 1.0 meter ground sample
distance, data were collected over areas in Baltimore City, MD (approximately 90 square miles). Multiple returns were recorded for each laser
pulse along with an intensity value for each return. The data acquisition occurred in 1 mission on April 15, 2008. During the LIDAR campaign,
the Sanborn field crew conducted a GPS field survey to establish final coordinates of the ground base stations for final processing of
the base-remote GPS solutions.
Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a Smoothed Best Estimate of Trajectory
(SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The overlap between flight
lines was removed to provide a homogeneous coverage, and the coverage was classified to extract a bare earth digital elevation model (DEM). Airborne
GPS is differentially processed using the GrafNAV V7.50 software by Waypoint Consulting of Calgary, Alberta, Canada. The PDOP and distance
separation is as follows: The classification and quality control (QC) of LiDAR data is carried out using TerraScan software by Terrasolid Limited
of Helinski, Finland.
IMU data provides information concerning roll, pitch and yaw of collection platform during collection event. IMU information allows the pulse
vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly positioned on the elevation model
surface. The IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. The reflective surface
is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia.
2008-04-15T00:00:00
2
The NOAA Office for Coastal Management (OCM) received data in LAS v1.1 format. The files contained LiDAR elevation and intensity measurements.
The data were received in state plane coordinates (Maryland; NAD83) and vertically referenced to NAVD88 using the Geoid03 model. The vertical
units of data were feet. The data were classified according to ASPRS LAS classification scheme (0 = never classified, 1 = unclassified, 2 = ground
3 = low vegetation, 7 = noise, 12 = overlap). 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 (NAD83).
2. The data were converted from orthometric heights to ellipsoidal heights (GRS80) using Geoid 03.
3. The vertical units of the data were changed from feet to meters.
2. The LAS data were sorted by latitude and the headers were updated.
2012-07-01T00:00:00
gov.noaa.nmfs.inport:49785
Anne Ball
2017-11-15T15:22:17
SysAdmin InPortAdmin
2022-08-09T17:11:36
2022-03-16
OCM Partners
OCMP
1002
Public
No
2022-03-16
1 Year
2023-03-16