Montgomery and Prince George's counties project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2. 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 1,413 individual 4000 ft x 6000 ft tiles, as tiled Intensity Rasters, and as tiled bare-earth DEM; all tiled to the same 4000 ft x 6000 ft schema. Ground Conditions: Lidar was collected in early to mid 2018, while no snow was on the ground and rivers were at or below normal levels. Sensor errors in mulitple locations were identified in processing, additonal acquisition on 7/20/2018 was completed to remedy the errors. 2016 lidar data was used with approval in a single area of restricted airspace. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Sanborn Map Company, Inc. established a total of 23 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 79 independent accuracy check points in Open Terrain and Urban landcovers were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/PrinceGeorges/MD_princegeorges_dem_ft/ImageServer

This data was developed in response to citizens’ road maintenance requests from across the state as to whom to contact as the official maintenance authority - be it MDOT State Highway Administration, MDOT Transportation Authority, a county, or a municipality.MDOT SHA Website

This layer is a high-resolution tree canopy change-detection layer for Prince Georges County, Maryland. It contains three tree-canopy classes for the period 2009-2014: (1) No Change; (2) Gain; and (3) Loss. It was created by first mapping tree canopy in 2014 using LiDAR and multispectral data and then comparing the new map directly to an existing tree-canopy map for the year 2009. Tree canopy that existed during both time periods was assigned to the No Change category while trees removed by development, storms, or disease were assigned to the Loss class. Trees planted during the interval were assigned to the Gain category, as were the edges of existing trees that expanded noticeably. Direct comparison was possible because both the 2009 and 2014 maps were created using object-based image analysis (OBIA) and included similar source datasets (LiDAR-derived surface models, multispectral imagery, and thematic GIS inputs). No accuracy assessment was conducted, but the dataset was subjected to comprehensive manual review and correction.

Geographic Extent: SANDY_Restoration_VA_MD_DC_QL2 Area of Interest covers approximately 2,002 square miles. Lot #5 contains the full project area Dataset Description: The SANDY_Restoration_VA_MD_DC_QL2 project called for the Planning, Acquisition, processing and derivative products of LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1. The data was developed based on a horizontal projection/datum of UTM Zone 18 North, NAD83, meters and vertical datum of NAVD1988 (GEOID12A), meters. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.2 Files formatted to 2283 individual 1500m x 1500m tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 1500m x 1500m schema, and Breaklines in ESRI Shapefile format. The data was then converted to a horizontal projection/datum of NAD83 Maryland State Plane Coordinate System, Feet. LiDAR was delivered in Classified LAS 1.2 Files formatted to 1927 individual 4000' x 6000' tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 4000' x 6000' schema, and Breaklines in ESRI Shapefile format. Ground Conditions: LiDAR was collected in Winter 2014, 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, Quantum Spatial established a total of 59 QA control points and 95 Land Cover control points that were used to calibrate the LiDAR to known ground locations established throughout the SANDY_Restoration_VA_MD_DC_QL2 project area.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://lidar.geodata.md.gov/imap/rest/services/PrinceGeorges/MD_princegeorges_2015_dem_ft/ImageServer

This layer contains bus routes and variations for Prince George's County's Public Transit System. Shapes were drawn in Google Earth, exported to GTFS and then converted to shapefiles. This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Feature Service Layer Link: https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_LocalTransit/FeatureServer/23

