![]() Use the following abbreviations, and do not include a period after them:.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.*If Otherwise, follow the nature of the stop names used on NextBus and/or the GTFS feeds.If a station has more than one name (common on T-Third stations) Only use the primary name in the name= * field, and add the secondary as an alt_name= *. The name found on the actual station signage is preferred, if there is one.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: 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. 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. The highways or rails that are traversed in this direction of service, in the order they are traversed. These relations should have a member for each way and stop that participates in this direction of service: Mostly relevant for the rail lines, which are not all fully accessible. Use approximately the terminal names used on the bus headsigns, but abbreviated as described for stop names below Use the Inbound/Outbound name designated by SFMTA, e.g. Route number and name followed by Inbound/Outbound designation Light_rail for Muni Metro, tram for historic streetcar and cable car lines,Įxactly as for the associated route masterĮxactly as on the associated route master (duplicated for renderers that don't yet support route masters) Suggested guideline: include only directions that Muni considers significant enough to include on NextMuni. Type= route for each "normal" direction of the line, but excluding short turns when vehicles enter/leave service These relations should have a member for each "normal" direction the line follows: Literally "San Francisco Municipal Railway"Īpproximation of color used in muni's maps and on stops, as a HTML-style RGB triple like #ff00ff. For example: 47-Van Ness, F-Market & Wharves, Powell-Mason The route number and name separated by a dash, or just the name for cable cars. Use tram= cable_car in addition for cable car linesĭo not include the route name here For cable cars use the abbreviations Muni uses on the official muni map: PM, PH, C Light_rail for Muni Metro, tram for historic streetcar and cable car lines ![]() These conventions are extensions of the general public transport tagging conventions. Here are the conventions currently in use and documented here in the hope that we can achieve consistency in how the general tagging conventions are applied to Muni's services. Several years ago ( User:Mart) had 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. 2.1 Muni Metro Routes, Cable Car Routes, Historic Street Car Routes. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |