You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can tell, the current rules are something like that:
When maxspeed:forward and maxspeed:backward have different values, use maxspeed:forward for the coloring
When railway:preferred_direction=backward, use maxspeed:backward instead
In either case, label the track with maxspeed:forward (maxspeed:backward)
I like the first two rules. But could we please label the track with maxspeed:backward (maxspeed:forward) if railway:preferred_direction=backward to make things consistent?
In my example link above, I would expect the western track to be labeled "70 (80)" instead of "80 (70)"
The text was updated successfully, but these errors were encountered:
My knowledge of SQL is somewhat rudimentary, but railway_speed_label seems to already do what I want?! I assume that speed_arr[3] = 2 is the railway:preferred_direction=backward, right? Then why don't I get the rendering as described above?
https://openrailwaymap.org/?style=maxspeed&lat=53.639433463029626&lon=9.905867278575897&zoom=18
As far as I can tell, the current rules are something like that:
I like the first two rules. But could we please label the track with maxspeed:backward (maxspeed:forward) if railway:preferred_direction=backward to make things consistent?
In my example link above, I would expect the western track to be labeled "70 (80)" instead of "80 (70)"
The text was updated successfully, but these errors were encountered: