Messages

[Anyway]

Let's wait for the next version. I'll do a few more tweaks till then. I'm also just now doing some battery benchmarks to measure if this has a noticeable impact on the battery.

Anyway
- basic centering on the current position (so the movement of the map cursor & map every second) should work ok
- when the navigation is active, the cursor still jumps every second, but map is moving smoothly - this should be improved

Which item is it in the expert settings. Haven't found anything in a hurry ?

"Fluent movement" in the english translation.

[Locus Map (4)]

New Locus Map (4) version

Important links
- list of news of public versions
- Public versions
- Beta versions

Versions
27. 9. 2023 - Locus 4.19.0

Nono, I did not describe it perfectly.

The app always allows to continue in the previous recording, even after a day or more.

What happens if you reboot the device within 10 minutes is that recording should continue automatically without the need to start it manually in the app. Otherwise, you have to open the app, the side recording panel should open automatically and you have to press the "Start" button. That`s all. No data should be lost in any case!

V1.1 with Christian's Sep. 2023 OAM vector maps as background (ZL 8+) is online now as direct downloads and torrents.

[New Beta version 4.18.2.3]

New Beta version 4.18.2.3

We focused mainly on the "Warnings" & bug fixes.

So still a valid topic related to warnings - LoRouter customization & warnings.

More updates in the "Customization" system will be introduced during the next months, but not in the coming version.

Enjoy the weekend!

Hi luxacalor,

I guess you mean the the screenshots of my latest draft of the lomap/oam v4 map theme.

It is pretty close to release now, just working on the pdf legends and final few fixes to the theme.

I was going to update the v3 theme to match, but with the v4 lomaps out now and the difficulty of doing this with less tags available and lack of time on my part, I think I'll leave the v3 map theme stay unchanged.

There is one thing I can't get to work on my phone, using zipped themes. Should work as I have latest Locusmap and android 11...

Watch this space for the new release.

[Online/Offline Lopoi (Eye toggle) to Presets]

One of those ideas... 

Online/Offline Lopoi (Eye toggle) to Presets

Reason: Better working together of Locus with themes. How? Themes can come up with no POI icons at all. I meanwhile have such a Layer in Tapiola. So Locus can exclusively display POI. And it would be convenient to turn everything on via preset.

[@freischneider]

@freischneider
thanks! This is on @Radim V as he is behind the main logic here.

@balloni55 & @Andrew Heard
"Tools" menu should not be visible for online setup, removed, thanks.
And visible slider > it is currently only for "MTB profile". But seems you see other ("is wet") parameters, good, so it should work.

Sharing from G-Maps works perfectly with the new version. I tried it with different types of maps poi.
Thanks

[New Beta version 4.18.2.2]

New Beta version 4.18.2.2

Major new change - LoRouter customization & warnings

Enjoy the weekend!

The google maps point sharing "fix" now extracts the points name from the funny url and does a new Locus "search" for that. It's unfortunately almost as unusable as before. I now tried it 10 times in real world situations (still being on an endless bike journey). 3/10 times Locus didn't find the point (by name) at all. 5/10 times if "found" something completely different by the same or a similar name, sometimes 100km away. 2/10 times it found the right thing.

Verdict: still an almost complete failure. re-searching in that way is not an option. if you cannot extract proper coordinates from a funny url, we're f*cked forever.

Apparently this "workaround point sharing fix app" that people here talk about manages to do it fine though. Too bad it's no longer supported and doesn't install on current Androids without jumping through hoops :-)

Again that Google Maps sharing. Wait please for next release of the app, I believe it will have major impact on your experience in this. Marek and Menion are doing their magic tricks there now. Lets just hope Google don't change the things on their side soon again..

On other hand, all reports of bad experience while using our new online search are welcomed as we are able to separate/sort  them into technical aspects which we are planning to focus on. This give us better ability to determine whether our expected implementations will make significant change for you or not. Thanks.

v1.2.7

• Menu reorganisation
• POI are included in basic profile
• Hide (place:locality) if suburbs are hidden
• Color correction: primary_link, tertiary roads.
• Access restriction indicators on roads were missing, fixed.

Hello,

my interest is, to get a more precise GNSS position for the track recording as it is done by the usage of the mobile phone internal GNSS receiver. Background is, that during my hiking tour, specially in mountain, valley and forest regions, the tracking of the position and related altitude is not as precise as I want to have it. One good example is, if you are standing close to the edge of a deep hollow and the measuring point jumps between bottom and top, the result is a altitude calculation, which is far from real.

In a first step, I bought a GNSS receiver from Adrusimple, which allows together with an RTK helix antenna very precise measurements, if the programming is done well, which I worked out over several weeks. I'm using this equipment since month now and I'm really happy with the related results. But: The costs are really high, about 300€ and not really an option for maybe other interested user.

https://c.gmx.net/@324496113698608933/o7FrrIyoRO2bJBvz3TvjnQ

So in the second step, I tried to reduce the cost by using catalog single components and a cheaper U-Blox M9N GNSS chip. After a lot of testing and programming, the new receiver delivers nearly the same positioning quality as the former one. I will now do some further optimizations on the housing and tests in mountain regions. 
If you like, I will keep you informed and show some comparison measurements with simple mobile phone logging afterwards.

https://c.gmx.net/@324496113698608933/O2pO6Q3PSVKd8CJFrGcSpQ

https://c.gmx.net/@324496113698608933/SPFE4rx-TYOWzHWZ7A_C1Q

I'm looking forward to get some feedback from you side, if you have same experience and maybe interest to get further information details.

Cheers

Olaf