Transit Network

Transit Network

The transit network is made up of three core components: transit lines, transit modes, and transit fares. The transit lines were built GTFS feeds from around 2015. The lines are coded with a mode (see below) and serve a series of stop nodes. Transit fares are coded according to Cube's TrnBUILD program (see below):

1. Transit Line File

Transit Line File

The transit lines are specified in a files ending with the extension .lin, organized by transit operator and line-haul mode. A name is assigned to each route based on the operator mode and a description of the route, usually the line number and the direction of the route if necessary. Attributes of the transit lines include runtime, stop node sequence, line-haul mode, and headways by time period (HEADWAY[1-5] which refer to Early AM, AM Peak, Midday, PM Peak, and Evening respectively). The sequence of nodes specify the path of the route, where the node numbers correspond to the nodes in the highway network. Consult the Cube manual for details on the specification of the transit line files. Fields or attributes present for each route in the line file are given below:

Cube Key	GTFS Key	Details
NAME	agency_id + route_id +time_period +direction_id + shape_id Concatenate, separated by an underscore (“_”)
agency_id	translated to transit operator integer (see next table for dictionary)
LONGNAME	route_long_name
USERA1	agency_id, GTFS file name (when agency_id is missing)	Transit operator string
USERA2	Line haul mode	See dictionary, crosswalk below
HEADWAY	headway_secs / 60	Integer
MODE	route_type	See dictionary, crosswalk below
FARESYSTEM	N/A	See dictionary, value is a function of MODE
ONEWAY	N/A	Should always be set to “T” (for TRUE)
OPERATOR	agency_id, GTFS file name	Transit operator integer (see next table for dictionary)
SHORTNAME	route_short_name
VEHICLETYPE	See dictionary, value is a function of MODE
N	shape_id	Travel model node IDs, with a leading “-” (to make the number negative) to indicate a shape point where the bus does not stop
ACCESS	pickup_type, dropoff_type
RUNTIME	Total travel time from start node to end node, calculated by adding all the NNTIMEs for the rail modes
NNTIME	stop_times Calculated from GTFS stop to stop travel time, in minutes

Transit Modes

Line-haul Mode	Description
10 - 79	Local bus
80 - 99	Express bus
100 - 109	Ferry service
110 -119	Light rail
120 -129	Heavy rail
130 -139	Commuter rail

The following transit modes are defined based on the Open511 attributes (but not completely, since they came from the GTFS database predecessor, the Regional Transit Database). These modes represent combinations of operators and technology.

TM2_operator	agency_name	TM2_mode	TM2_line_haul_name	faresystem
30	AC Transit	84	Express bus	9
30	AC Transit	30	Local bus	9
30	AC Transit	30	Local bus	11
5	ACE Altamont Corridor Express	133	Commuter rail	1
26	Bay Area Rapid Transit	120	Heavy rail	2
3	Blue & Gold Fleet	103	Ferry service	13
3	Blue & Gold Fleet	103	Ferry service	14
3	Blue & Gold Fleet	103	Ferry service	12
17	Caltrain	130	Commuter rail	3
23	Capitol Corridor	131	Commuter rail	4
19	Cloverdale Transit	63	Local bus	7
17	Commute.org Shuttle	14	Local bus	46
15	County Connection	86	Express bus	16
15	County Connection	42	Local bus	15
15	County Connection	42	Local bus	17
10	Emery Go-Round	12	Local bus	18
28	Fairfield and Suisun Transit	92	Express bus	10
28	Fairfield and Suisun Transit	52	Local bus	10
35	Golden Gate Transit	87	Express bus	8
20	Golden Gate Transit	101	Ferry service	19
20	Golden Gate Transit	101	Ferry service	20
35	Golden Gate Transit	70	Local bus	8
99	MVgo Mountain View	16	Local bus	21
39	Marin Transit	71	Local bus	23
39	Marin Transit	71	Local bus	24
21	Petaluma Transit	68	Local bus	47
13	Rio Vista Delta Breeze	52	Local bus	5
6	SamTrans	80	Express bus	6
6	SamTrans	24	Local bus	6
25	San Francisco Bay Ferry	101	Ferry service	28
25	San Francisco Bay Ferry	101	Ferry service	30
25	San Francisco Bay Ferry	101	Ferry service	31
25	San Francisco Bay Ferry	101	Ferry service	32
25	San Francisco Bay Ferry	101	Ferry service	29
22	San Francisco Municipal Transportation Agency	110	Light rail	25
22	San Francisco Municipal Transportation Agency	20	Local bus	25
22	San Francisco Municipal Transportation Agency	21	Local bus	26
1	Santa Rosa CityBus	66	Local bus	33
12	SolTrans	91	Express bus	35
12	SolTrans	49	Local bus	34
12	SolTrans	49	Local bus	35
19	Sonoma County Transit	63	Local bus	7
7	Stanford Marguerite Shuttle	13	Local bus	22
4	Tri Delta Transit	95	Express bus	36
4	Tri Delta Transit	44	Local bus	37
4	Tri Delta Transit	44	Local bus	36
36	Union City Transit	38	Local bus	38
31	VTA	81	Express bus	40
31	VTA	81	Express bus	41
31	VTA	111	Light rail	41
31	VTA	28	Local bus	41
31	VTA	28	Local bus	39
14	Vacaville City Coach	56	Local bus	48
38	Vine (Napa County)	94	Express bus	43
38	Vine (Napa County)	60	Local bus	42
38	Vine (Napa County)	60	Local bus	44
37	WestCat (Western Contra Costa)	90	Express bus	49
37	WestCat (Western Contra Costa)	90	Express bus	50
37	WestCat (Western Contra Costa)	46	Local bus	49
24	Wheels Bus	17	Local bus	45

Auxiliary Modes

Auxiliary Mode	Description
1	walk access connector Walk from centroid to auxiliary rail node/bus stop
2	drive access connector Drive from centroid to drive auxiliary node
3	stop-to-stop or stop-to-station transfer link Walk transfer link between transit stops
4	drive access funnel link Transfer between drive auxiliary node and station platform node
5	walk access funnel link Transfer between walk auxiliary node and station platform node
6	walk egress connector Walk from auxiliary rail node/bus stop to centroid
7	drive egress connector Drive from auxiliary node to centroid
8	Not used
9	Not used

Transit Fares

Transit fares are modeled in Cube's Public Transport (PT) program as follows:

• Each transit mode is assigned a fare system in the Cube factor files
• Each fare system is defined in the fares.far fare file
• Each fare system is either FROMTO (fare zone based) or FLAT (initial + transfer in fare)
• For FROMTO fare systems:
  1. Each stop node is assigned a FAREZONE ID in the master network
  2. The fare is looked up from the fare matrix (fareMatrix.txt), which is a text file with the following columns: MATRIX ZONE_I ZONE_J VALUE
  3. The fare to transfer in from other modes is defined via the FAREFROMFS array (of modes) in the fares.far file
• For FLAT fare systems:
  1. The initial fare is defined via the IBOARDFARE in the fares.far file
  2. The fare to transfer in from other modes is defined via the FAREFROMFS array (of modes) in the fares.far file