Popular Resources
-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (block.name) { %><% if (block.html_url) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% } %> <% if (block.description) { %><%= block.description %>
<% } %>
<% }) %>
Comments
7 comments
It appears that you marked the first boundary point at 0 feet, which set the altitude of the map to zero feet per the instructions:
The drone attempted to descend and fly to the start of the map after that, which must have been below the treeline…
I understand he marked the first point while still on ground. Yes ?
The first point was marked in the air above the map tree line. As described above, that happened the first time. I put the aircraft back up at mark one, pressed play, and it didn't descend this time. It just turned and flew towards me and into the taller tree line
I tried to share the photo of the map but had to create a link for it
If you look at the mission history in your account, the map mission shows the inputs that were used during the on the fly function (0ft on the first boundary point), and the resulting map altitude set at 0ft:
In such a case, maybe a warning should be raised.
This map function now disallows marking the first point at zero feet.
Please sign in to leave a comment.