Map Component - Multiple Camera Angles
This may not be practical due to timing issues among others. But I thought I'd ask.
Is it possible to get the mapping component to add multiple camera angles to auto capture.
EG Capture the -90 Degrees straight down for normal mapping, but also take two additional shots before the next straight down shot one at -70 to the left, and one at -70 to the right. These do NOT need to be at the same drone position as the -90, and if fact would be better if they are all are taken from different locations.
The straight down shots are perfect for making orthomosiacs, but if obliques were captured at the same time that would mean a single flight would make 3D model with the sides of buildings/trees captured as well.
I think a sideways left-right tip would be the way to go for the majority of drones.. but I don't know how long it would take to orientate the camera, or if we are getting into 'it takes too long to save that many photos' territory.
Extra Awesome: If an oblique could be taken facing forward as well. This would increase the number of photos captured on one flight to 4 times the current number.
Comments
5 comments
You could do this now by planning multiple map components on top of each other with different angles programmed. As far as the feature request, are you wanting the drone to stop at each point and take all the pictures (ideally)?
Dropping several maps over the top of each other would generate the images I'm looking for. But would triple the flight time. The idea is to maximize the data collected in a single flight.
My ideal result is that each picture was NOT at the same point. Photogrammetry needs movement between each picture to help eliminate error.
The pattern I have in my head is to keep the vertical photoset exactly as it was, but to put a left oblique and a right oblique 30% and 60% of the distance between the vertical shots. That should mean they have the same overlap as the vertical shots.
Here is DJI's ad for their (very nice) enterprise gear doing what I'm trying to describe. https://youtu.be/91fTUg6Y9hk?t=80
Glen, it sounds like you're asking for something similar to what the senseFly S.O.D.A. 3D camera can do, in addition to the Zenmuse P1. I agree this would be an awesome feature to add to Dronelink for photogrammetry work.
I honestly have no idea if the gimbals on most drones are set up for this quick type of movement... might not be possible on consumer-grade drones. I also wonder if we can reliably tilt multi-rotor drones the way you suggested, and stay on course? For example, taking photos with 80% overlap, flying ~28 km/h at 60m height off the ground. I'm not sure you can fit that many movements in between each nadir photo, unless you slow down the flight. The next best alternative would be what Jim suggested. It would take more time to fly, but so would slowing down a single flight to fit in the extra gimbal or "tipping" movements. I really love this idea though. How fast can Phantom or Mavic gimbals move to the desired yaw/pitch using code? If it's a fraction of a second, I think this is a winning concept.
Did you have any followup on this Jim? Just wondering if we can expect to see this feature in the future.
We are planning to give the Map component some love in the future, but working hard to get Modes out right now.
That's exactly the sort of thing I'm looking at Greg. I've had a bit of a go at trying to build a component to take a photo set each "shutter press" much like the SODA does (I'd forgotten it :) . I don't want to add it to a flight path a few hundred times, but I figured it could work as a proof of concept :) and may make Jims/Other Devs' lives easier if there is a working example (or not if its total junk :) )
I was trying to make it for my little toy mavic mini that doesn't have any sideways rotation on its gimble. There is a limitation on mechanical rotational speed on both the RPAS reorientation and the gimbles that appear similar, so I'm going to stick with trying to make it go, but I could borrow a P4P from work if it looks like the gimbal will work better.
It looks like it will take about a sec to re-orientate the 90 degrees. Which means if you are needing a photo down every 2 secs or so its gonna be tricky. But the overlap you need on the obliques is much less than the forward overlap you need on a vertical shot, so my refined (and not at all implemented) plan for the component was: Vertical Photo - Left Oblique - Vertical Photo - Right Oblique. Timing will still be tight.
Please sign in to leave a comment.