About this Dataset

MTA Transit Oriented Development (TOD) Data

*** DISCLAIMER - This web page is a public resource of general information. The Maryland Mass Transit Administration (MTA) makes no warranty, representation, or guarantee as to the content, sequence, accuracy, timeliness, or completeness of any of the spatial data or database information provided herein. MTA and partner state, local, and other agencies shall assume no liability for errors, omissions, or inaccuracies in the information provided regardless of how caused; or any decision made or action taken or not taken by any person relying on any information or data furnished within. ***

This dataset assesses rail station potential for different forms of transit oriented development (TOD). A key driver of increased transit ridership in Maryland, TOD capitalizes on existing rapid transit infrastructure. The online tool focuses on the MTA’s existing MARC Commuter Rail, Metro Subway, and Central Light Rail lines and includes information specific to each station.

The goal of this dataset is to give MTA planning staff, developers, local governments, and transit riders a picture of how each MTA rail station could attract TOD investment. In order to make this assessment, MTA staff gathered data on characteristics that are likely to influence TOD potential. The station-specific data is organized into 6 different categories referring to transit activity; station facilities; parking provision and utilization; bicycle and pedestrian access; and local zoning and land availability around each station.

As a publicly shared resource, this dataset can be used by local communities to identify and prioritize area improvements in coordination with the MTA that can help attract investment around rail stations.

You can view an interactive version of this dataset at geodata.md.gov/tod.

** Ridership is calculated the following ways:
Metro Rail ridership is based on Metro gate exit counts.
Light Rail ridership is estimated using a statistical sampling process in line with FTA established guidelines, and approved by the FTA.
MARC ridership is calculated using two (2) independent methods:
Monthly Line level ridership is estimated using a statistical sampling process in line with FTA established guidelines, and approved by the FTA. This method of ridership calculation is used by the MTA for official reporting purposes to State level and Federal level reporting.
Station level ridership is estimated by using person counts completed by the third party vendor. This method of calculation has not been verified by the FTA for statistical reporting and is used for scheduling purposes only. However, because of the granularity of detail, this information is useful for TOD applications.
*Please note that the monthly level ridership and the station level ridership are calculated using two (2) independent methods that are not interchangeable and should not be compared for analysis purposes.
Organization: State of Maryland
Last updated: 2020-11-10T17:24:32.664202
Tags: development, map, marc, metro, mta, oriented, station, tod, train, transit, transportation

Tables

Table 1

@usgov.state_of_maryland_mta_transit_oriented_development_tod_data.table_1

82.65 kB
93 rows
80 columns

