Skip to content

Networks

This page describes the components that make up the input ABM3 networks, which include the highway (i.e., roadways), transit and active transportation networks.

To learn how ABM3 handles the networks, refer to the Network Import from TNED page.

Transportation Network Editing Database (TNED)

The ABM3 networks are edited, maintained, and generated via SANDAG’s internal Transportation Network Editing Database (TNED) system, which leverages ESRI’s ArcGIS Enterprise and is hosted on an enterprise geodatabase. The TNED system, via an ETL (Extract, Load, Transform) process, outputs the input ABM3 networks in a variety of different formats including file geodatabase, CSV, and shapefiles.

When describing the ABM3 networks, this page is specifically referring to the networks in their post-ETL state. A typical TNED ETL network directory includes the following:

Note: Click on file name for additional details.

File Name File Format Description
EMMEOutputs.gdb File Geodatabase Houses a variety of feature classes and tables for the different ABM3 networks: highway, transit, and active transportation.
info Directory A directory that houses TNED ETL logs, network QAQC reports, and configuration file utilized to generate the network.

Only for reference. Not used for modeling purposes.
SANDAG_Bike_Net.shp Shapefile The links (arcs) of the active transportation network.
SANDAG_Bike_Node.shp Shapefile The nodes of the active transportation network.
special_fares.txt Text File Configures the zone-based fare scheme of the Coaster.
timexfer_{TOD}.csv CSV Timed transfer table between the Coaster and feeder buses. There is a file for each of the 5 TODs (time-of-day), which are EA (early AM), AM, MD (midday), PM, and EV (evening).
trrt.csv CSV List of all transit routes in network and information on their mode, frequencies, hours of service, and fares.
trlink.csv CSV Ordered sequential list of underlying network links (arcs) for each transit route in the network.
trstop.csv CSV List of stops for each transit route in the network.

EMME Outputs File Geodatabase

The EMMEOutputs.gdb is a file geodatabase that gets generated by the TNED ETL process. It houses link and node feature classes along with tables. The contents of the EMMEOutputs.gdb is as follows:

Note: Click on file names for additional details.

File Name File Format Description
Bike_Net_{year}_{alternative} File Geodatabase Feature Class The links (arcs) of the active transportation network for a given year and alternative (i.e., build, no build).

The shapefile version of this feature class (outside the geodatabase) is the version that gets used as an input.
Bike_Node_{year}_{alternative} File Geodatabase Feature Class The nodes of the active transportation network for a given year and alternative (i.e., build, no build).

The shapefile version of this feature class (outside the geodatabase) is the version that gets used as an input.
ERROR_RouteSegmentMissingInHwyNetOrRailNet File Geodatabase Table A list of roadway or rail segments flagged as being part of a transit route even though the specific segment may not be part of the roadway or rail network. Note that these records have already been checked and have been noted to be warnings rather than fatal errors.
TNED_HwyNet File Geodatabase Feature Class Road segment line feature class.
TNED_HwyNodes File Geodatabase Feature Class Road segment node feature class.
TNED_RailNet File Geodatabase Feature Class Rail (Transit) segment line feature class.
TNED_RailNodes File Geodatabase Feature Class Rail (Transit) segment node feature class.
TransitRoute File Geodatabase Feature Class Transit route feature class.
trrt File Geodatabase Table List of all transit routes in network and information on their mode, frequencies, hours of service, and fares.

The CSV version of this feature class (outside the geodatabase) is the version that gets used as an input.
trlink File Geodatabase Table Ordered sequential list of underlying network links (arcs) for each transit route in the network.

The CSV version of this feature class (outside the geodatabase) is the version that gets used as an input.
trstop File Geodatabase Table List of stops for each transit route in the network.

The CSV version of this feature class (outside the geodatabase) is the version that gets used as an input.
Turns File Geodatabase Table Turn prohibitor table listing vehicle turn movements that are not allowed.

TNED Transit Route Segment Mismatch Table

The ERROR_RouteSegmentMissingInHwyNetOrRailNet lists mismatches between the TransitRoute feature class and both the TNED_RailNet and TNED_HwyNet feature classes. If a transit route is coded along a rail or roadway segment that is not explicitly included in the network, it will flag the record. It should be noted that some records serve more as warnings rather than fatal errors. There are certain nuances, for example, for a proposed roadway that may have an uncertain horizon year and if a future transit route utilizes the roadway, the TNED ETL process will bring in the roadway as a bus-only street (no private vehicles allowed) as a fallback. This may be common in areas of the San Diego region where proposed development is far off in the future.

Attribute Description
OBJECTID An ObjectID is a unique, not null integer field used to uniquely identify rows in tables in a geodatabase.
TNEDSegmentGlobalID A unique TNED-generated globally unique identifier for records from the TNEDSegment feature class.
TCOVED_ID SANDAG-assigned link ID
SegmentInfoGlobalID A unique TNED-generated globally unique identifier for records from the SegmentInfo table.
Year Initial year of segment.
ProjectID Associated project code. If no project code is associated with segment, a value of 0 will be listed.
RouteID_from_TransitRoute The RouteID of the transit route using segment. The RouteID is the concatenated Route, direction and configuration of the transit route. This unique ID is best read from right to left as the last 2 digits refer to the Configuration, the 3rd digit from the right refers to the Direction (1 or 2), and the remaining leftmost digits refer to the Route. For example, 398212 is configuration 12 in the outbound (2 direction) of route 398.
Route_ID_from_trrt Sequential unique transit route identifier. This is not the same as the route number. To determine which Route_ID corresponds to which transit route, refer to the trrt.csv file.

The TNED_HwyNet feature class contains all the roadway links (arcs) of the network.

