I have now found the setting which tells OSMAnd to use the other routing engine (in App Profiles, select any profile -> OsmAnd development ->Safe Mode). With this set, it will navigate correctly, obeying max heights, weights etc. However, if the journey is more than an hour or so, you will be able to drive their quicker than it can work out a route!
On Monday, 10 August 2020 at 19:42:06 UTC+1 [email protected] wrote: > Hi, > > I've tried a few bridges, but used these two for testing: > 54.06711, -2.81458 > <https://www.openstreetmap.org/#map=19/54.06711/-2.81458> > 53.76551, -2.62154 > <https://www.openstreetmap.org/#map=18/53.76551/-2.62154> (small road > under the A59) > > They both have heights shown on the max height map... > On Monday, 3 August 2020 at 12:26:31 UTC+1 [email protected] wrote: > >> Hello! Thank you for the feedback. >> Could you please provide coordinates of the bridge so we can test it. >> >> On Friday, July 31, 2020 at 11:57:26 PM UTC+3 [email protected] >> wrote: >> >>> Hi, >>> >>> Max heights seem to be ignored in OSMAnd again. I used to be able to >>> get round the problem by using the Java engine (slow!), but I can't work >>> out how to switch routing engines in this version (3.7.4). >>> >>> Should max heights (and weights etc) not be respected by the default >>> search engine? >>> >>> The attached screenshot should be routed around because the railway >>> bridge is to low for the vehicle I have set. This routing used to work >>> with Java on older versions... >>> >>> Any ideas? >>> >> -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/0b4fc0be-4821-4e65-9fc5-32b80830b498n%40googlegroups.com.
