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/Charles/MD_charles_dem_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/Charles/MD_charles_aspect_m/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

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 acresJURSCODE (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).

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/Charles/MD_charles_shadedRelief_RGB/ImageServer

This layer contains bus routes and variations for Charles 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://geodata.md.gov/imap/rest/services/Transportation/MD_LocalTransit/FeatureServer/11

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://geodata.md.gov/imap/rest/services/BusinessEconomy/MD_IncentiveZones/FeatureServer/13

This is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. The Blue Infrastructure study area and extent of inventory data was defined as the 16 coastal zone counties (Anne Arundel - Baltimore - Calvert - Caroline - Cecil - Charles - Dorchester - Harford - Kent - Prince George's - Queen Anne's - Somerset - St. Mary's - Talbot - Wicomico - and Worcester) and Baltimore City. Including Baltimore City makes a total of 17 designated locations based on sixteen County Boundaries and one City Boundary. Four main models were created to perform the overlay processes to calculate the Zonal Majority used to determine the total rank for all the segments. The Blue Infrastructure assessment was designed as a spatial evaluation of coastal habitat - critical natural resources and associated human uses in the tidal waters and near-shore areas of Maryland's coastal zone. The Assessment is used to identify near-shore tidal habitat priority areas that support coastal habitats and the resources and economies that depend upon them. The Blue Infrastructure was developed through a partnership between the Maryland Department of Natural Resources' Chesapeake and Coastal Program - the National Oceanic and Atmospheric Administration and Towson University's Center for GIS. Last Updated: 5/1/2010 Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Hydrology/MD_BlueInfrastructure/FeatureServer/0 ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

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

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://geodata.md.gov/imap/rest/services/PlanningCadastre/MD_PriorityFundingAreas/FeatureServer/0

The Blue Infrastructure study area and extent of inventory data was defined as the 16 coastal zone counties (Anne Arundel, Baltimore, Calvert, Caroline, Cecil, Charles, Dorchester, Harford, Kent, Prince George's, Queen Anne's, Somerset, St. Mary's, Talbot, Wicomico, and Worcester) and Baltimore City. Including Baltimore City makes a total of 17 designated locations based on sixteen County Boundaries and one City Boundary. Four main models were created to perform the overlay processes to calculate the Zonal Majority used to determine the total rank for all the segments. The Blue Infrastructure assessment was designed as a spatial evaluation of coastal habitat, critical natural resources and associated human uses in the tidal waters and near-shore areas of Maryland's coastal zone. The Assessment is used to identify near-shore tidal habitat priority areas that support coastal habitats and the resources and economies that depend upon them. The Blue Infrastructure was developed through a partnership between the Maryland Department of Natural Resources' Chesapeake and Coastal Program, the National Oceanic and Atmospheric Administration and Towson University's Center for GIS.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://geodata.md.gov/imap/rest/services/Hydrology/MD_BlueInfrastructure/FeatureServer/0