ISO Table View
Alternate Views:
Get Data,
FAQ,
ISO Rubric,
CSW,
HTML,
Components, XML
Metadata Identifier: gov.noaa.csc.maps:2008_CityofBaltimore_m1199
MD_DataIdentification
| 1 |
|
2008 City of Baltimore Lidar |
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.
|
SV_Identification
| 1 |
|
2008 City of Baltimore Lidar |
|
|
| 3 |
|
None |
|
|
| 1 |
|
North American Datum 1983 |
|
|
| 1 |
|
|
|
|
|
resourceProvider |
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
| 1 |
NOAA CSC (originator) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
originator |
|
| 1 |
NOAA CSC (publisher) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
publisher |
|
| 1 |
NOAA CSC(distributor) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
distributor |
|
| 1 |
NOAA CSC (processor) |
|
DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic
and Atmospheric Administration, U.S. Department of Commerce
|
|
csc.info@noaa.gov |
processor |
|
| 1 |
EPSG Registry |
|
European Petroleum Survey Group |
|
|
publisher |
http://www.epsg-registry.org/ |
| 1 |
|
Josh Nimetz |
KCI/Sanborn Joint Venture Partnership, L.L.C. (hereafter referred to as KCI/Sanborn) |
LiDAR Production Manager |
jnimetz@sanborn.com |
pointOfContact |
|
| 1 |
|
Josh Nimetz |
Sanborn Map Company, Inc. |
LiDAR Production Manager |
jnimetz@sanborn.com |
processor |
|
| 1 |
|
|
KCI/Sanborn Joint Venture Partnership, L.L.C. (hereafter referred to as KCI/Sanborn) |
|
|
originator |
|
| 1 |
Mike Sutherland(author) |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
author |
|
| 1 |
Mike Sutherland |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
distributor |
|
| 1 |
Mike Sutherland (processor) |
Mike Sutherland |
DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department
of Commerce
|
|
mike.sutherland@noaa.gov |
processor |
|
| 1 |
|
http://www.epsg-registry.org/ |
European Petroleum Survey Group Geodetic Parameter Registry |
Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured
dataset of Coordinate Reference Systems and Coordinate Transformations.
|
search |
| 1 |
|
http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 |
NAD83 |
Link to Geographic Markup Language (GML) description of reference system. |
information |
| 1 |
|
Ellipsoid in Meters |
| 1 |
|
urn:ogc:def:crs:EPSG::4269 |
|
Bounding Box |
Temporal Extent |
| 1 |
|
|
-76.713701 |
-76.526548 |
39.372703 |
39.195787 |
|
|
| 1 |
|
-76.713701 |
-76.526548 |
39.372703 |
39.195787 |
| 1 |
Lidar Use Limitation |
These data depict the elevations at the time of the survey and are only
accurate for that time. 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. Any conclusions
drawn from analysis of this information are not the responsibility of NOAA
or any of its partners. These data are NOT to be used for navigational purposes.
|
| 1 |
Ellipsoid |
Ellipsoid in Meters |
|
| 1 |
NAD83 |
urn:ogc:def:crs:EPSG::4269 |
North American Datum 1983 |
| 1 |
|
2008-04-15T00:00:00 |
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.
|
| 1 |
|
2012-07-01T00:00:00 |
The NOAA Coastal Services Center (CSC) 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). CSC 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. 3. The data were converted
to LAZ format.
|
| 1 |
|
2013-01-22T00:00:00 |
The NOAA National Geophysical Data Center (NGDC) received lidar data
files via ftp transfer from the NOAA Coastal Services Center. The data are currently
being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/.
The data can be used to re-populate the system. The data are archived in LAS or LAZ
format. The LAS format is an industry standard for LiDAR
data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS);
LAZ is a loseless compressed version of LAS developed by
Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates
(either NAD83 or ITRF94). The data are referenced vertically to
the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most
up to date geoid model when transforming to orthometric heights.
|
|
