Thanks for all the interest and support so far. I should have the site up and running in the next week! Still trying to figure out the most cost effective hosting solution. :) I'll definitely contact everyone who has contacted me with interest in beta testing when it is ready. I took a few days off from coding to try and get my 3DR quad flying. It was almost a success until a tethered flight in the garage went bad! Lost a motor and some props, waiting on parts now. :)
Progress on each workflow/UAV:
Pteryx UAV - 9/10 completed. (.csvp)
MAVinci UAV - 9/10 completed. (.csvm)
ArduCopter - 7/10 completed. (.log) accuracy isn't the best / (.gpx file is lacking compass/heading info)
(blended mosaic has trouble from forest coverage, fewer auto detected control points. it does better once resolution is turned up)
MAVinci Sample Imagery Processed! :D Very big thanks to the MAVinci team and the support they have given me! It has been very helpful in improving the MAVinci support and making some nice maps. They have a couple of really nice sample imagery sets at the following link: ftp.mavinci.de
The processing will work with GPS EXIF enabled images or not. I don't have access to non-GPS enabled images and the associated flight logs so I haven't coded this fully yet. It supports Canon and Panasonic camera's at this point, as this is all the sample imagery I could get a hold of. I can certainly add the code once I get additional camera and imagery formats. So keep an eye out for that..
Issues/Problems:
* blended mosaic isn't georeferenced
* control point detection isn't the best in forest, desert type areas
* ie css/browser issues
* unfinished non-gps enabled imagery workflow
* a bunch of others
I also added a interface to open source bundler, which will create 3D point clouds from the images. Once completed you can download the ply/pointcloud bundle as a zip file and do as you wish. Most of the following workflow: http://diydrones.com/forum/topics/making-digital-elevations?xg_source=activity Thanks Mark!
Comments
@Chris Thanks Chris. I am not using those files in my workflow for Ardu. I will take a look at reworking the process. Thanks for the heads up!
JP: on ArduCopter/ArduPlane you should be using the tlog files (which are recorded on the ground, via telemetry), not the log files (which are recorded in dataflash on the board). The tlog files are much more complete and have the fields you need.
Users can turn on those extra fields in the log files, if they want, but they're off by default to maximize datalogging time. On the ground that's obviously not a constraint.
@Irvin Thanks so much! I will be in touch next week. :)
JP,
Looking forward to trying/testing your DroneMapper Aerial Image Processor tools.
We have non-GPS, Canon EXIF, .jpg images, .log, .tlog, and .log.gpx files ready for processing.
-
1
-
2
of 2 Next