Talk:Arizona/Maricopa County/Public Transport

The talk page is being used to sort out the design of the system based on all the other transportation and routing pages. Additional tags may be added as work commences and problems or additional understanding is discovered.

Bus Master Relationship Tags

Key	Value	Explanation
colour=*	a color name or a hex triplet	(optional) I don't know if this is useful yet. Colour code noted in hex triplet format. Especially useful for public transport routes. Example: "#008080" for teal colour.
description=*	a short description	The description helps expand on the ref value such as South Bound Central Avenue.
distance=*	distance	(optional) The distance tag will have to be added later. The distance covered by this route, if known. For information of users and automatic evaluation; e.g., of completeness. Given including a unit and with a dot for decimals. (e.g., "12.5km").
is_in=*	USA;AZ;Arizona;Maricopa;Phoenix	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:city=*	Phoenix	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:country=*	United States of America	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:country_code=*	USA	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:county=*	Maricopa	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:municipality=*	City of Phoenix	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:state=*	Arizona	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:state_code=*	AZ	There are several systems called Valley. These tags will set the location of the relationship textually.
name=*	bus 0	The name tag makes the relationship easy to locate in JOSM.
network=*	Tag:network=regional / Tag:network=local	For the Phoenix Metro area, Tag:network=regional will be used for express buses and Tag:network=local will be used for all local and circular routes.
note=*	Why is_in tags	I used Valley Metro Office location of 301 N Central Ave, Phoenix, AZ for the is in tags. I think some of the original relationships have gone missing.
operator=*	operator name	Valley Metro
operator:en=*	operator name	Valley Metro
public_transport:version=*	2	Useful for JOSM Validation.
ref=*	0	For example, 0 is used for the Central Avenue route.
route	bus
route_master	bus
roundtrip=*	yes/no	roundtrip=no on most of the routes. roundtrip=yes for circular such as the downtown Dash route.
symbol=*	symbol description	(optional) I don't know if this is useful yet.
type	route_master	Indicates this relation represents a route.
website=*	URL	Find the link to the Valley Metro page such routes.valleymetro.org/timetables/transit_route/611?type=2 for route zero.
wheelchair=*	yes	All of the Valley Metro buses and light rail trains are wheel chair accessible

Bus Master Relationship Member Tags

This section describes the member tags names to use when adding a way to the master relationship.

Way/node	Role	Recurrence?	Discussion
	child	Zero or more	The relationships that make up the route. Typically there are two member relationships in each master route. NOTE: I wonder if north/south/east/west/inbound/outbound would be more useful than child.

Bus Child/Detail/Member Relationship Tags

Key	Value	Explanation
colour=*	a color name or a hex triplet	(optional) I don't know if this is useful yet. Colour code noted in hex triplet format. Especially useful for public transport routes. Example: "#008080" for teal colour.
description=*	a short description	The description helps expand on the ref value such as South Bound Central Avenue.
distance=*	distance	(optional) The distance tag will have to be added later. The distance covered by this route, if known. For information of users and automatic evaluation; e.g., of completeness. Given including a unit and with a dot for decimals. (e.g., "12.5km").
is_in=*	USA;AZ;Arizona;Maricopa;Phoenix	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:city=*	Phoenix	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:country=*	United States of America	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:country_code=*	USA	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:county=*	Maricopa	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:municipality=*	City of Phoenix	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:state=*	Arizona	There are several systems called Valley. These tags will set the location of the relationship textually.
is_in:state_code=*	AZ	There are several systems called Valley. These tags will set the location of the relationship textually.
name=*	bus 0 XX	Where XX = NB, SB, EB, WB, IB, or OB for North Bound, South Bound, East Bound, West Bound, In Bound, or Out Bound respectfully. The IB and OB names will be more useful on the Grand Avenue limited or the express routes. In practice bus 0 NB is more useful because you will see this name in the JOSM relationship list. In addition, the routes sort together near transit centers by placing the route number first.
network=*	Tag:network=regional / Tag:network=local	For the Phoenix Metro area, Tag:network=regional will be used for express buses and Tag:network=local will be used for all local and circular routes.
note=*	Why is_in tags	I used Valley Metro Office location of 301 N Central Ave, Phoenix, AZ for the is in tags. I think some of the original relationships have gone missing.
operator=*	operator name	Valley Metro
operator:en=*	operator name	Valley Metro
public_transport:version=*	2	Useful for JOSM Validation.
ref=*	0	For example, 0 is used for the Central Avenue route.
route	bus
roundtrip=*	yes/no	roundtrip=no on most of the routes. roundtrip=yes for circular such as the downtown Dash route.
symbol=*	symbol description	(optional) I don't know if this is useful yet.
type	route	Indicates this relation represents a route.
website=*	URL	Find the link to the Valley Metro page such routes.valleymetro.org/timetables/transit_route/611?type=2 for route zero.
wheelchair=*	yes	All of the Valley Metro buses and light rail trains are wheel chair accessible

Bus Child/Detail/Member Relationship Member Tags

Still working on understanding this section based on the Relation:route#Members page.

Way/node	Role	Recurrence?	Discussion
	forward/backward	Zero or more	Since a relationship will be used for each route direction, forwared may be the only required member tag. If a route should be followed in only one direction for some or all of its length, the "role" can indicate this for some or all of the constituent ways. "Forward" means the route follows this way only in the direction of the way, and "backward" means the route runs only against the direction of the way. Rendered on the cycle map (example).
	stop:<XXXX>	Zero or more	A bus stop on the route. The order of the members in the relation should be identical to the order in the timetable. The number or XXXX is not needed to preserve the order of stops. It is only a guide to help mappers finding missing or misplaced stops. For XXXX use 0010 for the first stop. The leading zeros will keep the numbers sorted. The numbers will increment by 10. incrementing by 10 will let us slip in stops if one or more are skipped.