Welcome to the TSIP Project Webinar

Planning Technical Working Group28 July 20092 – 3:30 pm

Agenda

Use Case DiscussionEnumeration of Needs

◦Data◦Functional◦Output Format◦Terms to Define / Clarify

Use Cases for Regional Transit Planning

UC #1: Corridor Studies

UC #2: Long Range Planning and Air Quality Analysis

UC #3: Marketing Studies◦Accessibility◦Competitive Index

UC #4: Transit Development Plan

Use Case #1: Corridor Study

Stakeholders: NYSDOT, Counties, Municipalities, Transit Providers, MPO

Description: A corridor study for determining long-term improvements that should be made on a corridor. Potential improvements include: additional roadway capacity, roadway operational improvements, additional fixed-route bus service, and high capacity transit service, i.e., BRT

Use Case #2: TIP/RTP/AQ Conformity

Stakeholders: NYMTC, NYSDOT, Counties, Municipalities, Transit Providers

Description: TIP and RTP updates that provide improvements to the transit network. The short and long term changes need to get incorporated into the NYBPM model so that mobile source emissions can be accurately modeled.

Use Case #3: Marketing Studies

Stakeholders: NYSDOT, Counties, Municipalities, Transit Providers, MPO

Description: Marketing Studies are targeted towards increasing and retaining the ridership of existing transit systems. Marketing studies involve the understanding of the attitudes of potential and existing transit customers and what service quality attributes are important to the region’s potential and existing customers.

Use Case #4: Transit Development Plan

Stakeholders: NYSDOT, Counties, Municipalities, Transit Providers, MPO

Description: Transit Development Plans identify areas in which transit will be amenable. Questions that need to be addressed – ◦Are Pop/Job Density, socioeconomic characteristics

of area optimal/sufficient? ◦ Is Land Use optimal/ sufficient? ◦Which modes will thrive?

Planning Data Needs #1 & 2

1.  Need to access transit service information by temporal categories.

 2.  Need to access scheduled transit service information

from operators byRoutes, routes by route direction, trips, patterns, modes

◦ Activation and deactivation dates (schedule version)◦ Revisions, special schedules and detours

Transit Stops including complex stops, amenities, passenger access components, portals

Fare and transfer policies (by operator and among operators)

Planning Data Needs #3

3.  Need to access planning data including:◦Ridership (bus and rail)◦Passenger loads, boardings and alightings◦Span of service◦Accessibility◦Service type◦Transfer connection opportunities◦Running times◦Headways / Frequencies◦Service quality data (indicators such as schedule

adherence, quality index)◦Fare policies and implementation◦Ridership origin-destination survey data

Planning Data Needs #4

4.  Need to access planning data by the following Transit Service information categories

Routes (by route direction) or Transit Path (by stopping pattern) ◦ Mode◦ Geometry and transit features (e.g., stops)◦ Average running times (scheduled vs. actual)◦ Headways / Frequency◦ Service type (local, express, etc.)◦ Span of service◦ Average ridership and load◦ Accessibility of vehicles assigned to route◦ Fare Policy for route

Planning Data Needs #4 cont.

Trips (by route) Geometry and transit features (e.g., stops)◦ (scheduled / actual) running time by transit path◦Service Type◦Load and ridership◦Boardings / alightings at each stop along the trip◦Accessibility of vehicle operating trip◦Coordinated transfers between trips (Event

Connection)◦Actual fare for trip or trip segment

Planning Data Needs #4 cont.

Transit Stops Location◦Plant components including:  portals, passenger

access components, amenities◦Transfer opportunities (Transfer Cluster)◦Service Type of routes that serve stop◦Span of service (at stop)◦Boardings/Alightings at stop◦Ridership (for example, entering each station)◦Headway / Frequency of service at the stop◦Fare policy in effect at Stop (e.g., gated or open)◦Transfer fare in effect for transfer at stop

Planning Data Needs #5

5.  Need to compare transit service information and planning data from different time periods◦New service◦Eliminated service◦Expanded service◦Changed service

Functional Needs

Functional Needs◦ Query by Transit Data Concept (SDP data concepts)◦ Query by Agency (SDP or extension)◦ Query by temporal and spatial analytical parameters

Temporal categories include year, period, day type/date, time Spatial analysis includes:

◦ Points in polygon; Paths in Polygon

◦ Ability to compare two identical data sets and identify changes Save a request to use at a later date

◦ Ability to add new data concepts or adapt existing data concepts from a data dictionary

◦ Web service to share Data Catalog with other regional “Portals”

Data Format Needs

Major planning tool◦NYBPM◦Others?

Other formats◦Comma Separated Values (csv) for Excel◦XML?

Terms We Need to Define & Clarify?

Ridership◦ Rider Class / Classification / Category◦ Passenger Load, Boardings, Alightings◦ Revenue passenger / NTD reporting

Headway◦ Service Headway◦ Average Headway◦ Effective Headway

Frequency◦ Average Frequency◦ ??

Origin-Destination dataSpan of Service (for agency or route)