Hello,
my question is why not let user to fly higher speeds if using STI (stop to image) feature?
For instance, I was flying linear mission with 85% along track overlap at height of 60 m (P4Pv2 running MPP 5.4.2 on iPad mini 5).
STI option was on, so for best productivity MPP would let me to fly at 15 m/s between points. However, it let me to fly between image points no faster than 4.5 m/s, which unreasonably limited my productivity.
Can you, please, correct this undesired (by many I think) low speed for STI-enabled mission?
Regards!
We have already technically sped things up between the dots but the faster you go the longer it takes to settle. The end result being that it actually takes longer to execute a set of points.
Please sign in to leave a comment.
Zane, thank you for kind explanations.
Well, drone hardware limitations are definitely the strongest factor.
Pity that overall STI-mission speed is greatly reduced compared ti 15 m/s limit even in case of very low along track overlap. For instance average mission speed was aprrox. 4 m/s when I was flying linear mission with as low as 5% along track overlap at height of 50 m (P4Pv2).
Hi Zane
Thank you for kind clarification, it sounds very reasonable.
I have another comment. Today I flew several 1 pass linear missions with STI and very low (5%) along track overlap. Unfortunately drone stopped not only at points that allow for target overlap of 5% but also at every node (line vertices) of line and took photo. As the result I got 20-30% extra stops and subsequent reduction of average drone speed during mission.
I hope I don't sound picky but this may cause reduction of daily productivity.
Would it be possible to prevent drone from taking photos at these excessive locations at line vertices to avoid average speed reduction?
Thanks.
Each point in STI is a waypoint and we are using a DJI waypoint mode that stops at each waypoint. This means it will stop along linear paths, at the corners and at terrain inflection points.
I can see how this might cause an issue in super low overlap situations but in most cases it doesn't matter.
Thanks for explaining.
However, spot check missions in MPP also uses DJI waypoint mode (not sure), but it does not get excessive stops and photos. Sampling missions also avoid excessive stops and photos to get correct aerial sampling ratio.
I may try switching to spot check missions to solve my issue though.
For your specific case it is not something we can fix without redoing how STI is done. The goal for STI was to create a regular grid of dots to image from. For linear missions we have to reset the spacing at every vertex. Otherwise what would we do?
It sounds like the spot check mission will be more what you are looking for anyway.
"It sounds like the spot check mission will be more what you are looking for anyway." - Thanks for clarification. Is it possible to create spot check mission from imported kml, just like can be done with linear and polygon missions? It saves a lot of time.
Are there any plans to make "linear" sampling missions possible in MPP?
As of now you have only polygonal sampling missions available. Sometimes people need to subsample linear objects as well and may use this feature. Spot check can accomplish this but operator will need to do more manual work to prepare mission (sampling spots allocation in desktop GIS).
Noted here:
https://support.dronesmadeeasy.com/hc/en-us/articles/211429163-Opening-a-KML-from-Email
"As of version 4.1.10, you could also define a polygon, line string, or set of pushpins in Google Earth and import it into Map Pilot as you normally would (via Email or AirDrop) but rename the file from sample.kml to sample_boundary.kml to import as boundaries and linear flight plans. Adding the _boundary to the filename tells the system to import is as boundary definitions instead of just guidelines. The imported data will show up in the File Manager screen. "
