Brouter app seems to ignore Ferries allowed

[Rob G]

in the Brouter (android) app  I selected the trekking profile. In the profiel definition I selected Ferries allowed (box ticked)  but in OSMAND using a profile that uses Brouter completely ignores ferry crossings and routes around it.

Can anyone help?  would appreciated 

[A. Fischer]

I'm not an expert for OsmAnd.

But I did  short test with this route 

In OsmAnd I get something similar

Therefore, please check each parameter carefully

[Rob G]

Hi, thanks for your input. 

I did some tests using the trekking profile with the alternative routes 1,2,3 all with ferry allowed

the result are:

original plans around the ferry

alternative number:

1. around the ferry

2 uses the ferry to get across

3 uses the ferry

But when the closest waypoints on either side of the water are further apart, the results are different and original and 1,2 and 3 route over the bridge on the east side.

Consequently if one wants to force Brouter to use the ferry not only ferry allowed is a requirement but also 2 waypoints on either side close to the water .

Thinking about it, it makes sense  but it is something to remember when planning a route.

I think I am getting the hang of it......

[0709]

A problem I have often seen with ferries is that the access roads or landing stages are not always adequately accessible in the OSM edits.

One that I remember was a ferry in Dresden that was virtually inaccessible. WAS!   (Altstadt to Neustadt).

- Routing profiles walk or cycling differences.

For pedestrians, the slow ferry is mostly not  a problem.

But for cycling, a detour via nearby bridges can be faster

Op woensdag 20 augustus 2025 om 13:35:25 UTC+2 schreef robca...@gmail.com: