An overview of my workflow: Manual 3D Mapping

[RPR]

Flying the H Plus after a couple of modifications on Build 822 is now as solid and it can be. Today, I got bored, so I decided to manually capture my assigned asset for 3D mapping, and letting the H Plus do the caching.

Here is an overview, when I am doing an asset management report. Disclaimer: I don't map with my TH Plus, but here's an example that manual mapping is possible, without the aid of an app. For manual mapping, I record a video, while flying over my grid. After my mission, I convert the video using Video to Image Converter (for MAC) and export/convert an output file to TIFF every 4 seconds, this will give me an overlap close to 70% edit the photos in Lightroom, save as jpeg, when finish editing, and set coordinates to the photos in Geosetter.

Enjoy.......

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[claudius62]

Hello RPR, That's what I do with the Inspire, I film the subject in orbit from the lowest to the top by getting closer to the center. I film at 50i / s and then by adobe first I output the images by exporting the media in JPEG in frequency image 1 (1 frame per second) so on a media of 2 minutes, I get 120 images. I look at the overlaps and delete intermediate images if necessary, then we can do a 3D modeling.
I prefer this solution to that of the photos, because the camera is always centered on the subject and therefore less worries of reframing.
Now, I will be able to do it with the H520 since it has the orbit and also the ROI that we can use in manual.
some examples

Nice Job.

 

[RPR]

Hello RPR, That's what I do with the Inspire, I film the subject in orbit from the lowest to the top by getting closer to the center. I film at 50i / s and then by adobe first I output the images by exporting the media in JPEG in frequency image 1 (1 frame per second) so on a media of 2 minutes, I get 120 images. I look at the overlaps and delete intermediate images if necessary, then we can do a 3D modeling.
I prefer this solution to that of the photos, because the camera is always centered on the subject and therefore months of worries of reframing.
Now, I will be able to do it with the H520 since it has the orbit and also the ROI that we can use in manual.
some examples
View attachment 16245View attachment 16246View attachment 16247View attachment 16248
Nice Job.

Nice work, man. I also used to do it, with my Inspire, it’s quick and fast, at times, with the aid of litchi.

I have been keeping tabs on the H520 specially on how it handles its cache. I still can’t trust doing oblique via obit or systematic positioning, with my H Plus, without relocating to capture by frames, and I’m trying studying the orbit’s limitations, with the H Plus.

Wishing that Yuneec would give the TH Plus the ability to map, and solid connection like of that seen on the H620, because this drone has a lot to offer.

Nice work, btw.

 

[RPR]

sUAS: Yuneec Typhoon H Plus
Camera: C23

 

[RPR]

@claudius62

I have been talking to this gent in the CommercialDrone Pilots, and thrilled to learn that instead of creating geotagging through geosetter, it can be done via TLOG and script. Here's what a TLOG telemetry looks like.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

What is great about doing this, specially for us doing manual mapping it that this make our workflow faster, and more accurate than creating markers, and in occasion, stitching photographs due to rolling shutter blur.