Messages

Am besten du legst das Backup neu fest. Vielleicht geht es dann wieder. Im Backup Manager in den Einstellungen kannst du festlegen wo.
Wenn du es im Locus Ordner hast ist es nicht sicher bei deinstallieren. Oder Löschen vom Ordner. Ich habe im Download Ordner vom Phone einen Ordner angelegt und diesen festgelegt.
Zusätzlich noch in die Cloud.

[@freischneider]

@freischneider
 Sichtbarkeit von Kreuzungen > Hmm, guter Punkt, aber wie lässt sich das umsetzen? Die Standard-Navigationsfarben funktionieren hier recht gut. Die benutzerdefinierten Farben werden auf die gesamte Strecke angewendet, daher sind diese Kreuzungen nicht mehr so deutlich wie zuvor. Und da ich zuerst die gesamte Kontur und dann die gesamte Füllung zeichnen muss (hauptsächlich aus Performancegründen), sehe ich hier keine einfache Lösung.

Automatische Verbindung > Normalerweise verwende ich zwei Methoden:

• Direkter Zugriff auf den ,,Sensoren-Manager" auf der Kartenansicht, daher nur drei Klicks zum Aktivieren.
• Und hauptsächlich ist die automatische Verbindung im Aufnahmeprofil aktiviert. Ich habe also eine Reihe von Sensoren am Fahrrad, die sich immer verbinden, wenn ich das Aufnahmeprofil ,,Fahrrad" starte.

[/list]

It's too bad that displaying intersections doesn't work the same way as in the standard navigation yet. But maybe a solution will come along eventually.
The automatic connection of the sensor via the recording profile works great—thanks.
The idea of pinning the graph is a great solution.

I also tested the e-bike sensor for the EP8. My battery level was displayed perfectly on the dashboard.
But the first time I use it, I always have to activate it. That's very time-consuming: Menu, Settings, GPS Sensors, Sensor Manager, Connect.

If I turn off the e-bike while riding and turn it back on after a short time, the sensor is immediately recognized.

But when I launch Locus the next day, I have to reconnect the sensor.

Am I doing something wrong? Is there a faster way? Or is there a way to have the sensor connect automatically every time?

Translated with DeepL.com (free version)

The colors for elevation are now easy to read. I tested it for a few days in the mountains.
But I'd also like to see this option for the navigation route. I can choose a custom setting there, but I can't see which way to go at intersections. Sometimes there are two or three options for turning right.

It's not impassable. It is passable and has been graded. But with a warning—and that's important. If you ride your road bike into a pothole like that, you'll crash. That's why the warning is important.

I think it is a problem that there is only one fixed cutoff for all classes of "bad" surface. In my experience riding a rodadbike the smoothness=intermediate roads that I know do not pose a problem for road biking (except in a race maybe).

So in light of the discussion it would be useful if eiter

• More than one class of "bad" surface to get a better feeling of what to expect without checking every section, what exactly is meant by "demanding"
• make the cutoff configurable to get some liberty to what is accepatable as surface condition and what should generate a warning to accomodate different expectations/material

Greetings, Ulrich

I think it would be most sensible if you submitted a suggestion to the helpdesk. Discussing this here is the wrong place.

The route is marked as poor in OSM. Potholes, cracks, etc. Bad for road bikes. You should adjust the OSM data if it's better in your local area.

If you are referring to the smoothness=intermediate tag - I think to classify this as "demanding" still is a bit to harsh. Since there is only one category of bad road in locus, it is s bit broad to classify this the same way as some really unrideable roads.

All the smoothness=intermediate I found in my neighborhood do not qualify as demanding. The OSM description also just says "may cause trouble for racing bikes." This is a Konjunktiv and only refers to a small subset of bikes.

So in my opinion the cutoff is better suited at smoothness=bad.

Greetings, Ulrich

It's not impassable. It is passable and has been graded. But with a warning—and that's important. If you ride your road bike into a pothole like that, you'll crash. That's why the warning is important.

Hi,

Since a few versions, I noticed a change in how bike-routes are represented. Locus shows a lot of Streets as "demanding Surface", that are perfectly normal paved streets. I think the interpretation of the OSM flags seems to be off sometimes:

An example:

This is shown as demanding:

You cannot view this attachment.You cannot view this attachment.

On the other hand the way types and surface are the same between demanding and not demanding parts:

You cannot view this attachment.


The OSM Object is https://www.openstreetmap.org/way/16901568

There the way is shown as asphalt *and* grade1 - which means paved. So - at least for me - this does not imply "demanding".

For those interested, this is the streetview of the Road: https://maps.app.goo.gl/9LpCCxVVD4yCGRWd6

So I think there should be some tuning regarding the classification and/or representation as "demanding", because now it is more often misleading than helpful in route planning.

Greetings, Ulrich

The route is marked as poor in OSM. Potholes, cracks, etc. Bad for road bikes. You should adjust the OSM data if it's better in your local area.

"REORDER SECTIONS"

Maybe this way: 

I like the idea of being able to choose what's displayed. It's also good that you can move it around.
I'll select everything except "Interval," maybe in a different order.

But when I look at the chart, everything above it gets in the way.
You should be able to hide it temporarily. Then there would just be the chart and the map. I drew a button behind the word "Chart."
That lets you hide everything above it.
But when I open the track, everything should be displayed. Then, if I want to take a closer look at the chart, I'll hide everything above it.

can someone help <Colour legend (Premium) — tap the question-mark next to "Line style"> - where is the question-mark icon in the track chart? thanks

At the bottom

@freischneider example of bottom of a track chart; what am I missing?
You cannot view this attachment.

[Locus Map 4.34.1.3]

Locus Map 4.34.1.3
AI-generated news...

I hope @Menion isn't being replaced by @AI

can someone help <Colour legend (Premium) — tap the question-mark next to "Line style"> - where is the question-mark icon in the track chart? thanks

At the bottom

I don't like the new colors for the track in "Colored Gradient." I'm having trouble following the course of the track. The colors are very pale. With the old colors, I could see the track much more clearly, and I could spot steep sections much more easily. They stood out right away.

The bike sensor is great. Added the Shimano EP8 sensor / battery level to the dashboard. Works great.
Thanks
Question: Does the Bluetooth connection drain the battery constantly? Or only when the screen is on?

so sehe ich das auch. Evtl. kann ein Admin ihn schließen

Since 4.33 there is an issue when calculating routes with highways. Every exit is announced as a "keep left". Very annoying and this was not there before.

Reproduce: open the planner using offline locus router. Plan a route over a long stretch of highway. Inspect the details and you'll find hundreds of navigation points, all the same: "keep left".

Verified in latest beta.

You already posted this in the helpdesk; please do not post duplicates.

Karte drehen einfach mal im Handbuch nachlesen. Findest du im Hauptmenü ganz unten unter Helpdesk. Oder hier unter der 8:
https://docs.locusmap.app/de/doku.php/manual:user_guide:maps_mainscr_ctrl

Die Taste ist nicht immer vorhanden. Kann man aber in den Experteneinstellungen ändern. Dann ist sie imer da und kannst wählen Blickrichtung, Norden und Hand

Blickrichtung findest du in den Einstelungen, auch ganz unten im Menü. Dort bei Suche einfach eingeben.

Zum ständigen wechsel ein/aus findest du es in den SChnelleinstellungen

Am besten mal ein paar Stunden investieren und das Handbuch durchlesen.