Cards stacked against higher numbered bus routes on Transport Map

We all know about respecting our elders. But when it comes to higher numbered bus lines, the opposite occurs: the lower numbered lines get repeated much more often, there on layers=T (OpenStreetMap website Transport Map).

Pinging @Andy_Allan

I would assume, that all bus numbers are getting concatenated per highway-segment, starting with the lowest number. The shorter the segments, the less bus routes can be displayed. So your result is kind of expected.

Alas, it is all in the same segment,

One moment as I do a deep node check…
OK so there are a lot of nodes in that segment.
But, OK, if that’s what’s causing it, then how would we ever manage to get street names on the map, especially with curvy roads?


Here is a different version.

I’m told buses aren’t even to run by these routes. So FlixBus routes are visible in countless streets, but don’t actually represent anything on the ground.
IMO it’s preferable to not show buses on transport maps by default.

But some people like taking the bus.
Sometimes our BMWs are in the repair shop.

Why would we display random routes on streets? Some people like taking airplanes for the same journey, but we don’t display these either on random streets.

I’m not sure what you mean by ā€œrandom routesā€. In my city the majority of public transport is by bus - not displaying these would mean a public transport map wouldn’t really be a public transport map. There is nothing random about what is displayed.

7 Likes

Yes, your second version is just on overlay and in that all ways used by the same routes are combined into one line. So the labels are behaving more like you prefer (as I understand).

In your first example the streets are not combined and the route labels seems to have a lower priority than the stop labels. So their sequence gets interrupted.

1 Like

I am trying to represent buses on my own map and here’s what I found:

Bus routes are represented as separate lines from the streets they go on. On the OSM database they share the segments, but on the rendering database (which is not the same) they do not. You render the route and you label on the line. Since the rendering engine makes sure labels do not step on each other (unless told to), clumps of labels and missing labels are part of the pseudo randomness of how the data is.

As for Flixbus, we have the problem that there is no ā€œofficialā€ way to separate local from regional from national from everything else routes. There’s this proposal:

but was abandoned.

1 Like