Messages

Great theme.

For the changelog, the waking up of dusty rusty school Russian knowledge is advantage. I can still read  cyrilicsand understand it without much  troubles. :-)

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I think the both Locus ETA systems ( routing service ETA for the planner + Locus usage profiles for track statistics)  should be unified.

It would be nice to have the routing and the custom settings as the 2 extra options in addition to Locus ones.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I guess you do not mean altitude itself, but the total altitude ascend, which is computed from the recorded altitude profile or from SRTM data for planned route

Estimation of the true altitude ascend is tricky. There is no a priori way to determine the just proper level of filtering. It is always balancing of filter oversmoothing of real details with leaving residual altitude noise due GPS or SRTM artefacts.

It is quite common Locus planner comes with up to twice value, compared to Brouter value based on used built-in filtering.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

But I hoped that built in navigating is better than Brouter.

It is BRouter, just integrated one. It would be better then external one just in some secondary aspects, not related to navigation itself. Like not having time out issues for very long route segments, Brouter transparency, no limitation by Brouter API or integrated background BRouter data download/update.

Navigation is as good as the used navigation profile, with few exceptions of Brouter design limitations. Possibilities, relying on internal or external profiles are for both internal and external Brouter the same.





Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

https://web.locusmap.app

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I am afraid tweaking of foot profiles will not help in tweaking hiking/running ETA. ETA calculation for foot profiles is AFAIK hardcoded to BRouter, perhaps some variant of Naismith or Tobler formula.

You could experiment to pretend during running you are a bike, with some experimental tweaking of the to-be-for-bike parameters.

Hi,
How can I set up the ETA in the planner?

The ETA on the map using planner is not the same on the stat of the panel.

AFAIK, ETAs on the planner are those reported by BRouter according to its internal algorithm, affected by BRouter profile configuration of the Brouter profile kinematic model ( cars or recent ones for bikes ). 

Stats in the panel are calculated by Locus from its builtin activiity profiles for horizontal/vertical speed, according to the route altitude profile and chosen activity, independently on BRouter.

IMHO, both have their place, but perhaps the user could choose either of them as the planner default.

Using a brouter profile for ETA has an advantage - when using an external profile - that one can tune the profile according to his physical conditions or intended effort. E.g. you can set the biker's steady mechanical power, tyre rolling resistance, aerodynamical drag or the total bike mass. It becomes handy for planning long distance trips/expeditions, where a bike is heavy and affordable mean sustained power is rather low.

Most of these parameters can be well estimated but the power. My advice here is to tune the estimated mean power up/down, until its prediction for the relevant scenario matches the reality. E.g. I use for myself for 4+ hours trips 85 Watts.

Navíc hodně pomáhá, že nové Androidy mají vyhledávání v nastaveních, což hledaní toho pravého místa hodně ulehčuje.

Thanks for version clarification.
Regarding surface categorisation, it seems very fine to me.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

In contrary to profiles, extra specification does not make much sense. I have spoken  for specification for common users, not experts. For the stats to be really useful, not just bells and whistles.

Whatever will be Menion's final decision, I will be fine with that. I have just wanted him to hear various opinions.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

About the elevation + way type + surface chart, it may be good if they were somehow, even if not exactly, zoomed together with the map.

E.g.  a route is 120 km long, but the map is zoomed in to show just a 5 km long route section between 20 and 25 km. The charts should not show all 120 km, but just the relevant section, possibly with some padding.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Hmm, for bicycles, it would be good if similar surface qualities had the same category/colour. Too  many options is hard to remember and the bar chart could be too much scattered.

E.g.

• cobble stones and pebble stones are much closer to gravel than to sett
• sett is effectively close to concrete, both make you little jumping up/down.
• finegravel is quite far from gravel. considering smoothness and convenience.
• paved almost always means asphalt and should probably have the same colour/category.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

LM4 is not in Play store yet.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Note that BRouter does not store street names in its rd5 files. So even if Brouter were integrated, it would not provide the names.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

1. bei den Zu-Fuss Profilen "Hiking-Alpine-SAC4" auf schwierigeren Routen das Routing verweigert, Schwierigigkeit SAC4 ist anscheinend ja die Grenze, Zu-Fuß Profile mit höheren Graden seh ich nicht.

Google translated text ( original English below )
Beachten Sie, dass in Locus integrierte BRouter-Profile nur sehr wenige Profile enthalten, die vom Skript sedbatch Zeilen 613-660 aus meiner Wander- und Trekking-Profilvorlage generiert werden.

Unter HikeProfiles finden Sie die vollständige Liste der Wanderprofile, die aus dem aktuellen Wanderprofil generiert wurden.

Viele weitere Profile können manuell oder durch Hinzufügen einer zusätzlichen Zeile zum Skript erstellt werden, indem lediglich der anpassbare Parameter der Vorlage angepasst wird.
Was über das Wanderprofil gesagt wird, gilt auch für Fahrradprofile.

Original text:
Note that Locus builtin BRouter profiles involves just very limited set of profiles, that are generated from my Hiking and Trekking profile template by the script sedbatch rows 613-660.

See  HikeProfiles as the full list of Hiking profiles generated from then current Hiking profile.

Many more profile can be created manually or by adding an extra line into the script just by tweaking the template adjustable parameter.
What is said about hiking profile applies also to bike profiles.