To quantify shoreline rates of change (erosion or accretion), Maryland Geological Survey (MGS) used historical and recent shorelines spanning 1993-2010 as input into the Digital Shoreline Analysis System (DSAS) Version 4.3. DSAS, a computer program developed by the U.S. Geological Survey (USGS), determines linear rates of shoreline change along closely spaced, shore-normal transects. Based on DSAS output, MGS assigned generalized rate of change categories as attributes to a recent shoreline for Prince George's County. This recent shoreline consisted of the National Oceanic and Atmospheric Administration (NOAA) Continually Updated Shoreline Product (CUSP) digital shoreline currently available for Prince George's County; and 2) portions of the Maryland Department of Natural Resources (MD DNR) Critical Area Commission (CAC) digital shoreline for Prince George's County. Based on the results of an End Point Rate (EPR) analysis on the ca. 1990s shoreline and the ca. 2000/2010 shoreline (recent shoreline), MGS grouped the rate results into the following general categories: (a) No change (-0.01 to 0.01 feet/year), (b) Accretion (greater than 0.01 feet/year), (c) Slight erosion rate (0 to -2 feet/year), (d) Low erosion rate (-2 to -4 feet/year), (e) Moderate erosion rate (-4 to -8 ft/yr), (f) High erosion rate (greater than -8 feet/year), (g) Protected, (h) No data (insufficient shorelines to calculate 10-year EPR rate), (i) No data (no transects cast; unprotected or unknown shoreline condition), and (j) Rates not delivered (calculated rates suspect). The NOAA CUSP shoreline represents the shoreline position in Prince George's County between the years 2005-2010. The CAC shoreline represents the shoreline position in Prince George's County in 2007. In Prince George’s County, the NOAA CUSP data set covered approximately 60% of the shoreline in the county. MGS decided to supplement the NOAA CUSP data with CAC data in the following areas where NOAA CUSP data was missing: Anacostia River, from approximately the Bladensburg Road bridge, north to the Decatur Street bridge; Northwest Branch Anacostia River, from approximately the 38th Street bridge, south to its confluence with the Anacostia River; the lower reaches of Swanson Creek, west of Chalk Point; Spice Creek and an unnamed creek north of Spice Creek; and Patuxent River and its major tributaries, from approximately the Merkle Wildlife Sanctuary, north to the upper reaches of the Patuxent River. To identify which shoreline source is responsible for a shoreline segment, view the "DSAS_SRC" attribute table field -- "CAC" indicates a shoreline sourced from MD DNR CAC data set; "NOAA CUSP" indicates a shoreline sourced from the NOAA CUSP data set. Negative rate of change values indicate erosion, and positive values indicate accretion. In general, MGS tried to attribute lengths of shoreline of at least 80 meters in length sharing similar rates of change.Funding for this data set was provided by Project CZM # 14-15-2040 CZM 136, funded by a National Oceanic and Atmospheric Administration (NOAA) grant (NA13NOS4190136) and made available to MGS through the Department of Natural Resources (MD DNR) Chesapeake and Coastal Service (CCS). MGS wishes to thank the following entities/individuals: 1) MD DNR CCS, Contact: Mr. Chris Cortina, Role: CCS Project Manager; 2) NOAA, Contact: Mr. Doug Graham, NOAA National Geodetic Survey, Role: Guidance on NOAA shoreline data sets; 3) MD DNR Critical Areas Commission (CAC), Contact: Ms. Lisa Hoerger, Role: Permitted use of CAC shorelines; 4) Eastern Shore Regional GIS Cooperative (ESRGC), Salisbury University, Contact: Ryan Mello, Role: Performing the critical area re-mapping for MD DNR CAC and supplying MGS with CAC shorelines; and 5) Ms. Lamere Hennesse, MGS Geologist, retired, Role: Project guidance & technical support.This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Map Service Link: https://mdgeodata.md.gov/imap/rest/services/Hydrology/MD_ShorelineChanges/MapServer/12

