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.

Messages - poutnikl

Pages: [1] 2 3 ... 27
Ways other than roads? Not sure I follow you?

I mean by a "way" any OSM way intended for vehicle/horse/pedestrian travelling.
I,.e. tagged by highway=*

By a road I mean such a way, that is - more or less unrestricted - intended primarily or exclusively for cars for regular traffic.  Typically unclassified to motorways, mostly also the service and residential as well. 

In such a sense, tracks, paths, cycleways are not roads.

Does it apply to all ways or just roads ? As if I remember correctly, Elevate/Elemements theme does distinguish between unsealed and unknown tracks. ( I do not have a map handy to check ). Not sure about roads.

Podle hlášky to vypada spíš na problém s předávaním BRouter profilu z Locusu.

[CZ&SK] - diskuze o Locusu / Re: "Posunutá" orientace mapy
« on: December 11, 2017, 09:07:41 »
Pokud používáš zaklapávací pouzdro, např pro nošení v kapse, často používají magnetické příchytky, což samozřejmě může kompas ošálit. Ale to by Ti nejspíš došlo - píšu to,  že člověku tu a tam nedojde očividné....

[CZ&SK] - diskuze o Locusu / Re: "Posunutá" orientace mapy
« on: December 11, 2017, 09:04:24 »
Vyzkoušej nějakou jinou aplikaci, používající kompas. Je možné, že detektory magnetického pole jdou šejdrem.  Kalibraci často doporučují dělat 1-2x otočit okolo každé ze 3 navzájem kolmých os telefonu - např toto tvrdí GPS status kalibrace.

Pokud se to nepovede. tak nastavit Locus natvrdo používat GPS orientaci podle směru pohybu. Ale pro chůzi to nabude žádná výhra.

Themes - Vector maps / Re: [Theme] UniGCcz (for map from
« on: November 30, 2017, 11:23:20 »
Hi Poutnikl u  ;)


The effort is to plot everything in the source file on the map.  You can visit This is the bible for me. I do not worship on any side. Appearance is just my personal preference.

Hehe, it was not about taking the sides. It was about avoiding themes, the I may visually like, but with not so obvious disadvantage for PAWS maps.  Particular themes usually mention if they are aiming for LoMaps a/o OAM, but it is unclear about PAWS.  I am not sure if I can find the answer in the tag-mapping.xml file.

I mostly use your UniGZcz, but I like experimenting. I see I will have to  make some comparative screenshots...

