Messages

AFAIK, I unpacked it manually into the themes directory.

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

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 understand voting in this context is about the priority of implementation of basic, needed and useful features.

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

Já bych ji prostě ukončil a pustil, když ji potřebuji.

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

As a workaround, one can also use file transfer from their FTP file server, I use Android version of Total Commander for that.

ftp://ftp.gwdg.de/pub/misc/openstreetmap/openandromaps/

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

I personally insert short comments in similar spirit for some my challenging (on demand) profiles for MTB, that following routes given by that profile may cause heavy fatique, injury or even death of inexperienced users.

One of such 2 profiles have been for some reasons originally included as the built-in  MTB profile of the Locus internal Brouter, until I strongly recommended to replace it.:-)



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

I agree, as some unnamed inhabitants of the unnamed continent may use Locus this way and some 15 page disclaimer should be used, like what you should not do with a  microwave oven.

I personally insert short comments in similar spirit for some my challenging (on demand) profiles for MTB, that following routes given by that profile may cause heavy fatique, injury or even death of inexperienced users.

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

AFAIK, this is hardcoded in Brouter, so modification has to be coordinated with Brouter author, as all 3 Brouter versions (external, online, internal) should provide consistent results. IMHO, personalized settings exposed to profiles, already available for bicycle and car profiles, should be implemented.

OTOH, relying on ETA calculations for mountain hiking is dangerous and quite a stretch. Common sense and consulting available hiking info is assumed. If a tool fails because it was used, where it should not be, it is not the fault of the tool.

Bicycle route  planning has advantage ETA calculation can be directly affected by Brouter routing profiles, mostly by tuning the effective mechanical power of "human engine" in the used kinematic model. I use for myself 85W and true total weight for long/loaded trips, which includes fatique and technical/recreational stops.

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

Possibly related:
@Menion I remember myself reporting for early beta version of the planner something similar for bicycle route planning, that you promptly fixed.

In that case the issue of obviously wrong time occured only for long enough route segment, with the total ETA time fixed with following, formal very short extra route segment.

I guess it had something to do with internal timing.


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

Interesting. I ask myself the opposite question - When is navigation based on geometry useful ( aside of off-road navigation through free terrain ).

I used to it in past for precalculated routes, when using OSMand, but I have later switched to Brouter based navigation hints, never looking back.

But one has to understand, how and when Brouter creates the hints ( or does not ).
E.g. If passing a town via a secondary or tertiary road, Brouter will never raise a hint, no matter what turns are there, unless there is a crossroad with a road of the same or higher priority ( profile priority, not traffic priority). OTOH, If you are to go straight ahead to the town residential network, leaving the major road turning away, it would tell you.

Look - in Brouter context - for terms PriorityClassifier and TurnInstructionCatchingRange

For more see https://github.com/poutnikl/Brouter-profiles/wiki/Glossary

The priority classifier
-----------------------

Priorityclassifier is a BRouter numerical parameter calculated for ways and used for generation of pictogram/voice navigation instructions. Higher values means the more significant (noticeable) way, as far as it can be predicted from OSM data.

To avoid a navigation instruction flood, it was decided that the instructions are provided only if:

1/ You are supposed to turn at a crossroad/junction
    and some other leaving options have the same or higher Priorityclassifier value.
OR
2/ You are supposed to go straight ahead  and some other leaving options have the higher Priorityclassifier value.

----

assign turnInstructionCatchingRange = 20    # %turnInstructionCatchingRange% | Within this distance (in m) several turning instructions are combined into one and the turning angles are better approximated to the general direction | number

This parameter considers all crossroads/junctions within the range as a single one, providing rather a cartographic wider picture relative direction. So it takes all the potential crossraod maze within the range as a "crossroad black box". If you approach this black box e.g. from south, and if you are to leave it to northwest ( in a broader picture ), it would say - "turn slightly left". If you are to go to southeast, you get "turn sharply right".

Reasons for this are (my guess, not official explanation ):
- sometimes confused mapping of the road connections and their angle geometry
- sometimes confused precise road connection locations
- sometimes confused precise user location due position error
- sometimes confused user position timing, misleading the user he is elsewhere than reported position itself. ( Like the Locus reports there is 70 m to the crossroads, at the time when the physical distance is just 40 m. It may lead to taking a wrong turn.

I remember some recommended for good distinguishing desert from outdoor/desert V4 map theme package.

https://forum.locusmap.eu/index.php?topic=6551.0

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

there is nice aviation picture relating altitude, elevation and height on wikipedia

https://en.wikipedia.org/wiki/Altitude

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