To quantify shoreline rates of change (erosion or accretion), Maryland Geological Survey (MGS) used historical and recent shorelines spanning 1972-2010 as input into the Digital Shoreline Analysis System (DSAS) Version 4.3. DSAS, a computer program developed by the U.S. Geological Survey (USGS), determines linear rates of shoreline change along closely spaced, shore-normal transects. Based on DSAS output, MGS assigned generalized rate of change categories as attributes to a recent shoreline for Prince George's County. This recent shoreline consisted of the National Oceanic and Atmospheric Administration (NOAA) Continually Updated Shoreline Product (CUSP) digital shoreline currently available for Prince George's County; and 2) portions of the Maryland Department of Natural Resources (MD DNR) Critical Area Commission (CAC) digital shoreline for Prince George's County. Based on the results of an End Point Rate (EPR) analysis on the ca. 1970s shoreline and the ca. 2000/2010 shoreline (recent shoreline), MGS grouped the rate results into the following general categories: (a) No change (-0.01 to 0.01 feet/year), (b) Accretion (greater than 0.01 feet/year), (c) Slight erosion rate (0 to -2 feet/year), (d) Low erosion rate (-2 to -4 feet/year), (e) Moderate erosion rate (-4 to -8 ft/yr), (f) High erosion rate (greater than -8 feet/year), (g) Protected, (h) No data (insufficient shorelines to calculate 30-year EPR rate), (i) No data (no transects cast; unprotected or unknown shoreline condition), and (j) Rates not delivered (calculated rates suspect). The CUSP shoreline represents the shoreline position in Prince George's County between the years 2005-2010. The CAC shoreline represents the shoreline position in Prince George's County in 2007. In Prince George’s County, the NOAA CUSP data set covered approximately 60% of the shoreline in the county. MGS decided to supplement the NOAA CUSP data with CAC data in the following areas where NOAA CUSP data was missing: Anacostia River, from approximately the Bladensburg Road bridge, north to the Decatur Street bridge; Northwest Branch Anacostia River, from approximately the 38th Street bridge, south to its confluence with the Anacostia River; the lower reaches of Swanson Creek, west of Chalk Point; Spice Creek and an unnamed creek north of Spice Creek; and Patuxent River and its major tributaries, from approximately the Merkle Wildlife Sanctuary, north to the upper reaches of the Patuxent River. To identify which shoreline source is responsible for a shoreline segment, view the "DSAS_SRC" attribute table field -- "CAC" indicates a shoreline sourced from MD DNR CAC data set; "NOAA CUSP" indicates a shoreline sourced from the NOAA CUSP data set. Negative rate of change values indicate erosion, and positive values indicate accretion. In general, MGS tried to attribute lengths of shoreline of at least 80 meters in length sharing similar rates of change.Funding for this data set was provided by Project CZM # 14-15-2040 CZM 136, funded by a National Oceanic and Atmospheric Administration (NOAA) grant (NA13NOS4190136) and made available to MGS through the Department of Natural Resources (MD DNR) Chesapeake and Coastal Service (CCS). MGS wishes to thank the following entities/individuals: 1) MD DNR CCS, Contact: Mr. Chris Cortina, Role: CCS Project Manager; 2) NOAA, Contact: Mr. Doug Graham, NOAA National Geodetic Survey, Role: Guidance on NOAA shoreline data sets; 3) MD DNR Critical Areas Commission (CAC), Contact: Ms. Lisa Hoerger, Role: Permitted use of CAC shorelines; 4) Eastern Shore Regional GIS Cooperative (ESRGC), Salisbury University, Contact: Ryan Mello, Role: Performing the critical area re-mapping for MD DNR CAC and supplying MGS with CAC shorelines; and 5) Ms. Lamere Hennesse, MGS Geologist, retired, Role: Project guidance & technical support.This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Map Service Link: https://mdgeodata.md.gov/imap/rest/services/Hydrology/MD_ShorelineChanges/MapServer/13

State of Maryland Priority Funding Area boundary dataset. This dataset is created and maintained by the Maryland Department of Planning. These boundaries are not intended to serve as a legal description. Fields:CPFA (Certified PFA): If field is populated as “IN” then the PFA has been designated at a Priority Funding Area locally. MUN_CODE (Municipality Code): MUN = within Priority Funding Area (PFA); MUNCOM = PFA with comment; MUN_NONPFA = not in PFA Rural Village Code (RUVI_CODE): RV = within a Rural Village Rural Village Name (RUVI_NAME): Name of the Rural Village COMMENT_STATUS (Comment Status): If field is populated with “NO” then there is no state-placed comment on the area. If the field is populated with “YES” then the state has placed a comment on the area based on eligibility. ACRES (GIS Acres): GIS calculated acres. JURSCODE (Jurisdiction Code) – Four letter county code: ALLE (Allegany), ANNE (Anne Arundel), BACI (Baltimore City), BACO (Baltimore County), CALV (Calvert), CARO (Caroline), CARR (Carroll), CECI (Cecil), CHAR (Charles), DORC (Dorchester), FRED (Frederick), GARR (Garrett), HARF (Harford), HOWA (Howard), KENT (Kent), MONT (Montgomery), PRIN (Prince George’s) QUEE (Queen Anne’s), SOME (Somerset), STMA (St. Mary’s), TALB (Talbot), WASH (Washington), WICO (Wicomico), WORC (Worcester).CERT_DATE (Certification Date) (DD/MM/YYYY): This date is known as the “Certification Date” of the PFA. The date 1/1/1997, or NULL, is used as a default date of when the PFA was certified were first indicated in the GIS layer and not necessarily of when it was actually certified. If there's a date of 1/1/1997, it can be assumed that the PFA was certified on, or before this date. STATE_ELIGIBLE_STATUS (State Eligible): This field is based on whether the PFA has a comment. If there is no comment, then the field will be populated with YES; if there is a state-placed comment, the field will be populated with NO. Point of Contact: Ellen Mussman ellen.mussman@maryland.gov and Meagan Fairfield-Peak meagan.fairfieldpeak@maryland.govDate Last Updated 10/22/2024This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PriorityFundingAreas/FeatureServer/0

