Mapping Inconsistency - Over-Covering vs Under-Covering (Time vs Distance setting)
I performed identical Building mapping missions - one with time and the other with distance capture settings. The buildings were practically identical as were the flight parameters - same height, same speed, same overlaps (75% front / 65% side), same gimbal pitch, etc. I got 2 totally different coverages. Which one is correctly yielding overlaps (75% front / 65% side)? Check the spacing.
Top Building took 151 photos using Time capture, while the bottom Building took 256 photos using Distance capture. Which one is correctly yielding overlaps (75% front / 65% side)? Doth can't be right, and one has to be wrong.
Comments
6 comments
Mission plan please?
Here you have it: https://app.dronelink.com/daniel-snyder-rctunesv0hub0224z9yz/dronevideos-com/plan/t7iZ9Mct8oU2l6Bk3Yff/b9Zo6LC4abkYOz9PCQuM
The issue discrepancy seems to appear when you select min capture intervals less than 2 seconds. The map component was originally created before the M3E was released, and all the drones previously could not go below 2 seconds on interval photos so this is what the component was optimized for. It appears this make take some effort to correct if you have to have less than 2 seconds selected.
ok, but to answer my question - which mode yields the correct overlaps - Distance or Time? I am finishing 15 Orthos this week and need to know I I must do reshoots. Thanks.
What I’m trying to say is that neither will, unless you set it to 2 seconds, and then both will.
Seems like a broken function yielding false results for unaware pilot using Growth/Enterprise licenses. A prudent course of action would be to disable the function (Min Time parameter) till it can be fixed. Also there was an earlier warning there was something amiss here. https://support.dronelink.com/hc/en-us/community/posts/30308140701587-Inconsistent-number-of-Photos-for-0-7-vs-2-0-Sec-Interval-Orthos
Please sign in to leave a comment.