ratrun

@otbutz > NO IMPLICIT -> acting as a pedestrian TRAFFIC_SIGN -> bicycle=dismount, vehicle=no OK. > If we're not allowed to use the road either way, we can also keep `FALSE`/`NO`....

> isn't this accessibility information already available via foot_access && !bike_access? How would a custom model for bicycles theoretically look like which routes on such a combination? I put `foot_access`...

> Instead of the current code in BikeCommonAccessParser: could we not just remove the `vehicle` key from the `restrictionKeys`? Because without it this would make the code more complex and...

> And is a change required in BikeCommonAverageSpeedParser because of this? Should we reduce the speed for vehicle=forestry/agricultural to walking speed? As I understand we currently skip these roads and...

A probably simpler solution is to define a key with which it is possible to hide the route as long as the key is pressed. Komoot uses the `m' key...

> t would be really amazing to be able to add those bicycle infrastructure informations (f.e. for `cycleway:right = lane` or `cycleway:right=share_busway` ) as Encoded Values/"Road attribute". > It would...

@vizsim Thanks for the visualization. I think now I understood the basic idea, but I'm not sure about the details. If I got it right you want to derive this...

> It looks that living_street is avoided for bike and mtb profiles but racing bike seems routing fine. Where the difference come from? We are de-prioritizing `highway=residential` to SLIGHT_AVOID for...

> What do you mean about `MaxSpeedCalculator`? I enabled it in the config but with 4km/h for living_street it worked as in my initial post. Or you meant that it...

I didn't see that you already upgraded to version 3.0 ! But I also didn't notice any strange behavior with my version. Is it possible to trigger a build action...