# App: Waypoint names **URL:** \ **Category:** Implemented features\ **Tags:** implemented\ **Created:** [March 16, 2020, 5:07pm UTC](https://forum.kurviger.com/t/app-waypoint-names/2820 "2020-03-16T17:07:32Z")\ **Posts on this page:** 1\ **Showing post:** 29
**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:** [June 17, 2020, 7:31am UTC](https://forum.kurviger.com/t/app-waypoint-names/2820/29 "2020-06-17T07:31:13Z")
> [@rumbrummer](#): > > I’d like to use the name information also for shaping points to identify them More important is what is common, i.e. the rule for shaping points. (not how we like them to be) So how all other routing services handle shaping point names? Any other have them? Because we should remain compatible. > [@App: Waypoint types](https://forum.kurviger.com/t/app-waypoint-types/2821/3): > > 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 b… --- _[View the full topic](https://forum.kurviger.com/t/app-waypoint-names/2820)._