San Francisco Muni

From OpenStreetMap Wiki
Jump to: navigation, search

The type=route_master relations for each line (or type=route, for those that haven't be converted to the new scheme yet) are collected in the operator relation relation 2007571.

Tagging Conventions

(User:Mart) has started to convert the Muni routes over to the new tagging conventions with a type=route_master relation for each line which in turn contains a type=route relation for each direction of the line.

Here are the conventions he is using during this conversion, most based on work already done by others and documented here in the hope that we can achieve consistency in how the general tagging conventions are applied to Muni's services. These conventions are extensions of the general public transport tagging conventions.

Along with this he has done some tagging for NextBus integration.

Route Master Relations

Key Value Comment Recommendation
type route_master - mandatory
route_master tram for Muni Metro, historic streetcar and cable car lines
bus for diesel coach lines
trolleybus for trolley coach lines
Use tram=cable_car in addition for cable car lines mandatory
ref Route letter or number Do not include the route name here; For cable cars use the abbreviations Muni uses on the official muni map: PM, PH, C mandatory
name Route number and name The route number and name separated by a dash, or just the name for cable cars. Use spaces where Muni does. For example: 47-Van Ness, F-Market & Wharves, Powell-Mason mandatory
operator Literally "San Francisco Municipal Railway" - mandatory
colour Color Approximation of color used in muni's maps and on stops, as a HTML-style RGB triple like #ff00ff. If maps and stops disagree, prefer maps. recommended

These relations should have a member for each "normal" direction the line follows:

Element Role Recurrence? Description
relation none two or more type=route_master for each "normal" direction of the line, but excluding short turns when vehicles enter/leave service
Suggested guideline: include only directions that Muni considers significant enough to include on NextMuni.

Route Relations

Key Value Comment Recommendation
type route - mandatory
route tram for Muni Metro, historic streetcar and cable car lines
bus for diesel coach lines
trolleybus for trolley coach lines
Exactly as for the associated route master mandatory
ref Route letter or number Exactly as on the associated route master (duplicated for renderers that don't yet support route masters) mandatory
name Route number and name followed by Inbound/Outbound designation Use the Inbound/Outbound name designated by SFMTA, e.g. 22-Fillmore: Outbound to Potrero Hill mandatory
from Name of start terminal Use approximately the terminal names used on the bus headsigns, but abbreviated as described for stop names below mandatory
to Name of destination terminal Use approximately the terminal names used on the bus headsigns, but abbreviated as described for stop names below mandatory
operator Literally "San Francisco Municipal Railway" - mandatory
colour Color Exactly as on the associated route master (duplicated for renderers that don't yet support route masters) recommended

These relations should have a member for each way and stop that participates in this direction of service:

Element Role Recurrence? Description
way none one or more the highways or rails that are traversed in this direction of service, in the order they are traversed.
node stop one or more the bus stops (highway=bus_stop) or platforms (public_transport=platform) where this bus can stop in this direction of service, in the order they are passed.

Bus Stop and Station Names

There seems to be some sense of convention in how Muni names stops in the GTFS data and in NextBus, although there are often counter-examples which I assume arise from carelessness, and a different naming convention exists for the digital voice and sign used on the buses, presumably due to space constraints.

In the interests of consistency, the following naming conventions are suggested, based on what seems to be the intended convention used in Muni's GTFS data and NextBus:

  • Follow the nature of the stop names used on NextBus and/or the GTFS feeds. That is, if Muni names it as a pair of streets follow that, whereas if it's named after a landmark or an address follow that.
  • Use the following abbreviations, and do not include a period after them:
    • "Avenue" as "Ave"
    • "Street" as "St"
    • "Boulevard" as "Blvd"
    • "Alley" unabbreviated
    • "Point" unabbreviated
    • "Station" unabbreviated
  • Abbreviate "Bay Area Rapid Transit" as "BART" and not as "B.A.R.T." or "Bart".
  • Use "&" as the separator for a pair of streets. e.g. "North Point St & Stockton St"
  • Include the appropriate street type abbreviation at the end of a street name. e.g. "Buchanan St" and not just "Buchanan".
  • The names Muni uses for the stops that are the terminal of a line often don't match the names used on the headsign of that line; use the stop name for tagging the stop and use the headsign name (after applying the above style guidelines) on the from and to tags on the route relation.

Converting standalone routes to route master and directions

Several people created routes under the old scheme where all directions of service were included in a single route relation. Converting these is reasonably straightforward since the street ways are already split to accommodate the transit lines joining and leaving, we just need to make sure to follow the correct route where different streets are traveled in each direction.

Here's a process for converting which leaves the relation id of the original route intact as the new route master. To avoid confusing the map data during the conversion it's best to make submit these changes in a single changeset:

  • Create a new route relation for each direction and add the ways in the order of travel. A direction should be a single connected path with no branches.
  • Add any stops that already exist on the map to the appropriate direction relation.
  • Change the type of the old route relation to "route_master".
  • Rename the "route" key of the old route relation to "route_master".
  • Remove all of the stops and ways from the route master relation.
  • Add the direction relations to the route master relation.

Muni-related Data

The main "operator" relation for Muni is relation 2007571. This should contain all of the "route_master" relations shown below, and could also have added infrastructure and facilities maintained by Muni, such as the bus and train barns.

Muni Metro Routes

Route Status Relation Notes
J-Church Master: relation 63222

Inbound: Lua error in Module:Element at line 60: Given relation id parameter is not a number.
Outbound: relation 2877693

Incomplete conversion to route_master
K-Ingleside relation 63572 Not yet converted to route_master
L-Taraval relation 2124174 Not yet converted to route_master
M-Ocean View relation 91022 Not yet converted to route_master
N-Judah relation 63223 Not yet converted to route_master
T-Third Street relation 63250 Not yet converted to route_master

Bus Routes

Route Status Relation Notes
1-California Master: relation 2978570

Inbound: relation 2978568
Outbound: relation 2978569

1AX-California A Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
1BX-California B Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
2-Clement Master: relation 2978594

Inbound: relation 2978592
Outbound: relation 2978593

3-Jackson Master: relation 2980506

Inbound: relation 2980504
Outbound: relation 2980505

5-Fulton Master: relation 2995940

Inbound: relation 2995938
Outbound: relation 2995939

6-Parnassus Master: relation 331554

Inbound: relation 2007652
Outbound: relation 2007651

8X-Bayshore Exp Lua error in Module:Element at line 60: Given relation id parameter is not a number.
8AX-Bayshore A Exp Lua error in Module:Element at line 60: Given relation id parameter is not a number.
8BX-Bayshore B Exp Lua error in Module:Element at line 60: Given relation id parameter is not a number.
9-San Bruno Master: relation 2981259

Inbound: relation 2981257
Outbound: relation 2981258

9L-San Bruno Limited Lua error in Module:Element at line 60: Given relation id parameter is not a number.
10-Townsend Master: relation 2981335

Inbound: relation 2981333
Outbound: relation 2981334

12-Folsom/Pacific Master: relation 2996795

Inbound: relation 2996793
Outbound: relation 2996794

14-Mission Master: relation 3000715

Inbound: relation 3000713
Outbound: relation 3000714

14L-Mission Limited Lua error in Module:Element at line 60: Given relation id parameter is not a number.
14X-Mission Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
16X-Noriega Express Master: relation 3000879

Inbound: relation 3000877
Outbound: relation 3000878

17-Park Merced Master: relation 3000939

Inbound: relation 3000937
Outbound: relation 3000938

18-46th Avenue Master: relation 3001304

Inbound: relation 3001302
Outbound: relation 3001303

19-Polk Master: relation 3001323

Inbound: relation 3001321
Outbound: relation 3001322

21-Hayes Master: relation 3001343

Inbound: relation 3001341
Outbound: relation 3001342

22-Fillmore Master: relation 63225

Inbound: relation 2007949
Outbound: relation 2007950

23-Monterey Master: relation 3002742

Inbound: relation 3002740
Outbound: relation 3002741

24-Divisadero Master: relation 2996738

Inbound: relation 2996736
Outbound: relation 2996737

27-Bryant Lua error in Module:Element at line 60: Given relation id parameter is not a number.
28-19th Avenue Lua error in Module:Element at line 60: Given relation id parameter is not a number.
28L-19th Avenue Limited Lua error in Module:Element at line 60: Given relation id parameter is not a number.
29-Sunset Lua error in Module:Element at line 60: Given relation id parameter is not a number.
30-Stockton relation 1945794 Not yet converted to route_master
30X-Marina Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
31-Balboa Lua error in Module:Element at line 60: Given relation id parameter is not a number.
31AX-Balboa A Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
31BX-Balboa B Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
33-Stanyan Lua error in Module:Element at line 60: Given relation id parameter is not a number.
35-Eureka Lua error in Module:Element at line 60: Given relation id parameter is not a number.
36-Teresita Lua error in Module:Element at line 60: Given relation id parameter is not a number.
37-Corbett Master: relation 1328322

Inbound: relation 2007919
Outbound: relation 2007918

38-Geary Lua error in Module:Element at line 60: Given relation id parameter is not a number.
38AX-Geary A Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
38BX-Geary B Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
38L-Geary Limited Lua error in Module:Element at line 60: Given relation id parameter is not a number.
39-Coit Master: relation 2007116

Inbound: relation 2007467
Outbound: relation 2005406

41-Union Lua error in Module:Element at line 60: Given relation id parameter is not a number.
43-Masonic Lua error in Module:Element at line 60: Given relation id parameter is not a number.
44-O'Shaughnessy Lua error in Module:Element at line 60: Given relation id parameter is not a number.
45-Union/Stockton relation 1945795 Not yet converted to route_master
47-Van Ness Master: relation 1946363

Inbound: relation 2007910
Outbound: relation 2007911

48-Quintara - 24th Street Lua error in Module:Element at line 60: Given relation id parameter is not a number.
49-Mission-Van Ness Lua error in Module:Element at line 60: Given relation id parameter is not a number.
52-Excelsior Lua error in Module:Element at line 60: Given relation id parameter is not a number.
54-Felton Lua error in Module:Element at line 60: Given relation id parameter is not a number.
56-Rutland Lua error in Module:Element at line 60: Given relation id parameter is not a number.
66-Quintara Lua error in Module:Element at line 60: Given relation id parameter is not a number.
67-Bernal Heights Lua error in Module:Element at line 60: Given relation id parameter is not a number.
71-Haight/Noriega relation 331559 Not yet converted to route_master
71L-Haight-Noriega Limited Lua error in Module:Element at line 60: Given relation id parameter is not a number.
76-Marin Headlands Lua error in Module:Element at line 60: Given relation id parameter is not a number.
81X-Caltrain Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
82X-Levi Plaza Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
83X-Caltrain Lua error in Module:Element at line 60: Given relation id parameter is not a number.
88-BART Shuttle Master: relation 2852276

Inbound: relation 2852275
Outbound:relation 2852274

90-San Bruno Owl Lua error in Module:Element at line 60: Given relation id parameter is not a number.
91-Owl Lua error in Module:Element at line 60: Given relation id parameter is not a number.
108-Treasure Island Lua error in Module:Element at line 60: Given relation id parameter is not a number.
K-Owl Lua error in Module:Element at line 60: Given relation id parameter is not a number.
L-Owl Lua error in Module:Element at line 60: Given relation id parameter is not a number.
M-Owl Lua error in Module:Element at line 60: Given relation id parameter is not a number.
N-Owl Lua error in Module:Element at line 60: Given relation id parameter is not a number.
NX-N Judah Express Lua error in Module:Element at line 60: Given relation id parameter is not a number.
T-Owl Lua error in Module:Element at line 60: Given relation id parameter is not a number.

Cable Car Routes

Route Status Relation Notes
California Master: relation 1958845

Inbound: relation 2852265
Outbound: relation 2852264

Powell/Hyde relation 1959009 Not yet converted to route_master
Powell/Mason relation 1959010 Not yet converted to route_master

Historic Streetcar Routes

Route Status Relation Notes
E-Embarcadero Lua error in Module:Element at line 60: Given relation id parameter is not a number.
F-Market & Wharves relation 63224 Not yet converted to route_master