Very most Finnish people are said to speak English very well.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: john_percy on November 04, 2016, 09:58:44Surely Brouter route finding does not depend on downloading up to date vector maps.
Quote from: locuscycling on November 03, 2016, 10:23:49Well, the changes in vector maps are much more significant than in raster maps.
Since ca 1 year till last ''crash'' i didn't update RD5 files and Vector map as well.
Changes are microscopic so i don't see any reason to update.
Generally on my bike i use only rasters.
Quote from: locuscycling on October 30, 2016, 09:04:29
I downloaded ,,new'' E10 N50 file and it works . thx for an Idea.
(But it also means that i have to download and replace all my RD5 files ( ca 4gb in more then 50 files ))
QuoteQuote from: balloni55 on Today at 15:23:23QuoteI ask for a clear explanation added turn cost as start-direction bias (locus only) is best with an example
Menion has built into the call interface two new parameters, which should be used to ensure that a dynamic re-calculation is more "forward" and is not already outdated at the moment it is displayed:
direction
- noManveuverTime
Only this is not feasible at the time because it would require some of the structural changes that are necessary for turning restrictions.
But what I can do easily, I've done: I use the current start direction, and calculate the angle costs relative to this starting direction precisely, like any other angle, for the first step.
As a result, the point from which the forward solution wins is increased by "turncost / costfactor" meters so that in more cases, the forward solution is obtained at the first recalculation.
But as I said, just a light bias, no navi with artificial intelligence, which can guess what you're up to.
Quote from: Linad23 on October 17, 2016, 09:11:50...... why you don't want to do really good app for pc? I need to use android emulators http://android-emulator.net/en/ now, to have access to your app!
Quote from: Ulrich Kiermayr on October 15, 2016, 20:29:07Sure, I am well aware of that. But it is possible only if elevation profile is available.
A remark on that: during our vacation (cycling) the ETA often was not really usable. Reason: the topography of the route has a huge influence on the speed you are able to ride. Consider a tour where you go uphill the first half and downhill on the second. Just considering the current average speed, would result in unusable results,because it would estimate going up the whole tour. But this is wrong, since the second half will be faster because it is downhill.
I think the ETA algorithm (for cycling and probably also for hiking) should work somewhat like the algorithm to estimate the time for a track. The current avg speed could\should be used to set the parameters for that estimate (like piking the best profile in the trip time estimate).
Quote from: Andrew Heard on October 14, 2016, 23:41:25
@menion - that's great - I can extract a BRF file from your Locus ZIP, copy to the BRouter profiles2 folder, and now Locus advanced navigation settings will parse the special "hard coded" parameters and display equivalent checkboxes - very nice!
Quote from: TrulloF on October 13, 2016, 20:52:59
There are problems with the new version when brouter navigation needs to recalculate the route and there's already a point "to" used as target. The program tries to create another "to" point and gets confused. Result is that recalculation doesn't work at all (throws some java error or something, I can't remember). To recreate this behavior just use a point with the name "to" as target and force the program to recalculate by using a wrong turn.
Quote from: menion on October 06, 2016, 12:22:41@balloni55: if I remember correctly (@poutnikl corrects me), default BRouter profile do not generated navigation commands for a foot profile. Please try it with cycle/car profile if it works correctly. It was also one more reason, why I was in hurry with creating custom settings for BRouter directly in Locus > because many users wrote us that for cycle it works correctly, but for "foot", Locus do not navigate.Correct, the Brouter default foot profile is Shortest, that is for some reasons about a year old, not updated and not aware of the Brouter navigation instructions. The Hiking/Walking should work fine.
Quote"NAVIGACIA ZASA NAVIGOVALA ZMATOCNE"Nekonkrétní. JAK PRESNĚ zmatečně ?
Quote from: jusc on September 26, 2016, 15:48:39But be aware that it can exclude all the otherwise nice way from consideration if a little segment is forbidden or incorrectly tagged, like some small way segments, barriers or small foot bridges, E.g. searching the bike pass across Donau near Moldau leads to 5 km detour if 3m footway is forbidden.
Thank you for your efforts.