Messages

[You must than close Locus, wait a while]

reproducible report ?

After several new attempts. I suspect the problem was the following.
I tested v 4.29 to see if import in the database is now possible. Unfortunately no
Quickly switching to import as display only than showed this was no longer possible.
You must than close Locus, wait a while and only then import back as display only.
Then the icons import turns out to work still fine inclusive all images are shown.
The gpx viewer app anyway struggles a bit less and imports this without trouble.

Update.
What imports fine in the database is a combination of a (nav)track plus (merged) "any icon" waypoints.👍

In the version 4.28 the file .gpz shows the icons when set display only.
In the version 4.29 the file .gpz does not show the icons anymore.
No icons nor by set display only nor by database import.
The file .kmz shows the icons by set display only.
The file .kmz shows the icons by database import.

Update.
After more attempts and emptying the points folder.
It sometimes seems to work with gpz import display only.
It is rather fickle, sometimes it doesn't work.
No idea why sometimes it works or why sometimes it doesn't.
The icons are never shown with database import.
The imports via kmz are always very correct

Perhaps a forum member could test this and find a pattern to add a reproducible report ?

Strange and unfortunate . Given there is no further support for Locus Classic so I guess end of story from A14+.

On A13.
Map the external profile to some internal.
Eventually rename the in-app profile.
Ref: https://help.locusmap.eu/topic/32067-locus-3-brouter-custom-profile

I still barely use the Locus Pro planner.
I have now done a quick test on an A13 phone.
Add the external profile Zossebart MTB as indicated.

Then in the Brouter advanced panel
Add custom profile named (free name) "MTB Zossebart".
Choose and select in external Profiles - Zossebart MTB
I only than activated the profile MTB Zossebart.
Thus only 2 route planner profiles are shown.
Or Set Draw manually or MTB Zossebart.
I had a short test. Seem to work fine in the planner.

[new window 2]

A13.
Eventually the next file explorer can help.
https://play.google.com/store/apps/details?id=com.marc.files

By this file explorer find Locus pro in Android data.
If not existing create the folders router > profiles2

Android > data > menion.android.locus.pro > files > router > profiles2.

In this file explorer by the 3 dot menu select new window 2
In Android menu than select split screen operation.
Open than both the explorer window 1 and window 2.
In the first window 1 find your prefered xxx .brf file.
In the second window 2 open the (empty) profiles2 folder.
Drag the xxx.brf file from window 1 into to the window 2 profiles2 folder location.

On A14 + ?  Please report succes or not.

See gif

Android 10 ;-)

[Update: After several more tests.]

Any idea ?
The opacity is not applied in Locus v3 and v4;
While the width is applied in Locus v3 and v4.

Test file 1 import by topografix > Garmin extension NOK
(The opacity is OK in gps visualizer and in gpx-studio)
Note.
If Garmin is first than topografix the opacity is applied.

Testfile 2 import by topografix > OsmAnd extension OK.
Note.
If OsmAnd is first than topografix color is not imported in OsmAnd.

Update: After several more tests.

The extension order finally turns out to be very IMPORTANT !
See the attached file 3
Contains extensions Garmin > Topografix > xsi (Osmand reads this)
This extension order should be EXACTLY respected.

Result.
Garmin by garmin.
Track: color.

Locus 4.27 by topografix.
Track: color + opacity + width.
+ TBT guiding through the gpx navtrack !

Osmand 4.9.10 by xsi.
Track: transparancy-color + width.
Waypoint icon: transparancy-color.

for others, i struggled a long time to import "my_icon.zip"

Should sure be better documented and or indicated as hardly anyone will be able or detect how to export and import icon packages this way.

A compact gpx route import is possibly fast but after that the slower processing has yet to begin. The app router has to calculate a track to follow and that is an intense process that can take quite a long time and of which you also have to wait and see the result whether you like it or not. Contrary if you import a TBT navigation track, all the necessary is already there. Import press start and go.

Advantages ? None.

Locus simply replaces all (trkpt)trackpoints with (rtept)routepoints.
The export so contains a "direct" gpx route which hardly anyone uses.

When reimporting into Locus, it has serious disadvantages.
As Locus then converts every route point into a waypoint.
This has no added value but mainly pollutes the display.
The app becomes agonizingly slow or possibly crashes.

A rte (route) should only contain the via and shaping routepoints.
Through these route points the route planner can so recalculate.
The chance that the result is different from original is quite high.
Using routes is like a game of chance it often does not result in what you expect.

[does NOT exploit the IconStyle]

Useful and nice icon packs are available for Locus.

Some contain the identical base icon in color variants.
A fine pack from the Locus store is the NPS b/w icon pack.
Adding color variants in this rather large pack is unattractive.

Anyway you can apply heading scale and color by the kml IconStyle.
Such imports gives a fine result in both Google Earth and Locus map.
Notice a single white icon dot so allows to represent wpt's in any color.

- Current Locus does NOT exploit the IconStyle for compiling waypoint icons and the associated kmz exports!
- IconStyle applied in a simple offline klm file can usefully color an app default simple white dot waypoint icon.
A simple test kml file with IconStyle color is attached.
Import into Google Earth.
- Since the GE default pushpin body is yellow, unfortunately you can only combine red and green.
- Only the white needle of that default GE yellow pushpin allows itself to be correctly colored in blue.

Find In attachment zip.

- A kmz file shows what is possible with a b/w icon from the NPS pack.
- A gpz file shows what is currently possible with the same NPS b/w icon.
 
Import into Locus 4.26+, set display only, and compare both results.
Import by kmz or gpz does not require the receiver to provide an icon pack.

Notice the nice usefull kmz extra by applying the kml IconStyle.
This extra can be done without extending the b/w icon pack.

- Also through gpz transfer any icon and additonally transfer attachments plus TBT navigation track instructions.
- The gpx standard does not offer IconStyle but an extension imitating the kml_kmz IconStyle should do the trick.
This unique combination can be realized quite easily with Locus, but is not exploited due to lack of awareness.

A small test pack of icons asking to be colored is included.
This "white" pack contains mainly icons provided by slarti76.

Translated with DeepL.com (free version)

As above with a text editor.

I suppose the intention is to just add a via point for the announcement @ navigation this without triggering a recalculation ?
Once in a very distant Locus past you could easily create this with the track editor. With current versions you can't do this anymore I don't think anyway.
Since I hardly still use the Locus route planner anymore because of an easier alternative, I may not have noticed another Locus map possibility yet.

By means of Notepad++, you can promote EVERY track point (if you know exactly which one) into a via track point.
You edit the corresponding track point (no typo..track point) and then add a sym with pass_place text.  Done.
If you want a custom announcement you can also add a name tag text in that same track point without any problem.
After the track import Locus will recognize all this as a via track point and announce it in the navigation as well.

However, I suspect that almost nobody will want to do that very cumbersome detour via Notepad++.

Translated with DeepL.com (free version)

You added an ordinary waypoint this way, not a navigation via(way)point. What you need is a via(way)point which you create using the route planner.

The file contains a gpx (trk) track with 7 track points.
Apparently a gpx (rte) route_routepoints is expected.
Locus web does not offer gpx (rte) route exports.
So import this simple track in the Locus map app
In Locus map app export select as gpx rte route.
After re-import Locus sees route points as via's.

Btw.
Performant handling of gpx files is as described here.
https://www.zumouserforums.co.uk/viewtopic.php?p=21758&sid=e151cc3b27c63ffd441f30761d526154#p21758
Few apps (inc Locus) offer this so performantly but anyway still simple.
I know of one, but advertising in the Locus forum is delicate isn't it ?