This layer contains the boundaries and IDs of the Maryland tax maps produced by Maryland Department of Planning. Tax maps, also known as assessment maps, property maps or parcel maps, are a graphic representation of real property showing and defining individual property boundaries in relationship to contiguous real property.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer/2

Esri ArcGIS Online (AGOL) Map Image Layer for accessing the Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product.Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones consists of polygon geometric features which represent the geographic areas throughout the State of Maryland that are impacted by CRAB inundation (0 to 1ft, 1 to 2ft, and 2ft or more).The Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product was created using a GIS spatial analysis model, unique for each county in the State of Maryland. Coastal counties follow an analysis methodology that incorporates FEMA Stillwater wave action as it is understood from the FEMA identified VE zones. A Water Surface Elevation (WSE) and Still Water Elevation (SWEL) rasters are used as the baseline to identify existing water depths within each county. For all flood zones that are not classified as VE the WSE three feet was added to reflect a three-foot rise in the base flood elevations. For those WSEs falling within a FEMA floodplain identified V Zone, six feet was added (three feet for the increase in flood elevations for the CS-CRAB, and 3 feet to compensate for the minimum of 3 foot wave action typically mapped by FEMA) / wave heights greater than 3 feet were reduced to the 3 foot minimum for consistency across the shoreline. The newly calculated WSE plus three datasets were then converted to points and merged. Next, an Inverse Distance Weighted (IDW) Interpolation was used to compute the proportional weighted values between the WSE point locations based on proximity. The DEM for each county is then subtracted from the new IDW raster in order to show precise water locations as they relate to the land elevation, producing a freeboard depth grid representing the depth of flood waters above the existing ground elevation given a 3 foot increase in water level. A course resolution QAQC was applied to remove “islands” of data associated with DEM inaccuracies and other elevation anomalies. The analysis was run at a1 ft x 1 ft raster resolution. The DEM accuracy for each county varies based what is currently available. Here the breakdown of DEM accuracy for each county used in this project: Anne Arundel County DEM year is 2017 and horizontal resolution is 1ft. Baltimore County DEM year is 2015 and horizontal resolution is 2.5ft. Baltimore City DEM year is 2015 and horizontal resolution is 0.7m. Calvert County DEM year is 2017 and horizontal resolution is 1ft. Caroline County DEM year is 2013 and horizontal resolution is 3.125ft. Cecil county DEM year is 2013 and horizontal resolution is 0.6m. Charles County DEM year is 2014 and horizontal resolution is 0.9m. Dorchester County DEM year is 2013 and horizontal resolution is 0.9m. Harford County DEM is 2013 and horizontal accuracy is 1.5m. Kent County DEM year is 2015 and horizontal resolution is 0.7m. Prince George’s County DEM year is 2014 and horizontal resolution is 0.7m. Queen Anne’s County DEM year is 2013 and horizontal resolution is 0.6m. Somerset County DEM year is 2012 and horizontal accuracy is 1m. St Mary’s County DEM year is 2014 and Horizontal accuracy is 0.9m. Talbot County DEM year is 2015 and Horizontal accuracy is 0.7m. Wicomico County DEM year is 2012 and horizontal accuracy is 1m. Worchester County DEM year is 2011 and horizontal accuracy is 1m.The Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Inundated Zones data product was created by the Maryland Environmental Service (MES) in partnership with the Maryland Department of Environment (MDE) and the Coast Smart Council, under the guidance of the Maryland Department of Natural Resource (DNR).For additional information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Esri ArcGIS Online (AGOL) Imagery Layer for accessing the Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Coastal - Flood Depth Grid data product.Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Coastal - Flood Depth Grid consists of a flood depth grid image service depicting the Climate Ready Action Boundary (CRAB) for the coastal areas throughout the State of MarylandThe Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Coastal - Flood Depth Grid raster layer was created using a GIS spatial analysis model, unique for each county in the State of Maryland. Coastal counties follow an analysis methodology that incorporates FEMA Stillwater wave action as it is understood from the FEMA identified VE zones. A Water Surface Elevation (WSE) and Still Water Elevation (SWEL) rasters are used as the baseline to identify existing water depths within each county. For all flood zones that are not classified as VE the WSE three feet was added to reflect a three-foot rise in the base flood elevations. For those WSEs falling within a FEMA floodplain identified V Zone, six feet was added (three feet for the increase in flood elevations for the CS-CRAB, and 3 feet to compensate for the minimum of 3 foot wave action typically mapped by FEMA) / wave heights greater than 3 feet were reduced to the 3 foot minimum for consistency across the shoreline. The newly calculated WSE plus three datasets were then converted to points and merged. Next, an Inverse Distance Weighted (IDW) Interpolation was used to compute the proportional weighted values between the WSE point locations based on proximity. The DEM for each county is then subtracted from the new IDW raster in order to show precise water locations as they relate to the land elevation, producing a freeboard depth grid representing the depth of flood waters above the existing ground elevation given a 3 foot increase in water level. A course resolution QAQC was applied to remove “islands” of data associated with DEM inaccuracies and other elevation anomalies. The analysis was run at a 1 ft x 1 ft raster resolution. The DEM accuracy for each county varies based what is currently available. Here the breakdown of DEM accuracy for each county used in this project: Anne Arundel County DEM year is 2017 and horizontal resolution is 1ft. Baltimore County DEM year is 2015 and horizontal resolution is 2.5ft. Baltimore City DEM year is 2015 and horizontal resolution is 0.7m. Calvert County DEM year is 2017 and horizontal resolution is 1ft. Caroline County DEM year is 2013 and horizontal resolution is 3.125ft. Cecil county DEM year is 2013 and horizontal resolution is 0.6m. Charles County DEM year is 2014 and horizontal resolution is 0.9m. Dorchester County DEM year is 2013 and horizontal resolution is 0.9m. Harford County DEM is 2013 and horizontal accuracy is 1.5m. Kent County DEM year is 2015 and horizontal resolution is 0.7m. Prince George’s County DEM year is 2014 and horizontal resolution is 0.7m. Queen Anne’s County DEM year is 2013 and horizontal resolution is 0.6m. Somerset County DEM year is 2012 and horizontal accuracy is 1m. St Mary’s County DEM year is 2014 and Horizontal accuracy is 0.9m. Talbot County DEM year is 2015 and Horizontal accuracy is 0.7m. Wicomico County DEM year is 2012 and horizontal accuracy is 1m. Worchester County DEM year is 2011 and horizontal accuracy is 1m.The Maryland Coast Smart - Climate Ready Action Boundary (CRAB) Coastal - Flood Depth Grid data was created by the Maryland Environmental Service (MES) in partnership with the Maryland Department of Environment (MDE) and the Maryland Coast Smart Council, under the guidance of the Maryland Department of Natural Resource (DNR).For additional information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