Attribute Description
OBJECTID An ObjectID is a unique, not null integer field used to uniquely identify rows in tables in a geodatabase.
LENGTH Length of link in miles
HWYCOV0_ID SANDAG-assigned link ID
SPHERE Jurisdiction sphere of influence where value corresponds to either the jurisdiction code (1-18 excluding 14), the City of San Diego CPA Code (1400s), or the County of San Diego CPA Code (1900s):
1 = Carlsbad
2 = Chula Vista
3 = Coronado
4 = Del Mar
5 = El Cajon
6 = Encinitas
7 = Escondido
8 = Imperial Beach
9 = La Mesa
10 = Lemon Grove
11 = National City
12 = Oceanside
13 = Poway
15 = San Marcos
16 = Santee
17 = Solana Beach
18 = Vista
1401 = Balboa Park
1402 = Barrio Logan
1403 = Carmel Mountain Ranch
1404 = Centre City
1405 = Sabre Springs
1406 = Clairemont Mesa
1407 = East Elliott
1408 = Greater Golden Hill
1409 = Miramar Ranch North
1410 = La Jolla
1412 = Linda Vista
1414 = Midway-Pacific Highway
1415 = Mira Mesa
1417 = Mission Bay Park
1418 = Mission Beach
1419 = Mission Valley
1420 = Navajo
1421 = Carmel Valley
1423 = Ocean Beach
1424 = Old San Diego
1425 = Otay Mesa-Nestor
1426 = Otay Mesa
1427 = Pacific Beach
1428 = Greater North Park
1429 = Rancho Penasquitos
1430 = Peninsula
1431 = Rancho Bernardo
1432 = San Pasqual
1433 = San Ysidro
1434 = Scripps Miramar Ranch
1435 = Serra Mesa
1438 = College Area
1439 = Tijuana River Valley
1440 = Torrey Pines
1441 = University
1442 = Uptown
1444 = Skyline-Paradise Hills
1447 = Tierrasanta
1448 = Torrey Hills
1449 = Fairbanks Country Club
1450 = Kearny Mesa
1455 = Via De La Valle
1456 = Mid-City:City Heights
1457 = Mid-City:Eastern Area
1458 = Mid-City:Kensington-Talmadge
1459 = Mid-City:Normal Heights
1461 = Del Mar Mesa
1462 = Torrey Highlands
1463 = Los Penasquitos Canyon Preserve
1464 = Black Mountain Ranch
1465 = Pacific Highlands Ranch
1466 = NCFUA Subarea 2
1467 = NCFUA Reserve
1468 = Southeastern:Encanto Neighborhoods
1469 = Southeastern:Southeastern San Diego
1481 = Rancho Encantada
1482 = Miramar Air Station
1483 = Lindbergh Field
1485 = Scripps Reserve
1486 = Harbor
1488 = Flower Hill
1491 = 32nd Street Naval Station
1901 = Alpine
1902 = Central Mountain
1903 = Crest-Dehesa
1904 = Desert
1906 = Jamul-Dulzura
1907 = Lakeside
1908 = Mountain Empire
1909 = North County Metro
1911 = Otay
1912 = Pala-Pauma
1914 = Ramona
1915 = San Dieguito
1918 = Sweetwater
1919 = Valle De Oro
1920 = Valley Center
1921 = Spring Valley
1922 = Julian
1951 = North Mountain
1952 = Bonsall
1953 = Fallbrook
1954 = Pendleton-De Luz
1955 = Rainbow
1998 = Barona
1999 = County Islands
NM Street name
AN A node number. The value corresponds to the HNODE value of the connecting "from node" at the link's starting point.
BN B node number. The value corresponds to the HNODE value of the connecting "to node" at the link's ending point.
COJUR Count jurisidiction code where:
1 = Carlsbad
2 = Chula Vista
3 = Coronado
4 = Del Mar
5 = El Cajon
6 = Encinitas
7 = Escondido
8 = Imperial Beach
9 = La Mesa
10 = Lemon Grove
11 = National City
12 = Oceanside
13 = Poway
14 = San Diego City
15 = San Marcos
16 = Santee
17 = Solana Beach
18 = Vista
19 = San Diego County
20 = Caltrans
COSTAT Count station number
COLOC Count location code where:
0 = The count was taken on another link but is being applied to this link
1 = The count was taken on this link
DIR Link direction where:
0 = Center City Walk Links
1 = Northbound
2 = Westbound
3 = Southbound
4 = Eastbound
JUR Roadway link jurisdiction where:
1 = State Facilities
2 = Congestion Management Plan (CMP)
3 = Regional Arterial System (RAS)
4 = Regionally Significant Arterials (RSA)
5 = Local Facilties
6 = Local Road
FFC Federal functional class where:
1 = Freeway
2 = Prime Arterial
3 = Major Arterial
4 = Collector
5 = Local Collector
6 = Rural Collector
7 = Local (non circulation element) Road
8 = Freway Connector Ramp
9 = Local Ramp
11 = Rail Line
12 = Bus Street
13 = ADT (Average Daily Traffic) Link
ASPD Adjusted link speed in mph
YR The year the link opened to traffic
PROJ Project ID in the regional roadway network. The Project ID has an associated year value which indicates when the link is open to traffic.
FC Roadway functional class where:
1 = Freeway
2 = Prime Arterial
3 = Major Arterial
4 = Collector
5 = Local Collector
6 = Rural Collector
7 = Local (non circulation element) Road
8 = Freeway Connector Ramp
9 = Local Ramp
10 = TAZ Connector
11 = Rail Line
12 = Bus Street, Center City Walk Links
99 = Transfer Walk Links
HOV Roadway Operation Restriction where:
1 = General Purpose
2 = 2+ HOV (Operates as HOT if Toll by TOD attributes > 0)
3 = 3+ HOV (Operates as HOT if Toll by TOD attributes > 0)
4 = Toll Lane (Toll by TOD attributes should also be adjusted)
AMTRUCK AM Truck Restriction where:
1 = All Vehicle Classes
2 = HHDT Excluded
3 = MHDT & HHDT Excluded
4 = LHDT, MHDT & HHDT Excluded (All Trucks)
5 = HHDT Only
6 = MHDT & HHDT Only
7 = LHDT, MHDT & HHDT Only (Truck Only)
EATRUCK Early AM Truck Restriction where:
1 = All Vehicle Classes
2 = HHDT Excluded
3 = MHDT & HHDT Excluded
4 = LHDT, MHDT & HHDT Excluded (All Trucks)
5 = HHDT Only
6 = MHDT & HHDT Only
7 = LHDT, MHDT & HHDT Only (Truck Only)
MDTRUCK Midday Truck Restriction where:
1 = All Vehicle Classes
2 = HHDT Excluded
3 = MHDT & HHDT Excluded
4 = LHDT, MHDT & HHDT Excluded (All Trucks)
5 = HHDT Only
6 = MHDT & HHDT Only
7 = LHDT, MHDT & HHDT Only (Truck Only)
PMTRUCK PM Truck Restriction where:
1 = All Vehicle Classes
2 = HHDT Excluded
3 = MHDT & HHDT Excluded
4 = LHDT, MHDT & HHDT Excluded (All Trucks)
5 = HHDT Only
6 = MHDT & HHDT Only
7 = LHDT, MHDT & HHDT Only (Truck Only)
EVTRUCK Evening Truck Restriction where:
1 = All Vehicle Classes
2 = HHDT Excluded
3 = MHDT & HHDT Excluded
4 = LHDT, MHDT & HHDT Excluded (All Trucks)
5 = HHDT Only
6 = MHDT & HHDT Only
7 = LHDT, MHDT & HHDT Only (Truck Only)
SPD Link speed in mph
WAY One or two way roadway indicator where:
1 = One-way road
2 = Two-way road
Note that the TOD lane attributes (e.g., ABLNA, BALNP, etc.) should be appropriately adjusted.
MED Median type where:
1 = No median
2 = Raised or fixed median
3 = Continuous left turn center lane
TOLLEA Early AM Toll Cost in cents where for example:
1 = $0.01 per mile
200 = $2.00 per mile
TOLLA AM Toll Cost in cents where for example:
1 = $0.01 per mile
200 = $2.00 per mile
TOLLMD Midday Toll Cost in cents where for example:
1 = $0.01 per mile
200 = $2.00 per mile
TOLLP PM Toll Cost in cents where for example:
1 = $0.01 per mile
200 = $2.00 per mile
TOLLEV Evening Toll Cost in cents where for example:
1 = $0.01 per mile
200 = $2.00 per mile
ABLNEA Early AM number of lanes in the FROM-TO direction.
ABLNA AM number of lanes in the FROM-TO direction.
ABLNMD Midday number of lanes in the FROM-TO direction.
ABLNP PM number of lanes in the FROM-TO direction.
ABLNEV Evening AM number of lanes in the FROM-TO direction.
ABAU Number of auxiliary lanes in the FROM-TO direction
ABCNT Intersection control type at the TO end of the link:
0 = No Control
1 = Traffic Signal
2 = All-Way Stop Sign
3 = Two-Way Stop Sign
4 = Ramp Meter
5 = Ramp Meter with HOV lane meter
6 = Light Rail Crossing
7 = Toll Booth
9 = Prevent Control
ABTL Intersection approach through lanes at the TO end of the link:
0~4 = number of through lanes
9 = No dedicated lane for the movement
ABRL Intersection approach right-turn lanes at the TO end of the link:
0~2 = number of through lanes
7 = Free
8 = Prohibited
9 = No dedicated lane for the movement
ABLL Intersection approach left-turn lanes at the TO end of the link:
0~2 = number of through lanes
9 = No dedicated lane for the movement
ABGC Intersection green-to-cycle ratio at the TO end of the link (%)
ABPLC Per-lane capacity per hour in the TO direction of the link
ABCPEA Early AM period mid-link capacity in the TO direction of the link
ABCPA AM period mid-link capacity at the TO end of the link
ABCPMD Midday period mid-link capacity at the TO end of the link
ABCPP PM period mid-link capacity at the TO end of the link
ABCPEV Evening period mid-link capacity at the TO end of the link
ABCXEA Early AM period intersection-approachy capacity at the TO end of the link
ABCXA AM period intersection-approach capacity at the TO end of the link
ABCXMD Midday period intersection-approach capacity at the TO end of the link
ABCXP PM period intersection-approach capacity at the TO end of the link
ABCXEV Evening period intersection-approach capacity at the TO end of the link
ABCHEA Early AM period hourly mid-link capacity at the TO end of the link
ABCHA AM period hourly mid-link capacity at the TO end of the link
ABCHMD Midday period hourly mid-link capacity at the TO end of the link
ABCHP PM period hourly mid-link capacity at the TO end of the link
ABCHEV Evening period hourly mid-link capacity at the TO end of the link
ABTMEA Early AM period link time in minutes in the FROM-TO direction
ABTMA AM period link time in minutes in the FROM-TO direction
ABTMMD Midday period link time in minutes in the FROM-TO direction
ABTMP PM period link time in minutes in the FROM-TO direction
ABTMEV Evening period link time in minutes in the FROM-TO direction
ABTXEA Early AM period intersection delay time in the TO end of the link
ABTXA AM period intersection delay time in the TO end of the link
ABTXMD Midday period intersection delay time in the TO end of the link
ABTXP PM period intersection delay time in the TO end of the link
ABTXEV Evening period intersection delay time in the TO end of the link
BALNEA Early AM number of lanes in the TO-FROM direction
BALNA AM number of lanes in the TO-FROM direction
BALNMD Midday number of lanes in the TO-FROM direction
BALNP PM number of lanes in the TO-FROM direction
BALNEV Evening AM number of lanes in the TO-FROM direction
BAAU Number of auxiliary lanes in the TO-FROM direction
BACNT Intersection control type at the FROM end of the link:
0 = No Control
1 = Traffic Signal
2 = All-Way Stop Sign
3 = Two-Way Stop Sign
4 = Ramp Meter
5 = Ramp Meter with HOV lane meter
6 = Light Rail Crossing
7 = Toll Booth
9 = Prevent Control
BATL Intersection approach through lanes at the FROM end of the link:
0~4 = number of through lanes
7 = Free
8 = Prohibited
9 = No dedicated lane for the movement
BARL Intersection approach right-turn lanes at the FROM end of the link:
0~2 = number of through lanes
7 = Free
8 = Prohibited
9 = No dedicated lane for the movement
BALL Intersection approach left-turn lanes at the FROM end of the link:
0~2 = number of through lanes
7 = Free
8 = Prohibited
9 = No dedicated lane for the movement
BAGC Intersection green-to-cycle ratio at the FROM end of the link (%)
BAPLC Per-lane capacity per hour in the FROM direction of the link
BACPEA Early AM period mid-link capacity in the FROM direction of the link
BACPA AM period mid-link capacity at the FROM end of the link
BACPMD Midday period mid-link capacity at the FROM end of the link
BACPP PM period mid-link capacity at the FROM end of the link
BACPEV Evening period mid-link capacity at the FROM end of the link
BACXEA Early AM period intersection-approachy capacity at the FROM end of the link
BACXA AM period intersection-approach capacity at the FROM end of the link
BACXMD Midday period intersection-approach capacity at the FROM end of the link
BACXP PM period intersection-approach capacity at the FROM end of the link
BACXEV Evening period intersection-approach capacity at the FROM end of the link
BACHEA Early AM period hourly mid-link capacity at the FROM end of the link
BACHA AM period hourly mid-link capacity at the FROM end of the link
BACHMD Midday period hourly mid-link capacity at the FROM end of the link
BACHP PM period hourly mid-link capacity at the FROM end of the link
BACHEV Evening period hourly mid-link capacity at the FROM end of the link
BATMEA Early AM period link time in minutes in the TO-FROM direction
BATMA AM period link time in minutes in the TO-FROM direction
BATMMD Midday period link time in minutes in the TO-FROM direction
BATMP PM period link time in minutes in the TO-FROM direction
BATMEV Evening period link time in minutes in the TO-FROM direction
BATXEA Early AM period intersection delay time in the FROM end of the link
BATXA AM period intersection delay time in the FROM end of the link
BATXMD Midday period intersection delay time in the FROM end of the link
BATXP PM period intersection delay time in the FROM end of the link
BATXEV Evening period intersection delay time in the FROM end of the link
HWYSegGUID Highway segment globally unique identifier (GUID)
FXNM Program assigned cross street name at the FROM end of the link
TXNM Program assigned cross street name at the TO end of the link
MINMODE Transit and access mode type where:
1 = Special transfer walk links between certain nearby stops
2 = Walk links in the downtown area
3 = The special TAP connectors
400 = Commuter Rail
500 = Trolley & Light Rail Transit (LRT)
600 = Rapid Freeway
700 = Rapid Arterial
800 = Limited Exrpess Bus
900 = Express Bus
1000 = Local Bus