Themes - Vector maps / Re: [Theme] UniGCcz (for map from
« on: November 30, 2017, 08:34:44 »
Are PAWS maps closer to LoMaps or to OpenAndroMaps ?

Respectively, aside of UniGZcz theme, is better to prefer themes optimized to one or the other ?
I ask as recently there was reported for the Tiramisu theme some feature displaying issue if the map and the theme do not match.  ( LoMaps and Tiramisu aimed on OAM )

Troubles & Questions / Re: Time at Arrival
« on: November 21, 2017, 07:16:34 »
[...] Currently it's used exponential filter that use latest +- 1 hour of average speed for every activity separately. [...]

I see. I may have confused it with the old time span for the navigation hints. They use rather seconds than minutes now, after our discussion,AFAIK. 

The solutions that perform all of a/route calculation, b/route following and c/ETA estimation have an advantage. As they can calculate a nominal route speed profile and provide very good ETA estimation based on nominal and real-time profile comparison.

Troubles & Questions / Re: Time at Arrival
« on: November 19, 2017, 14:15:30 »
Hmm. the ETA ( Estimated Time at/of Arrival ) topic was discussed in last about 2 years quite a lot, either here or on the Helpdesk.  You may guess the proper ETA calculation is very tricky.

As the first step you could provide the procedure to reproduce the above results.

As you may know, LocusMap does not have its own routing feature.  It relies on the online or offline 3rd party routing services. The ETA can be either calculated by the routing service and returned to the LocusMap ( not sure if this happens as I am not a developer ), either LocusMap has to calculate it somehow.  But LocusMap has no idea about the quality and speed of particular route segments.

One option is to use hard coded nominal values, as some navigation software use.  E.g. 4 km/h for pedestrians, 15 km/h for bicycles, 60 km/h for cars. In average, they are neither very bad,  neither very good. There are many cases with significant bias to both sides.

Another option is to calculate ETA from the real time motion and motion history. This gives usually better results than nominal values, but can provide extremely wrong values in some cases. And here come the tricky part.......

If one gives too high weight to immediate speed, or uses too short history record, the ETA fluctuates, depending on short time variability of the speed history.
If one gives too low weight to immediate speed, or uses too long history record, the ETA gets too big bias, depending on long term variability of the speed history.

As far as I know, LocusMap currently uses ETA calculation based on the mean speed in last 3 or 5 minutes, based on the sliding exponential averaging. This is valid for real time navigation. If it generates a GPX navigation track, it puts there, AFAIK, some formal and funny time stamps.

jak tak koukám,je to založeno na starém profilu. Nějak jsi zkombinoval pěší profil s cykloprofilem. Chybí tam definice proměnné onewaypenalty pro vyhodnocení jednosměrek..

Co jsem to tak porovnával se současnou Hiking templatou , tak se mi jako jediný podstatný rozdíl zdá Tvoje nastaveni Offroad factor na 1.0.  Takže by sis to tam mohl znova nastavit a měl bys to.

Další možnost je ve starém profilu vyhodit
Code: [Select]
assign isbadoneway = not equal onewaypenalty 0
assign isgoodoneway = if reversedirection=yes then oneway=-1
                      else if oneway= then junction=roundabout else oneway=yes|true|1

a nahradit
Code: [Select]
assign isbadoneway = 0
assign isgoodoneway = 0

Ale druhý způsob moc nedoporučuji.

Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: October 03, 2017, 11:53:15 »
Generally for me a NOGO is only needed for the life of the route. No longer. As my cycle touring is always to a new area.

I see. But imagine everyday bicycle commuting in big cities with regular municipal announcements about short and long term road closures. There is even Android application to monitor them for my country. They are often not updated in OSM, or with delays, or routers generally do not deal well with time restrictions.

I have a nogo folder in Locus and put their nogos there with target date in name, periodically purging them.

Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: October 03, 2017, 11:38:01 »
They should not be used as "negative viapoints/shapepoints".
I sometimes find nogo's very convenient for negative viapoints/shapepoints. Sometimes it is the fastest method for shaping my route.
I mean - description of what I want is easier by expressing what I want, not by what I do not want. If I would try to order my dinner by nogo approach.....

The admitted advantage of nogos for route shaping is that it bypasses eventual viapoint count restrictions. Personally I prefer to use the profile that follows my priorities and eventually I choose viapoints that I do want visit or go through.

It not at all about users should act this way, I am just describing my way. That is all.

Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: October 02, 2017, 21:16:46 »
IMHO when I use the clear route button if I have a pop up to choose to: clear all nogo/profile nogo/current visible nogo points or something similar should be helpful.
I used the nogo points to avoid some sections of a track for a hike but next time  I do not want the nogo still there and to give them all an expieration of a week is tedious.

I do not agree with Arndt - the BRouter author - on nogo usage philosophy. IMHO, nogo points should serve as really nogo points, permanent(e.g. really bad road or always traffic jams or whatever) or temporary ( e.g. road fixing).  They should not be used as "negative viapoints/shapepoints".

Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: October 02, 2017, 19:34:11 »
Perceptions of using NOGO points.
1) The "ignore NOGO" option should be added to the route planning menu. This option would also be saved with the route. The point is that NOGO will be used mainly where you can not go by car or bike. However, if I plan a hiking trail, I can go through the NOGO areas through the pavement.

Note that the original BRouter nogo system can activate nogos separately for each profile, resp. transportation mode. E.g. all nogos for cars, some for bikes, none for pedestrians.
And yes, they are considered globally, so not limited to a particular route.

Na OSM je to už opravené. Takže nezbývá než počkat na aktualizaci LoMaps.

Anebo si stáhnout mapu z, kde je updatují  cca každé 3-4 dny.

Pages: [1] 2 3 ... 27