# Website: Add Waypoint/Shaping point info to GPX name

**URL:** <https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452>\
**Category:** Implemented features\
**Created:** [November 4, 2020, 6:06pm UTC](https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452 "2020-11-04T18:06:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\
**Post date:** [November 4, 2020, 6:06pm UTC](https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452/1 "2020-11-04T18:06:23Z")

</div>

As proposed by @rumbrummer here: [Website: Export Waypoint Names and Shaping Points - #18 by rumbrummer](https://forum.kurviger.com/t/website-export-waypoint-names-and-shaping-points/3706/18)

> [@Website: Export Waypoint Names and Shaping Points](https://forum.kurviger.com/t/website-export-waypoint-names-and-shaping-points/3706/18):
>
> Therefore I propose to add a hint at the routepoint name for that: For example ‘WP4’ for the 4th waypoint and a ‘FP7’ for the 7th shaping point. So If I have added a 4th Waypoint with the name ‘Lunch’ in kurviger, the name in the GPX would be ‘WP4 Lunch’.  
> It could be discussed, if the name prefix for shaping points should be ‘FP’ for german variant ( **F** orm **p** unkt).

Something like this could be added, when we add the Waypoint name export. So the output could be something like:

```auto
<name>(WP) Name</name>
<name>(SP) Name</name>

```

It would be good to find out who would be interested in this kind of feature? Please vote or provide a comment and maybe tell us a bit about your use case.

---

<div class="post-metadata">

**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\
**Post date:** [November 4, 2020, 7:02pm UTC](https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452/2 "2020-11-04T19:02:22Z")

</div>

What happens when export a GPX with extra name prefixes,  
then import it with those custom names and export it again?  
Will it have multiple “(SPN) … (SPN)” prefixes?

Cannot expect GPX parsers to regex erase “(SPN)” in order to extract / use the original waypoint names.  
Because if users happen to write a similar prefix intentionally, then they expect it to remain in the import.

My comment from that [discussion](https://forum.kurviger.com/t/website-export-waypoint-names-and-shaping-points/3706/19) is that names are set by users and expect them to remain _unchanged_.

---

<div class="post-metadata">

**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\
**Post date:** [November 5, 2020, 7:24am UTC](https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452/3 "2020-11-05T07:24:59Z")

</div>

If it’s really needed for better support some 3rd-party devices / programs,  
_then it should be optional_, via a new check box in website’s export dialog.

So not break the expected export of GPX names for the majority of users.

---

<div class="post-metadata">

**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\
**Post date:** [November 5, 2020, 8:52am UTC](https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452/4 "2020-11-05T08:52:57Z")

</div>

Yes, if enough people find this feature helpful, it could be added as an opt-in feature. I wouldn’t use this as default feature.

---

<div class="post-metadata">

**Author:** ![rumbrummer](https://forum.kurviger.com/user_avatar/forum.kurviger.com/rumbrummer/32/113_2.png) [@rumbrummer](https://forum.kurviger.com/u/rumbrummer)\
**Post date:** [November 5, 2020, 12:40pm UTC](https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452/5 "2020-11-05T12:40:05Z")

</div>

> [@devemux86](#):
>
> What happens when export a GPX with extra name prefixes,  
> then import it with those custom names and export it again?  
> Will it have multiple “(SPN) … (SPN)” prefixes?
> 
> Cannot expect GPX parsers to regex erase “(SPN)” in order to extract / use the original waypoint names.  
> Because if users happen to write a similar prefix intentionally, then they expect it to remain in the import.

No, prefixes should be removed during import.  
But I agree, this might lead to undesired effects. One possibility is to check the ‘creator’ tag of GPX to see if that GPX has been created by Kurviger - only in that case prefixes should be removed.  
But that solution still does not solve an intentional prefix matching a regular expression (regex) used to remove prefixes.  
A complex solution would be to store the info that a prefix has been added to a Kurviger specific extension of the route point and to use that information during reimport.  
But I have some doubt, if that effort is worth it - probably other tasks have higher priority.

---

<div class="post-metadata">

**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\
**Post date:** [July 25, 2025, 9:29am UTC](https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452/8 "2025-07-25T09:29:39Z")

</div>

Exporting points without a name, they are now named Shaping Point 1 or Via Point 2.

---

<div class="post-metadata">

**Author:** ![system](https://forum.kurviger.com/uploads/default/original/1X/72b08b060f194af26ec74d41fddb892e3084b1c1.png) [@system](https://forum.kurviger.com/u/system)\
**Post date:** [October 23, 2025, 9:30am UTC](https://forum.kurviger.com/t/website-add-waypoint-shaping-point-info-to-gpx-name/4452/9 "2025-10-23T09:30:08Z")

</div>

Closed on October 23, 2025, 9:30am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
