A position sequence does not define the image
ArduPilot Copter provides ordinary and spline waypoints; the latter support smooth paths. Placing points on a map does not fully define heading, camera direction, recording start or the usable edit interval. Confirm the altitude reference for the chosen command and ground-control interface. Evaluate every part of the path and available stopping space, not just the waypoint positions. Write camera aim and vehicle travel as separate requirements so a position sequence is not mistaken for a complete cinematic shot. Decide whether the shot needs a deliberate stop or continuous flow before adding waypoints. If it includes a stop, budget settling time separately from the usable edit interval.
Neighboring points influence the path
A spline’s shape depends on neighboring points and stopping conditions. Do not assume a curve will follow an imagined corridor between map markers; inspect the ground-control preview and simulation. Ordinary waypoint turns also depend on pass-through and delay behavior. Navigation and auxiliary commands have different execution semantics, so reaching a point does not automatically prove that every camera action has completed. Compare required timing, position, heading, gimbal and recording state with observed telemetry and logs. After editing a path, inspect neighboring segments as well as the changed point. Overlay the planned and observed trajectories so deviations are visible and explainable.
Validate the shot specification in SITL
ArduPilot SITL runs the autopilot without physical vehicle hardware. Our original exercise compares an ordinary three-point route with a spline route from the same initial condition. Record the path’s maximum deviation, where braking begins and how viewing angle to the intended subject changes. Terrain, wind, sensor and vehicle models have limitations, so the simulated curve is not a site-clearance guarantee. Preserve mission file, settings, software release and results together so later updates can be compared against a reproducible baseline. Include the intended image with test results. A correct path that loses the subject does not satisfy the shot. Separate flight acceptance criteria from visual acceptance criteria.
YOUR NEXT STEP
Put it into practice.
- Do not assess spline clearance using only straight lines between waypoints.
- Successful mission upload is not proof that every command will execute as intended.
Sources and editorial scope
Explanations and exercises are original editorial material. Verify product-specific conditions against the linked documentation version.
Research date: 21 October 2026. Check the linked version, supported hardware and applicable conditions. Evidence includes directly reviewed text and official search-index records.
Read the methodology and open questions →