The minmode is organized by combining transit modes (e.g., 400, 700, 1000, etc.) and walk to transit modes (e.g., 1, 2). For example, a MINMODE value of 1002 is for transit mode local bus (1000) and walk links in the downtown area (2).
SHAPE_Length Length of link in feet.

TNED Roadway Network Nodes Feature Class

The TNED_HwyNodes feature class contains all the nodes of the network.

Attribute Description
OBJECTID An ObjectID is a unique, not null integer field used to uniquely identify rows in tables in a geodatabase.
XNM1 First cross street name
XNM2 Second cross street name
X_COORD Coordinate value of the node in the X direction
Y_COORD Coordinate value of the node in the Y direction
Z_COORD Coordinate value of the node in the Z direction (elevation)
SPHERE Jurisdiction sphere of influence where value corresponds to either the jurisdiction code (1-18 excluding 14), the City of San Diego CPA Code (1400s), or the County of San Diego CPA Code (1900s):
1 = Carlsbad
2 = Chula Vista
3 = Coronado
4 = Del Mar
5 = El Cajon
6 = Encinitas
7 = Escondido
8 = Imperial Beach
9 = La Mesa
10 = Lemon Grove
11 = National City
12 = Oceanside
13 = Poway
15 = San Marcos
16 = Santee
17 = Solana Beach
18 = Vista
1401 = Balboa Park
1402 = Barrio Logan
1403 = Carmel Mountain Ranch
1404 = Centre City
1405 = Sabre Springs
1406 = Clairemont Mesa
1407 = East Elliott
1408 = Greater Golden Hill
1409 = Miramar Ranch North
1410 = La Jolla
1412 = Linda Vista
1414 = Midway-Pacific Highway
1415 = Mira Mesa
1417 = Mission Bay Park
1418 = Mission Beach
1419 = Mission Valley
1420 = Navajo
1421 = Carmel Valley
1423 = Ocean Beach
1424 = Old San Diego
1425 = Otay Mesa-Nestor
1426 = Otay Mesa
1427 = Pacific Beach
1428 = Greater North Park
1429 = Rancho Penasquitos
1430 = Peninsula
1431 = Rancho Bernardo
1432 = San Pasqual
1433 = San Ysidro
1434 = Scripps Miramar Ranch
1435 = Serra Mesa
1438 = College Area
1439 = Tijuana River Valley
1440 = Torrey Pines
1441 = University
1442 = Uptown
1444 = Skyline-Paradise Hills
1447 = Tierrasanta
1448 = Torrey Hills
1449 = Fairbanks Country Club
1450 = Kearny Mesa
1455 = Via De La Valle
1456 = Mid-City:City Heights
1457 = Mid-City:Eastern Area
1458 = Mid-City:Kensington-Talmadge
1459 = Mid-City:Normal Heights
1461 = Del Mar Mesa
1462 = Torrey Highlands
1463 = Los Penasquitos Canyon Preserve
1464 = Black Mountain Ranch
1465 = Pacific Highlands Ranch
1466 = NCFUA Subarea 2
1467 = NCFUA Reserve
1468 = Southeastern:Encanto Neighborhoods
1469 = Southeastern:Southeastern San Diego
1481 = Rancho Encantada
1482 = Miramar Air Station
1483 = Lindbergh Field
1485 = Scripps Reserve
1486 = Harbor
1488 = Flower Hill
1491 = 32nd Street Naval Station
1901 = Alpine
1902 = Central Mountain
1903 = Crest-Dehesa
1904 = Desert
1906 = Jamul-Dulzura
1907 = Lakeside
1908 = Mountain Empire
1909 = North County Metro
1911 = Otay
1912 = Pala-Pauma
1914 = Ramona
1915 = San Dieguito
1918 = Sweetwater
1919 = Valle De Oro
1920 = Valley Center
1921 = Spring Valley
1922 = Julian
1951 = North Mountain
1952 = Bonsall
1953 = Fallbrook
1954 = Pendleton-De Luz
1955 = Rainbow
1998 = Barona
1999 = County Islands
HNODE Unique Node identifier
YR Year the node is active
CNT Intersection control type where:
0 = No Control
1 = Traffic Signal
2 = All-Way Stop Sign
3 = Two-Way Stop Sign
4 = Ramp Meter
5 = Ramp Meter with HOV Lane Meter
6 = Light Rail Crossing
7 = Toll Booth
TAP Transit Access Point, where:
0 = Not a transit access point
> 1 = Transit access point

