Messages

Hmm, I've just created and published the new Beta version, but this, already fixed, is not yet there.

So next beta is during the week ... I'm also curious

[@luce]

@luce
Improved sharing & generally better work with points & tracks at once ... this is something we started work on last year, also because of the new iOS version. Not sure if results will be available this year on Android, but for sure next year and it will be a really nice big change ... you will see 

@Mick FU
settings of paired sensors are already backed in the "Backup of settings". There is most probably the problem in restoration, that the app may not always correctly detect sensors under the old known "ID". So it is harder to solve.

@Tapio
long click to delete attachments does not work? Anyway, there is no way to exclude links automatically. You may edit GPX manually ...

@CabrioTourer
Navigation commands > should be hidden. If they aren't it usually means, that for some reason, the connection between the track and these waypoints breaks and they are no longer considered as navigation points, but ordinary waypoints. ... ah, seems you find this. The question is why and how this happened.

So update ...

The "text-align" parameter is not necessary as it is already included in the "position" parameter. There is just a small issue that was just fixed and if confirmed, will be in the next version as well.

How "position" works together with wrapping may be visible in the new pull-request here.

Ah got it. Problematic wrapping in the latest app version was found & fixed, thanks!

The setup of the guidance line is in the app settings > Guidance > Appearance ...

[@Michael Bechtold]

Thanks for the route. It was a different one in the first post.

Anyway even here is also a clearly visible problem, so thanks. I think I've found one obvious problem (with the incorrect sum of the used distance for computing of the slope) and after the fix, I have these results (screen).

And now tell me ... is it wrong? Because here are the changes registered by the algo:

addElevationToStats, distance: 858.5077, elevation: 5.119999237060547
addElevationToStats, distance: 588.86194, elevation: -5.02999969482422
addElevationToStats, distance: 1270.1581, elevation: 5.179999084472655
addElevationToStats, distance: 411.74136, elevation: 5.209998779296875

It simply displays that after the first 858m, elevation change was finally above +-5m, then -5m after another 588m, etc. In the end, changes are so small, that distance up/down are simply = 0m! And I think it is correct.

App requires at least 2% slope change to be registered for up/down distance. So at least 2 metres change per 100m!

@Michael Bechtold
and here is the problem. I really do not want to have this parameter customizable. The main reason is to have exactly the same algorithm (results) on all three platforms. So track re-computed on the web after sync should be able to get identical results (that does not happen now).

@lor74cas
thanks. But it was worst before I believe  . You may also find apps that will have a higher values...

The difference 14% is not bad. Anyway best is to get better results of altitude values instead of tuning algorithm that filter these values. So suggest checking the "replace of SRTM data" or "Pressure sensor" values in the Altitude manager.

Hi guys, nice bunch of ideas, thanks. So when I noted and analyzed all, seems that we have here four major categories

• better work with online/offline LoPoints
• robust search system
• dashboard improvements
• geocaching features

Where
2. search system is currently (already for a few months) in massive rework. During the next week or two will be in Beta a completely new online search. More about it later ...

LoPoints & Dashboard are very high on my priority list, so definitely something I would like to work on this year.

And geocaching ... good question. Will have to think a little more.

---

Other smaller tasks
- backup system: agree, I'll look at it soon
- 3D maps: huge amount of work that still does not worth it I believe
- recording statistics: I would love to see them too, but we are not the majority
- live tracking: I know, sorry @joeloc. This has to start with a rework of our old server and uniting it to a new web.locusmap.app site. I'll try to push it a little more.

Yes, engines for LoMaps and OAM will be the same. And current Locus Map has already a highly enhanced MapsForge library version. I'll inform @voldapet about this, because we were playing with word wrap and ...

I'm not much skilled with tasker (unfortunately), but a simple task I made to execute quick bookmark, seems to work as expected, interesting. Do you think there are exact steps I may try to simulate this issue?

Hello,
in the Mobac should be a so-called "RMaps SQLite" format, so this is the best you may use.

And MapsForge maps, right this is a base app format, perfect.

Hi guys.
Again big help with work on this new version. Not everything is probably final. Field test may reveal some remaining problems in the new compute of elevation values + prepared support for new V4 LoMaps...

The last few weeks were not too productive in the "Locus for Android" world. I've promised to prepare support for DXF to Locus GIS for Petr and in the end, I've spent almost three weeks on preparing the GDAL library, uff. Most work is finally done so time to spend more time with Locus Map, finally .

We have of course some plans and things that need to be done, but still ... simple question (that may influence my personal preferences). What is the biggest pain/requirement you mostly have with the app, I should solve during the next cca 3-9 months? I have in mind a few main categories:

- backup system (united small and full backup & allow to set personal preferences what to backup)
- improve dashboard (missing items, simplify edit, improve charts, ...)
- management of the track waypoints (old topic)
- missing geocaching features (long list of missing features starting by live-map, mass edit & upload of notes etc)

Anything else serious?

Hi, ah I see. It is a problem on our server that does not send Gold subs item in case, user does not have enough LoCoins, we will fix it, thanks.

The system of backups needs to recreate. I wrote about it a few days ago (again). So use it as is. I need to find a time (week or rather too) and unite "settings" + "full" backups into a single system with options ...

Hi Viajero,
yes, this is a little bit different feature. In the side "Map content" panel, tap on the "Geotagged photos" text, not the icon. Here you get a list of places in the device, where Locus Map search for photos and displays them on the map. By default, it should be only from the DCIM directory so it should be your personal local photos.

Photos you attach to LoPoints (thanks for this!) are stored in the Pictures\Locus Map\LoPoints\ directory so feel free to add this directory to "Geotagged photos" if interested.

The best method to check your own LoPoints photos and their statistics is in your profile (Main menu > top profile button) > My LoPoint photos.

Simply "Main menu button" is ok

@svartbjorn sure I remember. Welcome back  .
And amazing ... thanks. I'll probably never be satisfied so can't fully agree, but yes, some nice features are there compare to Classic and some are in preparation (for example now we are finishing completely new search system, uff)