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

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

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

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