Messages

Locus Map will be published next week. The beta version (link in my signature) is already available for testing.

Locus Classic won't receive this change, because since the end of 2023, it is only in maintenance mode and won't receive any bigger updates anymore, only critical bug-fixes.

[MapGooglePlay_4.21.1.5 RC_1125_beta]

General notes
There are more modifications, mainly to keep the bottom panel hidden when re-routing or restoring the previous plan. "Inverse route" added into menu + bunch of other various improvements. Thanks a lot for your opinions!

Beta version MapGooglePlay_4.21.1.5 RC_1125_beta published!

@Agus
thanks for pointing to the missing times when using BRouter. The issue was that BRouter used the old system over GPX files. I've changed it to use an identical system to the internal LoRouter. Even way types & surfaces are visible now 

@Graf Geo
Problematic red warning circles > firstly, thanks for sharing the track, it helped. I've made some changes to prevent this issue. Anyway, I'm curious if you did anything special when you planned this track. Because it has on almost every segment (between two shaping points) duplicate points at the start and at the end, that caused this issue. Can't imagine how this happened. You wrote you've used an online Route planner right?

Missing error messages > thanks a lot. It was not an intent. Fixed.

Error 10103 > this is weird because it means a problem with the internet connection. This should not happen here. I've not seen this before, so hard to help here. Are you sure you used offline! LoRouter? Even in the case of online, this does not make sense...

@freischneider
sorry, but your description is too complicated for me. Should be possible to record a short video with this issue? And agree, some generated instructions between manual segments, hmm should be doable.

Hello Jonny,
all ideas related to the Wear, post please on our help desk: https://help.locusmap.eu/topics/idea/status/all/category/20/sort/popular/page/1

Btw. "compass" is already there.

Hi, in the next Locus Map 4 version, "Android/media" as a root folder will be supported.

1 out of 2 times? Any problem I may be able to simulate?

Measuring between two points > for this exists the so-called "Analyzer". Tap on the track > three-dot menu > Tools > Analyzer.

I'll discuss most of the feedback with Marek tomorrow, but just a few cents ...

Purpose of

"Navigate to" - is to start navigation from the current location to the selected target quickly. So the start is always GPS and the target is the selected point. When using the "Navigate to" function, search is the most logical step from my point of view. If you want to use the screen center - long click on the screen center > bottom panel Navigate to!

"Route planner" - is to start a blank planner where you may start and save your trip from scratch. There is also a shortcut from the detail of point (or again long-click anywhere on the map) > Plan route to. This does not automatically turn on GPS and only sets a point as a target, nothing more.

Is the difference clear? In our team were votes for merging both start-methods into one, but I consider both as specific use-cases that should remain separated.

[@Agus]

Thanks guys for the nice feedback!

General notes to Route planner

Expected requirement: do not force to use the bottom panel and keep it hidden. It is easy to hide it now, but I'll think about better support for this.

@Agus
missing estimates with BRouter > values very valid for you? This was changed because of this. Do you have enabled "Include navigation points"?

@Tapio
Choose location > under this menu is quite a lot of options, so I would rather stick with the united system across the app. Anyway, what is unexpected on the "Navigate to" call?

@Graf Geo
"Collapse" in all menus > you are good you've found it at all . We do not know where to place it for now. To all items? Eh, no, please. But a better place is needed for sure.

Red warning circles > may you please share this track with me over Share > Share URL link? Thanks

Warning message on unsaved route > from my point of view, this is correct behavior. You opened the planner to re-plan some track, but closed it without saving. So track-in-progress is still there.

Limit visible content in the "Altitude tab" > I'll consider the option. The best should be if the drag of the bottom panel will be to a user-defined height or at least two defined steps.

@T-mo
1. overview of the copy > hmm, this is already partially rewritten in new planned data manager, so let's hope 

2. 80+ waypoints on the map > and do you need to display these navigation points at all? It may be globally disabled in the settings > tracks > Show navigation commands on the map

3. collapse/expand > above in @Graf Geo

4. used profile > currently it is united behavior - the app always uses the currently selected profile. This may be changed, but I need to think more about it. It then should change also adding new intermediate points, dragging the middle red point etc.

5. reverse list button > planned, but currently same problem as with collapse/expand. Where to place it? 

6. content of point detail > individual preference. I believe the dialog may be done better, but I consider the current content as a good compromise for all.

7. interesting idea > I'll discuss it with Marek

Hi,

nice tool!

Missing features:

1. POIs along the track > it is missing, fully agree. Plans? Not for now in my head.

