Messages

[@wollewolle]

@wollewolle & @balloni55
ah,so the edit of coordinates > this is a big change in recent Beta versions. We completely removed the old "Grid" screen and integrated all into the search screen. No functionality should be lost, and all features are directly in the top row. So the edit of coordinates, projection etc., is all at the top row.

@menion
the old function was great. All in one view no scrolling that was fine. The most important for me "clipboard" and then "guide too" I didn't find yet.

Puh this change I don't understand from UI side. Maybe it has technical reasons but this is not helpful and I really don't like it. Sorry for saying that.

Wolfgang

+1

Just noticed a minor bug: When searching for a point, a small arrow is shown indicating the direction to the point. It's shown in the list and in the point details when I click on the point. However, it's turned 180°, pointing in the exact opposite direction!

I just realized this might be intentional, but I'd argue that's totally unintuitive: When I search for a point and want to quickly see whether it's east or west from my current position, not whether my current position is west or east from the point.

Just noticed a minor bug: When searching for a point, a small arrow is shown indicating the direction to the point. It's shown in the list and in the point details when I click on the point. However, it's turned 180°, pointing in the exact opposite direction!
Also, for some reason the elevation is not shown, even though I definitely have the SRT data for this are (it's shown on the map when I hover over it.

I like the new "Dotted style only" (although I think "Dots only style" would be better), but the color selection is unintuitive: It implicitly takes the color from the "Line", but to get dotted style, you need to deselect "Line", which also disables the color selector.

Minor bug:
When doing "Share as Screenshot", Locus displays the way the screenshot is going to look, then you have to press the "Share" icon again, and a system dialog showing the actual screenshot in small is shown.
That's all fine, but after I did  it once, the next time Locus always shows the same preview as the first time, even though the shared picture itself is correct. Only close/open of Locus resets the - obviously cached - preview.

• Track chart no longer swallows tap events, and chart zoom respects the selected location.
• Chart slope data gets stronger optimisation

@menion 4.33.0.10 - confirmed improvement of chart slope - below is comparison of Web Planner (top chart) & LM (bottom chart) with my previous example - now LM shows 5% instead of 8% slope - far more realistic; zoom respects the selected location - great, thanks.
You cannot view this attachment.

I do believe the web planner's way of filling the parts above and below the zero line is far superior to what Locus app currently does. Even better would be different colors (e.g. red for above, green/blue for below, perhaps with gradient).

400 Points shown, I turn AR on, rotate the camera a bit fore and back, along the points... LM crashes reliably.

"AR"? = Augmented Reality? Must have missed that, where can I find that? I searched in settings and functions, nothing...

Currently, app compute times as:

• track time - all times between trackpoints. Breaks are skipped and not computed
• track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)

What you want is to change this behaviour to

• track time - simply difference in time between the first and last point
• track time (movement) - all times between trackpoints. Breaks are skipped and not computed

Any opinions? Maybe introduce a third time? 

I'd wouldn't mind a third time or ability to change the threshold. For hiking and snowshoeing, the "movement" times are frequently too low, as in ascent, you easily get below 2km/h.

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.

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!

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.

[@T-mo]

@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...

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.

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?

[@Gerhard57]

@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...