Waypoint

Initializes a new waypoint object with the given geographic coordinate and an optional accuracy and name.

It is recommended that the value of this parameter be greater than the horizontalAccuracy property of a CLLocation object obtained from a CLLocationManager object. There is a high likelihood that the user may be located some distance away from a navigable road, for instance if the user is currently on a driveway or inside a building.

Initializes a new waypoint object with the given CLLocation object and an optional CLHeading object and name.

The geographic coordinate of the waypoint.

The radius of uncertainty for the waypoint, measured in meters.

For a route to be considered viable, it must enter this waypoint’s circle of uncertainty. The coordinate property identifies the center of the circle, while this property indicates the circle’s radius. If the value of this property is negative, a route is considered viable regardless of whether it enters this waypoint’s circle of uncertainty, subject to an undefined maximum distance.

By default, the value of this property is a negative number.

The direction from which a route must approach this waypoint in order to be considered viable.

This property is measured in degrees clockwise from true north. A value of 0 degrees means due north, 90 degrees means due east, 180 degrees means due south, and so on. If the value of this property is negative, a route is considered viable regardless of the direction from which it approaches this waypoint.

If this waypoint is the first waypoint (the source waypoint), the route must start out by heading in the direction specified by this property. You should always set the headingAccuracy property in conjunction with this property. If the headingAccuracy property is set to a negative value, this property is ignored.

For driving directions, this property can be useful for avoiding a route that begins by going in the direction opposite the current direction of travel. For example, if you know the user is moving eastwardly and the first waypoint is the user’s current location, specifying a heading of 90 degrees and a heading accuracy of 90 degrees for the first waypoint avoids a route that begins with a “head west” instruction.

You should be certain that the user is in motion before specifying a heading and heading accuracy; otherwise, you may be unnecessarily filtering out the best route. For example, suppose the user is sitting in a car parked in a driveway, facing due north, with the garage in front and the street to the rear. In that case, specifying a heading of 0 degrees and a heading accuracy of 90 degrees may result in a route that begins on the back alley or, worse, no route at all. For this reason, it is recommended that you only specify a heading and heading accuracy when automatically recalculating directions due to the user deviating from the route.

By default, the value of this property is a negative number, meaning that a route is considered viable regardless of the direction of approach.

The maximum amount, in degrees, by which a route’s approach to a waypoint may differ from heading in either direction in order to be considered viable.

A value of 0 degrees means that the approach must match the specified heading exactly – an unlikely scenario. A value of 180 degrees or more means that the approach may be as much as 180 degrees in either direction from the specified heading, effectively allowing a candidate route to approach the waypoint from any direction.

If you set the heading property, you should set this property to a value such as 90 degrees, to avoid filtering out routes whose approaches differ only slightly from the specified heading. Otherwise, if the heading property is set to a negative value, this property is ignored.

By default, the value of this property is a negative number, meaning that a route is considered viable regardless of the direction of approach.

The name of the waypoint.

This parameter does not affect the route, but you can set the name of a waypoint you pass into a RouteOptions object to help you distinguish one waypoint from another in the array of waypoints passed into the completion handler of the Directions.calculate(_:completionHandler:) method.

Initializes a new waypoint object with the given CLLocation object and an optional heading value and name.