I was looking at this post http://diydrones.com/profiles/blogs/maps-made-easy and am looking to get into mapping with an Iris and currently have a GoPro Hero3+ Silver camera.

I am thinking of either changing the lens to remove the fisheye or distortion, or buying a Cannon camera to use CHDK.

Here is a blog post about about changing your GoPro lens .

I am leaning towards buying a Cannon camera because I think you have better control over the images with CHDK and no distortion.  This Cannon SX 230 HD has built in GPS.

Anyone have any tips on mapping?

How do you get your pictures to overlap?

What is the best height to fly at?

Can anyone point me to a "mapping 101 for drones" webpage ?

Thanks :)

Views: 6213

Replies to This Discussion

Doug-  It seems the nice folk at 3DR customer service may say things they perhaps ought not to. My Iris Tarot gimbal, that came in a nice 3DR-labelled box, weighs-in at 284 grams with gopro. See this link for weight on the scale. My Iris will fly about 15 minutes with that rig while scanning a roof or taking other shots. It has never labored or struggled with that payload, (plus the video transmitter & antenna), btw.

Unless 3DR examined your tlogs and other data from your Pixhawk, its them guessing as to what caused your crash. My first Iris unit's crash was caused by a IMU fault that locked-up the pixhawk while coming out of follow-me (guided) mode. That was the extensive log analysis results from 3DR.

I do like your ortho images. 

When you were using the Canon, did you use the KAP-UAV script whilst running the camera under CHDK?  That script will essentially prevent blur in nearly all daylight lighting conditions...its well designed and constantly updated.

With so much control over all aspects of the aerial photo shot that I cannot get with a GoPro on auto mode only, I'm going to primarily use my Canon when I can. I've got my Nadir mount and the stock GoPro fixed mount on the Iris and use both. 45 degree angle shots of the structure with the camera on the GoPro mount, and straight down (using the Nadir mount) with a structure scan using a cross hatch pattern. Scan time is less than 15 min depending on flight speed..... and processing time, well, a few more hours on my Sony Vaio-L desktop with an i7 processor.

How heavy was your Canon rig? What camera were you using?

They looked at tlogs and told me not to fly my S100 under my Iris+ as it was too heavy.   That's what they said.

I was using the KAP-UAV script - and never, not once, could I get consistent un-blury photos.  I wasted days trying - and there's many a thread in this place and elsewhere talking about people having the same problems.

The GoPro solution is lighter, easier, more reliable - couldn't be happier. :)

Do you have your GP mounted on the gimbal?
I also note the S100 weighs 170 grams. Mine is newer and lighter, significantly.

iso 100-400, shutterspeed 1000-2000, infinity focus do the trick

even a ixus160 which is dirt cheap at 50 bucks gets more decent pictures compared to gopro imho!

I use a Sony RX100 with no gimbal (Nadir view) for aerial mapping. With my Iris+ I get maximum 10 min. But I must say my batteries are not so young now.

I always wondered how could be the quality of Gopro based mapping.

Nice!....1 inch 20mp sensor and 213 grams....what mount do you use? Something from impconcepts.com?
Man I'm envious.

Very simple : under the Iris 3 bolts holding a plastic plate, intermediate 1 cm thick piece of foam for vibration, and RX100 hold by its extended strap around the Iris body.

I also use a Sony RX100 without gimbal on the Iris+ (I use a Canon s100 in the same way). I made a simple interface plate out of thin plywood that allows the camera to be mounted with the top facing forward. The interface plate is attached with velcro straps that thread through the vent slits on the Iris underside. Velcro straps also hold the camera to the plate. I trigger the RX100 with a module from Mobilexcopter. The camera mount adds very little weight, and the slight angular variations during flight are of no significant consequence for processing.


© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service