As in my prior post, select all points in a waypoint mission (touch the wrench symbol, then 'batch edit', then 'select all') and then select 'Relative to Ground' for altitude and apply to all points. This must be done in the app as the batch edit function is not available in the mission hub.I can't find relative to ground on the litchi app (Android) anyone can let me know where to find it I would really appreciate it
Good stuff mate. Really appreciate thatAs in my prior post, select all points in a waypoint mission (touch the wrench symbol, then 'batch edit', then 'select all') and then select 'Relative to Ground' for altitude and apply to all points. This must be done in the app as the batch edit function is not available in the mission hub.
Just to clarify what you've said. So all WP would be set to, for example, to 50 agl referred to the ground under the WP regardless of what the altitude had been set to when building the mission? Any idea how litchi picks the AGL value?This is nice try but kind of useless. Only way to utilize relative to the ground is by batch editing all waypoints in existing mission. And if you do that new altitudes will all be the same relative to the ground, so any altitude changes will be discarded. They should put "Altitudes relative to the ground" as an option in Mission settings.
Sent from my SHIELD Tablet K1 using PhantomPilots mobile app
The reference AGL value is the first waypoint. And the feature is far from useless as you can now plot out the mission and set relative altitude based on terrain automatically ( and then make any individual waypoint adjustments if necessary. This saves a lot of time vs. doing it manually as in the past. It is true that if you use the 'relative to ground' feature on an existing mission it will discard any prior altitude settings, but that's life in the big city I guess. I do agree that an 'Altitudes relative to the ground' global mission setting would be a good idea though.Just to clarify what you've said. So all WP would be set to, for example, to 50 agl referred to the ground under the WP regardless of what the altitude had been set to when building the mission? Any idea how litchi picks the AGL value?
OK, useless is bit too harsh. But with current logic it is still faster to plot a mission in hub since AGL is there as an info for some time now.The reference AGL value is the first waypoint. And the feature is far from useless as you can now plot out the mission and set relative altitude based on terrain automatically ( and then make any individual waypoint adjustments if necessary. This saves a lot of time vs. doing it manually as in the past. It is true that if you use the 'relative to ground' feature on an existing mission it will discard any prior altitude settings, but that's life in the big city I guess. I do agree that an 'Altitudes relative to the ground' global mission setting would be a good idea though.
I can't agree with that at all. In hub the info is there but you must manually make the adjustment for each waypoint, which can get old fast. With the new feature altitude adjustment is done automatically for the entire mission with one click.OK, useless is bit too harsh. But with current logic it is still faster to plot a mission in hub since AGL is there as an info for some time now.
Ok, that can work for me. Setting the first WP and then being able to have all subsequent WPs set to the same height AGL at the WP would be a big help in maintaining scale in a video, for example. Got to look into updating.The reference AGL value is the first waypoint. And the feature is far from useless as you can now plot out the mission and set relative altitude based on terrain automatically ( and then make any individual waypoint adjustments if necessary. This saves a lot of time vs. doing it manually as in the past. It is true that if you use the 'relative to ground' feature on an existing mission it will discard any prior altitude settings, but that's life in the big city I guess. I do agree that an 'Altitudes relative to the ground' global mission setting would be a good idea though.
Problem is that those are not adjustments. Can you describe how would you make new mission utilizing AGL feature?I can't agree with that at all. In hub the info is there but you must manually make the adjustment for each waypoint, which can get old fast. With the new feature altitude adjustment is done automatically for the entire mission with one click.
I would plot the mission out as usual, then use the new feature to set all waypoint altitudes to reference ground level, and... done. If I needed any manual adjustments such as to account for man-made structures or tall trees or such I would then add them as necessary (since that information is not in the terrain database and thus can never be made automatically no matter how the feature is implemented.) With the hub method I would have to observe the altitude difference when creating each waypoint and make a manual correction for every one individually (hoping that I don't make any arithmetic errors.) Clearly the first method is easier since you only have to adjust some (or quite possibly none) waypoints, vs. every single one.Can you describe how would you make new mission utilizing AGL feature?
Yes, although I'm not sure what is so difficult about the concept as it is currently laid out. But like so many things Litchi you do have to analyze their way of thinking a bit.Obviously I'm missing something ...
I thought AGLThe reference AGL value is the first waypoint. And the feature is far from useless as you can now plot out the mission and set relative altitude based on terrain automatically ( and then make any individual waypoint adjustments if necessary. This saves a lot of time vs. doing it manually as in the past. It is true that if you use the 'relative to ground' feature on an existing mission it will discard any prior altitude settings, but that's life in the big city I guess. I do agree that an 'Altitudes relative to the ground' global mission setting would be a good idea though.
The reference AGL value is the first waypoint. And the feature is far from useless as you can now plot out the mission and set relative altitude based on terrain automatically ( and then make any individual waypoint adjustments if necessary. This saves a lot of time vs. doing it manually as in the past. It is true that if you use the 'relative to ground' feature on an existing mission it will discard any prior altitude settings, but that's life in the big city I guess. I do agree that an 'Altitudes relative to the ground' global mission setting would be a good idea though.
We use essential cookies to make this site work, and optional cookies to enhance your experience.