Topics

[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)

The Locus gpx (rte)route export.

Can it be offered in a more valuable way ?
Optimise by exporting as standard compact route.
Contains only start & shaping & Via and Finish as route points.

Picture. Locus navtrack. The coloured sections exported as the routepoints.

gpx file in the attachment. (Track + route)

Video: https://youtu.be/blarVfTsFIo

Notice the fast Mapsource route calculation.
Compare with the reference track overlay.

[Locus_app_BRouter]

Hi Menion.

The trackglitch indicator by the Locus_app_BRouter (offline) planner is sure very usefull
The indication is by a red circle "alert" indication at the end of the relevant (short) trackglitch section.
But when using the Locus_GH online router some trackglitches are surprisingly not indicated.

It seems GH generates a simplified track so there is not always that expected perfect 180° overlap track backfold. But as GH produces the U-turn commands in the export file by the -98 sign such should trigger a Locus  U-turn command by rtePointAction>12 or <sym>U-turn.

By actual Locus planner if no perfect 180° track backfolds means no visual red alert !

Suggestion.
Keep the usefull trackfold track line indication as is now.
Put the visual red circle alert onto those Shaping Points that do trigger.
- Or trackglitches by perfect 180° track back folds as detected by Locus_BRouter
- Or the unexpected U-turn instruction commands produced by GraphHopper.

This indication should do the job this for both routers GH and BRouter.
As only repositioning of the corresponding Planner Point solves a trackglitch issue. 
Reposition the Planner Points until the red circle alarm is gone = trackglitch gone.

U-turns both the unwanted and desired ones are triggered by either a Shaping or a Via Planner point.
If you need to correct U-turns, you must therefore have both types of Planner Points available.
It is therefore important that both Planner Points types remain available at all times, even by file transfers.

Actual Locus Version.
Locus supports U-turns commands at import by the sym U-turn. 
Route You web generates U-turns commands by the sym U-turn. 
Locus_GraphHopper nor Locus_Brouter generates sym U-turn.

If there is U-turn support, you can still "accentuate" suspicious u-turn elements with a circle, also later in the normal map display used for navigation. The standard turns get the usual discrete "blue" small dot. And the U-turns get that extra "alert circle". In this case, they will not escape special attention so quickly.

Routeyou Planner.

https://www.routeyou.com/

The first planner that exports a gpx Locus navigation track by instructions in trackpoints.

Requires some getting used to, so it's best to practise a little ;-)

Older low quality Route You tracks (routes) are aligned to the road by autosnap to map technique, but such very often leads to track glitches and by that  very annoying false instructions and U-turns.

Advice.
Plan a new quality traject, so always position the planner points away from road crossings.
Save your design into Route You Web. At download select Locus gpx track.

[Operational !]

UPDATE ! Locus 3.50.1  Operational ! (Import)

Gpx track navigation.

Instructions in trackpoints trkpt.

Trackpoints that contain a compatible [EN]sym are promoted to navigation instruction points.
The promoted trackpoints that contain [EN]type Via are announced.
The promoted trackpoints that contain [EN]type Shaping are not announced.
Only the Turn and Via points lead to navigation alerts and give distance values @ navigation.

Advantages.

- Navigates 100% faithfull after gpx track import even without (routable) maps present in the app.
- Manage/separate the free located (poi) waypoints without any risk to damage the navigation.
- Easy import, navigate 100% faithfull without "must" set: "Merge waypoints with imported track".
- Less fragile than the trk navwpt method with the more vulnarable associated waypoints.
- Compact POI wpt_list not cluttered by many associated wpt's as by the trk navwpt method.
- Synced gpx files to pc offers extra edit tools or an alternative for only Locus edit.
- You can simply add multiple additional selected freely positioned wpt's(poi) into the gpx file.
- Timestamps are not obligatory but recommanded and attached according to expected speed
- A single gpx file can also contain multiple navigation tracks including turn-by-turn instructions. 
  Contains the original plus several free to select alternative navigation tracks to choose from.

The Via trackpoints by the <sym>pass_place <type>Via can have a <name>text to be announced by TTS.

@ gpx IMPORT.
Locus map app. (V3.62.1)
Turn instructions by trkpt <sym>(turn) & Via Points by the trkpt <sym>pass_place
A <sym>pass_place <type>Shaping trackpoint is considered to be a "Silent Via Point"
Roundabout support.
A <sym>turn plus <type> Shaping or Via in the same trackpoint is NOT supported.

Cruiser app. (V3.0.0)  https://wiki.openstreetmap.org/wiki/Cruiser
Turn instructions by trkpt <sym>(turn) & Via Points by trkpt <sym>pass_place and <type>shaping or via.
Shaping & Via Point transfers by point <type> in gpx (trk)track (trkpt) and (rte)route (rtept) or wpt.
A <sym>turn plus <type>Shaping or Via in the same track point is supported.
Straight line route planner support by the segment target trkpt <src>beeline and the BRouter app.
  https://groups.google.com/g/cruiser-users/c/zvjvDrntLj8/m/8KhFB8ZBCAAJ[/i]
Roundabout support.
   

@ gpx EXPORT.
Locus map app.
Export is not supported


Cruiser app. (V3.0.0)  https://wiki.openstreetmap.org/wiki/Cruiser
Shaping & Via Point transfers by point <type> in gpx (trk)track (trkpt) and (rte)route (rtept) or wpt.
Turn instructions by trkpt <sym>(turn) & Via Points by trkpt <sym>pass_place and <type>shaping or via.
Via and Shaping by type are 100% supported: By trkpt <type>Shaping is a non announced planner point.
U-turn & Shaping or Via Point at the same track point position is supported.
Straight line route planner support by the segment target trkpt <src>beeline and the BRouter app.
  https://groups.google.com/g/cruiser-users/c/zvjvDrntLj8/m/8KhFB8ZBCAAJ[/i] 
Trackpoint timestamps according to the transportation mode selection are attached.
Roundabout support.

No .tcx file Import. Export .tcx file. Not compatible with Garmin Gps.