My projects get clipped to the bounds I input in the mission planning. In most scenarios, this isn’t a problem. However, my latest project I was mapping a bowl-shaped terrain. On the edge of this bowl are 200 ft trees. For optimal photos, I fly within this bowl rather than over the tops of the trees just beyond the edge. So my mission stays within the bowl when actually, I want to incorporate the edges of the bowl as well.
I’ve found that clipping doesn’t occur when you process photos with no mission logs, this can lead to way more terrain than necessary. It would be nice to have some control over where the clipping occurs so it’s not one extreme or the other.