Collin,
I have a small fleet of 6 Typhoons, some Q500's, some 500+s and some G's... all have the same limitation in that they dont geo-tag stills taken. What they DO have, is the ability to record flight data if you install a microSD card on the ST10 flight controller. Do this first. I have 4 GB cards in mine, that is enough to store flight data for a LOT of flying. You dont have to do anything to turn this recording feature in, the ST10 recognizes the presence of the microSD card (formatted FAT32) and begin storing flight data there as soon as the ST10 is properly powered up. I am finding that 3 sets of .csv files are recorded, and they all open up in MS Excel quite nicely and cleanly.
The DateTime format used by the ST10 is not a popular standard so I have put together an Excel spreadsheet I will share that has the formulas in it to 1) convert the Yuneec DateTime to a more common Excel format and one popular with other applications, and 2) convert altitudes from how they are recorded to what my mapping software uses. I have done this a dozen times now, but still consider this a testing phase because I want this to dump into several different mapping applications and services. When the Excel spreadsheet is done, it produces new columns that are directly readable by the next piece of this workflow - to create a 'synthetic' .gpx file - what Yuneec should have been recording all along. At least they do record flight data at about 3 Hz on the controller and about 5 Hz on the aircraft. If this works with the Typhoons... it should work with the H as well (my small company has one on order, but we have accomplished SO much with the original Typhoons we havent needed to purchase the new one at entry pricing).
Go get this first step done on your controller... and Ill work on finishing up my write up... but so far, I have extracted flight logs from all of my Typhoons... and ended up with successful composite maps from Pix4D Mapper, from MapsMadeEasy.com, and soon, from Propeller too.
The work flow is - collect the ST10 flight data, correct the format of the DateTime column and convert altitude (units) as needed..
Then use this .csv file and one of three different applications to generate a synthetic .gpx GPS file...
Then use another application to time sync the stills to the flight log, extract the GPS data and geo-tag the individual images to make them ready for mapping.
It sounds like a lot of work, but its really batch processing and takes only minutes per project... I 'have' found a few completely unexplainable bugs... images that for no apparent reason get geo-tagged Lat = 0, Lon = 0 when 150 other images taken in the same mission get tagged correctly... no clue as to why [yet]... but easily gotten around...
More later.
DocV
North American Robotics