Menu

Show posts

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 Menu

Messages - poutnikl

#376
Very most Finnish people are said to speak English very well.
#377
Umí to třeba tema UniGCCZ, delane  pro mapy http://osm.paws.cz/.
Nevím, jak to vypadá na LoMaps.
#378
Quote from: john_percy on November 04, 2016, 09:58:44Surely Brouter route finding does not depend on downloading up to date vector maps.

Surely it does not. But the user may get confused by inconsistency of the rendered and routing data, in case of deviations. Such a risk obviously depends on local frequency of OSM updates and the data timestamp difference. I do not say a user should update both at every update. But at the same time a user should critically evaluate acceptable time difference.

The same is valid for online routing as well, except one does not update routing data.

Personally, I use Windows batch downloads and PC<>Android wifi sync  for both MapsForge compatible maps and BRouter data. So frequent selective updates of home area is not a big deal.

Offline ( native ) routing in e.g. OSMAnd does not have such a problem, as rendering and routing uses the same data.
#379
Quote from: locuscycling on November 03, 2016, 10:23:49
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.
Well, the changes in vector maps are much more significant than in raster maps.
In urban areas because of  human activity,
In rural areas because of OSM mapping progress.
Additionally, BRouter, its profiles, lookups.dat and segment files evolves...
#380
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 ))

A general advice is to update simultaneously the vector map and related RD5 files. The RD5 files are much smaller than vector maps of the same area.

Particular files are independent, you may update frequently used maps and RD5's often, while the other occasionally.
#381
See the Arndt's notes in Deutsch > http://forum.locusmap.eu/index.php?topic=4064.msg45570#msg45570

What I have translated by Google is:

QuoteQuote from: balloni55 on Today at 15:23:23

QuoteI ask for a clear explanation added turn cost as start-direction bias (locus only) is best with an example 8)


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.
#382
Maps / Re: opentopomap
October 17, 2016, 11:51:50
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!

I think development for 2 or even more platforms would multiply the needed development effort, what is probably undesired. Menion is AFAIK the only app developer of the Locus team. The other team members focus on other things.
#383
Quote from: Ulrich Kiermayr on October 15, 2016, 20:29:07
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).
Sure, I am well aware of that.  But it is possible only if elevation profile is available.

As I have mentioned before on one of Locus forums,ideal would be if BRouter ( or Locus during the import ) would calculate the route nominal time profile estimation based on elevation profile. Then ratio of nominal and real speed for a particular route section would be used for the correcttion of  the nominal remaining time.

E.g. if you passed some distance in 9 minutes instead of nominal 10 minutes, based on nominal time profile,
than if nominal remaining time was 60 minutes, the corrected prediction would be 54 minutes.
#384
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!

Hi Andrew,
you can get the current profile versions from https://github.com/poutnikl/Brouter-profiles/wiki, as they are subjects of occasional change.
#385
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.

IMHO, Locus should avoid creation of its own "to" waypoint, as BRouter implies usage of "to" waypoint for its mode of the automatic route setting by points "from", "viaN", "to" .
#386
Such a hint is not about the turns and angles. It is about the forks, if the one *relatively* more to left or more to right is to be taken.

I do not see "keep right(way) / left(way)" in this scenario confusing..   If I would hear (slight) left because a left turn just before the fork, I would be confused. Should I go left left or right left ?

I remind myself some Indiana Jones scene about carriages on the cave railway. For them was keep right / left quite essential. Sometimes for downhill MTB as well, as the choice cannot often be undone.
#387
@Balloni55: The scenario is same for motorways or paths. The path may be turning left when you are to take the right fork. The only reasonable hint is to keep right.
#388
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.
#389
Přehlednější by bylo hodnoty parametru opsat.. :-).

Navigování nazáleží na mapě, alespoň ne u Locusu. Mapa slouží pouze jako vizuální vrstva, na kterou se promítají navigační detaily jako navigační body a, trasa.

Quote"NAVIGACIA ZASA NAVIGOVALA ZMATOCNE"
Nekonkrétní. JAK PRESNĚ zmatečně   ?

Navigace nebo navádění ? A je taky podstatné zmínit, jak je vytvořena trasa, eventualne ji prilozit jako GPX export.

Proč máš v oznámení mimo trasu nastaveno na 5 m , resp. 10 m ? To je příliš málo, mělo by to být více než je nepřesnost GPS polohy. Já to nedávám méně než 50 m.

Vzdálenost pro přepočet 30 m je příliš málo, srovnatelné s chybou GPS pozice při špatném GPS příjmu. To se Ti pak může stát, že navigační služba bude přepočítávat pořád, protože ( skoro ) pořád bude mimo trasu. Je lépe mít nastvený údaj o sjetí z trasy třeba na 60-100 m a přepočítání třeba 100-200 m.

Další renonc - mas prepnuti z navigace na navadeni na 30. V ramci chyby GPS si navigace pri spatnem prijmu ani neskrtne.

U navigace si ujasni vztah 3 hodnot nize,
Kdyz ma upozornit, pokud
Kdy ma prepocitavat
Kdy ma prepnout na navadeni.

a jeiich vhodne hodnoty v souvislosti s chybou GPS ktera muze byt az do 50m.

Sumárně bych řekl, že jsi Locus nastavil, aby se choval zmatečně.
#390
Quote from: jusc on September 26, 2016, 15:48:39
Thank you for your efforts.  ;D
But 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. 

It is always good to review the total cost.

Absolute forbidding by costfactor 10000 affects the voice-hint generator and is by standard Trekking limited to "hard cases".
For "soft cases" it is using the highest regular value 9999. I.e. the above 3m of footway have 30 km  of equivalent length.

I am going to follow it.