Transit Access and Commute Mode
Traditionally, transit deserts are defined by the number of transit stops in an area, or by buffered distances in relation to transit stops. However, this approach does not consider the frequency of service in identifying areas with low transit access, nor does it consider how that service frequency may vary across time of day. This use case pulls in such data on transit frequency of service by time of day and layers it with commute pattern and vehicle ownership data.
VALUE PROPOSITION
Combined, these data are useful in TDM program planning in terms of targeting areas to deploy programs or raise awareness. 511NY Rideshare Carpool program awareness efforts could be focused in areas with high drive-alone commute modes and low carpool rates. Efforts to make commuters aware of transit options and guaranteed ride home (GRH) can be targeted at areas with frequent service during peak hours. Micro transit options can be prioritized for areas identified as transit deserts—areas with low-frequency service—to connect commuters to frequent service lines, especially in places that also exhibit low household vehicle ownership rates.
TARGET AUDIENCE
Region 11 transportation planners and engineers, 511NY Rideshare NYSDOT staff and contractor staff, and Region 11 transit agencies could benefit from the information provided by this use case, as it enables data-driven decision making for TDM and transit planning.
GEOGRAPHIC EXTENT
Currently, this use case is limited to Region 11. An expansion of the transit departures data to the state is currently in progress. Commute and vehicle ownership data are also available statewide.
TIMEFRAME
Transit departures are based on GTFS feeds from September 2021. Commute and vehicle ownership data are 2019 estimates.
UPDATE FREQUENCY
Update frequency to be determined. Update frequency would be limited to GTFS feed updates, which vary from agency to agency. Commute and vehicle ownership data are available at a less granular temporal scale and may only be able to be updated once per year, at most.
ACCESS
This use case is publicly available and can be accessed via: