Phone performance problem during Locus Navigation
See observations here:
Phone performance problems during Navigation, using direct generated Locus Navigation.
Turnpoints are determined by looking over a certain track distance and NOT by one individual point angle of the original track. An new artificial track with a lot of extra trackpoints is created to help for the aritmics.
However it also seems that this same artificial track inclusive the turnindications is in use during real Navigation instead of using the original much smaller track. Is it not possible to "plant" the generated turnindications onto that original (small) track, to the nearest original trackpoints ? Keeping the unchanged original track, only add the turnpoints information (Coursepoints/ .tcx). Delete that artificial track when the turnindications aritmics job is done and finished. This should result in a much more responsive smooth phone Navigation experience. Without a phone continuously struggling with that very BIG artificial track with a lot (too many) trackpoints during real track driving.
0709 – Willy.