Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Graf Geo

#1
I use the dual centering button. The red arrow is hidden. But when you touch the button, the red arrow appears and the rotation is activated. Since a long click deactivates the "Hold map centre" function, I often activate the map rotation by mistake because I click too short.

When I deactivate the dual centring button, the red arrow is always there.
The following users thanked this post: freischneider
#2
Ein paar Verbesserungsvorschläge in den Locus Menüs (Stand 4.25.1.8):

Planungsmodus, in den Profilen:

Statt "Durchschnittsgeschwindigkeit auf ebenem Boden" wäre m. E. besser
"Durchschnittsgeschwindigkeit in flachem Gelände".

Statt "nasse Verhältnisse" besser "bei Nässe" (entspricht auch deutschen Verkehrsschildern) oder "nasse Bedingungen"

Statt bei gravel "Kies" besser "Schotter".

Beim Profil MTB:
Statt "Geländeniveau" besser "Schwierigkeitsgrad" oder "Geländetyp",
die Einteilungstypen ("weich, rollend...) sind m. E. nicht ideal, hier fällt mir leider noch keine gute Lösung ein.

Wie gesagt, das sind nur Vorschläge.
The following users thanked this post: Tapio, freischneider, kodela
#3
Locus Map / Re: [APP] - version 4.25.+ ( 8/2024 )
September 20, 2024, 12:55:15
Unfortunately, I now have to report a major problem. Internal LoRouter profiles no longer work for me:

After the latest update (4.25.1.7) I have massive problems with the route planner. The internal LoRouter profiles (offline) no longer work reliably for me. This affects all Internal profiles where the speed or power can be set, i.e. walking, hiking, touring, gravel, road and MTB, which are stored in the router/data/customised folder.
The orange-coloured error message always appears, stating that the value for speed/force is not known (unknown expression). See screenshots.
Internal profiles without this setting option (car fast, economical) and all external profiles work.
The joke is that sometimes it works again, but then it doesn't work again the next time I restart. I have already deleted all internal profiles in the data folder and all files in the customised folder, but the problem keeps recurring.
The following users thanked this post: luce
#4
Locus Map / Re: [APP] - version 4.25.+ ( 8/2024 )
September 20, 2024, 11:02:54
I agree, great update! Thank you very much!

3 comments:

Text rotation: excellent! But as @Tapio already wrote, the map jerks when rotating, in small fixed angle steps. Since I only use map rotation very rarely, I'm not quite sure if this was the case before. But I think the rotation was smooth before.

I also have the feeling that the rendering of the maps is somewhat slower than before. When moving the map, the labels (place names, mountain peaks etc.) appear first in the white areas and then the actual map. Could this be the case or is it just a subjective impression?

"Quick search results for functions and settings": Very good! I like the solution with the buttons ("x features", "y settings"). It would be even better if results were also offered in other local categories: "x results in tracks", "y results in points" etc.
The fact that you always have to select the category in the search before entering the search term is a bit annoying.
The following users thanked this post: freischneider
#5
Locus Map / Re: [APP] - version 4.25.+ ( 8/2024 )
September 17, 2024, 06:32:50
Hello @Andrew Heard, settings in LM4. Item is called "Route warnings":

The following users thanked this post: Andrew Heard
#6
Locus Map / Re: [APP] - version 4.25.+ ( 8/2024 )
September 14, 2024, 20:11:20
Two brief comments on the visual changes in the route planner menu:

New design of the slider for the average speed on flat terrain (screenshot 1): nice 🙂

New colour of the altitude chart symbol (pink, screenshot 2): a bit strong. Perhaps use a more subtle colour (Locus blue) or go back to black as before.

The following users thanked this post: freischneider, luce
#7
Locus Map / Re: [APP] - version 4.25.+ ( 8/2024 )
September 13, 2024, 19:31:51
Yes. Crashes when GPS is on.  :'(
The following users thanked this post: Tapio
#8
Confirmation: Fixed in new Beta. Perfect, thanks.  :)
The following users thanked this post: Menion
#9
When I activate LoPoints, a simple short click on the POI is enough to add it to the route. And it is also given the corresponding name.