Note that TAPs are part of the legacy TCOVED network editing system and no longer used as part of the new TNED network editing system
STOPTYPE Transit stop type where:
0 = No Stop
4 = Commuter Rail
5 = Light Rail Transit (LRT) or Streetcar
6 = Rapid Bus (Freeway Based)
7 = Rapid Bus (Arterial Based)
8 = Limited Express Bus
9 = Express Bus
10 = Local Bus
TSTOPYR Year transit stop is active
PARK Type of Park & Ride facility the transit node (if STOPTYPE > 0) falls within where:
0 = Not Available
1 = Formal Park and Ride
2 = Other Parking
4 = Non-Formal Park and Ride
ELEV Transit stop elevation in feet

The TNED_RailNet feature class contains all the railway links in the network.

Attribute Description
OBJECTID An ObjectID is a unique, not null integer field used to uniquely identify rows in tables in a geodatabase.
LENGTH Length of link in miles
HWYCOV0_ID SANDAG-assigned link ID
SPHERE Jurisdiction sphere of influence where value corresponds to either the jurisdiction code (1-18 excluding 14), the City of San Diego CPA Code (1400s), or the County of San Diego CPA Code (1900s):
1 = Carlsbad
2 = Chula Vista
3 = Coronado
4 = Del Mar
5 = El Cajon
6 = Encinitas
7 = Escondido
8 = Imperial Beach
9 = La Mesa
10 = Lemon Grove
11 = National City
12 = Oceanside
13 = Poway
15 = San Marcos
16 = Santee
17 = Solana Beach
18 = Vista
1401 = Balboa Park
1402 = Barrio Logan
1403 = Carmel Mountain Ranch
1404 = Centre City
1405 = Sabre Springs
1406 = Clairemont Mesa
1407 = East Elliott
1408 = Greater Golden Hill
1409 = Miramar Ranch North
1410 = La Jolla
1412 = Linda Vista
1414 = Midway-Pacific Highway
1415 = Mira Mesa
1417 = Mission Bay Park
1418 = Mission Beach
1419 = Mission Valley
1420 = Navajo
1421 = Carmel Valley
1423 = Ocean Beach
1424 = Old San Diego
1425 = Otay Mesa-Nestor
1426 = Otay Mesa
1427 = Pacific Beach
1428 = Greater North Park
1429 = Rancho Penasquitos
1430 = Peninsula
1431 = Rancho Bernardo
1432 = San Pasqual
1433 = San Ysidro
1434 = Scripps Miramar Ranch
1435 = Serra Mesa
1438 = College Area
1439 = Tijuana River Valley
1440 = Torrey Pines
1441 = University
1442 = Uptown
1444 = Skyline-Paradise Hills
1447 = Tierrasanta
1448 = Torrey Hills
1449 = Fairbanks Country Club
1450 = Kearny Mesa
1455 = Via De La Valle
1456 = Mid-City:City Heights
1457 = Mid-City:Eastern Area
1458 = Mid-City:Kensington-Talmadge
1459 = Mid-City:Normal Heights
1461 = Del Mar Mesa
1462 = Torrey Highlands
1463 = Los Penasquitos Canyon Preserve
1464 = Black Mountain Ranch
1465 = Pacific Highlands Ranch
1466 = NCFUA Subarea 2
1467 = NCFUA Reserve
1468 = Southeastern:Encanto Neighborhoods
1469 = Southeastern:Southeastern San Diego
1481 = Rancho Encantada
1482 = Miramar Air Station
1483 = Lindbergh Field
1485 = Scripps Reserve
1486 = Harbor
1488 = Flower Hill
1491 = 32nd Street Naval Station
1901 = Alpine
1902 = Central Mountain
1903 = Crest-Dehesa
1904 = Desert
1906 = Jamul-Dulzura
1907 = Lakeside
1908 = Mountain Empire
1909 = North County Metro
1911 = Otay
1912 = Pala-Pauma
1914 = Ramona
1915 = San Dieguito
1918 = Sweetwater
1919 = Valle De Oro
1920 = Valley Center
1921 = Spring Valley
1922 = Julian
1951 = North Mountain
1952 = Bonsall
1953 = Fallbrook
1954 = Pendleton-De Luz
1955 = Rainbow
1998 = Barona
1999 = County Islands
NM Rail link name
FXNM Program assigned cross street name at the FROM end of the rai llink
TXNM Program assigned cross street name at the TO end of the rail link
AN A node number. The value corresponds to the HNODE value of the connecting "from node" at the link's starting point.
BN B node number. The value corresponds to the HNODE value of the connecting "to node" at the link's ending point.
DIR Link direction where:
0 = Center City Walk Links
1 = Northbound
2 = Westbound
3 = Southbound
4 = Eastbound
YR The year the link opened for rail operations
FC Functional class where:
11 = Rail Line
HOV Roadway Operation Restriction where:
1 = General Purpose
SPD Link speed in mph
WAY One or two way link indicator where:
1 = One-way link
2 = Two-way link
MED Median type where:
1 = No median
MINMODE Transit mode type where:
400 = Commuter Rail
500 = Trolley & Light Rail Transit (LRT)
HWYSegGUID Highway segment globally unique identifier (GUID)
OSPD Operational speed in mph. For rail routes, operation speed refers to the speed at which the routes runs and considers the length, acceleration, cruise speed, decelaration and dwell time of the vehicle.
TMO Operational rail time
ACCTIME Acceleration time in minutes
DECELTIME Decceleration time in minutes
DWELLTIME Dwell time at transit stop in minutes
RUNTIME Travel (run) time between nodes/stops in minutes
SHAPE_Length Length of link in ft

