These are two bus stops, of the same line, exactly one in front of the other but with different code and name. In this case what should I do? Creating a bus stop and two platforms and assign the station code and name in the platforms? (All the examples put the name in the bus stop)
In Belgium I’ve been developing a system that works for us.
I don’t know why the examples on the wiki make the stop_position node the one with all the details.
Over here it’s the node next to the way, that has historically received the highway=bus_stop tag and now public_transport=platform, bus=yes + all the details like name, ref, route_ref, zone, etc.
If there is an actual platform, it gets mapped as a way or an area; separately though.
Then all the objects which belong together for 1 direction get grouped together in a stop_area. 1 per direction of travel, which get grouped together in the mistakenly abolished stop_area_group.
I’d like to see the next version of the public transport scheme changed in this direction. But I’m not holding my breath this will happen.
For the route relations, we’re only adding those public_transport=platform, bus=yes, highway=bus_stop nodes. Not the stop_positions (which aren’t all mapped anyway yet), nor the platform ways. This gives a very clean route relation per variation. Containing nodes for the bus stops and ways for the itinerary.
Figuring out which platforms, shelters, benches, waste baskets and stop positions belong together can be done conveniently using those stop_area relations.
I converted the bus routes to what could be called public_transport:version=2. I added stop_position and split the ways for what I hope are the terminus stops.
Please correct it if those aren’t the terminuses.
Also are there variations which don’t serve Florència?
In that case 2 more route relations would be needed.
I converted the route relations to 1 route per direction/variation.
In the schedules I found, I didn’t see anything about the western branch Cami de Raixa.
If there are more variations, let me know which stops they serve. It means more route relations would be needed. Hopefully I got the terminal stops correct on each side of the itineraries.
Oh, I developed a few tricks to make the job easier. One is a MapCSS file which shows a route relation with an odbl=new tag emphasized, so both the stops and the itinerary stand out from the rest. This makes a world of difference to work with those route relations.