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://lidar.geodata.md.gov/imap/rest/services/Montgomery/MD_montgomery_aspect_m/ImageServer

This metadata record describes the classified bare earth lidar digital elevation model (DEM) data products derived from the Montgomery County, MD LiDAR project covering the defined project area of Montgomery County and immediate surroundings.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/Montgomery/MD_montgomery_2013_dem_m/ImageServer

This metadata record describes the classified bare earth lidar digital elevation model (DEM) data products derived from the Montgomery County, MD LiDAR project covering the defined project area of Montgomery County and immediate surroundings.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/Montgomery/MD_montgomery_2013_shadedRelief_RGB/ImageServer

This metadata record describes the classified bare earth lidar digital elevation model (DEM) data products derived from the Montgomery County, MD LiDAR project covering the defined project area of Montgomery County and immediate surroundings.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/Montgomery/MD_montgomery_2013_slope_m/ImageServer

This layer shows all Montgomery County Ride On bus routes including all variations. The information was retrieved from January 2016 MCRO GTFS files. The GTFS file was converted to ArcGIS format by CMRT. 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/

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 elevated and tunnel segments of the alignment.

Polygon features that represent the political boundaries of Metropolitan Planning Organizations (MPO) that exist in Maryland and for which the Maryland Department of Transportation (MDOT) is a member. In several instances, these MPO boundaries extend beyond Maryland’s borders into neighboring states as well as the District of Columbia. MPO Boundaries’ data includes information on each boundary's name, geographic location, and the total size / extent of each area. MPO Boundaries data was intended to be used for planning purposes within governments at the National and State level. Maryland's MPO Boundaries data is a sub-set of the U.S. Department of Transportation (USDOT) Office of the Assistant Secretary for Research and Technology's Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). A metropolitan planning organization (MPO) is a federally-mandated and federally-funded transportation policy-making organization that is made up of representatives from local governments and governmental transportation authorities. Federal law requires the formation of an MPO for any urbanized area (UZA) with a population greater than 50,000. Federal funding for transportation projects and programs are channeled through this planning process. Congress created MPOs to ensure that existing and future expenditures of federal funds for transportation projects and programs are based on a continuing, cooperative, and comprehensive (“3‑C”) planning process. MPOs are charged with developing a 20-year long-range transportation plan (LRTP) and a short-term (usually 2-6 years) program called the transportation improvement program (TIP) for each of their respective regions. The seven MPOs of which Maryland jurisdictions and agencies are members are listed below. The Maryland member jurisdictions are listed under each MPO (note that some MPOs cover multi-State regions). The Maryland Department of Transportation is a member of each of the MPOs listed. Each of the listed member jurisdictions has a different level of involvement with its MPO.Maryland's MPOs are as follows: National Capital Region Transportation Planning Board (TPB)https://www.mwcog.org/tpb/- Charles County, Maryland- Frederick County, Maryland- Montgomery County, Maryland- Prince George's County, Maryland- City of Bowie, Maryland- City of College Park, Maryland- City of Frederick, Maryland- City of Gaithersburg, Maryland- City of Greenbelt, Maryland- City of Laurel, Maryland- City of Rockville, Maryland- City of Takoma Park, Maryland- Maryland Department of Transportation (MDOT)Baltimore Regional Transportation Board (BRTB)https://baltometro.org/- Anne Arundel County, Maryland- Baltimore County, Maryland- Carroll County, Maryland- Harford County, Maryland- Howard County, Maryland- Queen Anne's County, Maryland- City of Annapolis, Maryland- City of Baltimore, Maryland- Maryland Department of Transportation (MDOT)Cumberland Area Metropolitan Planning Organization (CAMPO)https://alleganygov.org/473/Metropolitan-Planning-Organization- Allegany County, Maryland- City of Cumberland, Maryland- City of Frostburg, Maryland- Maryland Department of Transportation (MDOT)Hagerstown / Eastern Panhandle Metropolitan Planning Organization (HEPMPO)https://www.hepmpo.net/- Washington County, Maryland- City of Hagerstown, Maryland- Maryland Department of Transportation (MDOT)Wilmington Area Planning Council (WILMAPCO)https://www.wilmapco.org/- Cecil County, Maryland- Maryland Department of Transportation (MDOT)Salisbury / Wicomico Metropolitan Planning Organization (S / WMPO)https://www.swmpo.org/- Wicomico County, Maryland- City of Fruitland, Maryland- City of Salisbury, Maryland- Town of Delmar, Maryland- Maryland Department of Transportation (MDOT)Calvert-St. Mary’s Metropolitan Planning Organization (C - SMMPO)https://www.calvert-stmarysmpo.com/- Calvert County, Maryland- St. Mary's County, Maryland- Maryland Department of Transportation (MDOT)Maryland's MPO Boundaries data is owned and maintained by the Transportation Secretary's Office (TSO) of the Maryland Department of Transportation (MDOT). Being a subset of the USDOT's NTAD, an annual update of Maryland's MPO Boundaries data is performed by TSO in close coordination with each MPO, the Maryland Department of Transportation State Highway Administration (MDOT SHA) and the Federal Highway Administration (FHWA). MPO Boundaries data is a strategic resource for the USDOT, FHWA, MDOT, as well as many other Federal, State, and local government agencies. Maryland's MPO Boundaries data is updated on an annual basis. For additional MPO information, contact MDOT's Office of Planning and Capital Programming:MDOTGIS@mdot.state.md.usFor additional data information, contact the MDOT SHA Geospatial Technologies Team:GIS@sha.state.md.usFor additional information related to the Maryland Department of Transportation (MDOT):https://www.mdot.maryland.gov/For additional information related to the Maryland Department of Transportation State Highway Administration (MDOT SHA):https://www.roads.maryland.gov/This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/BusinessEconomy/MD_IncentiveZones/FeatureServer/13

Updated as needed from https://www.montgomerycountymd.gov/rec/facilities/recreationcenters and municipal web pages. The INFO field can be used to query just County or municipal facilities.Can be downloaded from the GIS Data Portal here.Access directly in the TEBS-GIS database in SDE.LOCATIONS, SDE.Recreation_Center

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/Montgomery/MD_montgomery_hillshade_m/ImageServer

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_aspect_m/ImageServer

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:Municipality Name: Name of Municipality located in Maryland.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). Last updated: 9/5/2024This is an MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer/2

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://geodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer/5