TNED Railway Network Nodes Feature Class

The TNED_RailNodes feature class contains all the rail nodes of the network.

Attribute Description
OBJECTID An ObjectID is a unique, not null integer field used to uniquely identify rows in tables in a geodatabase.
XNM1 First cross street name
XNM2 Second cross street name
X_COORD Coordinate value of the node in the X direction
Y_COORD Coordinate value of the node in the Y direction
Z_COORD Coordinate value of the node in the Z direction (elevation)
SPHERE Jurisdiction sphere of influence where value corresponds to either the jurisdiction code (1-18 excluding 14), the City of San Diego CPA Code (1400s), or the County of San Diego CPA Code (1900s):
1 = Carlsbad
2 = Chula Vista
3 = Coronado
4 = Del Mar
5 = El Cajon
6 = Encinitas
7 = Escondido
8 = Imperial Beach
9 = La Mesa
10 = Lemon Grove
11 = National City
12 = Oceanside
13 = Poway
15 = San Marcos
16 = Santee
17 = Solana Beach
18 = Vista
1401 = Balboa Park
1402 = Barrio Logan
1403 = Carmel Mountain Ranch
1404 = Centre City
1405 = Sabre Springs
1406 = Clairemont Mesa
1407 = East Elliott
1408 = Greater Golden Hill
1409 = Miramar Ranch North
1410 = La Jolla
1412 = Linda Vista
1414 = Midway-Pacific Highway
1415 = Mira Mesa
1417 = Mission Bay Park
1418 = Mission Beach
1419 = Mission Valley
1420 = Navajo
1421 = Carmel Valley
1423 = Ocean Beach
1424 = Old San Diego
1425 = Otay Mesa-Nestor
1426 = Otay Mesa
1427 = Pacific Beach
1428 = Greater North Park
1429 = Rancho Penasquitos
1430 = Peninsula
1431 = Rancho Bernardo
1432 = San Pasqual
1433 = San Ysidro
1434 = Scripps Miramar Ranch
1435 = Serra Mesa
1438 = College Area
1439 = Tijuana River Valley
1440 = Torrey Pines
1441 = University
1442 = Uptown
1444 = Skyline-Paradise Hills
1447 = Tierrasanta
1448 = Torrey Hills
1449 = Fairbanks Country Club
1450 = Kearny Mesa
1455 = Via De La Valle
1456 = Mid-City:City Heights
1457 = Mid-City:Eastern Area
1458 = Mid-City:Kensington-Talmadge
1459 = Mid-City:Normal Heights
1461 = Del Mar Mesa
1462 = Torrey Highlands
1463 = Los Penasquitos Canyon Preserve
1464 = Black Mountain Ranch
1465 = Pacific Highlands Ranch
1466 = NCFUA Subarea 2
1467 = NCFUA Reserve
1468 = Southeastern:Encanto Neighborhoods
1469 = Southeastern:Southeastern San Diego
1481 = Rancho Encantada
1482 = Miramar Air Station
1483 = Lindbergh Field
1485 = Scripps Reserve
1486 = Harbor
1488 = Flower Hill
1491 = 32nd Street Naval Station
1901 = Alpine
1902 = Central Mountain
1903 = Crest-Dehesa
1904 = Desert
1906 = Jamul-Dulzura
1907 = Lakeside
1908 = Mountain Empire
1909 = North County Metro
1911 = Otay
1912 = Pala-Pauma
1914 = Ramona
1915 = San Dieguito
1918 = Sweetwater
1919 = Valle De Oro
1920 = Valley Center
1921 = Spring Valley
1922 = Julian
1951 = North Mountain
1952 = Bonsall
1953 = Fallbrook
1954 = Pendleton-De Luz
1955 = Rainbow
1998 = Barona
1999 = County Islands
HNODE Unique Node identifier
YR Year the node is active
CNT Intersection control type where:
0 = No Control
6 = Light Rail Crossing
TAP Transit Access Point, where:
0 = Not a transit access point
> 1 = Transit access point

