Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - 0709

Pages: [1] 2 3 ... 12
Versions / Re: [APP] - version 3.29.+ ( 1. 2. 2018 )
« on: February 09, 2018, 16:56:56 »
V 3.29.2
How to simulate a gps movement by the central cursor  (gps off ) ? 
Reinstalled to V 3.29.1.

Navigation & Guidance / Re: Locus Navigation experimental
« on: February 09, 2018, 11:44:15 »
@Menion:  Long text <desc> example:
Navigation Display text in Locus map top bar: 
By: <cmt> and <desc>:  2x single line Top Bars
<cmt> content = street name
<desc> content = Very descriptive information by Menion

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum====

Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: January 28, 2018, 11:52:09 »
Thanks John. I do use alternative vector maps too but....
I think ;) in the Locus store: There should be an indication by a 'Vector" Icon into the map description.

Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: January 28, 2018, 11:14:07 »
Locus V3.28.1.10 Start up ok.
After news, I had I look at the new concept of Locus Store  :)
Q: How do I know (selecting so before download) what maps are Vector ones ?  (Lomaps are)

Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: January 27, 2018, 10:02:23 »
Locus maps has usually.

Troubles & Questions / Re: Constant Re-Calc during Navigation
« on: January 23, 2018, 11:58:19 »
The strict mode is failing completely in Locus version 3.28.1
Locus general advice: Do NOT set strict unless realy necessary.
In 99% of the use cases the flexibility of NON strict is preferred.
Strict in combination with NO recalculation only when driving VERY complex (MTB) circuit designs.
A few examples by the different settings using a previous Locus version here:

Troubles & Questions / Re: Constant Re-Calc during Navigation
« on: January 23, 2018, 09:38:19 »
Double help desk and forum. I tested by Locus Pro 3.27.1. No such issue.
Your  Locus version ?  Your nav settings + Advanced ?
In Locus version 3.28.1:  There is a malfunction using Strict !  (Do not use strict)

[DE] - deutschsprachiger Forumsbereich / Re: GPX Track umbenennen
« on: January 17, 2018, 21:05:11 »
Display is not the filename but by the internal gpx trackname.
Change -> see pdf

Change many gpx tracks ? 
Edit the internal gpx trackname BEFORE import into Locus.
Pc: Easy by gpx editor, or Notepad++  Android: By Quoda Code Editor  etc.

Navigation & Guidance / Re: Locus Navigation experimental
« on: January 17, 2018, 12:41:05 »
Compare Locus (direct) route(rte) with standard (compact) route(rte) & the track(trk)_wpt system in the attached pdf. In this pdf see the simple Locus (direct) route(rte) navigation system.
Page 1. By reading the text in the list , browse the individual points one by one see the instructions. Simple. No need to puzzle and find the correct belonging instructions as used by the track(trk) + wpt system as shown in page 3.

Elements gpx as used in the Locus experimental navigation example files.

Required Information:
<lat> Latitude of the routepoint.
<lon> Longitude of the routepoint.
Optional Position Information:
<ele> Elevation of the routepoint.
<time> Date_time of the routepoint.
Optional Description Information:
<name> GPS waypoint name of the routepoint. (Local language)
<cmt> GPS comment of the routepoint. (Local language ex: street name)
<desc> Descriptive description of the routepoint. (Local language ex: track grade, path, surface)
<sym> Routepoint symbol. (Always English text "required element in Locus". Contains Via or Navigation information)
<type> Type (category) of routepoint. (Via_Shape_Nav)

Navigation & Guidance / Re: Locus Navigation experimental
« on: January 11, 2018, 17:25:21 »
By PM I noticed there is still some misunderstanding by the Locus direct route(rte) file system.

rte represents route - an ordered list of WAYPOINTS representing a series of turn points LEADING to a destination. Also a gpx route(rte) file is able to describe a detailed pathshape as exactly as tracks do.

