- Imagery should have at least 60% overlap and should have at least 20% orthogonal overlap.
- Imagery must be shot in sequence. See examples below.
- Images must contain required EXIF information. [more]
- Images are shot with one camera and focal length.
- Images should not be pre-processed. (i.e. Lightroom, Picassa, etc)
- Images are NADIR or near vertical.
- Flight Path should be Parallel Line (aka Lawn Mower) or other large overlapping style.
- Flight Path should provide sufficient coverage of survey area. Meaning a large amount of overlapping images for target area.
- Flight should be from sufficient elevation. (i.e. >80 meters)
- Try a small subset of your imagery as a test. We process 15 images or less for free!
Flight Mode / Geolocation Guidelines:
- Use a supported Flight Controller with supported export format. [more]
- Sync your camera internal time with your flight controller GPS time. [more]
- Imagery EXIF timestamps must match flight controller log timestamps to obtain rough georeference.
- Flight Controller log exports should be in WGS84 for Latitude and Longitude. Elevation in (m) above the earths surface or actual elevation of image. Camera direction in (d).
- Each image must have a matching GPS/IMU log entry.
Imagery Sequences with Problems:
Imagery Sequences with Good Results:
Hope this information helps all you UAV mappers out there. Cheers,
JP Stoermer
Comments
@Jasja sometimes EXIF tags are stripped out with this type of software. thx
@Joseph, yes, they do disapear as they dont store coords.
Thanks
What is wrong with preprocessing, in your opinion? I've had no problems getting good quality maps from processed images!
@Gareth we use a bunch of different method and techniques. Take a look at gdaldem, gdal utilities and also RunSFM, I have had good luck with these. :)
What software do you use to generate the DEM ?
either use relay repeat, or servo repeat.
or use a camera that had a repeat function, such as canon powershot cameras with chdk