2. distance along the route > during the navigation, tap on the route and in the route detail screen, tap on the first bottom icon. There you get all necessary information.

Hallo Axel, mir ist nicht ganz klar, wo das "Problem" liegt.
In beiden Fällen > siehst du diese Werte direkt in der Locus Map? Ich vermute, dass das Problem nicht im Export zu Strava liegt, sondern in der einfachen Tatsache, > dass Locus Map andere Werte berechnet als Strava. Liege ich da richtig?

Leistungswert: stammen diese Werte vom angeschlossenen Leistungsmesser? Wenn ja, sehen Sie dann korrekte Werte im Sensoren-Manager oder im Dashboard?

Original

Hello Axel,
I do not perfectly see, where the "problem" is.
In both cases > do you see these values directly in the Locus Map? I expect that the problem is not in the export to the Strava, but in the simple fact > that Locus Map computes different values than Strava. Am I correct?

Power value: these values comes from connected Power meter? If so, do you see a correct values in the Sensors manager or dashboard?

Díky za test, no to je ale opravdu divné ...

Pokud by ti nevadilo experimentovat a věnovat tomu chvilku, pak bych potřeboval
- nainstalovat Beta poslední Beta verzi (link v mém podpisu)
- po spuštění dlouhý stisk na hlavní menu > Setup logging > zapnout "Log to file" a "Sensors (V2)"
- pak zkusit nasimulovat problém
- a až se zadaří, ukončit Locus (dvojí klik zpět v mapové obrazovce)

No a teď se jen dostat k souboru uloženému v pod-adresáři "logs" aplikace a poslat mi ho (buď zpráva tady na fóru, nebo locus.map@asamm.com. Děkuju

[MapGooglePlay_4.21.1.4_1125_beta]

New version MapGooglePlay_4.21.1.4_1125_beta published!

@balloni55
hmm 8 minutes. Probably a high number of files in the geocaching directory? I'll look at the option to display at least some progress... (or better speed it up).

Hi Lupin,
I was not thinking about bigger support for fully flexible parameters yet. We are still fighting a little with full compatibility with custom profiles for BRouter itself (not everything is working now) + just now creating flexible server-side configuration so all our platforms will behave identically with every change on the server.

I'm also not satisfied with how parameters are set in the BRF files, so most probably there will always be a list of supported parameters like now (only extended).

So sorry, for now, there are no bigger plans in this area regards full customization by profile creators.

[Translation]

Hi guys, this is something that may be improved, but it is not so easy. Over time, I've created two separate packs of cursors. One for ordinary map screen and one for navigation. It may make sense to unite them, but because of existing packs and backward compatibility, it is not so easy. Just info ...

Translation
Hallo Leute, dies ist etwas, das verbessert werden kann, aber es ist nicht so einfach. Im Laufe der Zeit habe ich zwei separate Cursor-Pakete erstellt. Eines für den normalen Kartenbildschirm und eines für die Navigation. Es könnte sinnvoll sein, sie zu vereinen, aber wegen der bestehenden Pakete und der Abwärtskompatibilität ist es nicht so einfach. Nur zur Info ...

@Andrew Heard
Interesting :/
Check please next Beta version with planner, where we did some smaller changes in the bottom pannels. Thanks

[@Andrew Heard]

Hi guys,
thanks for the valuable feedback!

Global problems reported here regard planner improvements
- click on items: now it will open a point detail. It center map + is easy to change it (via, shaping, coordinates, ...)

- incorrectly working "Navigate to"

- easy recalculating of sections > similar to the web, is not implemented yet. The main reason is that the clickable area is on the device too small, so it will be necessary to make the space between points bigger. I'm not sure about it for now.

- graphical issues with system status and navigation bars should be improved

- and many other improvements. Beta version today a little later...

I'll not comment on everything, cause you will see it in tomorrow's version.

---

@Andrew Heard
Arrow at chart panel > hmm, yes, it should be consistent. Adding to todo, thanks.

Problem with hidding of the panel > thanks for the video. Hope, that the updated version will solve this (we updated the Google library that takes care of it).

Archived topic > there is some automation, that closes topics after 12 months of in-activity. This helps to make it clear and forces users not to re-use older topics when asking something. I've un-archived the mentioned topic. Sad news, I know ...

@michaelbechtold
sync problem > and does it change anything? You may check Sync screen > toolbar > "Last update" to see if something changed.

@balloni55
maybe it just took very long? Give it a few minutes, please. Maybe some procentual progress should be useful here right? Hmm ..

@T-mo
search suggestion, thanks, forwarded to @marek