# App: Waypoint types **URL:** \ **Category:** Implemented features\ **Tags:** implemented\ **Created:** [March 16, 2020, 5:08pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821 "2020-03-16T17:08:29Z")\ **Posts on this page:** 20\ **Page:** 1
**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:** [March 16, 2020, 5:08pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/1 "2020-03-16T17:08:29Z")
For reference see: > [@Website: Waypoint types](https://forum.kurviger.com/t/website-waypoint-types/1142): > > Wenn ich eine Route plane, besteht sie zunächst aus POIs, also interessanten Zielen, die ich anfahren möchte. Aber nicht immer Routet kurviger so, wie ich gerne fahren möchte. Deshalb setze ich in diesem Fall einen Zwischenpunkt und verschiebe den Routenverlauf. Das Blöde ist nun, dass dieser Zwischenpunkt genauso aussieht wie alle anderen Punkte. Das macht die Tour in der Ansicht sehr unübersichtlich. Deshalb hätte ich einen oder zwei Wünsche: Am liebsten hätte ich es, wenn ich die Route vers… ---
**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:** [March 16, 2020, 4:09pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/2 "2020-03-16T16:09:58Z")
I would start this very simple by allow setting 2 types on waypoints in the app: - Stopover points (visible in instructions / navigation) – _current implementation_ - Shaping points (invisible in instructions / navigation) _More advanced properties, colors, etc. will be examined in future in separate topics._ ---
**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:** [March 17, 2020, 3:52pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/3 "2020-03-17T15:52:51Z")
Garmin uses the “shaping point” term and we can use it for the UI texts: - [Garmin BaseCamp](https://support.garmin.com/en-US/?faq=POYXggoD3p19jQOwZCvFA6): Shaping points are any position along a route that will not alert you when you arrive. Shaping points do not contain arrival time or distance between points information. - [Google Maps](https://developers.google.com/maps/documentation/javascript/directions#Waypoints): `stopover` (optional) indicates whether this waypoint is a actual stop on the route (`true`) or instead only a preference to route through the indicated location (`false`). Stopovers are `true` by default. - [HERE Maps](https://developer.here.com/documentation/routing/dev_guide/topics/waypoints.html): A waypoint can be either a StopOver (for example, start or destination) or a PassThrough. A valid CalculateRoute request must include at least two StopOver waypoints. ---
**Author:** ![Patrick](https://forum.kurviger.com/user_avatar/forum.kurviger.com/patrick/32/7292_2.png) [@Patrick](https://forum.kurviger.com/u/Patrick)\ **Post date:** [March 17, 2020, 4:29pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/4 "2020-03-17T16:29:07Z")
One thing I want to mention that we should avoid in my opinion. Google Maps makes you CONFIRM a stopover on the screen. That is terrible UX in my opinion, because it distracts you from driving and actively interrupts your navigation if - for any reason - you decide to not stop at that point and drive on ---
**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:** [March 17, 2020, 4:40pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/5 "2020-03-17T16:40:07Z")
Stopover or shaping points are intended for UI use in route planning. Navigation (like the turn instructions) can use only the stopover points. So its workflow does not change, just the types of waypoints it parses. ---
**Author:** ![Patrick](https://forum.kurviger.com/user_avatar/forum.kurviger.com/patrick/32/7292_2.png) [@Patrick](https://forum.kurviger.com/u/Patrick)\ **Post date:** [March 17, 2020, 4:48pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/6 "2020-03-17T16:48:16Z")
All good. Just wanted to make sure to mention it ---
**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:** [March 28, 2020, 10:25am UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/7 "2020-03-28T10:25:00Z")
See HERE WeGo, it has an intuitive implementation of waypoint types (vs Google Maps): > **[HERE WeGo](https://wego.here.com/)** > > HERE WeGo ---
**Author:** ![SchlesiM](https://forum.kurviger.com/user_avatar/forum.kurviger.com/schlesim/32/1080_2.png) [@SchlesiM](https://forum.kurviger.com/u/SchlesiM)\ **Post date:** [March 28, 2020, 12:49pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/8 "2020-03-28T12:49:42Z")
Absolutely. In HERE WeGo you’re using different waypoints types (shaping point and waypoints to be visited) without even thinking too much about it. Google Maps offers a similar function but the usability is a little bit weird. ---
**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:** [March 28, 2020, 4:48pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/9 "2020-03-28T16:48:34Z")
> [@SchlesiM](#): > > Google Maps offers a similar function but the usability is a little bit weird. Google Maps uses the same symbol for both waypoint types, which is confusing. Also interesting is how the waypoint types are handled in GPX import and export. ---
**Author:** ![SchlesiM](https://forum.kurviger.com/user_avatar/forum.kurviger.com/schlesim/32/1080_2.png) [@SchlesiM](https://forum.kurviger.com/u/SchlesiM)\ **Post date:** [March 28, 2020, 6:35pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/10 "2020-03-28T18:35:16Z")
> [@devemux86](#): > > Google Maps uses the same symbol for both waypoint types, which is confusing. Yes, and it seems that you can’t convert a shaping point directly into a visit/stopover point because then this waypoint is suddenly your final destination point. Not very intuitive or logical. ---
**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:** [March 28, 2020, 6:46pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/11 "2020-03-28T18:46:53Z")
They both provide a _simple_ and intuitive approach, that most users expect. I could see waypoint type conversions _afterwards_, as a more exotic feature. Let’s start with the _basics_, include stopover / shaping points in all functions. ---
**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:** [April 2, 2020, 11:37am UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/12 "2020-04-02T11:37:04Z")
![Kurviger](https://forum.kurviger.com/uploads/default/original/2X/3/3f83999619d1552d9e344179c4dcc2a08faf5a3b.png) ---
**Author:** ![SchlesiM](https://forum.kurviger.com/user_avatar/forum.kurviger.com/schlesim/32/1080_2.png) [@SchlesiM](https://forum.kurviger.com/u/SchlesiM)\ **Post date:** [April 2, 2020, 11:47am UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/13 "2020-04-02T11:47:03Z")
A teaser for new things to come? 😃 ---
**Author:** ![zaphod\_42](https://forum.kurviger.com/user_avatar/forum.kurviger.com/zaphod_42/32/499_2.png) [@zaphod\_42](https://forum.kurviger.com/u/zaphod_42)\ **Post date:** [April 2, 2020, 12:55pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/14 "2020-04-02T12:55:34Z")
That’s already possible in 1.13.1 ![2020-04-02 14.52.52](https://forum.kurviger.com/uploads/default/original/2X/3/3afee4931acffbde5499811b62edf865dd94cbc3.png) ---
**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:** [April 2, 2020, 12:57pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/15 "2020-04-02T12:57:02Z")
> [@zaphod\_42](#): > > That’s already possible in 1.13.1 It’s about waypoint types (shaping dots) – not waypoint names. ---
**Author:** ![SchlesiM](https://forum.kurviger.com/user_avatar/forum.kurviger.com/schlesim/32/1080_2.png) [@SchlesiM](https://forum.kurviger.com/u/SchlesiM)\ **Post date:** [April 2, 2020, 1:20pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/16 "2020-04-02T13:20:21Z")
![wptypes](https://forum.kurviger.com/uploads/default/original/2X/4/4bff629a9d8e3cf1a1ad525389d9bd92a446a686.png) Right? 😁 ---
**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:** [April 2, 2020, 1:23pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/17 "2020-04-02T13:23:31Z")
> [@SchlesiM](#): > > Right? 😁 Correctly! 🙂 ---
**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:** [April 3, 2020, 3:31pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/18 "2020-04-03T15:31:32Z")
> [@SchlesiM](#): > > it seems that you can’t convert a shaping point directly into a visit/stopover point You will be able to also switch waypoint types [stopover vs shaping] in next (beta) release. ---
**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:** [April 6, 2020, 5:04pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/19 "2020-04-06T17:04:40Z")
Waypoint type changes can be done via their long press menu and in waypoints list (like their names). ![Kurviger](https://forum.kurviger.com/uploads/default/original/2X/9/99a2b139802c991c01290d84ba620756949dd657.png) ---
**Author:** ![SchlesiM](https://forum.kurviger.com/user_avatar/forum.kurviger.com/schlesim/32/1080_2.png) [@SchlesiM](https://forum.kurviger.com/u/SchlesiM)\ **Post date:** [April 7, 2020, 10:27pm UTC](https://forum.kurviger.com/t/app-waypoint-types/2821/20 "2020-04-07T22:27:32Z")
Looks great. I’m really looking forwards to test the new features (didn’t appear in my app updates yet) 😃. One question prior to my first tests: will the options of the rerouting mode distinguish between regular waypoints and shaping points? ![wp-navigation](https://forum.kurviger.com/uploads/default/original/2X/e/e0f99b2c3fe10993611bb1c1db5adb7c4f2e7814.jpeg) I mean: will the option “next unvisited waypoint” automatically omit shaping points and focus only on the next regular waypoint in the route? If so: will there be an additional rerouting option considering both types (something like “next unvisited way- or shaping-point”)? And of course: by introducing shaping points you created a new challenge for the Kurviger website to support a corresponding feature (with an appropriate integration into the app) 🕶. [Next page](https://forum.kurviger.com/t/app-waypoint-types/2821.md?page=2)