utack / utack_brouter_profile Goto Github PK

A BRouter profile for some light touring or commuting with a city bike

utack_brouter_profile's Introduction

utack_brouter_data

A profile for bike routing with BRouter (found at https://github.com/abrensch/brouter )

What is this profile useful for?

The profile was built for some light touring or commuting with a city bike.
It priorizies good ways and easy riding, but will suggest some more offroad ways to avoid traffic.

What does it do differently from most other profiles out there?

It was developed with "dense" OSM cities in mind, and should cover all oneway and cycleway tag situations found in OSM.
It evaluates all ways with the same logic - no heuristic assumptions are made based on waytype.
It has a method to find the waycost taking all types of road quality indicators into consideration (smoothness, surface, tracktype, mtb:scale, sac-scale).
It is generally carefuly - it avoids uncertain situations like reversible traffic, barriers or not explicitly whitelisted highway types.
All this means it takes a bit longer to calculate routes than most other profiles, but hopefully it should cover mostly everything found in OSM.

Related things

If you are looking for highly configurable profiles for a variety of other purposes give a try to
https://github.com/poutnikl/Brouter-profiles

utack_brouter_profile's People

Contributors

Stargazers

Watchers

Forkers

polyscias

utack_brouter_profile's Issues

could not calculate route. length=1 index=1

I'm using osmand with brouter.

Recently, I'm getting an error message about not being able to calculate a route.

Sometimes after restarting the apps, I can get it to work. but sometimes not. Is anyone also facing this?

add penatly for steeper slopes

steeper slopes are annoying to not manageable, they should get more penatly on top of normal elevation cost
Discussion about that
https://groups.google.com/forum/#!topic/osm-android-bikerouting/yIu72_FimNI

add "iswet" switch

Add a switch to "iswet" similar to other profiles, that can be used to put more focus on paved ways

Add all switches

All the new switches for easy 1-click config without profile rewrite need to be added

assume surface quality for all highway=* that are part of a bicycle route as better

currently surface quality for highway=path etc does not consider if it is element of an offical bike route

add "low traffic" property

use access rules to calculate what is a "low traffic" route and factor it into the traffic penalty

unable to find a route over causeway linking Singapore and Malaysia

I tried to route from Esso Woodlands Road (singapore) to KSL City Mall but received an error message
"Error: cannot find a route for given points. Maybe try to move them closer to roads?" (if allow_ferries is set to false)

However, profiles like Trekking, Fastbike, Fastbike-verylowtraffic have no problem.

Any idea what is causing this?

fix access when highway is construction

when highway is construction the access should not be used to route over it

when surface/smoothness are unknown, consider if the way is part of a bike route

currently surface=unknown leads to a high penalty
this should not be the case for ways that are part of a bike route

when detecting gravel/fine_gravel add bicycle=dedicated to the whitelist

in line
https://github.com/utack/utack_brouter_data/blob/master/streetbike_touring.brf#L452
where gravel tagging bugs that highly likely mean fine_gravel are detected, bicycle=dedicated should be added.

on ways with surface=unpaved, the tracktype should overrule it

Currently on tracks with no further information than "unpaved", the worst case selection can ignore additional information like tracktype=grade2

Add switch to not use offroad

Is it possible to add a switch to use only paved roads and cycleways?

Sometimes on a tour you are really tired or you are not confident of riding offroad. It would be nice to have a switch to force the route not to be offroad under these times.

Best Regards

fine_gravel bug

fine_gravel and gravel assumed to be gets two differnt smoothness penalties, but is really the same thing

Re-evaluate high tracktypes

Some tracktypes with higher numbers can be really bad
Same for some other unsurfaced ways
Some improvement should happen to give these higher penalties, but with good testing to still use them where it is needed

handle access=unknown situations

currently unknown values for the access like keys are ignored
they should be treated as "no" to be save

Add switch to ignore_cycleway

Hi
I'm trying to add a switch to ignore_cycleway

This is because in Singapore most of our cycleways are non segregated and shared. Their speed limit is 25kmh but at certain times of the day, they are very crowded making it extremely unpleasant to ride. My guess is that cycleways in big cities will face similar issues. With the switch, the tourer can choose to avoid cycleways until outside of town and then switch back to 'normal' routing.

I tried to implement this by adding the following code segment

if ignore_cycleway -> assign hascycleway = false

if ( ignore_cycleway ) then false 
# cycleway in both directions
else if and ( not cycleway= ) ( not cycleway=left|right|no|none|opposite|proposed|unknown ) then true

to replace line 174 of your original code

But it does not seem to work. Any idea why?

(I am testing on cheng san community club to Tuas lamp post 1. The route continues to use the PCN along Ang Mo Kio Ave 6 between Ang Mo Kio Ave 1 & Ang Mo Kio Ave 3 even though I set lefthandtraffic=true. By the way, was the profile supposed to ignore this cycleroute since it is on the opposite side of the road?)

consider ferries

for longer tours in unknown environment ferries might be needed as fallback solution

tracktype and surface/smoothness not properly evaluated

tracktype and surface/smoothness are not evaluated correctly at the moment.
tracktype=grade1 and surface=asphalt are an example where tracktype should not make smoothness of surface worse
Idea to solve:
Allow "brackets" of smoothness cost that go with a tracktype, and only downgrade when tracktype is significantly worse than surface or smoothness

tune traffic and maxspeed penalty

large roads are currently favoured too much, more traffic and maxspeed penalty is needed

better barrier evaluation

assume default values for barrier=* with missing access tags

for example
barrier=bollard should always mean yes for bikes
barrier=wall without more infroamtion always means no for bikes
and so on

Navigation hints

Dear Jakob, will your streetbike_touring profile feature the output of navigation hints in the future? Best, Lucas

use inofficial cycleroutes

unofficial cycleroutes should also be used to guess smoothness on ways with unknown properties and probably give a smaller bonus than an official cycleway in the "cycleroute_cost"