I just added some max_speed= tags for #OpenStreetMap in Bloomington, Indiana.
Our city code has a default speed limit 25 mph. Exceptions are published in a table in the city code.
It seems possible that adding the correct lower-than-default speed limits from city code to OpenStreetMap could reduce the likelihood that routing algorithms would route car traffic there, which could in turn keep the street safer for other road users.
Ref: https://library.municode.com/in/bloomington/codes/code_of_ordinances?nodeId=TIT15VETR_CH15.24SPRE
@markstos @DemonHusky @bloomington_in
What DemonHusky said:
A map app suggesting a route for a bike will try to minimize time via the slowest streets. For a car, it will try to minimize time via the fastest streets (which are usually more direct in terms of distance)
So if the algorithm suggesting a route thinks all streets are the same speed, bikes and cars will be suggested the same low-distance routes, which will usually be routes featuring excessive speeding by drivers
@pleaseclap @DemonHusky @bloomington_in In the absence of a speed limit signal, the algorithms look for other signals, like the type of road. Cars are routed to arterials over residential streets even they are a bit longer, while bike routing would prefer residential streets.
The Pointz bike routing app is nice because it puts you in control with more options.
@markstos @DemonHusky @bloomington_in I haven’t seen a routing algorithm’s code, but a preference for arterial roads can be explained solely by speed limits
@pleaseclap @DemonHusky @bloomington_in I’ve looked at the code. My servers have bike routing coverage for most of the US and EU with the OpenTripPlanner and Valhalla engines. Occasionally we find edge cases that don’t route optimally and look into patches.
Lots of roads don’t have max speeds in OpenStreetMap which they both use, so other signals are essential.
@markstos @DemonHusky @bloomington_in
You’ve seen your specialty bike routing algorithms. I’m glad they’re good algorithms, however
your first post is about misrepresenting speed limits in OpenStreetMap (which is a community resource, yes?) to effect driver behavior, and what systemic effects this would have for every user of every tool that uses OpenStreetMap
Even if you don’t think this will lead to congestion on the same roads, I’m not sure it’s ethical
@pleaseclap @DemonHusky @bloomington_in Misrepresentating? I found streets where the max_speed value was missing and added the correct values based on city code.
@markstos @DemonHusky @bloomington_in
Is that not your suggestion, here?
“It seems possible that adding lower-than-default speed limits to OpenStreetMap could reduce the likelihood that routing algorithms would route car traffic there, which could in turn keep the street safer for other road users.”
@pleaseclap @DemonHusky @bloomington_in In context, the rest of the post says that exceptions are published in city code and provides an example link to the table in our code.
I’m suggesting to use real speed limits from city code. Sorry if that wasn’t clear.
@markstos @DemonHusky @bloomington_in So the situation is, lots of low-speed streets are currently assigned a higher speed by default in OSS, and fixing that is a helpful service?
That’s my bad: sorry for being a deviant who assumes the worst
@markstos @DemonHusky @bloomington_in
Besides speed, there’s probably also an “is there a bike lane” check, which would mitigate the problem a bit in places where the main roads mostly also have bike lanes
@pleaseclap @DemonHusky @bloomington_in That’s right. Many signals are involved. Some factor in cyclist aversion to hills for example.