Messages

[Beta version 4.15.2.4]

So the new Beta version 4.15.2.4 was published.

I was quite sure, that it will already contain a new search system, but we are trying to make it perfect even for the Beta version, so a few more days are necessary. At least an improved Backup manager as @freischneider already noticed and few more tweaks.

@Tapio
are there any exact steps that cause this issue? Even on your side?

Most recent OAM Germany map vs. LM4 beta - anyone else?

I downloaded Germany-North 04.04.2023 today, zip, v5, and it's working fine with Elevate and with newer LoMaps-MF-beta-theme and VoluntaryUK-MF-beta-theme.
Haven't checked any map-feature though. Citynames and name-priority are somewhat different between themes.
All these different numbers are irritating, V4 here,V5 there, I suggest to call the new beta-themes simply MF-themes, as not being Locus-specific.

Hmm.. I think the LoMap approach to cycle/mtb routes is very different compared to OAM.

OAM seems to remap the cycle/mtb/hiking network values through to the highways they are related and uses separated tags for each type of route (network=cycle, mtnetwork=mtb and hknetwork=hiking).

OAM additionally resolves issues like route=mtb and network=ncn, by remapping these through to mtbnetwork=nmn. An example of this can be seen in the attached first pair of images showing LoMap/OAM with the latest v5 Voluntary theme, see how the mtb route is displayed in LoMap with blue/purple blobs but in OAM is only purple blobs.

I resolved this for now in LoMap maps by ignoring the network tag and using just the route=mtb/bicycle values to differentiate them. Separate rules are used for OAM and ignored by LoMap by checking for route="~", since OAM doesn't used route tags for network routes. See second pair of images comparing LoMap/OAM with my latest OS prototype theme.

LoMap having separated routes results in multiple renders for each route, advantage is ref labels for both routes, disadvantage is multiple highlight/emphasis drawn.
 
Another feature/issue... since LoMap is using separated route ways from the highways, I can't determine if a route is off-road. With OAM I am introducing hollow blobs when a route is off-road, see attached third pair of images.

Finally, I am missing OAM's feature to autogenerate route refs when a route has no ref tag, it does this by raking the first letter if each word in the routes name and any numbers, see examples attached and how OAM names the mtb route PWCR.

A beta version of the Voluntary and Velocity themes to work with both this Locus beta app & maps and OAM maps is now available at:
https://voluntary.nichesite.org/beta.html


The new versions are named Voluntary V5 LE and Velocity V5 LE (Locus Edition)

Right. We've tested it quickly with Petr and had positive results.

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.

OAM does suffer from the effect. Screenshot is Germany/NRW OAM with VolUK theme.

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:

1) management of the track waypoints (not surprisingly my favorite
2) improve dashboard (missing items, simplify edit, improve charts, ...)
I would add
3) rotating labels in vector maps (or, rather, make labels non-rotating in relation to the (rotating) map. That's the main area where Locus just looks so much worse than other concurrent map apps - and of course it's not just looks when actually navigating...
4) better overlay handling, e.g. with overlay presets. For example, I have overlays with hike routes, skiing routes, public transportation stops, all are best at different alpha values, changing between them is such a pain that I usually don't use the feature, even though it's quite good in principle.

I know very unlikely but a 3D map view would be awesome

a can of worms. SCNR.

Have you tried 3D apps for terrain on a smartphone already? I did, after all wasn't fun to use. I doubt it's worth putting it into Locus.

Andrew raises a good point, being able to better judge the terrains elevation could be improved. The simple grey hill shading isn't helpful enough.

Currently the best way IMO is using colored elevation.

But.

a) This is too hidden in Locus
b) People won't have the necessary cpt files for data/interpolators. Too complicated.
c) It is in need of a better overlay algorithm. We discussed it. See screenshot.

Really useful for planning. I've attached files for 300-900m elevation, if anyone is interested.

I think, Locus could do much more here. The information that is in the cpt files is easy, can be algorithmically generated. It could all be done by Locus internally on the fly, so that on UI side it just offers an easy way to set the currently needed elevation. Like with a slider.
Or what if Locus had a quick toggle for 2-finger pinching? In one mode, zoom map, in the other mode, change base elevation in the colored elevation... Just ideas. Maybe I'm a bit optimistic, but if colored elevation is made easy and well promoted it could be a killer feature and all of you @ Asamm millionaires. Almost.

"Search for backup" > backup manager was moved into the Settings into the new category "Backup & filesystem".

@Menion - yes but doing a Find should match "backup" right?

& your thoughts on Cloud Sync with new device? I think displaying all new POI & tracks by default is problematic - could crash the app if too many things to display - happened to me twice - instead did a full backup from old device into new virtual machine then restore, instead of Cloud Sync

dashboard list: dot-dot-dot- menu for last dashboard is hidden behind "+" icon & there was no way to drag list up or down in order to show the menu
You cannot view this attachment.

initial Cloud Sync: I suggest that new points & tracks are not shown by default, because if there are lots of new points & tracks (generally the case when setting up a new device to sync to existing device), the device or virtual machine grinds to a halt/ runs out of memory
You cannot view this attachment.

Hi Menione. Backup files sent to the cloud are too big. The last one has over 0.5 GB. Most of the space is occupied by the track.db (800 MB) file. It is unnecessary to back up routes and points for the Gold version because they are stored in the Webplaner. Would it be too difficult to miss these files for Gold users from autonatic backups?

I still want to backup these files as a Gold user.

Hi Menione. Backup files sent to the cloud are too big. The last one has over 0.5 GB. Most of the space is occupied by the track.db (800 MB) file. It is unnecessary to back up routes and points for the Gold version because they are stored in the Webplaner. Would it be too difficult to miss these files for Gold users from autonatic backups?

I strongly oppose leaving out the *.db by default. As an option, ok, but in my view, this is an absolute necessity - you can never rely on online storage service, I want to be able to restore my database even when e.g. Locus Web is down.

Sorry guys, this is my personal mistake in the code. Will be fixed in the next app version during the next few days, sorry.

[Blog]

The last update (LM4) brought a change in the backup management. The backup zip files are now 4-5 times as large as before, which is due to the fact that now also the segments with the rd5 files are zipped.

User Niklas had already noted this in the Blog (entry 10.12.2022).

As a result, I now have backup files of about 1 GB in size, which significantly increases the upload time and unnecessarily takes up disk space. The rd5 segments do not need to be secured in my opinion.

I would therefore welcome to take them out of the backup again. If some users absolutely want to backup these segments as well, please do so as a selectable option.

Thanks.