State of Maryland municipality boundary dataset.Maryland Department of Planning (MDP) maps annexations from municipalities. This dataset is created and maintained by the Maryland Department of Planning. These boundaries are not intended to serve as a legal description. Fields:MUN_NAME (Municipality Name): Name of Municipality located in Maryland.RESOLUTION_NUMBER (Resolution Number): Local Municipality Annexation Resolution Number.ANNEXATION_DATE (Annexation Date) (DD/MM/YYYY): The Annexation Date field shows when there's been a change in the boundary. This date is known as the “Effective Date” from the municipality. The date 1/1/1997 is used as a default date of when annexation changes were first indicated in the GIS layer and not necessarily of when it was actually annexed. If there's a date of 1/1/1997, it can be assumed that the annexation occurred on this date or before. For example, for Baltimore City, the city boundary was determined hundreds of years ago. Other than that default date, the date will show when the property was annexed. ACRES (GIS Acres): GIS calculated acres.JURSCODE (Jurisdiction Code) – Four letter county code: ALLE (Allegany), ANNE (Anne Arundel), BACI (Baltimore City), BACO (Baltimore County), CALV (Calvert), CARO (Caroline), CARR (Carroll), CECI (Cecil), CHAR (Charles), DORC (Dorchester), FRED (Frederick), GARR (Garrett), HARF (Harford), HOWA (Howard), KENT (Kent), MONT (Montgomery), PRIN (Prince George’s) QUEE (Queen Anne’s), SOME (Somerset), STMA (St. Mary’s), TALB (Talbot), WASH (Washington), WICO (Wicomico), WORC (Worcester).This is a MD iMAP hosted service. Find more information on https://imap.maryland.govhttps://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer/5

The Purple Line will have 21 stations – 10 in Montgomery County and 11 in Prince George’s County – all inside the Capital Beltway. The Purple Line is a 16-mile light rail line that will extend from Bethesda in Montgomery County to New Carrollton in Prince George's County. It will provide a direct connection to the Metrorail Red, Green and Orange Lines; at Bethesda, Silver Spring, College Park, and New Carrollton. The Purple Line will also connect to MARC, Amtrak, and local bus services. It is currently under construction and is anticipated to be completed in 2027. For more details visit the Purple Line website.

This data contains attributes that indicate station names.