gov.noaa.nmfs.inport:49782
eng
UTF8
dataset
OCM Partners
resourceProvider
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
pointOfContact
2024-02-29T00:00:00
ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data
ISO 19115-2:2009(E)
2004 Maryland Department of Natural Resources LiDAR: Anne Arundel, Charles, Howard and St. Mary's Counties
md2004_m27_metadata
2005-01-20
publication
NOAA/NMFS/EDM
49782
https://www.fisheries.noaa.gov/inport/item/49782
WWW:LINK-1.0-http--link
Full Metadata Record
View the complete metadata record on InPort for more information about this dataset.
information
1. The Sanborn Map Company, Inc. (flight firm)
2. Computational Consulting Services, LLC (processing firm)
3. Spatial Systems Associates, Inc. (post-processing firm)
4. Dewberry and Davis (QA/QC firm)
Light Detection and Ranging (LIDAR) is a method of locating objects on the ground using aerial-borne equipment. It is similar
to RADAR or SONAR in that the two-way travel time of an energy beam reflected off an object is precisely measured, but this technology
uses laser light instead of radio or sound waves. This technology has proven very useful in remote sensing of the earth. It can be used
for determining elevations of both the earth's surface and items (natural and man-made) on the surface. Analysis of LIDAR data is used
in detailed modeling of the earth's surface for drainage and floodplain studies, determining how a new structure will affect views from
various locations, shoreline erosion studies, and other reasons. This data set contains only the bare earth mass points. Bare earth
points represent ground features. Features that are above ground, such as buildings, bridges, tree tops, etc, have been eliminated.
Mass points may appear to have "holes" with no elevation values in areas where the surface could not be determined, such as very dense
forests or urban areas.
Original contact information:
Contact Name: Ken Miller
Contact Org: Maryland Department of Natural Resources
Title: Chief. Watershed Information Services Division
Phone: 410-260-8751
Email: kenmiller@dnr.state.md.us
The LIDAR-derived data were collected by the Maryland Department of Natural Resources in support of shore erosion studies along
the shorelines of the Chesapeake Bay. It also supports the Federal Emergency Management Agency's specifications for mapping floodplains.
These efforts required detailed elevation data and models, such as those available from LIDAR sensing. The data have also been made
available to aid in other projects that require detailed surface, vegetation and/or structure elevations.
Spatial Systems Associates, Inc. was the prime contractor for this project. It partnered with Sanborn Map Company, Inc.,
Computational Consulting Services, Inc., NXL Construction Services, Inc and Dewberry LLC. Charles County participated with DNR and its vendor.
completed
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
pointOfContact
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
custodian
notPlanned
Bald earth
Bare earth
Bathymetry/Topography
DEM
DNR
Digital Elevation Model
Elevation and derived products
Elevation model
First return
Gridded DEM
LIDAR
Last return
Surface model
Terrain model
theme
DNR General
Lidar - partner (no harvest)
project
InPort
otherRestrictions
Cite As: OCM Partners, [Date of Access]: 2004 Maryland Department of Natural Resources LiDAR: Anne Arundel, Charles, Howard and St. Mary's Counties [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49782.
NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose.
otherRestrictions
Access Constraints: None
otherRestrictions
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. The Department of Natural Resources makes no warranty, expressed or implied, as to the use or appropriateness of Spatial
Data, and there are no warranties of merchantability or fitness for a particular purpose or use. The information contained in Spatial Data
is from publicly available sources, but no representation is made as to the accuracy or completeness of Spatial Data. The Department of
Natural Resources shall not be subject to liability for human error, error due to software conversion, defect, or failure of machines,
or any material used in the connection with the machines, including tapes, disks, CD-ROMs or DVD-ROMs and energy. The Department of Natural
Resources shall not be liable for any lost profits, consequential damages, or claims against the Department of Natural Resources by third
parties. The liability of the Department of Natural Resources for damage regardless of the form of the action shall not exceed any
distribution fees that may have been paid in obtaining Spatial Data.
otherRestrictions
Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the OCM or its partners.
unclassified
NOAA Data Management Plan (DMP)
NOAA/NMFS/EDM
49782
https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49782.pdf
WWW:LINK-1.0-http--link
NOAA Data Management Plan (DMP)
NOAA Data Management Plan for this record on InPort.
information
crossReference
vector
eng; US
elevation
A variety of specialized hardware and software platforms were used to collect, process and quality assess
these data. Typically, Intel machines running Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4.
-76.472538
-75.297853
37.881527
39.124828
| Currentness: Ground Condition
2004-04-01
2004-05-01
These data are part of a suite of spatial data products generated using the LIDAR technology. First and Last
returns are generated. From these data, Bare-Earth Mass Points that represent the earths surface are produced. A gridded Digital
Elevation Model (DEM) is produced from the Bare Earth Mass Points. Imagery is also created that represents the intensity of the LIDAR
return; it is a 1-meter resolution product that resembles a panchromatic Digital Orthophoto Quad (DOQ).
The Anne Arundel/Howard Counties and Charles/StMarys Counties, Maryland QA Reports may be viewed at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/27/supplemental/index.html
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
distributor
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=27
WWW:LINK-1.0-http--link
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
download
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/27/index.html
WWW:LINK-1.0-http--link
Bulk Download
Simple download of data files.
download
dataset
Accuracy
There are four (4) attributes in the Bare Earth Mass Points files, representing the horizontal coordinates
(easting and northing) and vertical position observed and vertical assigned (see process description). Random inspections were made to
assure that each line in the file contained 4 values.
Horizontal Positional Accuracy
The horizontal coordinate values were designed to meet NSSDA accuracy for data at 1:2400 scale.
Vertical Positional Accuracy
The RMSE value of 14.3 cm at the 95% confidence level was determined by an independent accuracy
assessment conducted by Dewberry LLC according to the contract specifications. These specifications followed FEMA Appendix A guidelines
regarding assessing vertical accuracy. For data accurate to within 18.5 cm RMSE, the guidelines recommended a minimum of 20 independent
check points be located in each of 5 different land cover categories: Grass/Ground, High Grass/Crops, Brush/Low Trees, Forest, and
Urban/Pavement. A total of 125 points were used for the assessments. These points were surveyed by a licensed land surveyor and
provided a positional location and elevation with an accuracy that exceeded the predicted accuracy of the LIDAR data. The entire
accuracy reports can be found at http://dnrweb.dnr.state.md.us/gis/data/lidar.
; Quantitative Value: 0.143 meters, Test that produced the value:
The RMSE value is 14.3 cm. See the Vertical Positional Accuracy Report section for more
information.
Completeness Measure
Cloud Cover: 0
Completeness Report
Spatial Systems Associates performed various inspections of the data to ensure: that each file contained the points
located within that tile; that tiles were completely filled; that the point density per tile was within expected ranges, and that the
tiles were correctly named.
Conceptual Consistency
Computational Consulting Services, the LIDAR processing vendor used proprietary algorithms to remove features
and artifacts in the First and Last Return data that did not reflect true ground elevation. Subsequent quality assurance testing by
Dewberry determined that the data met FEMA and MD DNR specifications for both vertical accuracy and other consistencies with accepted
standards. The QA report can be accessed at http://dnrweb.dnr.state.md.us/gis/data/lidar.
LIDAR Data Acquisition. The Sanborn Map Company, Inc. flew the project area with the LIDAR sensor. Where overlaps
between the two series of data occurred, the newer data was used. No attempt at blending the two datasets was made to maintain the
highest data integrity. In an effort to permit correlation of the point values with tidal gauge stations, the Sanborn Map Company,
Inc. was required to fly tidal shoreline areas during the low tide cycle (slack water - low tide - slack water) as predicted by local
tide stations. The LIDAR sensor collected raw data that was referenced in UTM. The flight plan on this project included the following
specifications to meet the project requirements: *Single pass density - 1.696 square meters per sample; *Average area sampling
density -1.272 square meters per sample; *Swath width - 996.76 meters; *Flight altitude -1371 meters (4500 ft); *Flight line
spacing - 498.38 meters w/50% overlap; *Scan frequency - 21 Hz; *Firing rate - 25 kHz; *Scan angle - 20 degrees; *Ground speed - 140
knots. When complete, the raw data was delivered to Spatial Systems.
LIDAR Data Processing. Computational Consulting Systems. The First and Last Return data was delivered to CCS in
large blocks of data. CCS processed the data using both the First and Last Returns, removed artifacts using automated and manual
techniques, and reprojected the data into the client-specified X, Y, Z text files using the 1200 meter x 1800 meter tiles, NAD 83
meters, NAVD 88 meters. CCS also generated the Intensity Imagery using the client-specified USGS 3.75' tiling scheme. The data products
were delivered to SSA for quality assurance testing, formatting and final delivery.
LIDAR Data Post Processing. Spatial Systems Associates. SSA digitized the shoreline from the Intensity Imagery
for the purposes of delineating a shoreline. Any LIDAR points that fell seaward of this shoreline were assigned the value of zero (0).
In addition to the shoreline, SSA delineated upland ponds using the same technique and assigned all LIDAR points that fell within the
water area the value of the lowest observed point close to the shore. The observed elevation values were not lost - a fourth field
in the data file was added for the assigned value. SSA also performed a variety of QA procedures to determine if the point density
was within expected ranges; that each tile was completely filled; that all tiles were accounted for, and that the tiles were named
in accordance with client specifications.
LIDAR Data Check Point Surveys. NXL Construction Services. NXL was contracted to acquire the check-points in the
5 different land cover classes. SSA provided NXL with maps of each area where a check-point was to be located. The points were scattered
throughout the project area. NXL was permitted the latitude to select the exact location based on field conditions, provided the points
were generally within a 1 mile radius of the chosen location and that the land cover class was the same as the one specified. The land
cover classes were: Grass/Ground, High Grass/Crops, Brush/Low Trees, Forest, and Urban/Pavement.
LIDAR Data Quality Assurance. Dewberry LLC was provided with the check-point and LIDAR Bare Earth Mass Points
data to perform their independent quality assurance work. They performed detailed analyses to determine if the vertical accuracy
was within specifications and examined the data for flight, data collection and processing inconsistencies. Neither the flight vendor
(Airborne 1) nor the processing vendor (CCS) was given access to the check-point data. The entire accuracy report can be found at
http://dnrweb.dnr.state.md.us/gis/data/lidar.
The NOAA Office for Coastal Management (OCM) received LAS files containing the point cloud elevation data from Earth
Data, Inc. OCM performed the following processing on the data to make it available within the Lidar Data Retrieval Tool (LDART):
1. Variable length header records were added to the LAS files to identify projection, datum and sort order.
2. The LFIT (LDART formatted binary) files were sorted by latitude.
3. LFIT files were converted to xyz format ASCII files.
2005-01-01T00:00:00