WikiProject Belgium/Conventions/Bus stops

Belgian transport companies

There are 3 transport companies in Belgium.

De Lijn is divided in 5 entities, but they (mostly) assign only 1 reference number to each stop. The number is shown prominently on the stop sign.
STIB/MIVB is unitary. The number is visible on a sticker on the stop post itself, between the two metal plaques of the stop sign
TEC is subdivided in 6 divisions which each assign their own reference numbers. The number can be found at the bottom of the timetable.

Stops served by two or more operators should be grouped into one single bus stop in OSM. As a consequence, ref=*, route_ref=* and zone=* require suffixes to indicate the operator. There are several cases where each operator assigns a different name to the stop—TEC and De Lijn rarely provide a translation for stops they serve outside of their own region. To solve this, name=* can also have a suffix to identify how each operator names it.

network	full	ref	operator	full
IBXL	-	-	STIB/MIVB	Société des Transports Intercommunaux de Bruxelles - Maatschappij voor het Intercommunaal Vervoer te Brussel
DLWV	De Lijn West-Vlaanderen	(50xxxx)	De Lijn
DLOV	De Lijn Oost-Vlaanderen	(20xxxx)	De Lijn
DLAn	De Lijn Antwerpen	(10xxxx)	De Lijn
DLLi	De Lijn Limburg	(40xxxx)	De Lijn
DLVB	De Lijn Vlaams-Brabant	(30xxxx)	De Lijn
TECB	TEC Brabant-Wallon	(B.....)	TEC	Transports en Commun
TECN	TEC Namur	(N.....)	TEC	Transports en Commun
TECL	TEC Liège-Verviers	(L.....)	TEC	Transports en Commun
TECX	TEC Luxembourg	(X.....)	TEC	Transports en Commun
TECC	TEC Charleroi	(C.....)	TEC	Transports en Commun
TECH	TEC Hainaut	(H.....)	TEC	Transports en Commun

Bus or tram stop

Tags	Example
`public_transport=platform`	platform
`bus=yes`
`tram=yes`
`name=general name of the bus or tram stop or (in Brussels) a bilingual name`	Porte de Hal - Hallepoort
`not_served_by=485;410;306` For express service buses which don't serve all the stops they pass by. This makes it easier for human editors to decide whether to include the stop in the route relation. And it makes it possible to script quality control checks.
`source= -`	source should be included on the changeset
`shelter=yes`	yes/no
`bench=yes`	yes
`bin=yes`	yes

STIB/MIVB

Every bus stop has a name and a unique number xxxx (4 digits, or 4 digits and a letter). Use name:fr and name:nl tags when French and Dutch names are different.

The operator sometimes gives several numbers for the same stop: this happens when a route serves the same stop in both directions, or for platforms that host both tram and bus routes. In such a case, use a dual value with the ";" separator.

Tags	Example
`operator=;-separated list containing STIB/MIVB`	STIB/MIVB
`network=;-separated list containing IBXL`	IBXL
`ref:STIB_MIVB=xxxx`	1129;6354
`route_ref=7;8`	8

De Lijn

Every bus stop has a name, a unique number x0xxxx , and a zone-number yy.

Tags	Example
`name:De_Lijn=name De Lijn assigned to the bus or tram stop, if different from name`	Hallepoort
`ref:De_Lijn=303017`	303017
`operator=;-separated list containing De Lijn`	De Lijn
`network=;-separated list containing DLWV;DLOV;DLAn;DLLi;DLVB`	DLVB
`route_ref:De_Lijn=7;8;9`	7;8;9
`zone:De_Lijn=18`	18

TEC

Every bus stop has a name, a unique code, a zone-number of which only the last 2 digits are visible to the public.

Tags	Example
`name:TEC=name TEC assigned to the bus or tram stop, if different from name`	Porte de Hal
`ref:TECB=ref TEC Brabant-Wallon assigned to the bus or tram stop`	B.....
`ref:TECH=ref TEC Hainaut assigned to the bus or tram stop`	H.....
`ref:TECC=ref TEC Charleroi assigned to the bus or tram stop`	C.....
`ref:TECN=ref TEC Namur assigned to the bus stop`	N.....
`ref:TECL=ref TEC Liège-Verviers assigned to the bus stop`	L.....
`ref:TECX=ref TEC Luxembourg assigned to the bus stop`	X.....
`operator=;-separated list containing TEC`	TEC
`network=;-separated list containing TECH;TECC;TECB;TECN;TECX`	TEC
`route_ref:TEC?=see relations`	E; 365a	`zone:TEC=5163`	5163

Bus station

Tags	Description
The service ways where only the buses may ride: `highway=service` OR no highway tag at all, if the highway is represented as a polygon `vehicle=no` `bus=yes` `lanes=1 or 2` `ref=perron 11` Where the passengers wait: `highway=platform` can be a simple vector (preferably) or a an area optional: `shelter=yes` `bin=yes` `wheelchair=yes` `bench=yes` `tactile_paving=no` On one of the nodes of these platforms: `highway=bus_stop` `name=Leuven station perron 11` optional: `operator=De Lijn` `ref=xxxxx` `zone=yy`

Relations to tie it all together

Stop area relation

A stop is one physical location used by public transport vehicles. If there are bus stops on both sides of the road, they should be treated as two separate stops. Same if there are multiple stops one after each other, each serving a different bus route.

If there are more than one object associated with a particular stop, you may want to group them into a relation.

Create a relation including the various PT-related objects:

The members of the stop_area relation will be:

Role	Presence	Explanation
`platform`	! Required	The stop itself, i.e. main object containing the name, ref, etc. and used in route relations
`platform`	? Optional	The platform way/area, i.e. physical space along the road where passengers will be waiting
`stop`	! Required	The stop position node, i.e. a node attached to the road that has `public_transport=stop_position`, this is where the vehicle actually stops
	? Optional	Shelter (if there is more than one, add all of them)
	? Optional	Waste basket (if there is more than one, add all of them)
	? Optional	Ticket-vending machine (if there is more than one, add all of them)
	? Optional	Station entrances (for metro or premetro stations, typically), tagged with `railway=subway_entrance`

Bus station relation

Tags	Description
`type=site` `site=bus_station` `name=Station Leuven` `operator=De Lijn` `zone=yy` access: link to the platform entrance: in a complicated station links to escalators, elevators, corridors, moving walkways (no role): the child relations containing all the separate bus stops. This can include bus_stop nodes as well.

Group of bus stops with same name

The above type of relation could be used to group together bus stops that have the same name as well. Either on both sides of the street or on several spots around an intersection, then its type would be bus_stop.

Transport interchanges

It's also possible to group several of these relations together in a parent relation, in case of a railway station with a bus terminal next to it, or in case of an airport with a train station/bus station/metro station, etc.

Note: the above is not set in stone. It's a synthesis of the information I gathered during the past few days. So please comment if you have remarks