It is easy..
Each <select value structure in <way attribute="access">
<select value="accessvalue" t="tag" v="tag value"/>
is to be evaluated as
...
else if tag=tagvalue then access=accessvalue
.....
the conditional
<if param="avoid_unpaved">
<select value=.....
.....
</if>
is then to be interpreted as nested if.
First comes, first served. The priority is the order based.
If you do not agree with priorities, raise the feature request if
general improvement,
you modifify your personal routing.xml copy, if it is rather your
personal preference.
Dne 17.7.2017 v 12:13 Peter B napsal(a):
Hi,
I studied that file, but the more time I spend reading it, the less I
understand how it works...
Have a look on
<routingProfile name="car" ...
then on
<way attribute="access">
How is value in access set ?
First I thought, if value is set by a line, then value can't be
changed by subsequent lines.
Example:
allow_private = true
motorcar = private
Until now value is 1
then, later
barrier = bollard
would never be considered, but it should be!
Can anybody explain that ?
regards Peter
--
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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
Poutnik ( The Pilgrim, Der Wanderer )
https://github.com/poutnikl/Brouter-profiles/wiki
--
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].
For more options, visit https://groups.google.com/d/optout.
