Weird/broken waypoint names in FIT filesFORUMS HOME SEARCH FORUMS

Waypoint name limitation comes from a tcx to gpx conversion ?

1. In tcx max 10/15 (Name/Notes). Street name in Notes most favourable. Even then you have to cut sometimes.

2. In fit there is more Name margin. Notes there isn't. Both modes meant for Garmin navigation gps (+ apps).

3. In gpx trk with TBT wpt. (Locus navigation compatible).

Plotaroute gpx "services" also so the "non navigation" apps

As a result, rather is a somewhat "chaotic" gpx export.

And then something completely different.

Plotaroute does NOT generate !

Navigate by a gpx track by a simple, tight, yet complete mode.

4. In gpx trk with TBT trkpt. (Cruiser and Locus nav)

    (Loose (poi) wpt can be included in the same gpx file.) 

A gpx trk with regular and extended trkpt.

The extended trkpt contain extra gpx tags. 

name > optional @ Shaping or Via point.

cmt > street name.

desc > / (spare)

src > segment profile. (beeline)

link > /

sym > turninstruction. (Locus sym)

type > Shaping or Via point.

A gpx navtrack (motorbiking) example.

Compare navtrack vs track 

Unzip after download. 

Contains a navtrack + compare htm.

Import in 'standard' apps displays a normal track.

Import and enjoy TBT navigation in Cruiser & Locus.

That's a possibility Lasse but it may not suit everybody. At some point we plan to store street names separately so that we dont have this issue, then if a direction has been manually added we'll just use the first 14 characters instead.  

For GPX we understand that some devices reject files with names that are over 10 characters, hence the difference from FIT.

Aha, now I understand the logic, which is already helpful. I create my own waypoints, which usually are not just simple directions.

How about if the waypoint has a symbol set and not just a directional arrow, then instead of using the "on"-logic simply create the first 14 characters or so?

Speaking of waypoint names, I also noted that when downloading as a GPX file, the waypoint name is always the first 10 characters of the description. Any reason this could not also be 14 characters as with FIT?

Thanks for that feedback Lasse. That's not an easy one for us to solve unfortunately. The logic attmepts to find a street name in the description and looks for the text "on " when doing this. Normally the directions are something like "Turn left on West Street".

When downloading a route as FIT files, the names for some waypoints are generated from the description in a strange way, e.g. using only the last word or words from the middle of the description.

Something seems to confuse the truncation logic that generally works fine. Here are three examples of waypoint descriptions and the FIT file course point name generated:

• "Bridge underpass, then cross river on bridge" -> "bridge"
• "Cross river on bridge, then turn left and follow it on the trail" -> "bridge then t"
• "Left on trail" -> "trail"

To reproduce the issue, I took a random route I found on plotaroute and setup three waypoints with the descriptions. When downloading as FIT, the course point names are the strange ones I mentioned above: https://www.plotaroute.com/route/2101574?units=km