Missed some photos
As you can see from the photo, some pictures were missed. This resulted in a road that is very important to the photo being totally messed up (Need this for the fire marshal as my friend is trying to show he has good access to his resort). This was taken on the Air 2S at 290 ft with an overlap of 83/78. Is this a bug with the software or the drone? The whole picture was 907 photos so as a percent, it did quite well, sad it missed a very important part though. The follow up question is what is the best way to retake the missed photographs? I don't want to do the whole thing again as I just want those missing photos. Do I create a waypoint, manually do it, etc?
Comments
16 comments
In the map component, make sure you have verify file created checked.
In terms of the missing files. Just create a new map that covers the missing area and run that. There is a risk that the exposure will be different because the weather is different but, if they are similar enough, then any stitching software should be able to handle it.
Most commercial clients would tell you to re-run the whole thing because of the exposure problem.
Thank you but I checked and the verify file created was selected like you show above.
What speed were you flying, and what photo format was being used?
Not to revisit a old post, but this has been a ongoing issue for me. I have had to spot check before leaving sites and grab a few extra shots manually.
These missing shots are troubling for me too. I think this occurs when the drone to controller to phone to Dronelink connection goes down (spotty connection). Many times I have to hold the controller high and stand on a high spot to reduce missing shots. Also relocate yourself frequently during a flight to maintain better contact. I agree it would be beneficial to have a "capture missing shots feature within the App itself.
Did you try switching to time based capture (interval photos)?
Hello Jim,
Let me start by saying I really appreciate the Dronelink capabilities and the great support you always give. It's exceptional.
I could not use a time based capture, since the client specified the % Overlap approach to the mission. I would have otherwise.
Let me understand better how V-F-C is designed to work. It works by ensuring a file is created on the SD card in response to each command to take a photo sent from the controller - correct?
If so the breakdown usually occurs when the signal from the controller to the drone gets weak to the point the command is sent, but the drone does not capture it. Also I think the problem occurs when there is a gust of wind and the drone gets nudged off position somewhat (but I might be wrong however). So the problem won't be solved with V-F-C.
I work in the area of large & high building an roof congestion so this problem happens to me frequently.
I am thinking of ways to mount my controller on a 20 ft extension pole as a work around. Kind of silly I suppose, but I really need a way to go back and easily get the missing photos in the map gaps.
Here is a recent example where it was very hard to guess where to go back to take the filler shots after the mission ended. The roof was rather featureless without and reference points to see from the air, so it's quite a guessing game I usually fail at.
It would have been very helpful to have a "recapture mission" function, rather than try to guess where to go back and manually take new filler shots:
Many thanks if you can figure out a solution here.
Daniel
The map component automatically calculates the correct speed and interval photo setting to ensure the overlaps that you specify, even with time based capture.
So there is no time based commands originating from the controller? The time based triggers are onboard the drone? Could you clarify this would overcome the controller communication issue causing the gaps in the map photos? Maybe I do not understand where the time triggers are originating from or even the root cause of why there are gaps in the pattern. Thanks in advance for explaining.
Time based means it issues one command at the start of each segment to put the camera into interval photo mode, and from their the camera handles snapping a picture onboard, without needing more commands from the ground station. This approach means that slight delays with the signal which would have interfered with the single capture commands in distance mode don't happen.
OK, I think I understand. I used to think it would just blindly snap photos at 2 sec intervals, regardless or speed, AGL, or % overlap settings. So I was wrong(?)
So I think you are saying:
The Time based flag will support the % Forward Overlap setting, by calculating photo time intervals based on Overlap %, AGL and drone speed. Basically it will compute the time to next photo (as determined ONBOARD the drone), and not wait for the controller to relay what DL commands based on location. So it won't take too many pictures and won't take too few since its still trying to maintain the Forward overlap %.
I think that is the design you are describing. Do I have that correct?
If so does that guarantee the elimination of gaps in the map or just reduce them?
Correct. Nothing is fool proof but it should be much better for you use case.
Thanks Jim ! I am excited to try it out. In hindsight, maybe an Info Pop-Up might have helped guys like me if I had seen this when hovering over that field. Just a thought on having embedded documentation.
Once again thank you!
Hi Daniel Snyder, I know it's been a while, but I'm wondering if you found a workflow that helped avoiding those gaps in the photos during the flight? What settings have you been using please?
I've been facing the same issue and will try the solution suggested by Jim (time based capture) shortly.
Not foolproof, but Time Based capture seems to not skip as badly. However there may still be an error in the min interval setting...JIM_ETA to fix?
It isn’t prioritized right now.
Please sign in to leave a comment.