Must a waypoint include a stop?

Not always. That depends on the mission and navigation interface.

Can a waypoint specify orientation?

Yes; the supplied PAL Robotics definition includes it.

Is a waypoint list a full trajectory?

No. Speeds, timing and detailed motion may remain unspecified.

AI Glossary / Reinforcement learning and robotics / Advanced

Waypoint

Definition

A waypoint is a specified location used to organize navigation or another spatial task. In the PAL Robotics terminology supplied for this entry, it includes position and orientation and may have actions associated with arrival. A sequence of waypoints can describe places a robot should visit without specifying every movement between them.

What it means

A waypoint gives a navigation system a meaningful target, such as an inspection position or a delivery station. The robot still needs to determine where it is and how to reach the target. Coordinates identify the target only when their reference frame and units are understood.
Orientation can matter as much as position. Reaching a camera inspection point while facing away from the subject may satisfy a distance requirement but fail the intended task. Different systems use the word waypoint differently, so a specification should state whether it includes orientation, timing, arrival tolerance or an associated task.

How it works

A mission supplies a waypoint or a sequence of them. A navigation system interprets each target in the appropriate coordinate frame, uses localization to estimate the robot's pose and plans feasible movement through the environment. Control then follows the planned movement while responding to relevant feedback.
An arrival condition determines when the target is considered reached. This can involve position and orientation tolerances rather than exact equality with stored coordinates. Task execution may then trigger a separate operation, such as waiting or collecting an image. Reaching the location and successfully completing that operation are different events.
The waypoint sequence is not automatically the complete path. A planner can choose intermediate geometry around obstacles, and that geometry can change when conditions change. Nor does a location list necessarily define a trajectory with speeds and timestamps. Those details require additional planning or control decisions. Failure handling also matters: an unreachable waypoint should produce a defined response rather than an unexplained gap in the mission record.

Three practical examples

Inspection: a robot visits several designated observation poses and records an image at each. The pose helps determine what the camera can see; image quality still needs separate checking.
Internal delivery: a mission includes a pickup point and a destination. Arrival at the destination does not by itself prove that a handover occurred.
Demonstration route: a robot follows a sequence of named locations and pauses at selected stops. Names aid understanding; coordinates and frames support navigation.

Think of it this way

Think of a sightseeing itinerary listing a museum, a garden and a station. Those are destinations, not detailed instructions for every step between them. You may take a different street when one is closed. A robot's waypoint list plays a similar organizing role, while its navigation system works out the movement between destinations.

Worked example

Consider planar coordinates in meters in one map frame. A robot starts at S = (0, 0). It must visit W1 = (3, 4) and then W2 = (6, 4). Assume straight travel between these points is feasible for the distance calculation only.
The distance from S to W1 is sqrt(3 squared + 4 squared) = 5 meters. The distance from W1 to W2 is 3 meters. Visiting both in order therefore gives a geometric length of 8 meters under these assumptions. Going directly from S to W2 would have length sqrt(52), approximately 7.21 meters, but would not visit W1. A shorter route cannot omit a required visit.
Suppose a teaching arrival rule for W1 requires position error at most 0.25 meters and orientation error at most 5 degrees. W1's requested heading is 90 degrees. An estimated pose at (3.12, 3.84) has position error sqrt(0.12 squared + (-0.16) squared) = 0.20 meters. If its estimated heading is 84 degrees, the orientation error is 6 degrees. It passes the position condition but fails the orientation condition.
If the heading becomes 87 degrees while position remains unchanged, the orientation error becomes 3 degrees and both stipulated conditions pass. This says nothing about whether an associated photograph has been captured successfully. That task needs its own result.
Finally, imagine an obstacle forces the first leg to become 6.5 meters while the second remains 3 meters. The revised route length is 9.5 meters even though the waypoints have not changed. The example illustrates geometry and a hypothetical arrival rule; it does not prescribe operational tolerances or claim that these routes have been tested on a robot. Localization uncertainty and physical clearance would need additional consideration in a real system.

Illustrative case study

Fictional company Willow Facilities prepares an indoor inspection mission with named observation waypoints. Each record includes a map reference, position, orientation and the intended inspection action. The team logs navigation arrival separately from image capture so that a reached location is not incorrectly counted as a completed inspection.
After a layout change, an old observation position no longer gives the desired view. The team revises the waypoint and retests the route and inspection result. This fictional workflow reports no measured deployment results.

Common misconceptions and mistakes

A waypoint is not necessarily a physical marker. It can be a stored location with no visible sign in the environment. It is also not a guarantee that a collision-free route exists.
A common error is mixing coordinate frames: the same numerical coordinates can refer to different physical places in different frames. Another is checking position while ignoring a required heading. More waypoints do not automatically improve navigation; unnecessary targets can constrain useful routes or introduce avoidable stops. Finally, successful navigation to every waypoint does not prove that every associated business task succeeded.

Business use

Waypoints help translate a mission into locations that operators can name, inspect and update. They can support repeatable inspection, delivery and demonstration workflows. Records connect locations to purposes, map versions and completion criteria. Teams should track failed visits and failed tasks separately so that operational reports reflect what was actually accomplished.

Check your understanding

Why was the direct 7.21-meter route insufficient?

Answer: It omitted the required W1 visit.

Why did the first estimated pose fail arrival?

Answer: Its heading error exceeded the stipulated tolerance.

Why can route length change without changing waypoints?

Answer: The planner may need different movement between the same targets.

Related terms

Pose
Localization
Path planning
Trajectory
Navigation goal
Coordinate frame
Waypoint action

Learn next

Define a waypoint in a named frame, state its arrival criteria and distinguish navigation success from the task performed there.

Sources

PAL Robotics, PAL OS glossary, Waypoint and Waypoint action: https://docs.pal-robotics.com/edge/glossary . The coordinates, tolerances, route calculations and company scenario are original teaching illustrations.

Previous: Wavefront coding Next: Weak artificial intelligence