Messages

Actually it's not masterclass to make an app featurerich but simple in appearance and use.
Though you will easily find bad design or control solutions.
Look at the android-dark-material-design, where active controls or tabs in browser are with that darkgrey that it is pita to reliably distinguish from black. Assuming there might have been a LOT of meetings and finetunings to bring that android-design to life.

Well, that red sign next to position is the worst decision of 2025.
Everything else is said.

I guess Locus will never be for beginners. E.g. look at the simple satellite radar screen with GPS off and you're immediately out of the game, 'no visible sattelites'. Don't get in panic and touch the screen..
I'm fine and understand the logic

[@Gerhard57]

@Gerhard57
duplicate categories > hmm, good point. It is because of change in the language. Give a try next version please.

Problem still exists in 4.30.1
Change of language was just a try to see if it's a problem of translation.

How can I reset the list of categories?
I am using only online LoPoints with OAM maps.

It's the same with english language, see pic, and it's by design, it's actually there since several versions incl. new LoPoint-playground.

[@T-mo]

reg. https://forum.locusmap.eu/index.php?topic=9260.msg79024#msg79024

@T-mo
New LoPoints > I believe the profit of the change is quite big. No difference in online/offline work. A lot richer content of POIs, full compatibility of offline and online, better placement on the map and for use - very easy to modify both worlds at once.

Db documentation and support for 3rd parties > no, not planned and definitely not recommended. New system is a lot more complicated than the previous and we need to keep compatibility with the online and iOS world. That's why "Other POIs" will exist and will still be well supported.

well it's a db and therefore not more complicated as it is by itself.

No doubt it makes sense to unite online and offline if different and grown structures have been in use.
It also makes sense to use a consistent structure if data of different sources get used, parsed, loaded, combined, and processed, and shown in a consistent way. If the community and userbase will bring additional content, like e.g. it is with Komoot, the more important this is, sure.

Well, noone expects a full db-documentation, plain information can be dropped at a dedicated github-page without big efforts as you know.
Even the same GUI-part, category-filter, mechanism could generally be used, though be separated to distinguish and better identify problems due to external database-files (offline), just in case. And back-loading of those can also generally be disabled to never bring those online, if building a LM-driven database is the goal.

I personally tried the old but now preserved LoPoint-part from time to time but decided not to use it consistently as it never was a satisfying experience, category ui in early design-state, poi loading awkward, search pois puh.., poi difficult to distinguish from the background, too small size and too small frame and no features like temporary switch map to bw, etc. It was a start.


Well, I suggest to rethink your view and to support with informations about the changed db-structure, consider 3rd-party sources like e.g. OAM, in my opinion this might better preserve community support and bring a better and more satisfying Locus-experience at all.

Hmmm, I guess the new LoPoint needs some basic love.

see pics, made with 4.29.0.14, but still same with 4.30.0

• only new LoPoint enabled, only 1 category 'food & drink'. AFAIK those are online.
• beside the enabled category also a bunch of other poi-symbols get shown/drawn. They are without the rectanglular-icon-style, but old-school-style.
• if I select one of those it gets the rectangular-style for the time of selection
• ANY selected poi does not get highlighted in any way, maybe orange or neon-green rectangular frame, bigger size, only its item-details pop up
• selecting and switching between those additional (not enabled) poi takes some time, maybe 6 seconds, until the map-drawing gets updated, basic item-details are shown instantly. Maybe it's due some online-loading, parsing, checking for picture, whatever

However, I would appreciate it if this track info panel could be individually configurable. Unfortunately, this is not planned for the time being.

My choosen long track title results in 3 lines, this of course consumes a lot screen space. But the rest is not collapsable and the map size is still fixed and finally limited.
IMHO the applied size is too small.

"point, red marker"
Check the Expert Settings to see if "Centre on point" is enabled under points.

I disabled this setting as it can be annoying while checking different poi in a close area and poi can already be seen though not centered (so centering is more confusing than it helps), also search results in focus and then automatic map centering, and potentially loosing focus in situations not desired.
Enabling the setting activates the desired focus, centering map, sure.
IMHO pressing the dedicated UI-element (icon with indicator of off-screen-position) should also provide this functionality if actively pressed, my suggestion, currently it does nothing.

pt. 2

[New LoPoint]

MapGooglePlayAfa_4.29.0.11_1179_beta

see pictures

• track overview - shown map only uses a small amount of screen,  a lot of area is used and wasted with information not that relevant to me
• point, red marker - no action when clicking on it, centering to point not working
• LoPoints. When enabled also other symbols are shown. I guess their of 'other poi', though them are disabled in this menu

New LoPoint
Well, though it makes sense to optimize data generation, workflow and handling to optimize resources, the profit for the user is more or less low.
The GUI enhancements are a good start and a general rework was on the list for at least 1.5 years, maybe more, IIRC.

