Messages

Hello,

I have a question about importing GPX routes.
I import a route (not a track) that contains many <rtept> elements. After the import, Locus Map removes most of these route points.
For example, if the GPX route contains about 30 route points, only about 10 points remain as via points when I open the route in the route planner for editing.
Is there a way to import the route without losing any route points, so that a later route recalculation uses all original points?

If many route points are missing, the recalculated route is often very different from the original one.

Here is a simplified example of the GPX structure:

Code Select Expand

<?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.1" xmlns="http://www.topografix.com/GPX/1/1">
    <rte>
        <name>Locus Route</name>
        <rtept lat="49.88311" lon="8.594734"></rtept>
        <rtept lat="49.883197" lon="8.605491"></rtept>
        <rtept lat="49.870131" lon="8.607834"></rtept>
        ...
    </rte>
</gpx>

Am I missing a setting, or is this the expected behavior?

Thank you for your help.

I already created a dashboard with a black background. That's exactly the setup I'm using.

I also found a way to display the distance to the next maneuver and the turn instruction directly on the dashboard, which already helps a lot.

However, I still think it would be nice if Locus could automatically switch to the map for a few seconds when approaching a turn, and then switch back to the dashboard afterwards. That would provide the best balance between battery saving on OLED displays and visual navigation.

Why leave it on all the time? You're not staring at it the whole time, are you? Just turn it on when you want to watch something.

Because I want to keep an eye on live data such as power, heart rate, and cadence while riding.

A mostly black dashboard on an OLED display consumes much less power than keeping the map visible all the time. My idea is to have the best of both worlds: the dashboard for continuous ride data and the map appearing automatically only when a navigation instruction is coming up.

Thanks for confirming.

In that case, I'll submit this as a feature request.

I think it could be useful, especially for OLED devices and long-distance cycling. Keeping a mostly black dashboard visible would reduce power consumption, while automatically switching to the map only for upcoming turns would still provide visual guidance when needed.

Thanks for your suggestion.

My use case is a bit different. I would actually like to keep the dashboard visible all the time, preferably with a mostly black background to reduce power consumption on OLED displays.

The ideal behavior for me would be:

• show the dashboard during normal riding,
• automatically switch to the map only when a navigation instruction is approaching,
• then switch back to the dashboard after the maneuver.

I'm wondering if there's already a way to achieve this, or if it would require a new feature.

Hi everyone,

I'm looking for a way to reduce power consumption on OLED devices while using Locus Map 4 for navigation.

My ideal setup would be to keep a detached dashboard with a mostly black background visible during navigation (showing information like speed, distance to the next maneuver, etc.) to save battery. Then, whenever a navigation instruction is about to occur, Locus would automatically switch to the map for a few seconds and afterwards return to the detached dashboard.

Is there any way to achieve this with Locus Map itself, or perhaps using presets, Tasker, MacroDroid, or another workaround?

If this isn't currently possible, what workflow do you recommend for minimizing power consumption on OLED displays while still having the map available when it's actually needed?

Thanks in advance for any suggestions!