Creates many waypoints if you set photo capture to NONE
If you create a map and have photo capture enabled, then when you convert it to DJI waypoints, you have a small number of waypoints (one at each end of the flight path) which is normal for mission planned at an AGL above the take-off point. (ie not terrain follow).
But if you disable photo capture (set to none), when you convert it to DJI Waypoints there are the maximum number of waypoints allowed. So now you can not add points, and tweak the flight patter. (it is also at 100 points which exceeds the 99 limit which is odd).
By setting the photo capture to "None" it actually makes rounding off the turn around much easier by increasing the CURV radius to, 500ft. So that part is nice. But all the extra waypoints is not.
Comments
4 comments
This is the Beta version
While a little strange this will not affect our flying. So not a major deal. Will report back if we run into workflow issues because of this.
This was intentionally not supported right now, so moving this to feature requests. I think the real issue here, however, is that you are using this as a work-around for settings that you want in map in the first place (for LIDAR mapping), correct? It might just be better to submit feature requests for the original work-flow instead of the the work-around.
I am doing a work around for Lidar mapping. I only reported this because it seemed unusual to create all the additional waypoints when the altitude was set to reference the TakeOff point. In that case you only need a waypoint at the end of each segment. But this created waypoints along the path as you would for terrain following which seemed like a bug. I will submit a workflow request to suit Lidar mapping as a Feature Request. I feel like I have somewhat perfected the workaround but having the ability to support it as a mission creation would be very nice :)
Please sign in to leave a comment.