With the normal POIs, the address is adopted if you have the corresponding LoMap with address database installed. The name of the POI is actually not, but that's what LoPoints are for. So I don't see such a great need.
The following users thanked this post: Tapio
#10
Locus Map / Re: [APP] - version 4.25.+ ( 8/2024 )
August 31, 2024, 19:31:34
I cannot confirm this. Works as usual for me.
The following users thanked this post: Tapio
#11
Ja, das sollte für alle Tracks/Routen gelten, die keine Navigationsanweisungen enthalten. Egal ob selbst erstellt oder aus anderen Quellen importiert.

Zu deiner zweiten Frage:

Sorry, ich hatte diese erst missverstanden und muss die Antwort nochmal neu schreiben:
Tatsächlich sind es Wegpunkte, die in Locus einfach als Standard-Punkticons angezeigt werden. So wirklich Sinn kann ich darin auch nicht erkennen, nur dass du siehst, wo du in BRouter deine Klicks gesetzt hast. Wenn du dort bewusst eine Sehenswürdigkeit, einen Biergarten oder was auch immer angeklickt hast, siehst du die Position dann auch in Locus. Nur zur Orientierung.
Du könntest dann in Locus an der Stelle manuell einen "richtigen" Punkt (shaping point = grünes Dreieck) oder einen Zwischenpunkt setzen.

Sinnvoll kann das sein, wenn eine Tour aus einer anderen Anwendung exportierst, die Wegpunkte beinhaltet, die dort Etappenziele (Sehenswürdigkeiten, Gaststätten, sonstwas) bedeuten. Dann können diese in Locus so auch angezeigt werden.
The following users thanked this post: olliz
#12
Indeed, the "straight ahead" instruction is actually generated by LoRouter unnecessarily often in certain cases, especially in the city:

If I plan a route directly on a long street (not pavement!), no superfluous "straight ahead" instructions are generated.

If I plan in pedestrian mode (profile walking) along the same road on the pavement/sidewalk, numerous "straight ahead" directions are generated, not at road junctions, but always at the access roads to properties (driveways), which are naturally very common in the city. (OSM tag highway=service / service=driveway). And also at intersecting cycleways. See screenshots.

Somehow LoRouter thinks it has to generate a "straight ahead" instruction at every "driveway" and "cycleway" crossing. GraphHopper and BRouter do not generate these. Therefore I suspect a bug in LoRouter when routing on pavements.

Link: Route on pavement, numerous superfluous instructions at property access roads (LoRouter profile Walking)
https://link.locusmap.app/t/5247i2

Screenshot 3 is a straight way in a forest passing a allotment garden colony. A "straigt ahead" instruction is generated every few metres on every path/access road into the colony. A bit annoying.  8) 

The following users thanked this post: Menion
#13
No, unfortunately that's not possible. I also don't think the colours are well chosen and the map or planning is confusing as a result.

I therefore prefer to plan on the PC with brouter web (https://brouter.de/brouter-web), even if I can only export my routes and not synchronise them.

However, I usually plan with the route planner in the app, which I really like.
The following users thanked this post: GusGF
#14
In route planner. Choose planning mode and disable checkbox "include navigation commands".
The following users thanked this post: Andrew Heard
#15
Locus Map / Re: [APP] - version 4.25.+ ( 8/2024 )
August 23, 2024, 16:40:18
Thanks for the new beta!

I have not yet understood the first two new features ("support for alternative route" and "disable fill of street addresses"). Where can I find them?

First impression: the improved time displays in the route planner / track info window look good.

In my opinion, it would be better for the time if the unit "hour" was also displayed below 1 hour. So 0:35 h instead of 35 m.
With "m" I always think of metres as with the other fields. In addition, the saved space is unnecessary, as at least 3 digits are displayed from 1 hour (1:02 h).

In the dashboard (this is not a new request, but I have wanted to suggest it for a long time), I would like to see a little more space between the value and the unit. They are very close together, which looks a bit inelegant. In some cases, the number and unit are touching.

Zoom settings for overlays: when overlay is activated, the "Advanced options" button is half cut off or covered by the Android footer. You then have to pull up the menu a little. But that's not a problem.

The new design of the "all functions" menu actually looks a bit nicer.  :)

Have a nice weekend!
The following users thanked this post: Menion, Tapio