Started by Menion, June 27, 2016, 20:21:08
0 Members and 2 Guests are viewing this topic.
Quote from: abrensch on August 13, 2016, 16:49:54......Every request with a remote profile saves that profile on the brouter-side as brouter/profiles2/remote.brfSo after a timeout, you can repeat that long-distance calculation using the brouter-app, using the exact same destination point and a close-by starting point. That will automatically store the "reference-track" as brouter/modes/remote_rawtrack.dat, and with the help of that file the next try from Locus is guaranteed not to time out. Same for automatic recalulations (using endpoint priority). Recalculations should always be faster than the initial ones.......
Quote from: menion on August 17, 2016, 17:53:31...... I had to test BRouter & Locus on moto and it worked pretty well. I was used mainly "FastEco" mode and have to say, that few times track was longer then expected (usually a lot shorter track was over city which was probably considered as "not so eco"). .........
assign fastprofile 0 # default 0=economic, i.e. balanced cost and time, 1=prefers shorter time # implemented for Locus config switch system # fastprofile=0 is equivalent drivestyle=2(FastEco), fastprofile=1 is equivalent drivestyle=3(Fast)assign avoid_motorways 0 # default 0, 1=like if on moped or on "sightseeing tour", includes motorroad=yesassign avoid_toll 0 # default 0 / 1=avoid paid ways and toll points like booths or bridgesassign avoid_unpaved 0 # default 0 / 1=avoid unpaved roads, equivalent to road_restriction=2, implemented for Locus confing switches
Quote from: menion on August 17, 2016, 17:53:31Anyway in the end, I agree with opinion of @abrensch about duplicating of Locus routing profiles & brf selection. So I've removed it for now and Locus will have hardcoded custom profiles. So for car-fast will be used Libor's "Car-FastEco.brf" profile etc. without possibility to change it. You will be anyway still able to disable Locus custom-mapping and use old used system with mapping directly over BRouter. Reason for this is, that creating system with such huge customization of routing profiles needs more then one afternoon, so it's not possible to implement it now. I've decided to allow less features for now. Thanks for understanding.
Quoteand it is not visible in new "Items" screen?
QuoteSeems that "eye" icon needs three states ... nothing visible, something visible, all is visible.
QuoteAnyway I had made it that icon display action that happen. So item is not on a map > eye icon say "show it". Isn't it more logical?