Skip to main content

Mapping component does not take pictures in entire outlined area.

Comments

17 comments

  • Jim McAndrew

    Can you share a link to your mission plan?

    0
  • A

    Hi Jim,

    I didn't have the one in the photo any more, so I just made a simple plan that has the same symptom.  

    https://app.dronelink.com/alan-beverstein/bug-report-example-for-dronelink/plan/TQV6eZr0YFI6srGh4SRH/r5lDMyjxBspavKJwgljq

    That is one is doing the same thing on the first few lines and a couple towards the end.

    Thanks for the quick reply

    0
  • Arizona Wyldwest

    The mapping mission don’t take take photos at the end of each path. I’m still very new at mapping but doesn’t seem like there needed while turning around since the photos should cover what is needed. Jim can explain why or maybe a better way to get more coverage at end.

    One way is to turn the capture mode to off in the map. Then just add a component for the camera and add a list at the very beginning of the plan. This way it will start capturing photos every 2 seconds or what intervals you want from start to finish. If you run the mission preview on this setup you will see it captures continuously throughout the mission. 

    I checked your plan and charged it for you to look at. 

    Good luck. Mike….

    https://app.dronelink.com/wyldwestaz/forum-missions/plan/LQHp8kDig8cwwDE5Rd0E/XtqrqMWbc9zNSUlZbpYR

     

    0
  • A

    Hi Mike,

    If you run the preview of my flight plan you will see it doesn't take photos up to the edge of the area.  Refer to Original Post to see the footprint of the camera that the preview provides  In that example in my first post you can see it still has a fairly large portion of the line to fly but no more photos are captured (By eyeing it I would say that particular line needs 2 more photos to cover up to the edge of the mapping area with my overlap set to 35%).  I want photos that go up to the edge of the area I created, and not on the transition lines that are outside the coverage area (I think that is what you thought I was asking for).

    I appreciate you looking at it, but interval is not going to work for me.  As I don't want to miss an inch of the covered area and I don't want to have an over excess of photos that overlap (setting a higher overlap also fixes most of the issues, but I don't want high overlap).  Interval mode is to much trial and error for my purposes.  

    Imagine counting birds in a photo zoomed right in to see species, egg count, etc.  Then go to the next photo and count them there.  Some areas are only an acre with 1000's of birds.  With the amount of photos your mission set, it would be very difficult to not count the same area twice.  I am trying to avoid a lot of post processing, which would be required using interval.  As I mentioned I can just make the map a little bigger to compensate as well.  But that wouldn't work well if I was using On the fly mode to mark my area, which is a potential possibility.

    To me it feels like I am doing it wrong or there is a bug.  As drawing a box and asking that area to be map, all photos in my mind should cover that area.  Regardless if I set 10% or 80% overlap.

    Dronelink is proving to be a very powerful piece of software.  I do really like it, and this issues is by no means a deal breaker.  But its competitors don't seem to behave this way, and I have tried them all.  Figured it was worth bringing up, since DL has way more options and its likely I have overlooked or don't understand something.  I am hopeful it is user error and look forward to a solution.  

    Thanks for having a look.  Really appreciate it, but unfortunately your solution doesn't quite meet my needs.   

    Al

    PS.

    Just modded the photo I original added just to show you what I mean (sorry for the lame attempt at photo editing ;)  But the red area is not being photographed at all.  Since the blue box is the outline of the last photo taken on that line.  

     

    0
  • Arizona Wyldwest

    Ok. I understand the area your asking about. I don’t believe this is a bug in the app tho. Mapping uses photo intervals which will overlap for stitching together in processing. You can just extended the map a bit to easily cover that area. I’ll let Jim figure this out for you tho. I’m way to new to mapping to help much. I hope it works out for you tho. Great app. Good luck.  

    Added note: It shows in the plan preview the photos are being taken all the way up to the end and not back as you are indicating. Here is where the last photo will be taken at the end of path in the preview list. You can see it’s almost right up to the end of path in the second screenshot. The stop capture is right at the end of path. A slight adjustment to the map will give more coverage if needed. I’m not sure what those red dots are for but that’s not the photos. This plans indicates 211 photos.

    Maybe there is a misunderstanding of the mission preview. If this doesn’t help then I apologize. I’m Just trying to help. Best of luck and enjoy…

     

     

    0
  • A

    Mike,

     

    Thanks for playing around with things.  Your last post demonstrates to me that you were able to recreate the issue I was bringing up.  As you can see in the bottom line on the left side there are at least two photos missing (left of ‘22’).  The line above shows generally where the missing photos should be.  The same symptom can be seen on other lines as well.  I am sure you are aware that those red dots represent every time the drone is told to take a picture.  The position of the red dot are placed by the map function taking into account the parameters you set (overlap, camera type, alt, etc).  Therefore, you would expect the photos to be fairly similar from line to line. 

     

    As I mentioned before you can fix the problem both with increasing overlap and making the map larger.  For a hobbyist that is a simple solution to this issue.  If you want to fly in your backyard and get a nice ortho of your property, you have all the time in the world to find mistakes in your mapping and making adjustments to your map.  Adding 5 - 10% extra flying is not an issue if you are making one map.  

     

    If you want to do this on a large scale commercially, this solution is only acceptable if you have no other option.  There are days we do 20 maps, half days drive from our processing computer.  Preplanning only kinda works, as when you get to the job site you may need to change the direction of flight for various reasons.  If on one of those maps you forgot to add the buffer to your flight lines, it would mean having to drive back and redo the work at no cost to a client.  

     

    Extra time to a flight of a couple mins because you have to make the map a larger area than you intended, is compounded to an extra hour or two of flying when doing 20 flights. This becomes a problem as you drain batteries faster than you can charge them.  More battery usage means having to have more batteries on hand ($200 each in my currency).  There is also an extra cost in the business account of dronelink.  If you get their growth package, you pay for each minute of flying.  At time of posting its $0.60 a min.  For obvious financial reasons we would want to keep our flying time as efficiently low as possible if we transition to using Dronelink for our clients.  As every extra hour of flying is going to cost $36US ($43.50 cdn).  

     

    Every spring we have a look at the various pieces of software for mapping.  Give them a few tests and decide how to move forward with the year.  Changing software of any type for a company can be a pain in the butt, there has to be a good reason to do so, if what you currently  have is doing the job.  As I mentioned Dronelink is very good, and offers a lot of advantages.  That is why I am bringing this issue forward.  Usually I would have said nothing, stuck to what I know works, and waited a year to see if the issue is fixed.  

     

    Thanks again for your time in trying to figure this out.

    0
  • Jim McAndrew

    It appears to be a bug that was overlooked / masked because most people use much higher overlaps. I am looking into it.

    0
  • A

    Thanks Jim! 

    0
  • Arizona Wyldwest

    👍🏼

    0
  • Jim McAndrew

    After further investigation, it appears that this is just a bug in the mission preview. I released a fix for it if you want to refresh.

    0
  • ticotico

    Hi

    I seem to have a similar issue, that might be related to this.

    The mission plan is here: https://app.dronelink.com/ticotico/my-first-project/plan/X7ljyJ5kOUgGm1QdV4OD

    Looking at the pictures that were taken by the drone, I think that the camera on and off might have been reversed: Basically I only got pictures from the uninteresting areas and **no** images on the actually interesting area that I wanted to have mapped.

    In the mission previewer it looks fine, but the images take by the drone are unfortunately unusable.

    Too bad that I only noticed this (bug?) once back home without any access to the field now!

     

    0
  • Jim McAndrew

    Are you able to reproduce the issue every time?

    By the way, if you are flying for business you need to be on a business plan.

    0
  • ticotico

    It happened with two missions. Any ideas why that happened?
    I am using the personally and intend to use it for research.

    0
  • Jim McAndrew

    It is possible that we command the drone to start capture, and the DJI SDK reports success, even when there is actually a failure.

    0
  • ticotico

    Hm, sure it could be the SDK behaving weirdly...but it is kind of consistently weird, as if start and stop recording would be the wrong way around.

    0
  • Jim McAndrew

    consistently weird

    The question is: how consistent. Does it happen every single time or just sometimes?

    0
  • ticotico

    2/2...I will do another mapping test in the upcoming days and will let you know if it happens again.

    0

Please sign in to leave a comment.