Hello!

We configured a mapping mission with overlap 80/80 + buffer 35m. Flight speed 7m/sec @90m AGL, GSD 1cm/px

After we flew the mission, the calculated overlaps end up much lower than configured : 72/73 ( which create issue with AI/ML processing of customer )


Any idea what could cause this? The mapping was above a field of approx 10x400m ( main reason we added 35m buffer ).


Regards,


AR

Are you sure the M300 was flying at the planned 90m AGL? On my last flight(2 weeks ago after the recent firmware update) using DJI Pilot2 I planned a flight for 250ft AGL and it flew at 215-220ft AGL. Thats nearly a 10 meter difference and caused me to refly the site on a future visit. I have been using UGCS for flight control for years but wanted to try DJI pilot2 again due to being in very close proximity to an airfield and UGCS does not support airsense for real time manned aircraft detection. I have since switched back to using UGCS exclusively.  I would compare your exif data to that of one of your ground control points to see what the altitude the M300 was actually flying.

JesseG Posted at 5-17 15:59
Are you sure the M300 was flying at the planned 90m AGL? On my last flight(2 weeks ago after the recent firmware update) using DJI Pilot2 I planned a flight for 250ft AGL and it flew at 215-220ft AGL. Thats nearly a 10 meter difference and caused me to refly the site on a future visit. I have been using UGCS for flight control for years but wanted to try DJI pilot2 again due to being in very close proximity to an airfield and UGCS does not support airsense for real time manned aircraft detection. I have since switched back to using UGCS exclusively.  I would compare your exif data to that of one of your ground control points to see what the altitude the M300 was actually flying.

Thanks for advices, will check that.
I was using "terrain follow" I wonder if that could have created the issue...but the terrain was flat-ish ( Belgium is flat )