Map grid component...
I would like to do a grid path to capture an outdoor shopping area that will be torn down and see if I can make a 3D model of it.
I was reading on the Pix4D site that for a cluster of buildings or city scan with visible façades, you want a grid path and a camera angle of between 10 and 35 degrees from straight down. So that seems to be 55 to 80 degrees from horizontal.
So it would rock if there was a grid map component that also had an input for camera angle - perhaps with a few selectable common settings.
Also, it should allow you to set the percent overlap of frames, as there is also guidelines for that also, and I am not sure how to calculate it.
And when you set the altitude, it tells you how many inches per pixel. It would be nice if it indicated this in inches and cm at the same time.
Also, the map component says that Mavic Air has a 4mm focal length. I believe it is actually 4.5mm.
Comments
8 comments
Expand the advanced settings on Map component.
I see. Thanks. That is working.
Would it be possible to show flight time right there? I know my maximum flight time from Airdata, so I would like to be able to play with map settings until I can do it within the battery limit.
It's in the mission preview.
I know but going back and forth is cumbersome and so I want to be able to slide around the grid and see the time change as I do it so that I can pick a grid size that is within the flight time limits or also when I change any map component setting. And likewise a change in the map component height or overlap setting could also update it. Or for that matter, any mission could always show the flight time somewhere on the screen without having to do a formal preview.
If you need to change battery Dronelink will continue where you left.
The mission preview produce a millisecond accurate time estimate but this is of course at a cost of several seconds of intense processing. It is possible to generate less accurate estimates in a shorter period of time, but there will always be a trade-off between speed, accuracy, and providing a fluid user experience when doing things like dragging waypoints around and seeing the path warp in real-time (the path estimate is the same code as the time estimate). What level of accuracy are you okay with in the real-time case?
How does one change the battery and continue the mission? Would you put it into sport mode, land, then remove battery, then take off, then do what? Push play again?
Within 30 seconds would be accurate enough for me for a real-time estimate just to give an idea if it could be completed on one battery or not.
Please sign in to leave a comment.