It does not make sense to use a single value.
It should be evaluated per way segment basis within the profile script file.
If fact, the more values the better.
--
Dne 5. prosince 2018 16:38:25 "'Osmandtrier' via Osmand"
napsal:
I used Priorityclassifier with the value 10 and made
I used Priorityclassifier with the value 10 and made still this experience.
Am Montag, 3. Dezember 2018 13:18:22 UTC+1 schrieb Poutnik:
>
> Brouter does not announce every direction change
> by design, it tries to omit trivial ones.
>
> This can be modified in the profile.
> A quote from my
Brouter does not announce every direction change
by design, it tries to omit trivial ones.
This can be modified in the profile.
A quote from my unofficial Glossary GitHub page:
"Priorityclassifier is a BRouter numerical parameter calculated for ways
and used for generation of pictogram/voice
> The exception is, if the GPX is generated with navigation hints by BRouter
> navigation.
> GPX will tell OSMand, where and what to tell.
>
> Osmand talks to much, but it talks normaly, if you have to change the
> direction.
>
Brouter hints produce a very silent phone. But it is in my
You could also calculate the route natively within OsmAnd and save that to
a GPX.
This how-to video is aimed at routing via hiking trails, but the principle
for roads is the same: https://youtu.be/o84C0z3Kydc
On Thursday, November 8, 2018 at 10:27:50 AM UTC-8, Poutnik wrote:
>
> In
In contrary of natively calculated routes,
OSMAnd ( other apps usually too) takes GPX route as a simple point sequence.
The is no difference to an off-road outdoor GPX route, just this time
points happen to sit on roads.
OSMAnd in gpx-route-following mode ignores road network data from the
I use the application to navigate fun curvy roads on my motorcycle from
preplanned .gpx routes and it works great. The one annoying feature though
that I hope someone can help me with is for every sharp corner it tells me
turn right or left in so many feet when there is no turn it is just a
