There seems to be a lot of information out there to get someone from zero to flying with a triggered camera and then from images to processed output. But there is a gap in what to do in between. 

There are several parameters we all mess with when setting up a mapping flight (sidelap, overlap, altitude, ground speed) I would like to hear if anyone has good rules of thumbs on how to get efficient data collection and any pitfalls they have come across. 

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • T3

    Hi Brady,

    sidelap, overlap and the resulting ground resolution are the driving factors. Camera trigger distance is a function overlap, ground speed and altitude. Another factor, especially at altitudes < 50m a.g.l., is the camera shooting delay.

    For example, if you fly with 4m/s and your camera trigger distance is 8m you camera should be able to take an image each 2 sec. If you fly higher you can fly faster and thus can set camera trigger distance to higher values. But this has a negative effect on ground resolution.

    The Tower App has a nice and intuitive interface for mission planning (although you have to set WPNAV_SPEED manually).

    For stitching 60% sidelap and overlap should be sufficient. For generating digital surface models and orthomosaics up to 85% over- and sidelap can be required. Under ideal conditions 75% and 65% can be sufficient. But in general I use 80% and 70-75%. More overlap is required if you have a hard-mounted camera and deviations from the flight path as well as from nadir view due to gusty wind.

    You find some guideline for generating orthomosaics based on UAV data at http://mavis.bitmapping.de/guidelines/ 

    Best regards,

    Thorsten

    PS: Mavis is currently in beta testing and will be announced soon

  • Good morning,

    I am very interested in this. I have two models that currently work fairly well:

    1) Set the camera on a 3 second interval and "over shoot".

    2) 60% side and forward overlap

    #2 is working pretty well but going with #1 is appealing. The downside of #1 is volume of imagery. The upside is lower risk of gaps.

    -David

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @a1k0n: @DanielChiaJH @diyrobocars @circuitlaunch Here's my car's view of that race. About 8.4 second lap times for laps 2 and 3... both…
yesterday
DIY Robocars via Twitter
RT @DanielChiaJH: Great racing against @a1k0n today at @diyrobocars! Pretty cool to both break sun-9s at the track today I think I got very…
Sunday
DIY Robocars via Twitter
Broadcasting the @circuitlaunch race live now at https://m.twitch.tv/diyrobocars Races begin around 2:00pm PT
Saturday
DIY Robocars via Twitter
RT @a1k0n: ran a huge number of hyperparameter tuning experiments yesterday; now I can train a new policy, far with better quality, in 15 m…
Saturday
DIY Robocars via Twitter
RT @a1k0n: Did I get rid of hand-tuned parameters? Yes. Am I still hand-tuning more parameters? Also yes. I have a few knobs to address the…
Sep 26
DIY Robocars via Twitter
RT @a1k0n: I'm not going to spoil it, but (after charging the battery) this works way better than it has any right to. The car is now faste…
Sep 26
DIY Robocars via Twitter
RT @a1k0n: Decided to just see what happens if I run the sim-trained neural net on the car, with some safety rails around max throttle slew…
Sep 26
DIY Robocars via Twitter
Sep 24
DIY Robocars via Twitter
RT @SmallpixelCar: @a1k0n @diyrobocars I learned from this. This is my speed profile. Looks like I am too conservative on the right side of…
Sep 24
DIY Robocars via Twitter
RT @a1k0n: @SmallpixelCar @diyrobocars Dot color is speed; brighter is faster. Yeah, it has less room to explore in the tighter part, and t…
Sep 24
DIY Robocars via Twitter
RT @a1k0n: I'm gonna try to do proper offline reinforcement learning for @diyrobocars and throw away all my manual parameter tuning for the…
Sep 23
DIY Robocars via Twitter
RT @circuitlaunch: DIY Robocars & Brazilian BBQ - Sat 10/1. Our track combines hairpin curves with an intersection for max danger. Take tha…
Sep 22
DIY Robocars via Twitter
RT @SmallpixelCar: Had an great test today on @RAMS_RC_Club track. However the car starts to drift at 40mph. Some experts recommended to ch…
Sep 11
DIY Robocars via Twitter
RT @gclue_akira: 世界最速 チームtamiyaのaiカー https://t.co/1Qq2zOeftG
Sep 10
DIY Robocars via Twitter
RT @DanielChiaJH: Always a good time working on my @diyrobocars car at @circuitlaunch. Still got some work to do if I’m to beat @a1k0n howe…
Sep 10
DIY Robocars via Twitter
RT @SmallpixelCar: My new speed profile for @RAMS_RC_Club track https://t.co/RtLb7TcgIJ
Sep 10
More…