The percentage of commuters that use public transit out of all commuters aged 16 and above. Source: American Community SurveyYears Available: 2007-2011, 2008-2012, 2009-2013, 2010-2014, 2011-2015, 2012-2016, 2013-2017, 2014-2018, 2015-2019, 2016-2020, 2017-2021, 2018-2022, 2019-2023Please note: We do not recommend comparing overlapping years of data due to the nature of this dataset. For more information, please visit: https://www.census.gov/programs-surveys/acs/guidance/comparing-acs-data.html

Maryland Transit Administration METRO routes. The 15.5-mile, 14-station Metro Subway system operates every. 8-10 minutes during the morning and evening peak periods; 11 minutes during weekday evenings; 15 minutes on Saturdays, Sundays and holidays. See http://mta.maryland.gov/metro-subway for more information.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/Transportation/MD_Transit/FeatureServer/5

The regional transit data was acquired through the jurisdictional GIS offices, Baltimore County Department of Public Works and Transportation, MTA (MDimap), Rabbit Transit, Regional Transportation Agency, TRIP Center for Mobility Equity, York County Planning Commission (YCPC) for the latest release.Dates: - MTA: 01/27/2025- Annapolis: 01/17/2024- Anne Arundel County: 01/15/2025- CATS (Carroll County): 01/26/2024- Charm City Circulator: 01/02/2025- County Ride (Queen Anne's County): 01/30/2025- HCTS (Harford County): 01/03/2025- Rabbit Transit (PA): 12/23/2024- RTA (central MD): 12/26/2024- Towson Loop: 12/26/2024This dataset has been edited by BMC to add type, transit operator, date of source data, and date the dataset was updated by BMC.Date: Updates acquired on or before 01/30/2025.Update: Annual.Attributes:Route_Short: Abbreviated name for transit route. Route_Name: Route name.County_FIPS: County Federal Information Processing Standard code.Municipal_FIPS: Municipal Federal Information Processing Standard code.Operator: Agency operating the route.Location_Description: JurisdictionLINENAME: Additional descriptor for route name.TYPE: Populated with Bus (MTA), Local Bus, Commuter, Intercity, Local Ferry, Light Rail, MARC and Subway.TYPE_NAME: Alternate category names for map legends: Bus (MTA), Local Bus, Commuter Bus, Intercity Bus, Local Ferry, Light Rail, MARC and Metro.Source_Date: Date of data source.BMC_Updated: Date BMC received updated data from the provider.

Baltimore City’s Freight Network consists of linear features which represent the street centerlines of the official truck routes in the City of Baltimore, Maryland. The purpose of this data is to identify through, local, and restricted truck routes within Baltimore City. These routes specify where large trucks are allowed to drive, for the use by truck operators, trucking companies, and City transportation offices. The linear geometric features of this dataset were created by merging the National Highway Freight Network (NHFN) (https://ops.fhwa.dot.gov/freight/infrastructure/nfn/index.htm) with Baltimore City's Freight Network (data provided by the Baltimore City Department of Transportation). A “NHFN_ID” field is provided to distinguish City freight routes that are also a part of the NHFN. Annual Average Daily Traffic (AADT) values from 2017 are provided for each line segment where applicable. AADT values and percent utilization are provided for each vehicle classification (Motorcycle, Car, Light Truck, Single Unit Truck and Combination Unit Truck). A “Freight AADT” field and a “Freight Percent Utilization” field are also provided. Freight AADT was calculated by summing Single Unit Truck (FHWA Class 5 to 7) and Combination Unit Truck (FHWA Class 8 to 13) AADT values. Freight Percent Utilization was calculated by dividing the Freight AADT by the total AADT. Light Trucks (FHWA Class 3) were intentionally excluded from the Freight AADT and Freight Percent Utilization as these vehicles are not restricted to traversing on the City’s freight network. AADT data was obtained from the “Annual Average Daily Traffic - MDOT SHA Statewide AADT Lines” layer on MD iMAP (https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_AnnualAverageDailyTraffic/FeatureServer/1).

Every reasonable effort has been made to ensure the accuracy of these data. The City of Baltimore, Maryland makes no representations nor warranties, either expressed or implied, regarding the accuracy of this information or its suitability for any particular purpose whatsoever. The data is licensed "as is" and the City of Baltimore will not be liable for its use or misuse by any party. Reliance of these data is at the risk of the user.

Last updated: 10/07/2019

It takes a lot of fuel to move Marylanders from point “A” to point “B.” The Maryland Energy Administration (MEA) offers incentives to reduce the amount of energy residents expend on travel. This table includes information about electric vehicle charging stations and alternative refueling stations that received funding by MEA as well as those that did not. Data on non-MEA funding projects in Maryland is from the U.S. Department of Energy: http://1.usa.gov/13VN2Vi. For more information on Maryland's transportation programs, visit: http://energy.maryland.gov/Transportation/index.html

This dataset represents the locations of MTA Bus Stops as of 2022 within the City of Baltimore. To leave feedback or ask a question about this dataset, please fill out the following form: Bus Stops feedback form.

The TZ_2016 feature class combined with the Int_2016 feature class represents the intersections with a level of service rating of D, E or F and the associated commutershed as represented on the 2016 Transportation Basic Services Map.The 2016 Transportation Basic Services Map was enacted under bill number 18-16 and is part of the Baltimore County Zoning Regulations, 1955 as amended by the bill adopted May 2, 2016. Effective May 16, 2016.

The percentage of commuters that use public transit out of all commuters aged 16 and above. Source: American Community Survey Years Available: 2007-2011, 2008-2012, 2009-2013, 2010-2014, 2011-2015, 2012-2016, 2013-2017, 2014-2018, 2015-2019, 2016-2020, 2017-2021, 2018-2022, 2019-2023

The USGS Topo base map service from The National Map is a combination of contours, shaded relief, woodland and urban tint, along with vector layers, such as geographic names, governmental unit boundaries, hydrography, structures, and transportation, to provide a composite topographic base map. Data sources are the National Atlas for small scales, and The National Map for medium to large scales.

This file represents the final list of projects (preferred alternative) in the Maximize 2040 Long Range Plan. There are two layers that make up the Maximize 2040 project data (a point layer and a line layer) which should be used together. Points and lines are exclusive of one another, there is not a point if the project can be represented by a line. Some projects cannot be mapped, such as regional bus improvements. A long-range transportation plan is the statement of the ways the region plans to invest in the transportation system over the next twenty years. Field DescriptionsUID - This field is the master ID that connects the GIS data with the access project master database. PROJECT - This field matches the model group's master network project. Note that most of the time this layer's projects are drawn differently from the master network.NAME - Project name.LabelID - This is the field that will be used to label the projects in the map and matches the table in the printed report.TYPE - Type of project can be highway or transit.Date: 6/1/2016Update: Every 4 years, updates will be added separately. Source: Baltimore Metropolitan Council

This is the project data from the draft TIP 2021-2024 report. It represents data from the time of publication only and not subsequent amendments. There is a point for each project. There is a line for projects with easily defined limits, such as highway projects. Intersections and transit stations are only depicted as points.The Baltimore Region Transportation Improvement Program (TIP) documents the anticipated timing, cost, and rationale for federally-funded transportation improvements to be made in the Baltimore region over the next four years. It is a program of specific projects, not a plan. In accordance with federal guidelines, the TIP is a translation of recommendations from the long-range transportation plan for the Baltimore region into a short-term program of improvements. This includes specific capacity improvements that have been identified in the long-range plan, as well as system preservation projects and operational initiatives that are supported in the plan but have not been previously detailed. As such, the TIP ensures consistency between plan recommendations and project implementation in the region. The Transportation Improvement Program (TIP) lists all federally funded projects and regionally significant, non-federally funded projects programmed for implementation in the next four years. It includes approximately $4.3 billion in proposed federal, state and local money for highway, transit, bicycle and pedestrian projects. The TIP helps establish a transportation program that implements the goals of Maximize2045, the Baltimore region’s long-range transportation plan. There are numerous projects in the TIP that are not location specific and thus do not appear on this map. These projects include items such as SHA area-wide improvements, MTA rolling stock and infrastructure improvements, Baltimore citywide projects, and county bridge inspection projects. More information on the TIP and these projects is available on the 2021-2024 TIP webpage. Date: 7/7/2020Update: Every 1-2 years, updates for future reports will be added as separate layers.Source: Baltimore Metropolitan Council. If you have any questions, contact Mara Kaminowitz at mkaminowitz@baltometro.org.Each TIP project list is superseded by the next year's report. There also may be amendments throughout the year which are not reflected in the GIS data. If there is a discrepancy, the most recent approved and published report is the authoritative source. For more information, see the TIP webpage.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the Maryland Coordinate System, U.S. Survey Foot. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

This measure provides the number of structurally deficient bridges and number of total bridges owned by MDTA. The latitude and longitude is also provided for the structurally deficient bridges.

The MDTA's Annual Inspection Report consists of a walk/climb through physical inspection resulting in a thorough hands-on inspection of all structures, roadways, tunnels and tunnel ventilation buildings (including the mechanical and electrical systems), drainage structures, toll plazas, Variable Message Signs (VMS), incident detection equipment housings and structures, retaining walls, noise barriers, traffic and safety equipment, and truck weigh scales under the jurisdiction of the Maryland Transportation Authority at the following facilities: I-95 (John F. Kennedy Memorial Highway), I-895 (Baltimore Harbor Tunnel Thruway), Seagirt Marine Terminal, Thomas J. Hatem Memorial Bridge, I-395 and I-95 in Baltimore City (Fort McHenry Tunnel), I-695 (Francis Scott Key Bridge), Harry W. Nice Memorial Bridge, the Bay Bridge (twin structures) and the Intercounty Connector (ICC/MD200). The annual inspection process includes the development of a Structural Inventory and Appraisal (SI&A) assessment that is submitted to the Federal Highway Administration each April for the preceding calendar year.The data for this measure is collected from the SI&A assessment that is performed yearly by the MDTA's facilities inspection consultant.

The MDTA continued to be successful in having 100 percent of its bridges fully operational and functioning (no weight restrictions), allowing all emergency vehicles, school buses, vehicles serving the economy of an area, and legally loaded vehicles to safely traverse. Bridges are considered structurally deficient if significant load carrying elements are found to be in a poor (or worse) condition due to deterioration and/or damage, or have a low weight restriction. The fact that a bridge is structurally deficient does not imply that it is unsafe.

The Int_2016 feature class combined with the TZ_2016 feature class represents the intersections with a level of service rating of D, E or F and the associated commutershed as represented on the 2016 Transportation Basic Services Map. The 2016 Transportation Basic Services Map was enacted under bill number 18-16 and is part of the Baltimore County Zoning Regulations, 1955 as amended by the bill adopted May 2, 2016. Effective May 16, 2016.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the Maryland Coordinate System, U.S. Survey Foot. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

This is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. Traffic monitoring data is a strategic resource for SHA and Maryland's Department of Transportation. The data is essential in the planning - design and operation of the statewide road system and the development and implementation of state highway improvement and safety programs. TMS is a product of the ISTEA Act of 1991 - which required a traffic data program to effectively and efficiently meet SHA's long-term traffic data monitoring and reporting requirements. The quality control feature of the system allow data edit checks and validation for data from the 84 permanent - continuous automatic traffic recorders (ATRs) and short-term traffic counts.The Maryland Traffic Volume Maps depict the Annual Average Daily Traffic (AADT) at various locations on Maryland's roadways by county. Traffic Volume data is collected from over 8700 program count stations and 84 ATRs - located throughout Maryland. To date - four (4) ATRs have been removed from the ATR Program. Program count data is collected (both directions) at regular locations on either a three (3) year or six (6) year cycle depending on type of roadway. Growth Factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday - respectively. The ATR and toll count data is collected on a continuous basis. Toll station data is provided by the Maryland Transportation Authority. A special numeric code was added to the AADT numbers - starting in 2006 - to identify the years when the count was actually taken. The last digit represents the number of years prior to the actual count. Where '0' represents the current year when data was collected (in 2014) - '1' represents the count taken in 2013 - '2' represents the count taken in 2012 - '3' represents the count taken in 2011 and so forth. Last Updated: Feature Service Layer Link: https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_AnnualAverageDailyTraffic/FeatureServer 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.

DPWFacilities contains point features that represent the locations of public works and transportation facilities in Baltimore County. The feature classes can be categorized by facility type where facility types include highway shops, salt storage facilities, utilities facilities, equipment operation and maintenance (EOM) facilities, solid waste management facilities, and other facilities. These points are used to produce a map of all the locations where the Department of Public Works and Transportation performs work. This data is duplicated in utility and solid waste vertical models (see UTILITY.Wells, UTILITY.WaterTreatmentPlants, UTILITY.PRV, UTILITY.WastewaterTreatmentPlant, LANDUSE.swm_SSR and LANDUSE.swm_FACILITY)

This is the project data from the TIP 2023-2026 report. It represents data from the time of publication only and not subsequent amendments. There is a point for each project. There is a line for projects with easily defined limits, such as highway projects. Projects locations such as intersections and transit stations are only depicted as points.The Baltimore Region Transportation Improvement Program (TIP) documents the anticipated timing, cost, and rationale for federally-funded transportation improvements to be made in the Baltimore region over the next four years. It is a program of specific projects, not a plan. In accordance with federal guidelines, the TIP is a translation of recommendations from the long-range transportation plan for the Baltimore region into a short-term program of improvements. This includes specific capacity improvements that have been identified in the long-range plan, as well as system preservation projects and operational initiatives that are supported in the plan but have not been previously detailed. As such, the TIP ensures consistency between plan recommendations and project implementation in the region.The Transportation Improvement Program (TIP) lists all federally funded projects and regionally significant, non-federally funded projects programmed for implementation in the next four years. It includes approximately $4.26 billion in proposed federal, state and local money for highway, transit, bicycle and pedestrian projects. The TIP helps establish a transportation program that implements the goals of Maximize2045, the Baltimore region’s long-range transportation plan. The Baltimore Regional Transportation Board approved the 2023-2026 TIP on Tuesday, August 23, 2022. A comment period was held from Wednesday, June 29 through Monday, August 1, 2022.There are numerous projects in the TIP that are not location specific and thus do not appear on this map. These projects include items such as SHA area-wide improvements, MTA rolling stock and infrastructure improvements, Baltimore citywide projects, and county bridge inspection projects. More information on the TIP and these projects is available on the 2023-2026 TIP webpage.Date: 10/17/2022Update: Every 1-2 years, updates for future reports will be added as separate layers.Source: Baltimore Metropolitan Council. If you have any questions, contact Erin Bolton at ebolton@baltometro.org.Each TIP project list is superseded by the next year's report. There also may be amendments throughout the year which are not reflected in the GIS data. If there is a discrepancy, the most recent approved and published report is the authoritative source. For more information, see the TIP webpage.

This layer contains all existing bicycle trails and lanes (facilities) in the region. Planned, programmed, and under construction bicycle and pedestrian facilities are not included. The data was compiled by local jurisdictions using planning data, bicycle master plans, and capital improvement reports. The regional layer was consolidated at BMC. Information includes trail type, status, side of road, name (if applicable), and speed limit (if applicable). There are two status and facility fields for where a line segment has more than one facility or status type. All facility information was attributed to the jurisdiction street centerline with the exception of off-road trails. Off-road trails are included in the same layer but they are not part of the original centerline. This project started in 2016 and was approved by our region's mayors and county executives. The project is managed by BMC's Baltimore and Pedestrian Advisory Group (BPAG). The main goal of the data is to enable better transportation planning, especially a way to look at gaps in connectivity. Commuting is the focus more than recreational trails. Bicycle trails that do not aid in commuting (ex. a small loops in a park) may not be represented. The data is sourced from the local jurisdictions in the BMC region and is required to adhere to standards set by BMC for quality and completeness.

Date created: August 2017, updated December 2020

Update: Annual

Field Names

Field Name

Description

DateRec

Currency of the data provided.

Juris

The county or city of the facility.

Location

An optional field for detailed location data (town, park, neighborhood, etc.)

Owner

Ownership of facility (county, state, private, etc.)

Website

Website of facility or property, if available.

RoadName

Name of street.

TrailName

Name of trail.

Status1

Status of road or trail (Existing only).

FacType1

Type of bicycle facility. See facility type definitions below this table.

Status2

Status of road or trail (Existing only). Some segments can have more than one status and facility type.

FacType2

Type of bicycle facility, if the segment has more than one facility type.

FacSide

Whether the bicycle facilities are on one or both sides of the road.

Trl_ECGW

Is this segment part of the East Coast Greenway?

Trl_ADT

Is this segment part of the American Discovery Trail?

Trl_GHL

Is this segment part of the Grand History Loop?

HoursOp

Hours of operation, for trails that have limited hours of access.

SpeedLimit

Posted speed limit for on-road facilities as well as speed limit for trails/shared use paths if applicable.

Facility Type Definitions (for FacType1 and FacType2)

Bike lane - A bike lane is a dedicated lane for cyclists that is separate from vehicular travel lanes. It is delineated with striping and pavement markings on the roadway and with signage. This category also includes buffered bike lanes, which are bike lanes with an additional painted separation from travel lanes. Buffering can also be used between a bike lane and parked cars. Bike lanes typically are located to the right side of vehicular travel lanes and generally run in the same direction as traffic, except for contraflow bike lanes which travel in the opposite direction of traffic. Bike lanes in this category do not have any physical barrier of separation from vehicular travel lanes (other than paint), which distinguishes them from separated bike lanes.

Separated bike lane - A bike lane that is separated from the travel lanes with a physical barrier which may be either a curb, median, parked cars, a landscaped strip, or other type of barrier that works within the streetscape's character.

Signed designated bike route - A signed route is a roadway that is specifically designated as a bike route to a specific destination and includes signage, but does not use specific lane markings for bicyclists. Roadways with "share the road" signs alone are not included.

Sharrows or marked shared lane - bicycle facilities that share the lane with vehicular traffic. Sharrows are used when there is not enough space within the roadway for a bike lane, and the roadway is specifically designated for shared use. Sharrows work best on low volume or low speed streets that connect together sections of the overall bicycle network. Sharrows should include sharrow roadway markings.

Transportation trail or shared use path - Trails are separate paths that allow bicycles and pedestrians (including, in some cases, roller bladers, skaters, manual and motorized wheelchair users) and other non-motorized traffic. Two subcategories of trails/shared use paths include Side Path Trails, which run parallel to roadways, and Off Road Trails, which have their own alignment independent of any roadways. Trails are not sidewalks, which are intended for pedestrian use only. Off Road Trails included in this layer serve a transportation purpose (i.e. not purely recreational). For example, this category would not include loop trails in parks used solely for recreational purposes.

This map is created by Baltimore City Department of Transportation GIS group for the Baltimore Marathon (Running Festival) Routes & Road Closures, taking place on October 19, 2019.