Note that TAPs are part of the legacy TCOVED network editing system and no longer used as part of the new TNED network editing system
STOPTYPE Transit stop type where:
4 = Commuter Rail
5 = Light Rail Transit (LRT) or Streetcar
TSTOPYR Year transit stop is active. Not presently used by model.
PARK Type of Park & Ride facility the transit node falls within
0 = Not Available
1 = Formal Park and Ride
2 = Other Parking
4 = Non-Formal Park and Ride
ELEV Transit stop elevation in feet

TNED Transit Route Feature Class

The TransitRoute feature class contains all the transit routes in the network.

Attribute Description
OBJECTID An ObjectID is a unique, not null integer field used to uniquely identify rows in tables in a geodatabase.
GlobalID ESRI-generated Global IDs which are unique and identify a feature or table row in a geodatabase and across geodatabases.
Route Transit Route Number
Direction Direction of transit route where:
1 = Inbound
2 = Outbound

Although not a global nor strict rule, a value of 1 typically refers to the direction of the route destined to Downtown San Diego
Configuration The configuration, or alignment version, of the transit route
RouteID The concatenated Route, direction and configuration of the transit route. This unique ID is best read from right to left as the last 2 digits refer to the Configuration, the 3rd digit from the right refers to the Direction (1 or 2), and the remaining leftmost digits refer to the Route. For example, 398212 is configuration 12 in the outbound (2 direction) of route 398.
Operator Route Operator where:
1 = MTS
2 = NCTD
3 = SD Trolley

