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 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx).

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 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx). 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 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation not defined yet
Outbound: Relation 2877693 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Incomplete conversion to route_master
K-Ingleside Relation 63572 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master
L-Taraval Relation 2124174 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master
M-Ocean View Relation 91022 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master
N-Judah Relation 63223 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master
T-Third Street Relation 63250 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master

Bus Routes

Route Status Relation Notes
1-California Master: Relation 2978570 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2978568 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2978569 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

1AX-California A Express Relation not defined yet
1BX-California B Express Relation not defined yet
2-Clement Master: Relation 2978594 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2978592 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2978593 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

3-Jackson Master: Relation 2980506 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2980504 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2980505 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

5-Fulton Master: Relation 2995940 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2995938 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2995939 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

6-Parnassus Master: Relation 331554 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2007652 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2007651 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

8X-Bayshore Exp Relation not defined yet
8AX-Bayshore A Exp Relation not defined yet
8BX-Bayshore B Exp Relation not defined yet
9-San Bruno Master: Relation 2981259 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2981257 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2981258 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

9L-San Bruno Limited Relation not defined yet
10-Townsend Master: Relation 2981335 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2981333 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2981334 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

12-Folsom/Pacific Master: Relation 2996795 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2996793 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2996794 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

14-Mission Master: Relation 3000715 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 3000713 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 3000714 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

14L-Mission Limited Relation not defined yet
14X-Mission Express Relation not defined yet
16X-Noriega Express Master: Relation 3000879 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 3000877 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 3000878 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

17-Park Merced Master: Relation 3000939 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 3000937 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 3000938 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

18-46th Avenue Master: Relation 3001304 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 3001302 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 3001303 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

19-Polk Master: Relation 3001323 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 3001321 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 3001322 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

21-Hayes Master: Relation 3001343 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 3001341 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 3001342 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

22-Fillmore Master: Relation 63225 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2007949 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2007950 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

23-Monterey Master: Relation 3002742 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 3002740 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 3002741 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

24-Divisadero Master: Relation 2996738 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2996736 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2996737 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

27-Bryant Relation not defined yet
28-19th Avenue Relation not defined yet
28L-19th Avenue Limited Relation not defined yet
29-Sunset Relation not defined yet
30-Stockton Relation 1945794 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master
30X-Marina Express Relation not defined yet
31-Balboa Relation not defined yet
31AX-Balboa A Express Relation not defined yet
31BX-Balboa B Express Relation not defined yet
33-Stanyan Relation not defined yet
35-Eureka Relation not defined yet
36-Teresita Relation not defined yet
37-Corbett Master: Relation 1328322 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2007919 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2007918 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

38-Geary Relation not defined yet
38AX-Geary A Express Relation not defined yet
38BX-Geary B Express Relation not defined yet
38L-Geary Limited Relation not defined yet
39-Coit Master: Relation 2007116 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2007467 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2005406 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

41-Union Relation not defined yet
43-Masonic Relation not defined yet
44-O'Shaughnessy Relation not defined yet
45-Union/Stockton Relation 1945795 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master
47-Van Ness Master: Relation 1946363 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2007910 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2007911 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

48-Quintara - 24th Street Relation not defined yet
49-Mission-Van Ness Relation not defined yet
52-Excelsior Relation not defined yet
54-Felton Relation not defined yet
56-Rutland Relation not defined yet
66-Quintara Relation not defined yet
67-Bernal Heights Relation not defined yet
71-Haight/Noriega Relation 331559 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master
71L-Haight-Noriega Limited Relation not defined yet
76-Marin Headlands Relation not defined yet
81X-Caltrain Express Relation not defined yet
82X-Levi Plaza Express Relation not defined yet
83X-Caltrain Relation not defined yet
88-BART Shuttle Master: Relation 2852276 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2852275 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound:Relation 2852274 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

90-San Bruno Owl Relation not defined yet
91-Owl Relation not defined yet
108-Treasure Island Relation not defined yet
K-Owl Relation not defined yet
L-Owl Relation not defined yet
M-Owl Relation not defined yet
N-Owl Relation not defined yet
NX-N Judah Express Relation not defined yet
T-Owl Relation not defined yet

Cable Car Routes

Route Status Relation Notes
California Master: Relation 1958845 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Inbound: Relation 2852265 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)
Outbound: Relation 2852264 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx)

Powell/Hyde Relation 1959009 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master
Powell/Mason Relation 1959010 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master

Historic Streetcar Routes

Route Status Relation Notes
E-Embarcadero Relation not defined yet
F-Market & Wharves Relation 63224 (XML, Potlatch2, iD, JOSM, history, analyze, manage, gpx) Not yet converted to route_master