Hi guys I have been encountered with this problem for a long time and still haven't solved yet.

The major problem of geotaging not working in FireFLY 6 Planner seems to be the numbers of both pictures taken and log data do not match out as the same.  I always see more log data being read than the images being read. (You can see the picture below that shows log read : 484, image read 470.)

I have bought many of this DIY products and still haven't received satisfied solution from this company. (It seems they do not provide technical problems for the customer support to DIY UAV purchasers). Any of you guys have encountered this problem? and anyone has solved this?

I have read many forums some suggestions that I had were

: Change SD card because it may read slower when the drone takes the pictures in automatic mode.

: Change certain value of the log file.

I haven't still found a solution to this problem.

Please help for this frustrated situation.

3691331020?profile=original

I really appreciate for your comments and advices !

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

Join diydrones

Email me when people reply –

Replies

  • Charles,

    I have not used Pix4D Mapper as I have access to Photoscan Pro for SfM (point cloud reconstruction). I do not routinely use Geosetter although some think that is good practise. I tend to use it only if MP fails. The issue of accurate position for your images is a different matter. Using standard GPS these will always be inaccurate. For our AP work we use GCPs measured at present with a single frequency dGPS (accurate to ~4cm if you are lucky).  When alignment is done it is clear that the standard GPS in the UAV is very poor or more likely the time of shutter release is poorly recorded. A better solution (which we are about to deploy) is to use a dGPS system on the UAV (we have both  emlid reach [ https://emlid.com/reach/ ] and a drotek [ https://drotek.com/shop/en/drotek-parts/762-l1-rtk-gnss.html ] system). We have also now switched to a sony A6000 (i.e. a compact camera with hotshoe) so that we can record shutter release time using one of these ( http://www.tuffwing.com/support/reach_geotag_event_hot_shoe_cable.html ). We hope this will give us better accuracy on the images and eventually cut out the need for GCPs (everyone is searching for this!).

    Hope that is of interest.

    Darrel

    Reach M+
    Reach M+ is a compact and affordable GNSS RTK module for precise navigation and UAV mapping. Centimeter accuracy without GCP for $265.
  • Darrel,

    You have given to me such great resources!

    Geosetter seems to be an alternative solution to the Mission Planner that has inaccurate geo tag functions. I currently do have Pix4D Mapper Pro to geo tag the images, however, I am not sure which software to use among Geosetter, Pix4DMapper Pro, and Mission Planner. I want to find out which could be the best solution to use for geo tagging. Could you tell me if I think for each characteristic of program is right?

    • Pix4D Mapper : I know how to geo tag with Pix4D mapper but I am not sure if it is fairly accurate. I am not sure Pix4D Mapper is better than Geosetter for geotagging because I have never used geosetter.
    • Geosetter : Seems to be popular because they are accurate, however, manually checking the geo tagging images take some time.
    • Mission Planner : Originally people used the most but many errors have been occurred for geotagging and program is not stable. two options : time offset : very inaccurate to geo tag , CAM message : there are errors for reading the numbers of log and images.


    I hope this discussion gives many feedbacks to everyone and helps for people who have troubles with geotagging and want to find out the best way to geo tag. Lets discuss about this topic because I know everyone wants to find out the solution!

    Charles Kim.

  • Charles,

    I have also had this problem a number of times and not yet resolved a solution. I turn to geosetter ( http://www.geosetter.de/en/download/ ) when I get this. It also has problems but sometimes I get a satisfactory solution, There is a nice video here ( https://www.youtube.com/watch?v=QXBNRqo6q8E ) if you have not used this before,

    I will watch this thread with interest

    Darrel

This reply was deleted.

Activity

DIY Robocars via Twitter
Sunday
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…