Messages

Hmmm, mbtiles and sqlitedb are quite common, beyond Locus, and not a Locus private bitmap format.

Maybe time to upgrade Locus, too?

In Locus you can move major folders to different locations, and as far as I remember, Locus will do the moving for you.
This option always applies to the SRTM folder (Settings->Backup&FileSystem->FileSystemManager).
So, first do this move, then replace the respective files with Sonny's latest
Now, WHERE TO let Locus move any stuff?
- /Android/media is the best place, because more file managers can access those structures propoerly, even on Android 14
- INT or EXT SD? I have tons of SRTMs (mix of 1" and 3" across the world) on EXT SD and it works fine

Release notes 202406-1.0

    The OAM background from ZL 8 and up now is rendered from May/June 2024 edition of Christian's OAM vector maps (incl. Near East, for which the OSM vandalism repair seems completed).

    In less densely populated areas, not every - even significant - peak has a name, and even if it does, such a peak is far from being in OSM. Based on the 30m Copernicus DEM, I have identified peaks with a dominance of 100km or 200km for all continents except Antarctica. If one of these peaks does not have a known peak in its vicinity in OSM, it is displayed in these new world maps as 'Loc.HP' (for 200 km isolation) or as 'loc.HP' (for 100 km isolation), in each case with the coordinate (2 decimals) and its altitude. There are a bit more than 1000 of these.

    So if a user knows a name for such a 'local high point', please enter it in the OSM database so that I can replace the (virtual) auxiliary summit with the real OSM summit in the next release of the maps. I expect that in the vastness of northern Canada, Alaska and Siberia as well as the tropical rainforests, many of them will remain nameless. But they are still relatively high and isolated 🙂

Versionsinformationen 202406-1.0

    Der OAM-Hintergrund für ZL 8 und höher ist jetzt aus Christians Mai/Juni-2024-Vektorkarten generiert (inkl. Naher Osten - die OSM-Vandalismus-Reparatur scheint abgeschlossen).

    In weniger dicht besiedelten Gebieten hat nicht jeder - selbst signifikanter - Gipfel einen Namen, und selbst falls er einen haben sollte, ist solch ein Gipfel noch lange nicht in OSM. Auf Basis des 30m-Copernicus-DEMs habe ich für alle Kontinente außer der Antarktis Gipfel identifiziert mit Dominanz 100 km bzw. 200 km. Falls einer dieser Gipfel keinen in OSM bekannten in seiner Nähe hat, wird er in diesen neuen Weltkarten als "Loc.HP" (für 200 km Dominanz) bzw. als "loc.HP" (für 100 km Dominanz) angezeigt, jeweils mit der Koordinate (2 Dezimale) und seiner Höhe. Es gibt davon gut 1000 Stück.
    Falls also ein Nutzer einen Namen für solch einen "local high point" kennen sollte, sei sie oder er aufgerufen das in der OSM-Datenbank einzutragen, damit ich den (virtuellen) Hilfsgipfel durch den echten OSM-Gipfel ersetzen kann im nächsten Release der Karten. Ich erwarte, dass in den Weiten von Nord-Kanada, Alaska und Sibirien sowie den tropischen Regenwäldern viele davon namenlos bleiben werden. Aber in Relation hoch und isoliert sind sie trotzdem 🙂

Hast Du den automatischen  Export  aktiviert?
Der schreibt für jeden Track die zugehörige gpx-Datei in das export-Verzeichnis von Locus.

PS: es ist auch (für die Zukunft) ratsam, tägliche Backups zu konfigurieren (gerade wenn mensch unterwegs ist). Locus überschreibt dann automatisch immer die ältesten.

Interesting case indeed. Root cause of differences are the two fundamentally different data sources
- track recording, regardless if by Locus, any other app or Garmin is they rely on GPS signals from satellites. Reflections, blockages, spoofing and alike impact those, by physical effects. In particular the elevation data is not too reliable. You can see horizontal and vertical fluctuations when you look at the graph.
- update elevation on the other hand gets its data from DEM data files. Typically 3" (90m) resolution, but Sonny's data has 1" (30m) resolution for most of Europe. Typically an "update elevation" will reduce the flucuations, hence reduce the gain/loss totals rather than inflating them.
I'd look at the graphs to see if the updates curve as visual anomalies.
And I'd check if using Sonny's 1" data gives better results.
Cheers
Michael

Hi selfishchalk,
you should report this to the help desk rather than the form.
They will guide you to take detail logs e.g. to look "under the hood".
20-30%/h is EXTREME (I never read of such in my Locus history since 2012), so there should be a "smoking gun".
Cheers
Michael

I just tested with a Discovery_Walking_Guides map and can tell you that you can be lucky with your view.
Above map has a solid white border, all legends - like a scan of a paper map. Which definitely is not created by Locus, but rather integral part of that map itself.
Can you test your case by displaying one of your maps exclusively, alone (i.e. no overlay mechanics of any kind) and check how it looks like at its border.
If there is such border like in your screenshot, then it would smell like my experience with DWG maps - only "nicer" ...

Die Beschwerdeadresse ist: Google Inc, Mountainview. Seit Android 11 sind die was Dateizugriff betrifft auf einem Paranoia-Trip.
Aber es gibt jetzt einen einfachen Weg: schaffe Deine Rasterkarten nach /Android/media(!!!)/menion.android.locus.pro/maps
Auch das Nachbarverzeichnis mapsVector richtet Locus Pro beim ersten Start ein.
Solche Strukturen gibt es auf der internen und - falls existent - der externen SD. Locus liest diese Ordner bei jedem Start.
Also einfach Deine Sammlungen per Dateimanager hinkopieren (x-plore, Solid Explorer und TC können das auf jeden Fall).

providers.xml im Unterverzeichnis mapsOnline/custom

https://help.locusmap.eu/topic/32424-locus-map-lite-ios-beta-program-open-for-new-testers

should give you some insights into the beta program.

- map shading?
- dynamic elevation?

That's a brutal one ...
I very rarely had a crash related to memory in more than 10 years, but blank popup menues and screens and alike have been a regular issue.
Hence I suspect there might be more than one leak OR one root cause leak that develops towards different, more or less serious consequences, based on still unknown conditions.
Good luck!!
Cheers
Michael

TXs, Menion. After deleting this 1.1 GB sync.db and adding a test waypoint and later deleting that one again, my sync.db is 4kB. And the operation is correctly showing "uploading" or so in the first place.