2020 Maryland Lidar: Anne Arundel County, MD
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:75711 | Updated: May 5, 2025 | Published / External
- View As
- View in Hierarchy
Summary
Short Citation
OCM Partners, 2025: 2020 Maryland Lidar: Anne Arundel County, MD, https://www.fisheries.noaa.gov/inport/item/75711.
Full Citation Examples
Original Product: These are the lidar point cloud data as part of the required deliverables for the lidar project.
Original Dataset Geographic Extent: Anne Arundel county, Maryland, covering approximately 459 square miles.
Original Dataset Description: The lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83 (HARN), State Plane, Feet and vertical datum of NAVD88 (GEOID12B), Feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 619 individual 6000 ft x 4000 ft tiles, as tiled intensity rasters, and as tiled bare-earth DEMs; all tiled to the same 6000 ft x 4000 ft schema.
Original Dataset Ground Conditions: Lidar was collected in late 2020, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Sanborn Map Company, Inc., utilized a total of 10 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 50 independent accuracy check points, 30 in Bare Earth and Urban landcovers (30 NVA points), 20 in Tall Grass and Brushland/Low Trees categories (20 VVA points), were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data.
There was no point cloud metadata record available from iMAP, so this record, which supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV), was created from the Digital Elevation Model (DEM) metadata that was provided on the Maryland iMAP site. The 2020 Anne Arundel County, Maryland lidar point cloud data were downloaded from the Maryland iMAP site and the data were processed to be made available for bulk and custom download from the DAV.
PurposeTo acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 1 foot cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.
Distribution Information
-
Format: Not Applicable
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.
-
LAS/LAZ - LASer
Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum.
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.
Controlled Theme Keywords
COASTAL ELEVATION, elevation, TERRAIN ELEVATION
URLs
-
The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.
-
Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) data that were created from this lidar data set.
-
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.
-
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer.
Child Items
No Child Items for this record.
Contact Information
Point of Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Extents
-76.8406552171° W,
-76.3931776623° E,
39.2381837° N,
38.7117806526° S
2020-12-08 - 2020-12-11
Item Identification
Title: | 2020 Maryland Lidar: Anne Arundel County, MD |
---|---|
Status: | Completed |
Creation Date: | 2020 |
Publication Date: | 2021-06-24 |
Abstract: |
Original Product: These are the lidar point cloud data as part of the required deliverables for the lidar project. Original Dataset Geographic Extent: Anne Arundel county, Maryland, covering approximately 459 square miles. Original Dataset Description: The lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83 (HARN), State Plane, Feet and vertical datum of NAVD88 (GEOID12B), Feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 619 individual 6000 ft x 4000 ft tiles, as tiled intensity rasters, and as tiled bare-earth DEMs; all tiled to the same 6000 ft x 4000 ft schema. Original Dataset Ground Conditions: Lidar was collected in late 2020, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Sanborn Map Company, Inc., utilized a total of 10 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 50 independent accuracy check points, 30 in Bare Earth and Urban landcovers (30 NVA points), 20 in Tall Grass and Brushland/Low Trees categories (20 VVA points), were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data. There was no point cloud metadata record available from iMAP, so this record, which supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV), was created from the Digital Elevation Model (DEM) metadata that was provided on the Maryland iMAP site. The 2020 Anne Arundel County, Maryland lidar point cloud data were downloaded from the Maryland iMAP site and the data were processed to be made available for bulk and custom download from the DAV. |
Purpose: |
To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 1 foot cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION
|
ISO 19115 Topic Category |
elevation
|
Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA
|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MARYLAND
|
Global Change Master Directory (GCMD) Location Keywords |
VERTICAL LOCATION > LAND SURFACE
|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords |
LIDAR > Light Detection and Ranging
|
Platform Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Platform Keywords |
Airplane > Airplane
|
Physical Location
Organization: | Office for Coastal Management |
---|---|
City: | Charleston |
State/Province: | SC |
Data Set Information
Data Set Scope Code: | Data Set |
---|---|
Data Set Type: | Elevation |
Maintenance Frequency: | None Planned |
Data Presentation Form: | Model (digital) |
Distribution Liability: |
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. |
Data Set Credit: | Sanborn Map Company, Inc., MD iMAP |
Support Roles
Data Steward
Date Effective From: | 2025 |
---|---|
Date Effective To: | |
Contact (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 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2025 |
---|---|
Date Effective To: | |
Contact (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 |
URL: | https://coast.noaa.gov |
Metadata Contact
Date Effective From: | 2025 |
---|---|
Date Effective To: | |
Contact (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 |
URL: | https://coast.noaa.gov |
Point of Contact
Date Effective From: | 2025 |
---|---|
Date Effective To: | |
Contact (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 |
URL: | https://coast.noaa.gov |
Extents
Currentness Reference: | Ground Condition |
---|
Extent Group 1
Extent Group 1 / Geographic Area 1
W° Bound: | -76.8406552171 | |
---|---|---|
E° Bound: | -76.3931776623 | |
N° Bound: | 39.2381837 | |
S° Bound: | 38.7117806526 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2020-12-08 |
End: | 2020-12-11 |
Spatial Information
Spatial Representation
Representations Used
Grid: | No |
---|---|
Vector: | Yes |
Text / Table: | No |
TIN: | No |
Stereo Model: | No |
Video: | No |
Reference Systems
Reference System 1
Coordinate Reference System |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Access Information
Security Class: | Unclassified |
---|---|
Data Access Procedure: |
Data is available online for bulk and custom downloads. |
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. |
Distribution Information
Distribution 1
Start Date: | 2025 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10311/details/10311 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2025 - Present) |
File Name: | Customized Download |
Description: |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. |
Distribution Format: | Not Applicable |
Compression: | Zip |
Distribution 2
Start Date: | 2025 |
---|---|
End Date: | Present |
Download URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10311/index.html |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2025 - Present) |
File Name: | Bulk Download |
Description: |
Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. |
Distribution Format: | LAS/LAZ - LASer |
Compression: | LAZ |
URLs
URL 1
URL: | https://coast.noaa.gov/dataviewer/ |
---|---|
Name: | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
URL Type: |
Online Resource
|
File Resource Format: | HTML |
Description: |
The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. |
URL 2
URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10308/details/10308 |
---|---|
Name: | Custom DEM Download |
URL Type: |
Online Resource
|
File Resource Format: | Zip |
Description: |
Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) data that were created from this lidar data set. |
URL 3
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10311/supplemental/md2020_arundel_m10311.kmz |
---|---|
Name: | Browse Graphic |
URL Type: |
Browse Graphic
|
File Resource Format: | kmz |
Description: |
This graphic shows the coverage for the 2020 lidar acquisition for Anne Arundel County, Maryland. |
URL 4
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/10311/ept.json |
---|---|
Name: | Entwine Point Tile (EPT) |
URL Type: |
Online Resource
|
File Resource Format: | json |
Description: |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL 5
URL: | https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/10311/ept.json |
---|---|
Name: | Potree 3D View |
URL Type: |
Online Resource
|
Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
Data Quality
Vertical Positional Accuracy: |
This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. |
---|---|
Completeness Report: |
Datasets contain complete coverage of tiles. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. There are no void areas or missing data. The raw point cloud is of good quality and data passes Non-Vegetated Vertical Accuracy specifications. |
Conceptual Consistency: |
Data covers the pilot area specified for this project. |
Data Management
Have Resources for Management of these Data Been Identified?: | Yes |
---|---|
Approximate Percentage of Budget for these Data Devoted to Data Management: | Unknown |
Do these Data Comply with the Data Access Directive?: | Yes |
Actual or Planned Long-Term Data Archive Location: | NCEI-NC |
How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to cloud storage. |
Lineage
Lineage Statement: |
Data were collected for the state of Maryland by Sanborn. The data were downloaded by the NOAA Office for Coastal Management (OCM) from the MD iMAP site and processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from S3 AWS. |
---|
Sources
MD iMAP Files
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | MD iMAP |
Citation URL: | https://doitdataservices.maryland.gov/s/N9xGBYPKq4QSZNq?path=%2FAnne%20Arundel%20County%2F2020%2FLAZ |
Citation URL Name: | MD iMAP - Anne Arundel County Lidar Point Cloud Data |
Process Steps
Process Step 1
Description: |
Because there was no metadata record for the lidar point data, the following information was taken from the Abstract of the Digital Elevation Model (DEM) metadata that was downloaded from the Maryland iMAP site. The lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83 (HARN), State Plane, Feet and vertical datum of NAVD88 (GEOID12B), Feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 619 individual 6000 ft x 4000 ft tiles, as tiled intensity rasters, and as tiled bare-earth DEMs; all tiled to the same 6000 ft x 4000 ft schema. Lidar was collected in late 2020, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Sanborn Map Company, Inc., utilized a total of 10 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 50 independent accuracy check points, 30 in Bare Earth and Urban landcovers (30 NVA points), 20 in Tall Grass and Brushland/Low Trees categories (20 VVA points), were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data. |
---|---|
Process Date/Time: | 2021-06-24 00:00:00 |
Process Step 2
Description: |
The NOAA Office for Coastal Management (OCM) downloaded LAZ data files from this MD iMAP site: https://doitdataservices.maryland.gov/s/N9xGBYPKq4QSZNq?path=%2FAnne%20Arundel%20County%2F2020%2FLAZ The data were in MD State Plane (NAD83 HARN), US feet coordinates and NAVD88 (Geoid12B) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 3- Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 6 - Buildings, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise, 20 - Ignored Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 3, 4, 5, 6, 7, 9, 17, 18, 20. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to NAD83 (2011) ellipsoid elevations using the Geoid12B model b. Convert from Maryland State Plane (NAD83 2011), meters coordinates to geographic coordinates c. Convert from elevation values in feet to elevation values in meters d. Assign the geokeys, sort the data by gps time and zip the data to database and to AWS S3 |
---|---|
Process Date/Time: | 2025-03-25 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Data Set (DS) | Cross Reference |
2020 Maryland Lidar DEM: Anne Arundel County, MD |
Catalog Details
Catalog Item ID: | 75711 |
---|---|
GUID: | gov.noaa.nmfs.inport:75711 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2025-05-05 15:44+0000 |
Metadata Record Last Modified By: | Rebecca Mataosky |
Metadata Record Last Modified: | 2025-05-05 17:37+0000 |
Metadata Record Published: | 2025-05-05 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2025-03-26 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2026-03-26 |