# Micasense Troubles
**URL:** https://community.opendronemap.org/t/micasense-troubles/12388
**Category:** OpenDroneMap Desktop
**Created:** [July 18, 2022, 12:38am UTC](https://community.opendronemap.org/t/micasense-troubles/12388 "2022-07-18T00:38:59Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@mdk](https://community.opendronemap.org/u/mdk)
#### Post date: [July 18, 2022, 12:38am UTC](https://community.opendronemap.org/t/micasense-troubles/12388/1 "2022-07-18T00:38:59Z")
I flew a micasense mission over a patch about 500mx400m at 60m elevation.
The mission had 80% overlap. I ended up with 8200 images or so.
WebODM runs the process just fine but there are gaps in the resulting mosaic and blurred areas in the remaining coverage.
I have processed micasense before with no issues from about 80m elevation.
It was windy the day I flew and the drone was tipped forward as it headed into the wind maybe 15 degrees. Could this be causing my issues?
I have tried removing the rows headed into the wind with no better result.
Does anyone have any suggestions?
m
---
### Author:  [@Maurice.Sobiera](https://community.opendronemap.org/u/Maurice.Sobiera)
#### Post date: [July 18, 2022, 6:32am UTC](https://community.opendronemap.org/t/micasense-troubles/12388/2 "2022-07-18T06:32:00Z")
First, check if the rolling distortion update covers your drone. Next check how many gap filler steps you use. Then check for pc-rectify. This may help you. There are also plenty of similar post with problems like this.
---
### Author:  [@Gordon](https://community.opendronemap.org/u/Gordon)
#### Post date: [July 18, 2022, 6:37am UTC](https://community.opendronemap.org/t/micasense-troubles/12388/3 "2022-07-18T06:37:28Z")
It seems like a very large number of photos for only 20 hectares.
Are the images blurred due to drone speed/exposure time?
---
### Author:  [@mdk](https://community.opendronemap.org/u/mdk)
#### Post date: [July 18, 2022, 1:35pm UTC](https://community.opendronemap.org/t/micasense-troubles/12388/4 "2022-07-18T13:35:47Z")
I don’t see anywhere a description of the rolling shutter update. And wouldn’t it be particular to a camera and not a drone? I believe Micasense cameras have global shutters anyway.
Gordon, it is a Micasense camera so divide that number by 5 imagers. So in my case 8990/5=1798.
Is 60m too low to fly that? I can’t think of why it would matter?
All the images I looked at appear clear (though with the different spectra it is a little hard to tell)
---
### Author:  [@Gordon](https://community.opendronemap.org/u/Gordon)
#### Post date: [July 18, 2022, 11:05pm UTC](https://community.opendronemap.org/t/micasense-troubles/12388/5 "2022-07-18T23:05:40Z")
> [@mdk](#):
>
> Is 60m too low to fly that?
Not at all, so long as your exposure time is short enough to avoid motion blur at the speed you are flying.
> [@Incomplete Orthomosaic](https://community.opendronemap.org/t/incomplete-orthomosaic/9773/17):
>
> During a recent big job under varying lighting conditions I spent a lot of time adjusting shutter speeds, aperture and ISO to avoid motion blur, having to do mental calculations whilst walking over rocky, rough ground and keeping my eye on the drone. So I’ve grabbed an envelope, turned it over and found that for a given GSD the general equation is shutter speed needs to be close to, or shorter than speed in m/s \* 100 /GSD. speed in km/hr \* 28/GSD speed in mph \* 45/GSD For example @ 40km/hr…
---
### Author:  [@APOS80](https://community.opendronemap.org/u/APOS80)
#### Post date: [July 19, 2022, 5:54am UTC](https://community.opendronemap.org/t/micasense-troubles/12388/6 "2022-07-19T05:54:37Z")
I found that Sift works much better when there’s a lot of tricky angles, it does take a lot more time to match though.
---
### Author:  [@system](https://community.opendronemap.org/u/system)
#### Post date: [August 18, 2022, 5:55am UTC](https://community.opendronemap.org/t/micasense-troubles/12388/7 "2022-08-18T05:55:19Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.