Re: [APP] - version 4.33.+ ( 03/2026 )

[freischneider]

After reading the entire thread, it seems the problem is the same as mentioned here:

I think there ist a nasty bug in Beta 4.33.0.1

Routes created using the route planner cannot be edited. Selecting 'Reroute' displays a brief 'Initialising' message, hides the route to be modified, and brings up the screen where I can create a completely new route. It's as if I were starting the route planner from scratch.

Routes created using the web planner can still be edited (once).

See screenshots.

Though, it does not seem to be limited to routes made in a specific small time window. Older routes, i.e. more than a year old, open well, but routes that are from 2026 do not seem to open.

I also found one from February 10, 2026, but it doesn't work either. The route planner is empty when I open it. Luckily, it's just one I forgot to delete.

[Blihi]

For me it's the entire holiday planning for this year, unfortunately 

Well, I'll just hope it will be fixed soon.

[Blihi]

Routes can be restored in the following way: open them in the web planner, recalculate with the correct profile, store as new. Then you can edit them in the app again.

Or, sometimes on a tablet: open the route in the webplanner, select edit, open in planner. Then refresh the page, now the Locusmap app will open with the route in the routeplanner. Here you can save it directly to the app.

[Menion]

@T-mo & @0709
eh, it already exists. Just uncheck all "Line", "Pattern" and "Outline" values in the track style.

@WildWortWechsel
map glitch - ah, I see this. It is an issue in the online backup map. We will probably be changing our base online map during the next few months, so it should be fixed automatically.

two tracks highlighted > yes, this looks like a bug. Thanks, fixed.

@Andrew Heard
hiding of "Optimise" - I made it as you propose at first. But after the discussion, we decided to hide it completely if not needed. All new users will never need it. And this is currently the priority > not to complicate UI to new users.

track highlight - you should see a light or dark border around the selected track

@Tapio
visibility of charts is not based on the track activity. Selecting of every chart separately > maybe later.

waypoints > I'll look at it

@Blihi
share a problematic route with me over "Share by link". Thank you.

[slarti76]

@Gerhard57
smoother charts > this is also question to others. Currently, there is no filtration of chart values. Should I invest some time in it and try to apply a little more clever solution that will preserve the shape and cut the biggest peaks? For all chart types? I'm open to discussion ...

The way it's done in 1210 looks good to me. But I came across one problem recently: Sometimes, the SRT files contain nonsense, where data obviously oscillates between min and max integer, so -32.767km to +32.768km, which makes all charts display nonsense. Can you filter these out? At least in charts, but perhaps also for the map shading, because those sudden gorges are not natural, I fear...

[slarti76]

Question:
Is there a way to jump to the location of the photos shown in the track view? I know, they're selected according to timestamps, but if they also have a location, it would be great to be able to jump there on e.g. long-click.
Or am I overlooking something?

[Menion]

@slarti76
- improved system for interpolation/shading/etc. ... I'm looking forward to it.
During this year hopefully

- photos on the map > not yet

[slarti76]

b) Add (embedded) waypoint to track- on that screen. This would make preparation (also postprocess) of tracks much easier - too exhausting atm. Both types of WP, embedded and non-embedded. But embedded more important as we are in a track context.

I've been hoping for an "Add waypoint" option in the track editor for ages - not sure if we want the same thing, but perhaps both go together. I know, it's possible to add waypoints to a track, but they're not timestamped, they're more POIs. For example, "Hut" is a feature of the landscape and not really related to the track, but "Put on snowhoes here" is related to the specific track and thus the timestamps is relevant.

[slarti76]

@T-mo & @0709
eh, it already exists. Just uncheck all "Line", "Pattern" and "Outline" values in the track style.

Seems to work, but then it says "Style not defined", which is at least midleading...

[slarti76]

Little update if you're also having problems with GPS reliability on Samsung S24 (or perhaps others), see https://forum.locusmap.eu/index.php?topic=9488.msg80515#msg80515 for my initial post:

I didn't find any setting in Locus to prevent this, so I solved it with a Tasker profile that turns GPS in Locus off and on again every min (configurable, of course). Works well. If you're interested, import attached file. Needs Locus Tasker plugin, of course.

[Mick FU]

b) Add (embedded) waypoint to track- on that screen. This would make preparation (also postprocess) of tracks much easier - too exhausting atm. Both types of WP, embedded and non-embedded. But embedded more important as we are in a track context.

I've been hoping for an "Add waypoint" option in the track editor for ages - not sure if we want the same thing, but perhaps both go together. I know, it's possible to add waypoints to a track, but they're not timestamped, they're more POIs. For example, "Hut" is a feature of the landscape and not really related to the track, but "Put on snowhoes here" is related to the specific track and thus the timestamps is relevant.

