quaelnix

> So it means that if uphillcutoff=5 than slope more than ~5 will be exclude to the compute? `uphillcutoff=5` means that BRouter treats roads that are less steep than 5...

If you want to maximize the slope, you need to trick the system as follows: ``` ---context:global # Disable the elevation penalty assign downhillcost = 0 assign downhillcutoff = 0...

You can use this instance of BRouter-Web for testing, it is using v1.7.0: http://148.251.191.149/brouter-web/#map=12/39.9134/8.6160/standard

My profile increases the cost of one-way streets by a factor of 5: ``` assign onewaypenalty switch or ( not badoneway ) ( or cycleway=... ) 1 switch not junction=roundabout...

> your profile is misbehaving, look here for example: No, it does what it is supposed to do. It concludes that [~ 90 meters of pushing](https://brouter.m11n.de/#map=19/39.90187/8.60124/standard&lonlats=8.601378,39.902198;8.600301,39.902432&profile=quaelnix-gravel) is better than [~...

> I have an old instance (1.6.1) of brouter running on my homeserver and this also calculates the "wrong" route. It's possible that the bug that causes the calculation of...

@LupinSun, I thought about it some more and the trick I mentioned above works even better if you set both `downhillcutoff` and `upillcutoff` to a small number > 0. The...

> Can you eventual (x2) discriminate returning (overlap) road sections after a shaping(via) point ? No, but you could increase the turncost penalty: ``` assign turncost = if is_ldcr then...

@LupinSun, I don't know enough about enduro motorcycling to make any suggestions without being shown specific examples of where the profile is currently not making a good choice. If you...

@EssBee59, I just implemented your idea and the results are very promising even without taking the priorityclassifiers, roundabouts or oneways into account. We should definitely follow through with your proposal!...