San Francisco Muni

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  2007571 (XML, check, manage, JOSM, history, view, gpx ).

Contents 1 Tagging Conventions 1.1 Route Master Relations 1.2 Route Relations 1.3 Bus Stop and Station Names 1.4 Converting standalone routes to route master and directions 2 Muni Metro 3 Buses 4 Cable Car 5 Historic Streetcar

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.

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
	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 start/end names	Use approximately the terminal names used on the bus headsigns e.g. 22-Fillmore: Bay St => 20th and Third	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
	none	one or more	the highways or rails that are traversed in this direction of service, in the order they are traversed.
	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 Metro

Route	Status	Relation	Notes
J		63222 (XML, check, manage, JOSM, history, view, gpx )
K		63572 (XML, check, manage, JOSM, history, view, gpx )
L
M		91022 (XML, check, manage, JOSM, history, view, gpx )
N		63223 (XML, check, manage, JOSM, history, view, gpx )
T		63250 (XML, check, manage, JOSM, history, view, gpx )

Buses

Cable Car

Historic Streetcar