My concern is mostly data usability.
From my point of view the strength of Locus has always been community awareness and community support and the potential of integrating data of other community or enthusiast projects and open or free available sources like OAM, brouter, Sonny's DTM, themes etc.

As far as I remember the offline POIs had a huge community interest and some individuals managed it to reverse-engineer the used db-structure IIRC, with huge efforts, maybe it was also delivered at some strongly progressed point.

Will the new used db-structure be documentated and released to also be used by the Locus-community, to also integrate other POI-sources, adapted OAM-data or other future projects?

Hello,

I've discovered a problem with the route planner.
When I create and save a route, my route is saved with the date 1970-01-01T and the time 00:00Z, see attachment.
...
I don't know which version this is from. I just noticed today that I exported a GPX file and another app displayed it with the date 01/01/1970.

Mystical 1970-date.
Just search the forum for 1970
I temporarily struggled with it with LM 4.28 and some older db-entries.

I guess it's hardcoded somewhere in Locus-code and used as fallback-date by Menion at some function-calls. Or whatever. Obviously it also seems to be used for those waypoints-time-stamps during generation.

Yes, no-one needs those 1970-dates. Though it indicates some lack and outdated handling  

I was finally able to nail down the issue with center button only each 2nd time
LM 4.29.0 (and latest 4.28.x)

• only appears in center-lock-mode
• sliding out of center of last known position the center-state does not immediately change, still stays white inside like being on center
• 1st hit center only changes the button-state to no-white-fill, like it already should be
• 2nd hit center then moves to last-known-position
• without lock the state changes directly when sliding off-center, everything's fine there
• seems like some cycle-issue with center-state or missing check-state-call on center-button-event

I mostly have the lock on (with a 7 seconds window)

pic below: center in lock-mode (blue tag), being off center (last known position 6.7km away), button though tells on-center-state (white fill), obviously wrong

Falls wer noch nicht den Vortrag gesehen hat von Arndt Brenschede und Serge Bellina auf der FOSSGIS 2025 in Münster, die gerade stattfindet:
https://media.ccc.de/v/fossgis2025-57806-brouter-und-brouter-web-fur-anfanger-und-fortgeschrittene
oder Youtube.

Das Konzept und die Möglichkeiten mit den Tags ist echt spannend, die Implementierung hatte ich nicht mitbekommen da ich kaum die web-Variante nutze, tolle Idee und Ansatz, muss man mal sagen !

I also had to switch the browser into desktop-mode, then download via 3-dot-menu was possible.
Btw 4.28.3 is in release and 2025_02.

4.28.3:
Center-button still works only every 2nd time, GPS-off, center to last known location.

balloni55 meint diese hier:
siehe Bild

- kurzer Klick: ein Auswahlmenü erscheint
- langer Klick: Koordinaten werden in die Zwischenablage kopiert

So geht's einfach und schnell. Es geht auch über das Share-Menü, map cursor location, ist aber unnötig kompliziert.

from the GPS in history, no matter how old, it should center on it.

Today my LM tells me "Still waiting for accurate location". What is that history and can't you also try to get the last known position via Android Api?

I'm also thinking a quick and temporary position retrieval would be better here.

Here the new method only works from time to time.

Though last known location is given (of last GPS ON-event), with GPS OFF I often get 'still waiting for the accurate position' as orange popup and title bar shows 'Waiting for GPS', both makes no sense. After some time (20s) it works once (1x) as expected and centers to the last known location.

IMHO a waiting-state-message does not makes sense if GPS is actually off (intended by user), 'GPS is off' would fit, 'Waiting for GPS-fix' or 'Waiting for GPS acquiring accurate position' e.g. otherwise.

I prefer to get rid of this red gearwheel-sticker

OK, see pics, 4.28.0 still with 1970-date, but track-copy shows populating the db-cells only need yo be triggered.

I will identify those 18 tracks by 1970-date and edit and eg. set activity, this will trigger re-populating statistics (incl. evelation-profile), times etc. with 4.28.0 (incl. MyLibV2).

There we go.

reg. https://forum.locusmap.eu/index.php?topic=9137.120 #125:
see PM for db.
I had to use a db-Viewer to get a better idea of tracks.db and to understand your comment.
I assume tracks gained statistics and times firstly somewhere in mid 2016?
db-cells of earlier tracks are completely empty here.
Probably alternative values of track-points have been used so far to deal with given null-values, to not display nothing?

Would be OK to me if db gets reprocessed once to exchange such null-entries, as it might be with single track-modification.
At least RC2 (4.28.0.2_1166) showed different and strange values, 1970-dates, etc.


For nostalgic reasons I'll take some screenies of now (MyLibV1) and charge 4.28.0