Recent Posts

Pages: [1] 2 3 ... 10
Themes - Vector maps / Re: [Theme] VanLifeMapV4
« Last post by Martin Holý on Today at 17:34:38 »
@Magellan yes you are right, the casing is wrong, thank you for mentioning it.
[DE] - deutschsprachiger Forumsbereich / Trackdatum ändern
« Last post by Wole on Today at 17:28:51 »
Ich habe heute einen Track aufgezeichnet. Aus mir unerklärlichen Gründen ist das Datum der 18.01.,
Obwohl die Systemzeit richtig ist.

Lässt sich die Zeit manuell ändern?
Themes - Vector maps / Re: [Theme] VanLifeMapV4
« Last post by Magellan on Today at 15:42:07 »
Martin, I tested your theme a bit and find it very nice and balanced. Thanks for your hard work!
Found this:
Pay attention to intersections and crossroads.
It's located here:
It seems to me that the sequence of specifying different types of roads is wrong here. (casings / cores for residential, tertiary, service, etc.)
Or is it intended?
Locus Map (4+) / Re: Locus Map 4, discussion (beta)
« Last post by balloni55 on Today at 13:48:14 »
- "must be no log option" in parent cache panel > why this?
if, then in the last waypoint or?
but as said a button to create waypoints/projection would be helpful
Versions / Re: [APP] - version 3.50.+ ( 7. 1. 2021 )
« Last post by balloni55 on Today at 13:42:57 »
problém with thumbnails in caches have to be a different problem. Give me please a cache code where I may test this, thanks
the problem is gone :D
Versions / Re: [APP] - version 3.50.+ ( 7. 1. 2021 )
« Last post by Menion on Today at 13:39:14 »
Understand. I'm trying it and online & vector maps, both works correctly for me.
Locus Map (4+) / Re: Routing over online/internal BRouter
« Last post by poutnikl on Today at 13:38:20 »
All the above implies the routing is able to assess the route about correctly, based on available OSM data. E.g. and just illustratively, it takes 3 min/km for one part on an easy road and 20 min/km for other part on a steep woody trail.

I repeat my comment about the extremalities. You do not really expect the planner would consider the muddiness, unless there is tag surface=mud. If you do not evaluate in advance yourself the ETA in extreme conditions would not match, is it yours fault when they do not match and you are surprised.

You would also use different profile configuration for short sportive rides and long trips or expeditions.
Thinking is required. ETA calculation is not magic, it is simple calculation, that can be easily fooled. If one does not count with it, it is his fault.
Locus Map (4+) / Re: Routing over online/internal BRouter
« Last post by lor74cas on Today at 12:36:27 »

It makes still sense to provide ETA, if you provide also information, what you can and should expect and the range of applicability. Applying it in extreme circumstances and expecting standard behaviour would be rather an extreme than standard state of mind.
I agree.

I remember it was also discussed, not sure if implemented, that the "nominal" ETA, calculated at route planning, would be in real time updated by comparison of partial values of nominal versus real time for the passed part of the route. (whole or last x km/minutes ).
Yes, locus adapts the ETA based on the pace held in the previous period and the path still to be covered. But of course this is not the context of the planner.

E.g. a route has estimated ETA in 100 minutes. After passing the first half ( by expected spent time ), i.e. with the nominal  ETA 50 minutes, you realize you have spent 55 minutes, i.e. 5 minutes more. So for the rest nominal 50 minutes, you should expect rather 50*55/50=55 minutes  as well. Or, it could be evaluated for the last nominal 10 minutes, instead of the whole 50 minutes. So 50*11/10=55 min.
Not necessarily, you have to consider the type of path you have already taken and what remains to be done. If in the first 55 minutes you did the flat part, on easy terrain and then you still have 1000 meters of altitude difference left on a bumpy path? Not everyone is able to make this type of assessment, it takes experience and knowledge of their skills that are lacking in those who rely more on technological tools.
Furthermore, I have not seen the fatigue in the formulas that calculate the ETA. If on journeys within 3 hours it may not even be taken into consideration, beyond a certain threshold is instead decisive. If we take an example similar to yours, a 6-hour ride estimated by the ETA: if after 3 hours and 30 minutes I am halfway (with the same track between the first and the second part) it will not take a total of 7 hours, but maybe 8 due to performance degradation due to fatigue. In addition, the longer the routes are, the easier it is for the difference between real time and ETA to become large, also entailing the risk for those who are out to find themselves still far from their destination and with the sun setting down.

Locus Map (4+) / Re: Locus Map 4, discussion (beta)
« Last post by slarti76 on Today at 12:24:24 »
- currently, bottom buttons are limited to max. 5 buttons. Hmm, maybe it may be more "dynamic" based on the device width. I'll look at it. An alternative may be a user-defined number of buttons but hope this won't be necessary.
I second that it should be somehow dynamic. Depending on device and, that got kinda forgotten at all, landscape mode! Right now, in landscape it's just wasted space. I know, LS is not used that often, but still. At least some of the additional buttons should float to the bottom bar.
Locus Map (4+) / Re: Locus Map 4, discussion (beta)
« Last post by Diddi on Today at 11:59:51 »
A 6th bottom button would be great.

I'm able to simulate this bug every time.
See link:

Pages: [1] 2 3 ... 10