CREATE TABLE table_1 (
  "station" VARCHAR,
  "station_id" BIGINT,
  "station_name" VARCHAR,
  "rail_lines_served" VARCHAR,
  "jurisdiction" VARCHAR,
  "tod_place_type" VARCHAR,
  "area_population_2010" DOUBLE  -- Area Population (2010),
  "station_type" VARCHAR,
  "transit_score" DOUBLE,
  "station_facility_score" DOUBLE,
  "parking_score" DOUBLE,
  "bike_access_score" DOUBLE,
  "ped_access_score" DOUBLE,
  "tod_zoning_score" DOUBLE,
  "development_market" DOUBLE,
  "total_rail_lines" DOUBLE,
  "modes_served" DOUBLE,
  "transit_connections" VARCHAR,
  "connecting_bus_routes" VARCHAR,
  "connecting_bus_routes_text" VARCHAR  -- Connecting Bus Routes (Text),
  "weekday_ridership_marc_penn" DOUBLE  -- Weekday Ridership: MARC Penn,
  "weekday_ridership_marc_camden" DOUBLE  -- Weekday Ridership: MARC Camden,
  "weekday_ridership_marc_brunswick" DOUBLE  -- Weekday Ridership: MARC Brunswick,
  "weekday_ridership_metro" DOUBLE  -- Weekday Ridership: Metro,
  "weekday_ridership_light_rail" DOUBLE  -- Weekday Ridership: Light Rail,
  "weekend_ridership_marc_penn" VARCHAR  -- Weekend Ridership: MARC Penn,
  "weekend_ridership_marc_camden" VARCHAR  -- Weekend Ridership: MARC Camden,
  "weekend_ridership_marc_brunswick" VARCHAR  -- Weekend Ridership: MARC Brunswick,
  "weekend_ridership_metro" DOUBLE  -- Weekend Ridership: Metro,
  "weekend_ridership_light_rail" VARCHAR  -- Weekend Ridership: Light Rail,
  "frequency_of_service_weekday_marc_penn" DOUBLE  -- Frequency Of Service Weekday: MARC Penn,
  "frequency_of_service_weekday_marc_camden" DOUBLE  -- Frequency Of Service Weekday: MARC Camden,
  "frequency_of_service_weekday_marc_brunswick" VARCHAR  -- Frequency Of Service Weekday: MARC Brunswick,
  "frequency_of_service_weekday_metro" DOUBLE  -- Frequency Of Service Weekday: Metro,
  "frequency_of_service_weekday_light_rail" DOUBLE  -- Frequency Of Service Weekday: Light Rail,
  "frequency_of_service_weekend_marc_penn" DOUBLE  -- Frequency Of Service Weekend: MARC Penn,
  "frequency_of_service_weekend_marc_camden" VARCHAR  -- Frequency Of Service Weekend: MARC Camden,
  "frequency_of_service_weekend_marc_brunswick" VARCHAR  -- Frequency Of Service Weekend: MARC Brunswick,
  "frequency_of_service_weekend_metro" DOUBLE  -- Frequency Of Service Weekend: Metro,
  "frequency_of_service_weekend_light_rail" DOUBLE  -- Frequency Of Service Weekend: Light Rail,
  "track_crossing" VARCHAR,
  "schedule_information" VARCHAR,
  "route_information" VARCHAR,
  "ticket_booth_machine" VARCHAR,
  "shelter" VARCHAR,
  "benches" VARCHAR,
  "public_restrooms" VARCHAR,
  "public_phones" VARCHAR,
  "parking_spots_regular" DOUBLE,
  "parking_fee" VARCHAR,
  "parking_spots_ada" DOUBLE,
  "evc_charge_stations" DOUBLE,
  "evc_charge_stations_occupied" DOUBLE,
  "vehicles_parked_2010" DOUBLE  -- Vehicles Parked (2010),
  "vehicles_parked_2014" DOUBLE  -- Vehicles Parked (2014),
  "utilization_rate_2014" DOUBLE  -- Utilization Rate (2014),
  "spaces_relative_to_number_of_average_daily_riders_week_c7070b80" DOUBLE  -- Spaces Relative To Number Of Average Daily Riders (Weekday) Total Lines,
  "spaces_relative_to_number_of_average_daily_riders_week_55d955e3" DOUBLE  -- Spaces Relative To Number Of Average Daily Riders (Weekend) Total Lines,
  "spaces_relative_to_other_stations_on_the_same_line" DOUBLE,
  "intersection_density_1_mile_diameter" DOUBLE  -- Intersection Density (1 Mile Diameter),
  "short_trip_opportunity_analysis_1_mile_buffer" DOUBLE  -- Short Trip Opportunity Analysis (1 Mile Buffer),
  "number_of_bicycle_racks" DOUBLE,
  "type_of_bicycle_racks" VARCHAR,
  "number_of_bicycle_lockers" DOUBLE,
  "number_of_bicycle_lockers_occupied" DOUBLE,
  "locally_designated_tod" VARCHAR,
  "zoning_summary" VARCHAR,
  "local_zoning_descriptions" VARCHAR,
  "area_master_plans" VARCHAR,
  "residential_alterations_units" DOUBLE  -- Residential Alterations (units),
  "residentail_alterations_permits" DOUBLE  -- Residentail Alterations (permits),
  "residential_new_construction_permits" DOUBLE  -- Residential New Construction (permits),
  "residential_new_construction_units" DOUBLE  -- Residential New Construction (units),
  "non_residential_alterations_permits" DOUBLE  -- Non Residential Alterations (permits),
  "non_residentail_new_contruction_permits" DOUBLE  -- Non Residentail New Contruction (permits),
  "mixed_use_new_construction_permits" DOUBLE  -- Mixed-Use New Construction (permits),
  "mixed_use_new_construction_units" DOUBLE  -- Mixed-Use New Construction (units),
  "count_of_md_property_view_parcels" DOUBLE,
  "cumulative_composite_score_yearblt_score_x_sqftstrc_score" DOUBLE  -- Cumulative Composite Score (YEARBLT Score X SQFTSTRC Score),
  "location" VARCHAR
);