Changing Waypoint Altitude affects the altitude of other waypoints
Whilst looking at the behaviour described here I came across another problem:
using this mission https://app.dronelink.com/martin-reading/beta-4/plan/zJYakFLyK162J0LjFG5o/R3p5ytf3zmEv9bZrnZXY as the start reference all Altitudes are set at 100feet
Now change WP B to 50 feet as here https://app.dronelink.com/martin-reading/beta-4/plan/bC2BOEYcYIk6jHVE83jm/ILzlib55yJ1m0gOK20qH and note that WP C changes to 80 feet with everything else stay at 100 feet
Now change WP D to 75 feet as here https://app.dronelink.com/martin-reading/beta-4/plan/c2NjkUEWXD2lyAyHJSwm/eE7Kgl11mb2ZUl9h9lYC and note that WP C has reduced from 80 feet to 65 feet, WP A & B are still correct, however WP E & F have both reduced to 75 feet
Comments
7 comments
I think there is confusion about waypoint set altitude and waypoint "will be altitude". I think the plan initially shows what the altitude will be when crossing each waypoint. It's just a reference number. If an altitude is actually manually set at a waypoint then future waypoint "pass by" altitudes will reflect the changes, including interpolated adjustments to the next un-set altitude. Just because an altitude shows on the waypoint doesn't mean it was actually set at that waypoint.
It looks like waypoints B and D were set manually to 100 feet, while the others did not have specific set waypoints so they would show the "pass by" altitudes. When manually changed B to 50 feet, it interpolated the pass by altitude for C to reach the set altitude for D.
Try adding a path action altitude between waypoints and see what happens. It adjusts future pass by waypoint altitudes.
I don't like adding altitude and speed to waypoints because of confusion. I like the old way of markers/path actions.
David, all the 100 feet waypoint altitudes in the first mission are the default altitude when adding the waypoints component
David is correct, it is because the waypoints that don’t have an altitude explicitly set are just showing you what the interpolated altitude will be when it passes by. I agree, David, I like markers better as well (which is why I started with that and held my ground for so long on not adding waypoint settings), but what can you do. Most people just didn’t want to learn what a marker was.
Fair enough, I must admit I normally use path actions for altitude, speed changes etc
Just at my 2 cents worth. I’m a big marker/ Path action guy still. Plus if gives you more control anywhere on the path, not just at a waypoint. Pilots choice.
Totally agree Mike, which is why I normally use them myself, just noticed this while looking at the problem(since sorted) that was occurring in the other thread I linked to.
Please sign in to leave a comment.