Messages

I see. I think I would then switch to another app, Elevate is really indispensible to me (unless something equivalent which really shows OSM data in detail exists for MapLibre). But I am just one datapoint.

iOS version will use MapLibre library for maps, so there is a huge chance, it will have 3D maps quite easily (at least compared to Android).

I guess that means mapsforge themes like Elevate will not work on iOS, right?

Also, would 3D support mean moving from mapsforge on Android?

I already see them on the map, it is not a problem when I need to navigate. ie. know where to go. The use case is counting the distance and elevation change so I know how far I have to go. In the screenshot above, the distance is 43.3 km. However, when I add a few shaping points just before 5 to trace my blue line (which is a path), the real distance is more like 50 km.

Another thing is that elevation says 194m, whichs is clearly wrong, this goes over a high pass from 1800 to around 3000 and then back down to 2000, so it seems the elevation change is taken only from brouter/loroute, it does not actually trace the route to count the elevation gain correctly. Not sure if this is intentional?

When you add a route to OSM, it is not immediately available on the map. But BRouter has the data a day later. The LoRouter (BRouter) makes an update every 7 (4) days.

Aha, cool! I did not know that.

Turn-by-turn directions are not yet possible. I change the shaping point before the manual segment to a via as a turn-off hint. You can also name the via Attention, so that it indicates the area you want to look at in particular. The name of the via is announced during navigation.

I personally do not need turn-by-turn directions. Just to be on the same page, I am using the route planner as attached. Between points 1 and 2, Locus correctly uses a trail that is in OSM. between 3 and 4, there is nothing, so a straight line is sensible. However, between 2 and 3 and 4 and 5, there are my tracks that get unused. I guess my request/question is if Locus Map could use these tracks as shaping points automatically maybe? 

Well, specifically I was using Locus on the Greater Patagonian Trail: https://wikiexplora.com/Greater_Patagonian_Trail

it is a collection of trails, some are on OSM, some not, some could be added, some probaly not (for example especially the one on water, part of the trail assumes you ahve a boat).

But even in a general case - let's say I download a recorded track from somewhere and first want to explore it before adding it to OSM (and anyway, there is quite a lag before the edit in OSM makes it into a map I would be using in Locus). It would be nice if Locus could use this for routing. I am not familiar with the implementation so I have no idea if this is totally out of scope of how it is being done now.

I am an OSM contributor and I know about all that. However, uploading these specific files is not really an option (also because some of the trails are non existent - they are virtual paths through open landscape without any visible trails, so it is dubious if they belong to OSM, which should map only things existing in reality).

Is it possible to get routing using GPX tracks added by me? Ideally I would like to be able to select point A and point B and get a route using my tracks so that the route would display the distance elevation etc. Now when I am using the route planner, the app says "the routing service can't find the start point, please redefine it". Would it work if I had routes instead of tracks in my GPX file?

This applies to cases where there are no paths under my GPX tracks in the map data.


My understanding is that for routing to work, the map used needs to have "routing information". So my question is if I can add my GPX info to that routing information? I tried searching but could not get a definitive answer.

That would not help me, I use Locus mostly offline, Google Earth isn useless in such a setting. Thank you for the tip though.

Any update on this in last four years?

My friend uses Gaia maps and 3D view is the only feature I am envious about. Not that it is a dealbreaker, I can still interpret contour lines with shading, but it is cognitively heavier and so it takes longer.