Automatic display activation = guiding with display and sounds

Christian shared this idea 4 years ago
In Progress

The discussion is already here. Thanx to @jusc for opening.

My expectation were always that Locus turn on the display on junctions or crosssroads even when guiding (not navigating) along existing tracks. But it doesn't :(

So the new request is:


: Locus should compute navigational orders as sounds along the track but w/o the common used signs displayed for left or right, w/o any voice guiding

: Locus should activate the display when a turn / junction / crossroad is ahead (if notifications are enabled) to give the user (biker) a short hint where to go = hand free = matter of safety

: adding manual turn instructions should not be necessary

: different sounds should be generated for "left", "right" and "attention" (if a situation is not clear). Suggestion for sounds are either using international morse code or arbritrary sounds choosen by the user

: Alerts for "away from track" and POI notification are unaffected

: the track should keep the color and line style of the folder where the track is called from

: The arrow line to the next trackpoint should be kept 'cause its very helpful

: Filter like in navigation (hight, medium, low) shoud be kept also.

: The battery consumtion should be similar to pure guiding plus the additional time when the display is on (automatic dimming can switch of the display again).


This feature gives a minimum information about the further way to go with a maximum on battery saving and safety while biking or hiking.


Would be nice to have a lot of votes for these feature request.

Christian

Comments (10)

photo
1

Waypoint Snapper.

All (free) Waypoints along track in 6 m corridor are snapped, and listed in correct trackdistance order, then used for Navi guiding during track drive.

Waypoint Snap on track action.

Waypoints along track in 6 m corridor should be "snapped ontrack" when exporting to a new trackfile with merged way(course)points.

photo
1

Some of the ideas published in the forum to generate L/R Morse signals where never published in this help desk because far too complicated to realise.


Lets hope that this proposal is a better solution, by using a "fixed" Locus .tcx solution. In A next Locus version ?


Using the .tcx file format possibilities as explained in the attachment. Alternatively even .gpx files format could be used. But thats for later.


The notify arbitrary sound alert should work independently from the used local language. The TTS sound (and eventual visual text notify) alert should be available in the used local language.


Pse. See the .pdf attachment.

photo
1

+1 would be great

photo
1

If I corrently understand ... ehm. Implemented ;).


I'll be waiting for feedback after some field tests with new Beta version (planned on tomorrow 26. March).

photo
1

Awesome, thanks Menion! :)


Is there a changelog, or can we try the Beta somehow?

photo
1

new Beta version (planned on tomorrow 26. March).


https://plus.google.com/communities/105669867009952671671

photo
1

Thanks!

photo
photo
1

This must be heaven! Thanx menion! Looking forward to new version...


(I'm not able to leave a comment here with smartphone due to strange design for mobiles :( )

photo
1

ok, guidance with automatic display activation is implemented. Great!

But the thread should not marked as 'completed' because sound and track styles are missed.