Waypoints - What is displayed?

[fazel]

@halajos Check this out…

Waypoints

During the navigation user is alerted when coming in close proximity of the waypoint. Normally being used to identify specific locations, crossroads, camping sites etc.

Waypoints are generated from:

• wpt -elements that have same coordinates as some rtept or trkpt -element.
• rtept and trkpt -elements that have name and/or type.

The data imported from above mentioned elements are:

• name
• type
• latitude
• longitude
• elevation

An unnamed waypoint is created if name is missing but a type exists.

A waypoint with type Waypoint is created if type is missing but a name exists.

The type of waypoint determines the icon shown in Suunto watches. The type can be one of (case-insensitive):

• Begin
• Building
• Cafe
• Camp
• Camping
• Car
• Cave
• Cliff
• Coast
• Crossroads
• Emergency
• End
• Food
• Forest
• Geocache
• Hill
• Home
• Hostel
• Hotel
• Info
• Lake
• Lodging
• Meadow
• Mountain
• Parking
• Peak
• Restaurant
• River
• Road
• Rock
• Sight
• Trail
• Valley
• Water
• Waterfall
• Waypoint

If the type is not any of the above, the default, Waypoint is used.

[isazi]

@halajos said in Waypoints - What is displayed?:

@isazi did the watch show waypoint names upon arrival?

Yes, I used the export in which Plotaroute generates direction waypoints for you and got all the names.

[fazel]

@fazel @halajos this suggests the fact that because your PAR export has <name></name> but not <type></type> (as does mine), the generic “Waypoint” is used. From what I can surmise, the only two fields that are interpreted by the watch are <name></name> and <type></type>. Type is case INsensitive and can only be an item from those listed. If I’m right, <name></name> should include all of the text you want displayed. The other tags exported by PAR (<cmt></cmt> and <desc></desc>) can be deleted/ignored, and <sym></sym> should be replaced with <type></type>.

This is easy to do in a text editor.

[halajos]

@fazel thank you for the explanation!

[fazel]

@halajos truth is…I’m just winging it…

[Fenr1r]

@fazel Where did you land on the sensitivity of type case? In the official-looking-material post it’s not (“in-”) but in your last it … is. Which applies? Before competing interpretations inevitably result in discord, factionalism and physical hostilities.

[fazel]

@Fenr1r I see case sensitive? Where to you see “non-”? Also - I’m a big fan of your vocabulary/writing prowess.

[fazel]

PAR Export:

<wpt lat="40.612411" lon="-82.272338">
<time>2021-01-13T00:08:06Z</time>
<name>Up</name>
<cmt>3-step up (1)</cmt>
<desc>3-step up (1)</desc>
<sym>Left_slight</sym>
</wpt>

After editing

<wpt lat="40.612411" lon="-82.272338">
<time>2021-01-13T00:08:06Z</time>
<name>3-step up (1)</name>
<type>Hill</type>
</wpt>

We’ll see if this works.

[Fenr1r]

@fazel You mean my fantastic ability to get the words wrong? Thunk you. Not “non-” but “in-”. Up above:

The type of waypoint determines the icon shown in Suunto watches. The type can be one of (case-insensitive):

[fazel]

@Fenr1r Oh geez - you are right. It is not case-sensitive. I will correct. Thank you!

[fazel]

@fazel This doesn’t appear to work. At least not as a direct import into SA from the GPX file.

[fazel]

@fazel however, I uploaded to QS and it subsequently showed up in SA with the waypoints (on iOS). So - success.

[Dimitrios Kanellopoulos]

SA iOS stil ldoes not parse the waypoints from a GPX (I think)

WAypoints need to be inside the track for the watch / app to display them

[fazel]

@Dimitrios-Kanellopoulos two questions.

1. Does this mean even if I see the waypoints in the app, they won’t appear when I complete the route? (For clarification, I do see the waypoints in SA after uploading to QS on iOS.)
2. If this is the case, can I get around it by inserting the points within the <trk></trk> tags?

Thanks

[fritzbt2013]

@Dimitrios-Kanellopoulos Just tested this. As you suggested still not working in iOS. I see the Waypoints in the GPX file but SA ignores on import. Any idea on when this might get resolved? Makes sharing routes a real pain … (anyone have a good workaround here?).

[fazel]

@fritzbt2013 it did work for me if I uploaded via the services menu is QS. Do you have SA connected with QS? I’m on iOS which is not officially supported according to the uploader, but it works. I tested a route yesterday using this process.

1. Straight export from PAR. You only need to fill out the label field. Select POI in the export options.
2. Upload to QS

The file then shoes up in SA. If you select it, you will see the waypoint flags.