Messages

Hallo Christian,
bei mir kommt das nur wenn ich eine Suche mit Treffern habe, ein Treffer ausgewähkt ist, dieser aber nicht im Fenster sichtbar ist.
Wenn ich auf die Karte tippe, geht das Biest bei mir weg. Und wenn ich auf diese Lupe tippe springt der Bildschirm zur Lokation und ich kann "hide" wählen.
Probiert mit dem aktuellen RC.
Schönen Urlaub da oben und LG
Michael

Backup is working again ! Thank you.

Tested RC beta: backup broken on my devices, too.

Stable on S10 (2019), S25 Ultra.
Few crashes on Tab S10 Ultra, e.g. using 2 fingers to zoom across a number of levels.
Nothing serious, restart is Ultra quick ;-)

Copy providers.xml from your working/older phone to Locus-Root/mapsOnline/custom - I keep mine like an eyeball :-)
But as long as you have the information around your map of interest, you can build a working entry to this file yourselves.

PS: while access speed is no different in either location (data versus media), the benefit of media is file manager access.

In case you move the root folder, I do not know if the current media structure is MERGED or SUBSTITUTED.

If your LoMaps are recent enough, you could re-download in case of destruction.
In case you have Gold subscription you do not care and just download again.

The (in your case only map) data from media can easily be backed up to PC, in case you do not have Gold.

On a Pixel you do not have an external SD card, hence speed is no criteria for optimizing locations, for the databases and alike (any maps could be on a 1.5 TB ext SD and it works like a charm on my Tab S10 ultra).
In other words, you can have maps in either or in both locations without any difference for operations.
When it comes to updates, I do not know if Locus substitutes in place for the location not mentioned in the Locus file system settings.
You may post a screenshot of the set root folder settings page and the set sub-directories settings page.

Locus does scan both of those locations for offline maps. HOWEVER, the /Android/media location is the smarter choice, as you can access it with capable file managers directly (/Android/data needs Shizuku geek approach to overcome Google's insane restrictions).
Did you change the Locus root location in recent times (again, both locations are possible)? Or the offline map location? Both you can defined/change in the Locus settings.
Cheers
Michael

Die Weltkarte wird eingestellt über Settings->Maps->Advanced->Preload.
Zuvor muss mindestens eine Rasterkarte (mbtiles oder sqlitedb) heruntergeladen sein, am besten durch den entsprechenden Installationslink in OAM World Maps.
WELCHE Karte Du da herunterlädst bestimmt den Umschaltpunkt zwischen Raster und Vektor; ZL 9 oder 10 nehmen wohl die meisten.

Valide Frage.
Ich persönlich finde schon bei ZL 10 (und drunter ohnehin) die Vektorkarten grottig.
Und generell sind Labels/Namen in OSM/Mapsforge-Vektor-Maps oft zufällig sichtbar. Z.B. Siedlungen: Definitionen von City, Towns etc. sind in OSM chaotisch. In den OAM-Weltkarten definieren Einwohnerzahlen die Sichtbarkeit. Windräder als Orientierungspunkte: habe ich bei den Vektorkarten noch nicht gesehen - vielleicht übersehen. Kuratierte Inhalte versus Zufall eben.
Aber am Ende ist es ganz einfach: wer's nicht braucht oder will, lässt es einfach.

Versionsinformationen 202507-V1

Der komplette OAM-Hintergrund für ZL 8 und höher ist jetzt aus Christians Juni-2025-OAM-Vektorkarten generiert.
Die Auswahl und Priorisierung der Siedlungen (Großstädte, Städte, Dörfern etc.) wurde nach 1 1/2 Jahren wieder einmal komplett neu berechnet.
Vermehrt werden Siedlungen in OSM als Relationen definiert, allerdings in uneinheitlicher Manier. Somit war auch eine Erweiterung des Algorithmus nötig (,,Warum fehlt Grävenwiesbach in ZL 9??" war hier mein Augenöffner zum Problem).

Viel Spaß ...
Gruß
Michael

Release notes 202507-V1

- The complete OAM background for ZL 8 and above is now based on Christian's June 2025 OAM vector maps release.
- After one and a half years, the selection and prioritization of settlements (cities, towns, villages, etc.) was recalculated once again.
Settlements are increasingly defined as relations in OSM, but in an inconsistent manner. Thus, an extension of the algorithm was necessary (,,Why is Grävenwiesbach missing in ZL 9?" was my eye-opener to the problem).

Enjoy!
Cheers
Michael

[@Michael Bechtold]

@Michael Bechtold
missing pattern > interesting problem I'm unable to simulate. Both features use the identical method of drawing track/route on the map, there is no difference. May you share a track with me, where this happens? Thanks
...

@Menion: just sent you a mail with the attachments. TXs.

Not fixed in current beta - no surprise, as it is not in Menion's list of changes :-)

[@Michael Bechtold]

@Michael Bechtold
missing pattern > interesting problem I'm unable to simulate. Both features use the identical method of drawing track/route on the map, there is no difference. May you share a track with me, where this happens? Thanks
...

@Menion: just sent you a mail with the attachments. TXs.

Track overview lacks track pattern

While "Image & stats" correctly uses the track pattern, the "Track overview" employs the default red line without pattern.

(Moved here from help desk as per Michal's advice.)