T3

An example of automated photomapping:

typical GPS precision plus turbulence gives around 10-15m precision.


After spending one minute on manual adjustments:


This is what you have after importing automatically, without any manual adjustments, IMU corrections included but the major factor is that the camera is already almost vertical and the platform is stable:




Since the protos are taken with roll-stabilised head using Pteryx UAV,

they are ortorectilinear as the shooting angle was at worst a few deg relative to vertical.

FLEXIPILOT log decoder now take camera lens angle and mounting offset angles as a parameters, generating Google Earth file with matching photos within seconds! This is particularly useful
for isolated shots, since overlapping images when mapped in quantity give an impression of 'randomized crowd'.


Another approach: Microsoft ICE and 10min processing after drag & drop:

Unfortunately the image is a little skewed.


The major benefit of stabilised head is that all photos are of acceptable geometry and useful for stitching. However, because the precise moment of taking the photo cannot be known, an important angle and positional error will always be present in the logs. Another factor to include is changing lighting and altitude, inevitable in real-life operation and during turbulent weather (this time 42km/h flight speed and 20km/h wind speed plus strong thermals affecting pitch).


Automated mapping (AerialRobotics LogDecode) applied to a linear map:

E-mail me when people leave their comments –

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

Join diydrones

Comments

  • Moderator
    Well done Chris, you are moving forward with an elegant airframe and perhaps more importantly, imaging solution. I think that might just put Flexipilot at the top of the pile at the minute.
  • Thanks for comments and hints. I have been using ImageMagic on a few occations. The problem is I forget the programs syntax between each time I use it. (Must remember to write the commands down in a bat-file next time). The Advanced JPEG Compressor I didn't know about. May need to take a look at that one too.
  • T3
    Yes, resizing is a good idea, EasyUAV software manual also mentions ImageMagic for batch resizing.
  • @brakar, Have you tried using some tool like Advanced JPEG Compressor? I use it to batch compress photos before loading them into Google Earth or Global Mapper. You can tweak the setttings, but the default settings generally cut the file size by 80 - 90% with no reduction in resolution and no noticeable loss of detail. Your 6MB photos would be less that 1MB.

  • Think I will get used to this tool, and later wonder how I did manage without it. Incredible usefull with regard to inspecting results after a photomission. Only regret that GoogleEarth crash after loading some 100+ images (6MB each), probably due to insufficient memory on my laptop. Hence, only 4 of 11 stripes of photos are shown on the attached image.
  • T3
    Thank you for the comments. What you see this doesn't means my business is data processing - the decoder has been made 'because it can be done and it had to be done'. In practice it is available as a basic log processing tool for FLEXIPILOT+family, which in turn used only in ready-made UAVs.
    The project is spinning slowly but steadily:
    one of the tasks in the field is 'was the photo coverage sufficient and should I repeat the mission, quick'.
    This software answers that need.
    Instead of a user looking at blinking green dots on a laptop screen and counting the photos, I have opted for post-processing told. Note this procedure also works during simulation, it will just generate translucent, empty boxes as no corresponding images from the camera will be found.
  • Moderator
    Top banana
  • Brilliant! Should be great way of presenting photos for inspection purposes etc.
  • Outstanding! Will this be a product you'll be selling?
  • Moderator
    Love it!
This reply was deleted.