nodeaccessgranted

17 views
Skip to first unread message

Poutnik

unread,
Sep 30, 2014, 2:21:23 AM9/30/14
to osm-android...@googlegroups.com
I may do not understand it well.....

Variable nodeaccessgranted is defined in trekking profile in way context, but used in node context.
In my understanding it should be defined either in global or node context, if it follows similar principles of variable declarations in programming languages.

Poutnik

unread,
Sep 30, 2014, 2:27:43 AM9/30/14
to osm-android...@googlegroups.com
OTOH, it does not trigger error msg, so I am rather confused.
Is it like it does not matter where the variable is defined ?
Just in case if definition is present in current context, it takes preference ?

Poutnik

unread,
Sep 30, 2014, 3:32:36 AM9/30/14
to osm-android...@googlegroups.com
Perhaps context thing applies only to defining system variables....

abre...@googlemail.com

unread,
Sep 30, 2014, 5:00:27 AM9/30/14
to osm-android...@googlegroups.com
This is a hardcoded hack.

There are (meanwhile..) 6 variables that are "exported" from the way-context:

  costfactor, turncost, uphillcostfactor, downhillcostfactor, initialcost, nodeaccessgranted

"nodeaccessgranted" is then turned explictly into a lookup-variable and propagated from the way to the teminating node.

This is needed to enable routing over bicycle-routes with access=no/private nodes.

However, there's not (yet) a general concept to propagate data from the way to the node context.

Reply all
Reply to author
Forward
0 new messages