I think what I'm trying to say is: there are many more bus routes (and their variations) than train route relations to be mapped. If we insist that it has to be:
stop_position platform so double tagging, I think I'll abandon and I'll understand that most people will never start mapping public transport as it is effectively too complicated. I'm working on automating it, during a second GSoC of code project now, but that is something that will always remain a burden. Duplication of tagging and the apparent need for adding information about stops twice to the route relations. So my question remains: why can't we have NODES with all the details next to the road. These nodes in the route relations and have the stop_position, the platform way, the shelter, the waste_basket, the bench as extra items that go into a stop_area relation, preferably one per direction of travel ? I just spent another hour and 20 minutes converting 1 line from version 1 to version 2. The 'simple' way. It might have taken me 2 hours or more if everything had needed to be mapped double. https://www.youtube.com/watch?v=_R9cQ73YZp8 Polyglot 2017-05-12 23:25 GMT+02:00 Tijmen Stam <mailingli...@iivq.net>: > On 12-05-17 20:12, Colin Smale wrote: > >> How about a step back for a second here... What is the stop_position >> intended for? Who is it intended to help or inform? A bit of context >> would help to rank the possibilities. >> >> I remain by my earlier standpoint that a stop_position is too much >> detail for a route as it is too variable to be useful. Trains on the >> same route will be longer or shorter, and will use different tracks and >> different platforms from time to time. What stays constant when >> considering the route is the station itself, so this would be the right >> entity to make part of the route. >> > > For railway routes, I see the stop_position as the technical point that > ties together the track with (railway realm) to the platform (pedestrian > realm). Not the actual exact point at which a train should stop. > > For bus routes it has the added bonus of being the (approximate) position > of where the bus stops. I say approximate, because in the bus company I > work at, the bus stop's position in our systems is averaged from the bus' > GPS readings at the point the doors open. On some buses however, the GPS > reader is over the driver, while at others, it's at the rear end. Something > that can make a difference of 25 metres on our long double-bendy buses, > which is quite a lot, as the "geofence" around a bus stop is by default 30 > metres, so a small misalignment of 5m combined with a different GPS > position on the bus, with added GPS disturbance in built-up areas, might > make the bus think it's not at the stop yet, making a difference in price > for those who use contactless ticketing. > > Tijmen/IIVQ > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
