Proposal:Public Transport
Jump to navigation
Jump to search
| Public_Transport | |
|---|---|
| Proposal status: | Approved (active) |
| Proposed by: | Teddych |
| Tagging: | public_transport=stop_position, platform, station, stop_area |
| Applies to: |    
|
| Definition: | This proposal covers a complete view on the public transport and extends the existing and well known tags with more exact and clearly defined new tags. Most of the proposed tags are already widely used and are a de facto standard in several cities in Central Europe. |
| Statistics: |
|
| Rendered as: | Identical to railway=halt, railway=tram_stop, highway=bus_stop and highway=platform |
| Draft started: | 2010-11-29 |
| RFC start: | 2010-12-05 |
| Vote start: | 2011-03-31 |
| Vote end: | 2011-04-20 |
Goal of this Public Transport Proposal
This proposal is an advancement of Oxomoa's Public Transport Schema (English translation).
This proposal covers a complete view on the public transport and extends the existing and well known tags with more exact and clearly defined new tags. Most of the proposed tags are already widely used. With some differences between the cities described in several wiki pages, the new tags are a de facto standard in several cities in Central Europe.
Main Problem with the existing Schema
- Inconsistent handling of railway=tram_stop / railway=halt (node on the way) and highway=bus_stop (node beside the way).
- Missing tag for stop position causes extra preprocessing for routing software.
- No separate tags for stop position and platform / pole.
- Insufficient possibility for line variants for bus lines.
The new Schema in Short
- on the way (street/rail) which marks the stop position (public_transport=stop_position).
- or beside the way which marks the platform or beside the way which marks the pole (public_transport=platform).
- for stop area that contains all relevant elements of a train/subway/monorail/tram/bus/trolleybus/aerialway/ferry stop (type=public_transport/public_transport=stop_area) (optional).
- The route- is split up into two separate direction-s and separate route variants, if required.
- The route master- contains all the relations for the route directions and variants (optional).
What this Proposal does not cover
- This proposal does not replace, deprecate or obsolete the already existing and well known tags. The usage of the proposed tags is recommended but not mandatory.
- Splitting up a route- into segments. This is covered by a separate proposal: Proposed_features/Route_Segments.
- Facilities for handicapped passengers.
- Timetable information.
Stop
Stops are physically represented by poles, shelters, timetables, platforms, bus bays and/or zigzag lines on the street. At the stop passengers are waiting for the transportation vehicle (train/subway/monorail/tram/bus/trolleybus/aerialway/ferry) and can board and leave them when they have stopped.
Stop Position
The stop position is the place where the vehicle usually stops on the rails or on the street.
The stop position is tagged as a on the way, even when the bus stops in a bus bay. The stop position is tagged with the following attributes:
| Key | Value | Comment | Recommendation |
|---|---|---|---|
| public_transport | stop_position | Defines this point as a stop position of the vehicle. | mandatory |
| train | yes / no | If at this stop position stop trains. | recommended if yes, else optional |
| subway | yes / no | If at this stop position stop subways. | recommended if yes, else optional |
| monorail | yes / no | If at this stop position stop monorails. | recommended if yes, else optional |
| tram | yes / no | If at this stop position stop trams. | recommended if yes, else optional |
| bus | yes / no | If at this stop position stop buses. | recommended if yes, else optional |
| trolleybus | yes / no | If at this stop position stop trolley-buses. | recommended if yes, else optional |
| aerialway | yes / no | If at this stop position stop aerialways. | recommended if yes, else optional |
| ferry | yes / no | If at this stop position stop ferries. | recommended if yes, else optional |
| name | Individual name | The name by which the stop position is known. | recommended if no public_transport=stop_area exists, else optional |
| ref | Reference | The reference by which the stop position is known. | recommended if no public_transport=stop_area exists, else optional |
| uic_ref | UIC reference | The UIC reference by which the stop position is known. | recommended if no public_transport=stop_area exists, else optional |
| uic_name | UIC name | The UIC name by which the stop position is known. | recommended if no public_transport=stop_area exists, else optional |
| operator | Operator | Name of the company that operates the stop position | recommended if no public_transport=stop_area exists, else optional |
| network | Local / regional network | Name of the network the stop position belongs to | recommended if no public_transport=stop_area exists, else optional |
Platform
The platform is the place where passengers are waiting for the vehicles.
The platform is tagged as or where the passengers can wait for the vehicles. If there is no platform in the real world, one can place a at the pole with public_transport=platform.
| Key | Value | Comment | Recommendation |
|---|---|---|---|
| public_transport | platform | Defines this way or area as a platform where passengers are waiting for the vehicle. If there is no platform in the real world, one can place a node at the pole. | mandatory |
| area | yes / no | If the platform is an area. | recommended if yes, else optional |
| name | Individual name | The name by which the platform is known. | recommended if no public_transport=stop_area exists, else optional |
| ref | Reference | The reference by which the platform is known. | recommended if no public_transport=stop_area exists or differs, else optional |
| uic_ref | UIC reference | The UIC reference by which the platform is known. | recommended if no public_transport=stop_area exists, else optional |
| uic_name | UIC name | The UIC name by which the platform is known. | recommended if no public_transport=stop_area exists, else optional |
| operator | Operator | Name of the company that operates the platform. | recommended if no public_transport=stop_area exists, else optional |
| network | Local / regional network | Name of the network the stop position belongs to | recommended if no public_transport=stop_area exists, else optional |
| shelter | yes / no | If there is a shelter that is not tagged separately with amenity=shelter. | recommended if yes, else optional |
| bench | yes / no | If there is a bench that is not tagged separately with amenity=bench. | recommended if yes, else optional |
| covered | yes / no | For platforms under the surface. This does not replace a correct layer key. | recommended if yes, but not needed if there is a specific structure (other than a general landuse classification) on a higher layer covering the whole platform. |
Station
A station is an area dedicated to and particularly designed for passenger access to Public Transport, considerably bigger than a pair of bus stops or tram stops.
These are typical properties of a station (not all of them need to be present):
- A schematic layout
- Multiple lanes or rail tracks with stop positions in parallel, with platforms along them
- Alternatively, in particular at bus stations, there is one big platform in the middle, with stop positions and a service highway around it and maybe an additional platform on the outside with additional stop positions around the service highway
- Of course, other layouts are possible
- The station is not a normal part of the road network
- No access for private motorcars (maybe except station related things, such as a drop-off zone for passengers) inside the station
- The outline of the station (the schematic layout) can be recognised easily
- There are amenities for waiting passengers, such as
- Protection against the weather, which may be anything from a small shelter, up to a building around the whole station
- Kiosks or vending machines
- A Park&Ride parking beneath the station
- Extensive Information Services
- Many stations provide amenities for waiting drivers
The station itself is mapped as an , usually covering the outline described above, including amenities located inside the dedicated area. If the station is completely (or most of it) inside a station building, the building is the outline. If the station is not fully or mostly covered by a building, any existing buildings should be mapped at their place inside the station outline.
If a station outline is not known, the station can be mapped as a , leaving the details to others.
Please note that more than one station can be member of one and the same stop area. Conversely, it can happen that one station belongs to more than one stop area - if the station contains stop areas (or parts of these) with different attributes, such as different networks.
| Key | Value | Comment | Recommendation |
|---|---|---|---|
| public_transport | station | Defines the station as such. | mandatory |
| name | Individual name | The name by which the station is known. | recommended |
| area | yes / no | If the station outline is an area and not a building. | required if yes, else optional |
| building | yes / no | If the station outline happens to be the main outline of the station building. | required if yes, else optional |
| operator | Operator | Name of the company that operates the station building/area. | optional |
| network | Local / regional network | Name of the network the station belongs to | optional |
| covered | yes / no | For stations under the surface. This does not replace a correct layer key. | recommended if yes, but not needed if there is a specific structure (other than a general landuse classification) on a higher layer covering the whole station. |
Stop Area
The stop area is a relation that contains all elements of a train/subway/monorail/tram/bus/trolleybus/aerialway/ferry stop.
The stop area is the logical combination of the stop position(s) and the platform(s) and is tagged as a . The relation can also contain other elements like public_transport=station, amenity=shelter or amenity=bench. Alternatively they may be captured by appending the proper tags shelter=yes or bench=yes to the public_transport=platform-primitive.
Usually a stop area has one unique UIC reference and one unique name.
If only one node exists (e.g. only one node public_transport=platform representing the pole), it is recommended to forgo the stop area relation. Instead, put the information usually stored in the relation into the node attributes.
| Key | Value | Comment | Recommendation |
|---|---|---|---|
| type | public_transport | Defines this relation as a public transport relation. | mandatory |
| public_transport | stop_area | Defines this relation as a stop area. | mandatory |
| name | Individual name | The name by which the stop is known. | recommended |
| name:<qualifier> | Operator's or network's name | The name by which the stop is known by a specific operator or network. | recommended if the stop is known under different names by different operators or networks |
| ref | Reference | The reference by which the stop is known. | recommended |
| ref:<qualifier> | Operator's or network's reference | The reference by which the stop is known by a specific operator or network. | recommended if the stop is known under different references by different operators or networks |
| uic_ref | UIC reference | The UIC reference by which the stop is known. | recommended if available |
| uic_name | UIC name | The UIC name by which the stop is known. | recommended if available |
| operator | Operator | Name of the company that operates the stop. | recommended if available |
| network | Local / regional network | Name of the network the stop belongs to. | recommended if available |
Members of this relation are:
| Role | Refers to | Comment | Recommendation |
|---|---|---|---|
| stop | public_transport=stop_position | position(s), where the vehicle stops | recommended if available |
| platform | public_transport=platform | the platform(s) | recommended if available |
| none | public_transport=station | the station building/area | recommended if it belongs to the stop area |
| none | amenity=* | examples: shelter, bench, bicycle_parking, taxi | recommended if available |
Route
A route/service is represented by vehicles that always run the same way with the same reference number.
Route Direction / Variant
Each direction or variant of a route is represented by a separate relation.
Each direction of a route should be tagged as a separate . If a route has several variants (e.g. different way at weekend), these variants should also be in separate relations.
The roles alternate, forward and backward should not be used any more.
Each direction/variant relation contains all available stop_positions, platforms and ways.
Each stop is included with two elements (if available): first the stop_position tagged with role stop and immediately followed by the corresponding platform tagged with role platform. The stops (stop_positions and platforms) should be inserted beginning with the initial stop_position/platform and ending with the terminal stop_position/platform.
If a stop is only for exiting or entering the vehicle (common for nightly services) the roles stop and platform should be replaced with stop_exit_only or stop_entry_only and platform_exit_only or platform_entry_only.
Inserting the stop_position is important to know where the vehicle stops. Inserting the platforms is needed for correct pedestrian routing.
After all the stops all the used ways should be inserted into the relation with an empty role. The ways should be inserted beginning with the way at the initial stop position and ending with the way at the terminal stop position.
| Key | Value | Comment | Recommendation |
|---|---|---|---|
| type | route | Defines the relation as route. | mandatory |
| route | train / subway / monorail / tram / bus / trolleybus / aerialway / ferry | Defines the route as train, subway, monorail, tram, bus, trolleybus, aerialway or ferry route. | mandatory |
| from | Initial stop | Initial stop where the variant starts. | recommended |
| to | Terminal stop | Terminal stop where the variant ends. | recommended |
| via | Important via stop(s) | If there are several variants of a line here should be inserted an important and well known stop to clarify via where the route goes. | recommended if several variants in one direction of a route exists |
| name | <vehicle type> <reference number>: <initial stop> => <terminal stop> | Prose description of route variant. <Vehicle type> should be identical to route=*. Example: Bus 201: Uitikon Waldegg, Bahnhof => Uitikon, Wängi | recommended |
| ref | Reference | The reference number by which the service is known. | recommended if no route_master=* exists, else optional |
| ref:<qualifier> | Operator's or network's reference | The reference by which the service is known by a specific operator or network. | recommended if the service changes the reference number when crossing the network's border and no route_master=* exists |
| operator | Operator | Name of the company that operates the service. | recommended if no route_master=* exists, else optional |
| network | Local / regional network | Name of the network the route belongs to. | recommended if no route_master=* exists, else optional |
| colour | Colour | Route/Service colour (HTML named colour or web colour in hexadecimal format). | recommended if no route_master=* exists, else optional |
Members of this relation are
| Role | Refers to | Comment | Recommendation |
|---|---|---|---|
| stop / stop_exit_only / stop_entry_only | public_transport=stop_position | stop positions ordered in sequence from=* .. to=* followed by the corresponding platform (if available) | recommended if available |
| platform / platform_exit_only / platform_entry_only | public_transport=platform | platforms and/or poles orderedin sequence from=* .. to=* headed by the corresponding stop position | recommended if available |
| none | all s used by the vehicle |
in sequence from=* .. to=* representating the route of the vehicle | mandatory |
Route Master
The route master is a relation that contains all the direction and variant routes and the information that belongs to the whole service.
A master- contains all the important information that belongs to the service. All the variants/directions are members of this master relation.
| Key | Value | Comment | Recommendation |
|---|---|---|---|
| type | route_master | Defines the relation as route_master. | mandatory |
| route_master | train / subway / monorail / tram / bus / trolleybus / aerialway / ferry | Defines the route_master as train, subway, monorail, tram, bus, trolleybus, aerialway or ferry route_master. | mandatory |
| ref | Reference | The reference number by which the service is known. | recommended |
| ref:<qualifier> | Operator's or network's reference | The reference by which the service is known by a specific operator or network. | recommended if the service changes the reference number when crossing the network's border |
| name | <Vehicle type> <Reference number> | Short prose description of route master. <Vehicle type> should be identical to route=*. Example: Bus 201 | recommended |
| operator | Operator | Name of the company that operates the service. | recommended if available |
| network | Local / regional network | Name of the network the route belongs to. | recommended if available |
| colour | Colour | Route/Service colour (HTML named colour or web colour in hexadecimal format). | recommended if available |
Members of this relation are
| Role | Refers to | Comment | Recommendation |
|---|---|---|---|
| none | all route variant/direction s |
mandatory |
Examples
All the examples presented here are full featured examples. In practice after the first visit of an area one can only map the stop_position (sitting in the bus) or the platform (walking through). So it is common only to map one node per visit, hoping another mapper or will do further work.
Because the proposed tags do not get rendered at the moment, in these examples the well known tags are also added to the proposed tags. When and if this proposal gets approved and rendered, these duplicate tags will be removed.
| Map | Relation | Used Tags | Description |
|---|---|---|---|
| <map lat="47.337727" lon="8.4778555" z="17" w="200" h="200" /> | 1342737 1342737 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
Simple bus stop served in only one direction. public_transport=platform represents the pole, a platform does not exist.
|
| <map lat="47.3600164" lon="8.4673981" z="17" w="200" h="200" /> | 1320851 1320851 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
Simple bus stop served in only one direction. public_transport=platform represents the platform.
|
| <map lat="47.3735676" lon="8.4486366" z="17" w="200" h="200" /> | 1343475 1343475 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
Simple bus stop served in both directions situated exactly opposite each other. |
| <map lat="47.3722393" lon="8.4511578" z="17" w="200" h="200" /> | 1244882 1244882 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
Simple bus stop served in both directions, with the opposite bus bays offset against each other. |
| <map lat="47.3112" lon="8.4933664" z="17" w="200" h="200" /> | 1283483 1283483 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
Simple bus stop where the bus has a segregated service way. The stop position is located on the highway=service. |
| <map lat="47.37594" lon="8.53736" z="17" w="200" h="200" /> | 7572006 7572006 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
A combined bus and tram stop. |
| <map lat="47.3681545" lon="8.4626128" z="17" w="200" h="200" /> | 1281532 1281532 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
Two bus stops close to each other. |
| <map lat="47.3662" lon="8.4656" z="17" w="200" h="200" /> | 1274170 1274170 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
One bus stop and one railway halt close to each other. |
| <map lat="47.35755" lon="8.4377" z="16" w="200" h="200" /> | 1279034 1279034 |
public_transport=stop_position// public_transport=platform type=public_transport+public_transport=stop_area |
A railway station with building and parking and a bus station for several bus lines. |
| 1244886 1244886 |
public_transport=route public_transport=route_master |
Bus route with route master. One way has simple course, the other way has two variants. | |
| 1342798 1342798 |
public_transport=route public_transport=route_master |
Bus with ring route. Initial stop and terminal stop is identical, so from=* and to=* is identical. This route has two variants. |
Compatibility with well known tags
The proposed tags can and do coexist with the well known tags. The usage of the new tags is recommended but not mandatory.
This proposal covers several already existing and well known tags related to public transport. These well known tags still have their eligibility and can and do coexist with the well known tags. The usage of the new tags is recommended but not mandatory.
How the well known tags can be mapped/reused with the new public transport schema is described below:
| Existing Tag | Interpreted as | Comment |
|---|---|---|
| highway=bus_stop beside a way/street where buses are allowed | public_transport=platform | This covers the pole/shelter of a bus stop and can be on a footway or sidewalk. |
| highway=bus_stop on a way/street where buses are allowed | public_transport=stop_position + bus=yes | This covers the stop position of a bus. |
| amenity=bus_station tagged as node beside a way/street | public_transport=platform | This covers the pole/shelter of a bus stop. |
| amenity=bus_station tagged as node on a way/street | public_transport=stop_position + bus=yes | This covers the stop position of a bus. |
| amenity=bus_station tagged as area | public_transport=station + area=yes | This covers the area of a bus station. |
| amenity=bus_station tagged as building | public_transport=station + building=yes | This covers a bus station building. |
| highway=platform | public_transport=platform | This covers the platform of a bus stop. |
| railway=tram_stop on the rails | public_transport=stop_position + tram=yes | This covers the stop position of a tram. |
| railway=halt on the rails | public_transport=stop_position + train=yes | This covers the stop position of a train. |
| railway=platform | public_transport=platform | This covers the platform of a tram/train stop. |
| railway=station tagged as area | public_transport=station + area=yes | This covers the area of the station. |
| railway=station tagged as building | public_transport=station + building=yes | This covers a building of a train station. |
| building=train_station | public_transport=station + building=yes | This covers a building of a train station. |
Rendering
Stop Position
A stop position can be mapped as an icon depending of the vehicle type that is stopping at the position (e.g. highway=bus_stop) or as a blue or red point.
If the stop position is not part of a stop area then the name should get rendered too. If there is a stop area relation, the name of the stop area should get rendered instead once per stop area.
Platform
Should be rendered identical to railway=platform/highway=platform. Additionally also a node should get rendered.
If the platform is not part of a stop area then the name should get rendered too. If there is a stop area relation, the name of the stop area should get rendered instead once per stop area.
Station
If the station is a building, it should get rendered as a building. If it is an area, it can get rendered with a similar but different colour then the background.
Stop Area
For simple maps the name of the stop area should get rendered instead of the names of the underlaying nodes/ways. Special public transport maps can also draw the area where the stop area is located.
See also
- User:Oxomoa/ÖPNV-Schema (German)
- User:Oxomoa/Public_transport_schema (English)
- RU:Рисование общественного транспорта по схеме Oxomoa (Russian)
- Proposed_features/unified_stoparea
- Proposed features/Stop Area
- Tag:highway=bus_stop
- Talk:Tag:highway=bus_stop
- DE:Tag:highway=bus_stop
- DE_talk:Tag:highway=bus_stop
- Public_Transport
- Relation:route#Public_Transport_Routes
Voting
Voting ended at 2011-04-20.
I approve this proposal. --Teddych 08:36, 31 March 2011 (BST)- I approve this proposal. --Johnwhelan 09:02, 31 March 2011 (EST)
- I approve this proposal. --TobWen 08:45, 31 March 2011 (BST)
- I approve this proposal. --ipodolsk 09:56, 31 March 2011 (BST)
- I approve this proposal. --Zverik 10:04, 31 March 2011 (BST)
- I approve this proposal. --Bernd 10:17, 31 March 2011 (BST)
- I approve this proposal. --Kolen 10:20, 31 March 2011 (BST)
- I approve this proposal. --Xificurk 09:22, 31 March 2011 (UTC)
- I approve this proposal. --Ilis 10:23, 31 March 2011 (BST)
- I approve this proposal. --mdk 10:27, 31 March 2011 (BST)
- I approve this proposal. --dkiselev10:34, 31 March 2011 (BST)
- I approve this proposal. --Hind 10:36, 31 March 2011 (BST)
- I approve this proposal. --Eugene 10:44, 31 March 2011 (BST)
- I approve this proposal. --Vrs 10:53, 31 March 2011 (BST)
- I approve this proposal. --MetiorErgoSum 10:55, 31 March 2011 (BST)
- I approve this proposal. --Spontex 10:05, 31 March 2011 (UTC)
I oppose this proposal. This is much too complicated. We need to make best use of existing tags, not invent a whole new tagging system. --RichardMann 11:00, 31 March 2011 (BST)- I oppose this proposal. I'm of the same opinion like RichardMann.--R-michael 17:50, 31 March 2011 (BST)
- I approve this proposal. It's about time we come up with a consistent way of mapping PT and I know Teddych already tried to 'reuse' the existing tags, so it's probably better to start from scratch. I hope this will get rendered soon! --Polyglot 11:12, 31 March 2011 (BST)
- I approve this proposal. --vsandre 11:32, 31 March 2011 (BST)
- I approve this proposal. --EdLoach 11:37, 31 March 2011 (BST)
- I approve this proposal. -- Artyomka 11:59, 31 March 2011 (BST)
- I approve this proposal. -- Derick Rethans 12:10, 31 March 2011 (BST)
- I approve this proposal. -- Dieterdreist 12:21, 31 March 2011 (BST)
- I approve this proposal. -- Ueliw0 12:27, 31 March 2011 (BST)
- I approve this proposal. --Guerda 12:34, 31 March 2011 (BST)
- I approve this proposal. -- Dl8utl 12:37, 31 March 2011 (BST)
- I approve this proposal. -- Almich 12:41, 31 March 2011 (BST)
- I approve this proposal. -- Kaitu 13:11, 31 March 2011 (BST)
- I approve this proposal. -- Pecisk 13:20, 31 March 2011 (BST)
- I approve this proposal. --Landwirt 13:33, 31 March 2011 (BST)
- I approve this proposal. --Flaimo 13:57, 31 March 2011 (BST)
- I oppose this proposal. This is much too complicated. We need to make best use of existing tags, we didn't need such a complex new tagging system. -- ReLuc13:58, 31 March 2011 (BST)
- I approve this proposal. --1piedsurTerre 14:09, 31 March 2011 (BST)
- I don't like this proposal. I find many problems in this proposal which seems not mature enough for a vote :
1. your replace highway=platform and highway=bus_stop by public_transport=platform. How do I know if the platform is for a bus or a tramway ? And in the daily language, people go to a 'bus stop' not to a 'platform'. Sounds that it is a proposal done by and for professionals, not for the average public of OSM contributors. And the wiki said until know that the 'stop' was about the area for passengers (user point of view), not the 'stop' for the bus itself (operator point of view). You change this fundamental definition and it will confuse a lot since many mappers tag as public transport users, not as operators.
2. You suggest to replace amenity=bus_station by public_transport=station + area=yes. This is an overuse of the current tag area=*. Once you have a polygon, you don't need a tag area=yes in most of the current OSM tags (basically it is just required for highways because we don't know if a closed highway is a loop or a surface).
3. I don't understand why you add train=yes on your public_transport=stop_position. If the node is on the railway, we know it is a train, not a bus !
4. in the section 'Compatibility with well known tags', you suggest to replace highway=bus_stop by public_transport=platform. It's only true for those how tagged the bus-stop for passangers, not for those who tagged the node on the highway. Both co-existed in the past with the same tag and you ignore it in this paragraph.
5. asking a relation for each variant of the route is over complicated. The method of how routes relations are already breaking highways is already stupid but that's another story. -- Pieren 14:26, 31 March 2011 (BST)
- to 3.: "If the node is on the railway, we know it is a train, not a bus!" Sure? In Karlsruhe bus and tram/light_rail share some nodes and also train and light_rail share some nodes and at http://commons.wikimedia.org/wiki/File:25a_Bf_Zwickau_Zentrum,_VT45_VB.jpg there may stop also a bus instead of the train ... --Mueck 18:05, 31 March 2011 (BST)
- okay for 3. you ask all bus stops and trains stop to add bus=yes or train=yes because you can have a bus stoping on a railway. I though that we only map exceptions in OSM... --Pieren 21:01, 31 March 2011 (BST)
- where do you get this from? Generally there are no defaults (besides some exceptions like layer=0) for omitted keys. --Dieterdreist 17:33, 6 April 2011 (BST)
- okay for 3. you ask all bus stops and trains stop to add bus=yes or train=yes because you can have a bus stoping on a railway. I though that we only map exceptions in OSM... --Pieren 21:01, 31 March 2011 (BST)
- to 3.: "If the node is on the railway, we know it is a train, not a bus!" Sure? In Karlsruhe bus and tram/light_rail share some nodes and also train and light_rail share some nodes and at http://commons.wikimedia.org/wiki/File:25a_Bf_Zwickau_Zentrum,_VT45_VB.jpg there may stop also a bus instead of the train ... --Mueck 18:05, 31 March 2011 (BST)
- I approve this proposal. --Kellerma 14:33, 31 March 2011 (BST)
- I approve this proposal. --Rad-ab 15:47, 31 March 2011 (BST)
- I approve this proposal. --Dchiles 15:20, 31 March 2011 (BST)
- I approve this proposal. --Oli-Wan 16:12, 31 March 2011 (BST)
- I approve this proposal. georg@familieverweyen.de 16:22, 31 March 2011 (BST)
- I approve this proposal. --geri-oc 17:42, 31 March 2011 (BST)
- I approve this proposal. but I oppose names for route and route master relations, not deprecating the old tags and using area=yes where it's not necessary. -- Errt 17:20, 31 March 2011 (BST)
- I approve this proposal. Renaud 17:55, 31 March 2011 (BST)
- I approve this proposal. --Mueck 18:05, 31 March 2011 (BST)
- I approve this proposal. --Surveyor54 18:54, 31 March 2011 (BST)
- I approve this proposal. --Don-vip 20:21, 31 March 2011 (BST)
- I approve this proposal. OK and already in wide use, even if some minor tags such as bin=yes/no and ref_name=* (replacement for uic_name=*, which would be ref_name:uic=* if needed) are still missing here. --Fabi2 20:45, 31 March 2011 (BST)
- I approve this proposal. --DINENISO 21:19, 31 March 2011 (BST)
- I approve this proposal. Good for complex public transports (multi-modal stops...) but not for simple bus stops (highway=bus_stop is better for that) --Dri60 21:25, 31 March 2011 (BST)
- I approve this proposal. --JonathanMM 21:59, 31 March 2011 (BST)
- I approve this proposal. --wambacher 22:59, 31 March 2011 (BST)
- I approve this proposal. I don't think that all of the relations are strictly necessary for every instance of e.g. a stop group, though. --Tordanik 22:24, 31 March 2011 (BST)
- I approve this proposal. Kachkaev 22:45, 31 March 2011 (BST)
- I approve this proposal. --Langerweher 05:38, 1 April 2011 (BST)
- I approve this proposal. --Hobby Navigator 07:05, 1 April 2011 (BST)
- I approve this proposal. --Ajoessen 07:18, 1 April 2011 (BST)
- I approve this proposal. --SB79 09:31, 1 April 2011 (BST)
- I approve this proposal. --Head 09:33, 1 April 2011 (BST)
- I approve this proposal. --Agsochi 12:36, 1 April 2011 (BST)
- I approve this proposal. --Elster 16:44, 1 April 2011 (BST)
- I approve this proposal. --MarkS 22:20, 1 April 2011 (BST)
- I approve this proposal. --Pobice 22:47, 1 April 2011 (BST)
- I approve this proposal. --higa4 05:09, 2 April 2011 (BST)
- I approve this proposal. --luch86 08:13, 2 April 2011 (BST)
- I approve this proposal. Stud 13:46, 2 April 2011 (BST)
- I approve this proposal. Walterschloegl 17:30, 2 April 2011 (BST)
- I approve this proposal. --Julienfastre 17:59, 2 April 2011 (BST)
- I approve this proposal. flacus 14:13, 3 April 2011 (BST)
- I oppose this proposal. LMB 15:45, 3 April 2011 (BST). It's overblown, and forces mappers to do many things that could be easily done by a script. It's not mature enough.
- I approve this proposal. --Seehundeführer 17:43, 3 April 2011 (BST)
- I approve this proposal. Johan Jönsson 18:30, 3 April 2011 (BST) good to have only one key: public_transport=platform
- I oppose this proposal. Pnorman 20:09, 3 April 2011 (BST) Aside from the difficulties with mapping (see LMB's objections) it is not backwards compatible.
- I approve this proposal. --Sev 21:47, 3 April 2011 (BST)
- I approve this proposal. --Weide 06:57, 4 April 2011 (CEST)
- I approve this proposal. Soldier Boy 09:27, 4 April 2011 (BST)
- I approve this proposal. --Wolfbert 17:03, 4 April 2011 (BST)
- I approve this proposal. And I think, that the name for route_master should be line. Roles for the stop_position and platform aren't necessary in my opinion. I agree with Pieren that area=yes shouldn't be used and with his 4th point. --Uboot 18:14, 4 April 2011 (BST)
- I approve this proposal. -- Dancingfrank 15:57, 5 April 2011 (BST)
- I don't like this proposal. -- I generally agree with Pieren Wowik 21:15, 5 April 2011 (BST)
- I approve this proposal. -- Janko 11:35, 7 April 2011 (BST)
- I approve this proposal. --BorisC 12:49, 8 April 2011 (BST)
- I approve this proposal. ... thinking that it's at least a step forward. However, I don't like the idea of creating a relation per direction / variant, requiring the wrong people to manage so many relation memberships for ways. We have to extend route relations to handle directions, variants, etc in general - not only for public transport. --Marl 15:16, 9 April 2011 (BST)
- I approve this proposal. --Ant 21:01, 9 April 2011 (BST)
- I approve this proposal. --MForster 22:53, 9 April 2011 (BST)
- I approve this proposal. Lzhl 08:30, 10 April 2011 (BST).
- I approve this proposal. mok0 17:03, 10 April 2011 (UTC).
- I don't like this proposal. agree with dieterdriest. --Hanska 08:21, 12 April 2011 (BST)
- I approve this proposal. --Kallies 07:48, 13 April 2011 (BST)
- I approve this proposal. --Hetzi 09:57, 14 April 2011 (BST)
- I approve this proposal. --Oligo 17:53, 14 April 2011 (BST)
- I approve this proposal. --EvanE 22:09, 19 April 2011 (BST)
- I oppose this proposal. Tizianos 12:07, 20 April 2011 (BST) It is too complicated, see [1] for a better proposal
Voting ended at 2011-04-20. Result is: 83 approve the proposal, 6 oppose the proposal and 3 don't like the proposal. This proposal has been approved.