There are two types of request points. A waypoint is a destination. Use it when you plan to stop there. Via points (throughpoints) correct the route to make it pass through all the via points. Waypoints are guaranteed to be between sections in the resulting route. Via points are embedded into sections.
For each request point, you can provide a point context. It's an opaque string that describe entrances, driving arrival points and so on. If such context is provided then a client will get routes to those additional points.
- Implemented types
Constructors
- RequestPoint(Point point, RequestPointType type, String? pointContext, String? drivingArrivalPointId)
-
factory
Properties
- drivingArrivalPointId → String?
-
Specifies what driving arrival point to use. If point is not
specified then server will select one.
no setter
- hashCode → int
-
The hash code for this object.
no setteroverride
- point → Point
-
The request point.
no setter
- pointContext → String?
-
Opaque string that describe entrances, driving arrival points and so
on.
no setter
- runtimeType → Type
-
A representation of the runtime type of the object.
no setterinherited
- type → RequestPointType
-
The type of request point specified.
no setter
Methods
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a nonexistent method or property is accessed.
inherited
-
toString(
) → String -
A string representation of this object.
override
Operators
-
operator ==(
covariant RequestPoint other) → bool -
The equality operator.
override