Some time ago, there have been implemented syntax
assign parameter = 0/1 # %parameter%
for chosen set of parameters of my embedded car/bike/hiking profiles.
is_wet
avoid_toll
avoid_motorways
avoid_unpaved
It works well even for external BRouter profiles.
The problem is, Locus does not detect the parameter, if it's value is defined
assign parameter = false
instead of
assign parameter = 0
Would it be possible to extent Locus profile parsing analysis to Brouter values true/false, that were implemented later?
Current implementations of the new car profiles by Arndt, based on very good kinematic model, prefers true/false for logical values, even if Boolean type is not implemented yet.
BTW, I recommend these car profiles, instead of mine.
See also https://github.com/abrensch/brouter/issues/197
Sent from my Xiaomi MI A2 / Android 9, via Tapatalk
Hello Libor,
done (will be already in next 3.40 version).
Menion
Using the latest car profiles from GitHub and the latest version of Locus I get an error(https://uploads.tapatalk-cdn.com/20191002/2d1f74627c5fd21f986b31b8ed509768.jpg)
The built in profiles are fine.
I don't know if this is a Locus error or a Brouter one.
@john_percy Try also lookups.dat file from the GitHub, the same folder as profiles. As I remember I had had the same error, until I updated the file some time ago.
Sent from my Xiaomi MI A2 / Android 9, via Tapatalk
@poutnikl Thanks, that does the job!
Sent from my moto g(6) plus using Tapatalk
I confirm the Locus update for selected BRouter parameters in the release works, i.e.
assign parameter = false # %parameter%
works as well as with " = 0 "
Sent from my Xiaomi MI A2 / Android 9, via Tapatalk