1. Standard (compact) route(rte) only contains the Via routepoints and the Shape routepoints.
Marked in the attached picture example by element <type>Via_Shape.

- When the precise path being taken to the destination(s) Via Points is not important.
The activated "mobile" router planner creates an onroad path to pass all Points in correct order.
2. Locus (direct) route(rte) also includes normal (no sym) routepoints and the Navigation rtept's.

- When it's PREFERED to travel on a very specific path to reach the desired destination(s).
By a mobile router recalculate may navigate by an alternative onroad path to a next Via Point.
- When it's NECESSARY to travel on a very specific (offroad) path to reach the desired destination(s).
By unactivated mobile (re)router strictly navigates to precisely follow the original pathdesign.

*** Locus route navigates at OFFROAD paths and thereby maintains the (re)routing function when driving "off path". ***

Navigation & Guidance / Re: Locus Navigation experimental
« on: December 31, 2017, 09:14:59 »
Tap individual rtept's for details in description and comment.
Question by Marius in helpdesk is to be able at planning by selecting individual rtept's "point details" or in the route graphics screen, find distance and +/- realistic travel time, so BEFORE operational start.
That #6 web example only offer you a 'standard' setting. The Locus track(route) coloriser already has a free to set personal operational %Slope range. According to the activity both %Slope range and according speed set (NEW) to be integrated into a single tool. By comparing real trackrecords (yours) the speed settings are to be 'trimmed' to a best time estimate performance pro activity.

Navigation & Guidance / Re: Locus Navigation experimental
« on: December 30, 2017, 18:00:57 »
@Marius.  This is open for discussion only. No idea launch in help desk !

- No need for timestamped rtpe's, but can be added optional to represent a certain 'speed'

By Direct Route(rte) navigation. - Timestamps can be added optional in total freedom.
Flexible timestamped rtept's without worry to damage the navigation strictness

At Planning !
Router adds timestamps according to +/- realistic speed expectations.
Set your personal avg speed, visualised in the Locus % Slope trackcolor legend.
Speed is variable within the % Slope zones by using the gpx <ele> data.
Dark Blue_36kmh - Green_16kmh - Red/brown_3.2 kmh (off bike).
Use case: In "statistic" route detail find the expected travel time between selected rtept's.

Update: The principle does work...had a quick test by website generator:
- Consider Elevation in Calculating Speed !  See the attached gpx route(rte) file.

Die ahumm...actuelle en_sample_v4.tts Locus file hat schon der indication "version": 6
TTS files sind benötigt wann man sich etwas compactere anweisungen wunscht.
Am besten bearbeitet ihre persönliche (compact) version mittels (pc) Notepad ++.
Lade die actuelle "en.sample_v6.tts" file und eine (der) copie zum editieren !
Vergleich der neu_edit (ganz kritisch) mittels plugin compare tool in Notepadd ++
"Stempeln" sie ihre bearbeite version zum sprachtest am anfang der navigation.
"Stempel": "tts_set": "Sprachausgabe version 6.0709 erfolgreich geladen.",

Files in attachment: (heute editiert, nur kurztest am sofa)

Der [DE] compact version ist nicht fertig ! (Freiwilliger meldet sich)

- Umbennnen in en.tts // de.tts und kopieren in der Locus TTS ordner.
- Sichern sie der alte xx.tts wann der neue version nicht gefält oder nicht functioniert (test).

Nach kopieren in der Locus TTS ordner ! Mach ein anfangs hörtest der bearbeite version
Acitvier der hörtest durch neu selection der stimme in Navigation !
Man bekommt die sprachanweisungstempel version 6.0709. = OK.

Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: December 23, 2017, 18:51:53 »
V 3.28.1.  Tested...
See more strange new problems...trouble list becomes too long.
Advise return to previous nav system. (I reinstalled to old Pro V 3.27.1)

Pages: [1] 2 3 ... 12