Note that this field has no effects on model results.
Mode Transit mode where:
4 = Commuter Rail
5 = Light Rail Transit (LRT) or Streetcar
6 = Rapid Bus (Freeway Based)
7 = Rapid Bus (Arterial Based)
8 = Limited Express Bus
9 = Express Bus
10 = Local Bus
RouteDesc A description of the transit route
Origin Description field that may be used to distinguish what study or project the record belongs to. E.g., 2021 Regional Plan, 2025 Regional Plan, Airport Transit Connection, etc.
StudyUse Description field to indicate status of configuration and/or alternative. E.g., Final, Initial, Long Range
Stop Jurisdiction or community plan area where transit route terminates
Start Jurisdiction or community plan area where transit route begins
SHAPE_Length Length of transit route alignment in feet

TNED Turns File Geodatabase Table

The Turns file geodatabase table lists prohibited vehicle turn movements.

Attribute Description
OBJECTID An ObjectID is a unique, not null integer field used to uniquely identify rows in tables in a geodatabase.
TurnID Unique turn record identifier
GlobalID ESRI-generated Global IDs which are unique and identify a feature or table row in a geodatabase and across geodatabases.
FromNode First node's ID in turn sequence where the value references the TNED_HwyNode HNODE attribute
MidNode Second/mid node's ID in turn sequence where the value references the TNED_HwyNode HNODE attribute
ToNode Final node's ID in turn sequence where the value references the TNED_HwyNode HNODE attribute

The SANDAG_Bike_Net.shp contains all the active transportation (bike, walk) links of the network.

Attribute Description
FID Sequential field ID (i.e., index) starting at 0.
GlobalID ESRI-generated Global IDs which are unique and identify a feature or table row in a geodatabase and across geodatabases.
ROADSEGID Road segment ID
RD20FULL Road/Street name
A_LEVEL Level of first node
B_LEVEL Level of second node
A Foreign key of first node
B Foreign key of second node
Distance Arc length of link (ft)
AB_Gain Cumulative non-negative increase in elevation from A to B nodes (ft)
BA_Gain Cumulative non-negative increase in elevation from B to A nodes (ft)
ABBikeClas Type of Bike Classification in AB direction where:
0 = No bike facility
1 = Multi-Use Path
2 = Bike Lane
3 = Bike Route
4 = Separated Bikeway; Coded as 2 with Bike2Sep = 1
5 = Bike Boulevard; Coded as 3 with Bike3Blvd = 1
10 = MGRA/TAZ Connector
BABikeClas Type of Bike Classification in BA direction where:
0 = No bike facility
1 = Multi-Use Path
2 = Bike Lane
3 = Bike Route
4 = Separated Bikeway; Coded as 2 with Bike2Sep = 1
5 = Bike Boulevard; Coded as 3 with Bike3Blvd = 1
10 = MGRA/TAZ Connector
AB_Lanes Number of Vehicle Lanes in AB direction
BA_Lanes Number of Vehicle Lanes in BA direction
Func_Class Roadway functional classification where:
0 = Pedestrian / Bikeway / Recreational Parkway
2 = Prime (Primary) Arterial
3 = Major Road / 4-Lane Major Road
4 = Light (2-lane) Collector
6 = Rural Collector / Rural Light Collector / Local Road
7 = Private Street / Rural Mountain Road
8 = Freeway to Freeway Ramp
Bike2Sep Separated Bike Lane Flag where:
0 = No
1 = Yes
Bike3Blvd Bike Boulevard Lane Flag where:
0 = No
1 = Yes
SPEED Road Speed
ProjectID Project ID in the regional bike network
Year Year built/open to public
ScenicIdx Scenic index represents the closeness to the ocean and parks
ABBikeLn Number of bike lanes in the AB direction. Set to 1 if AB_Lanes=0 and ABBikeClas in (1,2,3)
BABikeLn Number of bike lanes in the BA direction. Set to 1 if BA_Lanes=0 and BABikeClas in (1,2,3)
Shape_Leng Length of the link (ft)

TNED Active Transportation Network Nodes Shapefile

The SANDAG_Bike_Node.shp shapefile contains all the active transportation (bike, walk) nodes of the network.

Attribute Description
FID Sequential field ID (i.e., index) starting at 0.
GLOBALID ESRI-generated Global IDs which are unique and identify a feature or table row in a geodatabase and across geodatabases.
NodeLev_ID Unique node ID value - matching values for A & B fields in SANDAG_Bike_Net.shp
MGRA MGRA ID if node is MGRA centroid. Field will be 0 if node is not a centroid.

For Series 15 networks, MGRA may span from 1 to 24321.
TAZ TAZ ID if node is zone centroid. Field will be 0 if node is not a centroid.

For Series 15 networks, TAZ may span from 1 to 4947.
XCOORD X Coordinate of Node in NAD 1983 State Plane California Region VI FIPS: 0406 (US Feet)
YCOORD Y Coordinate of Node in NAD 1983 State Plane California Region VI FIPS: 0406 (US Feet)
ZCOORD Elevation (ft)
Signal Traffic signal presence where:
0 = Absence
1 = Presence

Special Fares Text File

The special_fares.txt configures zone-based fare schemes and also houses the daily and regional pass fares. The Coaster is presently the only transit route in the San Diego region that has a zone-based fare system. To account for this, its fare structure is laid out in the special_fares.txt file. The contents of the file are as follow:

SANDAG's input special fares file
special_fares.txt

Under the boarding_cost section, the base sub-section provides the one-way fare (i.e., cost) for each direction of the coaster (i.e., line). Note that under this file, the Coaster is referenced via the RouteID (see RouteID under TransitRoute for further details) for each direction. The stop_increment section was previously utilized when the Coaster operated on a 4-zone fare system (prior to 2019) and therefore the cost values under that section are zeroed out.

The in_vehicle_cost section is where we can account for the zone-based fare system of the Coaster. Using the above excerpt as an example, the first 2 rows reference the Coaster in the southbound direction. When the Coaster passes through Solana Beach, it receives an additional $0.75 to the fare and another additional $0.75 when it passes through Sorrento Valley. The reverse is the same for the northbound direction with the only difference being the stations at which it receives the additional fares. The name of the station must be written out exactly as is it comes out in the network. The trstop.csv or may be referred to for exact Coaster station naming.