@slarti76

What about opening your track in the Route Planner (not in Track Editor).
Then you can click on any point,
You cannot view this attachment.

change it into a Via Point,
You cannot view this attachment.
You cannot view this attachment.

do not recalculate, save as new track, and you have a time stamped WP embedded in your track.
You cannot view this attachment.

[slarti76]

b) Add (embedded) waypoint to track- on that screen. This would make preparation (also postprocess) of tracks much easier - too exhausting atm. Both types of WP, embedded and non-embedded. But embedded more important as we are in a track context.

I've been hoping for an "Add waypoint" option in the track editor for ages - not sure if we want the same thing, but perhaps both go together. I know, it's possible to add waypoints to a track, but they're not timestamped, they're more POIs. For example, "Hut" is a feature of the landscape and not really related to the track, but "Put on snowhoes here" is related to the specific track and thus the timestamps is relevant.

@slarti76

What about opening your track in the Route Planner (not in Track Editor).
Then you can click on any point,
<snip>

Interesting, never thought of that, will try. Actually sounds weird that this way, the WP gets a timestamp, but I'll take it. Still, the workflow would be much better if everything is available in track editor...
But thx!

[0709]

Embedded ?
The gpx navigation track mode with instructions in trackpoints offers this "by default."
No more hassle with the "fragile" easily broken gpx waypoint associations based on timestamps.
Imo, the association method is hopelessly outdated given this very simple robuust alternative.

It uses only the track points. This works flawlessly every single time, without fail.
A super-simple, robust proposal was submitted to Locus but not implemented.
https://forum.locusmap.eu/index.php?topic=5953.msg49519#msg49519
Locus Map could have been the first to offer this but gave up before the finish line was reached.
The alternative is therefore a successful implementation realised into another excellent navigation app.

Trackpoints with or without timestamps, in a calculated or a recorded track — it doesn't matter.
Easily promote any trackpoint into an announced via trkpt, silent shaping trkpt, or turn trkpt.

The trackpoint element sym handles the turn instruction.
The track point element type via or type shaping (=muted via) determines whether is announced or not.
(Locus map only supports an promotes the trkpt sym pass_place to be a via point).
The trkpt name than provides the (TTS) via point name announcement.

A combination of a via trkpt with turn trkpt is possible. See a trackpoint example.
<trkpt lat="51.04955" lon="3.9908283">
<ele>3.7</ele>
<name>Just for fun</name>
<cmt>Willebochtenlaan</cmt>
<sym>u-turn</sym>
<type>via</type>
</trkpt>

The "via" point by the trkpt type element is announced by the trkpt name element: "Just for fun".
The turn is announced by the trkpt element sym: "u-turn". 
The TTS announcement in the navigation: "Just for fun, make a U-turn"

By the way. Locus does succesfully read an imported gpx navigation track.
(Only the combination by the type via together with a turn sym is not supported)
Locus map navigation announcement: Make a u-turn. (Locus does not offer the via announcement)

For those willing to do a little test. (Using basic notepad++ edits)
Source is a Locus navigation track or a Plotaroute web gpx exported navigation track.
The Locus default navigation track = a gpx track with associated navigation gpx waypoints.
- Add extra into a single selected trackpoint. (INTO THE trackpoint!)
- Add a trkpt sym turn (for example a left or right or straight).
Or better add a tkrpt sym pass_place plus tkrpt name (local language text expression).
Than test the Locus navigation announcement result.

[slarti76]

Embedded ?
The gpx navigation track mode with instructions in trackpoints offers this "by default."
No more hassle with the "fragile" easily broken gpx waypoint associations based on timestamps.

It's not about associating waypoint with trackpoints. The timestamp is an information in itself: During a recording, I can add a waypoint, which marks that point in time as some kind of event. There don't need to be a trackpoint recorded at the same time.
Obviously, during track edit, that would be a major extra dialog to add a timestamp to a trackpoint (or waypoint, for that matter), so as an approximation, when selecting a trackpoint, it should be possible to set a waypoint at the same location and with the same timestamp. Which should also be kept if the trackpoint were to be removed. Totally independent.

I'm not saying your idea is bad or useless, but I can see how this would be a bigger change for Locus. Waypoints otoh already exist and can be created during recording with timestamp. I'd just like a way to create those I forgot during recording, but still with timestamp.

[0709]

No problem. Stand alone gpx wpt or embedded trkpt in a trackrecord. No problem. See txt attachment.