The last 2 elements of the special_fares.txt file are the day_pass and regional_pass fare variables. The day_pass refers to the daily pass that provides all-day access to the following routes: MTS Bus, MTS Trolley, MTS Rapid, Sprinter or Breeze. The regional_pass refers to the Coaster Adult 1-Day Pass which provdes all-day access to routes to the following routes: Coaster, Sprinter, Breeze, Flex, MTS Bus, MTS Trolley, MTS Rapid, MTS Rapid Express and MTS Rural. The newer Premium Regional Pass (presently $12) is not currently accounted for.

Timed Transfer CSV Files

The timexfer_{time_of_day}.csv file contains the timed connections between the Coaster and feeder buses. There is a file present for each of the 5 time-of-days, which are EA (early AM), AM, MD (midday), PM, and EV (evening).

Attribute Description
from_line Specifies the origin transit route RouteID (see RouteID under TransitRoute for further details) transferring to the destination (to_line) transit route.
to_line Specifies the destination transit route RouteID (see RouteID under TransitRoute for further details) from which the origin (from_line) transit route transfers to.
wait_time The specified transfer time between the origin (from_line) and destination (to_line) transit route.

The time-of-day timed transfer files were developed specifically for the Coaster given it is a high-end transit mode that has infrequent service in the base year and as a result, is difficult to calibrate. In order to model Coaster ridership that is closer to calibration targets, the timed transfer files were developed so that the travel demand model was informed of more realistic transfer times between the Coaster and feeder transit routes; this was done by comparing default transfer times and calculated average transfer times. Normally, the travel demand model defaults to a transfer time of half the transfer route’s headway. For calculated average transfer times, the transit routes connecting to/from the Coaster were identified at each station for each of the 5 time-of-days and, using the Coaster and transfer route existing schedules, average transfer times were calculated. If the calculated average transfer time was lower than the default transfer time, the calculated average transfer time was added as a record to the corresponding time-of-day timed transfer file. Otherwise, it was omitted and the default transfer time was utilized by the model. The above methodology was carried out for the base year and subsequent future year files are subsets of it, where records may only be omitted (never added) if future frequency updates generate default transfer times that are less than the calculated average transfer times.

Transit Routes CSV File

The trrt.csv lists all transit routes in the network and provides information on their mode, frequencies, hours of service, and fares.

Attribute Description
Route_ID Sequential unique transit route identifier
Route_Name The concatenated Route, direction and configuration of the transit route. This unique ID is best read from right to left as the last 2 digits refer to the Configuration, the 3rd digit from the right refers to the Direction (1 or 2), and the remaining leftmost digits refer to the Route. For example, 398212 is configuration 12 in the outbound (2 direction) of route 398.
Mode Transit mode where:
4 = Commuter Rail
5 = Light Rail Transit (LRT) or Streetcar
6 = Rapid Bus (Freeway Based)
7 = Rapid Bus (Arterial Based)
8 = Limited Express Bus
9 = Express Bus
10 = Local Bus
EarlyAM_Headway Early morning (EA) headway/frequency of transit route where EA hours of operation are from 3:00 AM to 5:59 AM
AM_Headway Morning (EA) headway/frequency of transit route where AM hours of operation are from 6:00 AM to 8:59 AM
Midday_Headway Midday (MD) headway/frequency of transit route where MD hours of operation are from 9:00 AM to 3:29 PM
PM_Headway Afternoon (PM) headway/frequency of transit route where PM hours of operation are from 3:30 PM to 6:59 PM
Evening_Headway Evening (EV) headway/frequency of transit route where EV hours of operation are from 7:00 PM to 2:59 AM
EarlyAM_Hours Number of hours, within the EA hours of operation, the transit routes provides service
Evening_Hours Number of hours, within the EV hours of operation, the transit routes provides service
Config The concatenated Route, direction and configuration of the transit route. This unique ID is best read from right to left as the last 2 digits refer to the Configuration, the 3rd digit from the right refers to the Direction (1 or 2), and the remaining leftmost digits refer to the Route. For example, 398212 is configuration 12 in the outbound (2 direction) of route 398.
Fare One-way transit fare in dollars ($)

The trlink.csv contains an ordered sequential list of underlying network links (arcs) for each transit route in the network. The records are ordered by the Route_ID attribute, which is not the same as the Route number, but rather a sequential transit route identifier unique to the network. It is recommended to refer to the trrt.csv file’s Route_ID to determine which transit route is being referenced. For each Route_ID, every row represents an underlying TNED_HwyNet (or TNED_RailNet) link the transit route is traversing over in order from start to finish.

Attribute Description
Route_ID Sequential unique transit route identifier.

To determine what Route the Route_ID is referring to, refer to the trrt.csv file
Link_ID The ID referring to TNED_HwyNet HWYCOV0_ID attribute
Link_GUID The GUID referring to TNED_HwyNet HWYSegGUID attribute
Direction The direction of the transit route (i.e., inbound (+), or outbound (-))

Transit Stops CSV File

The trstop.csv lists all transit stops for all transit routes in the network. The Route_ID in the file is not the same as the Route number, but rather a sequential transit route identifier unique to the network. It is recommended to refer to the trrt.csv file’s Route_ID to determine which transit route is being referenced.

Attribute Description
Stop_ID Sequential unique transit stop identifier
Route_ID Sequential unique transit route identifier.

To determine what Route the Route_ID is referring to, refer to the trrt.csv file
Link_ID The Link ID referring to TNED_HwyNet HWYCOV0_ID attribute
Link_GUID The link GUID referring to TNED_HwyNet HWYSegGUID attribute
Pass_Count The number of times the transit route services the transit stop.
Milepost Transit stop mile post
Longitude Transit stop longitude coordinate
Latitude Transit stop latitude coordinate
Node Node number transit stop is nearest to
StopName Name of transit stop
Elev Elevation of transit stop in feet
Park Type of Park & Ride facility the transit node falls within
0 = Not Available
1 = Formal Park and Ride
2 = Other Parking
4 = Non-Formal Park and Ride