Appreciate the video Rich. Do you have a video or more detail on how to import a texture or obj file from webodm to qgis? I'm getting better with both programs but I'm a bit stumped here.
Not yet. Your question got me wondering about how you could import a texture or obj file, and I've been doing a little reading. I pulled up ChatGPT, and it looks like there is a way, but not working for me yet. If you'd like to do a little investigation as well, here is the question I asked the AI. "how to import a texture or obj file from webodm to qgis". ChatGPT came up with a suggestion, but like I said, not working for me yet.
Hi. Great videos. You said that the model is not that great, as a hobbyist myself, do you mind expanding/explaining how it is different from other platforms model. Thanks again for the great videos.
WebODM does offer their 3D Model and Texture. Together the models coming out look "okay" but never high end like some other platforms. Pix4D, Drone Deploy, Maps Made Easy, and Metashape are a few examples of higher end modeling platforms. In the case of several, you can send clients directly to your models online. The resolution and detail surpass WebODM, and they offer many more import and export options. Here's the thing though, for practicing and learning about modeling WebODM offers a fair amount. But there's only so much Open Source platforms can offer.
I know you tend to use the autonomous piloting software to handle the missions, but I’m stuck with a mini 4 pro at the moment without sDK support so I have to dial in my own settings using waypoints and then used timed shots (usually every 3 seconds). My question is, when you’re doing missions to do orthos and 3D models, what is your gimbal angle at? Is it -90’ for ortho and maybe -45’ for models? Or will a 3d model improve having both? I’ve been experimenting with webODM the last few days and have had some issues with everything being wavy.
More often than not we're shooting at -90 as folks are very interested in the orthos. When I do shoot for 3D models normally I'll go for -70. With the M3E I have additional options with their Obliques. The demand for 3D models has been low in my area (disappointment). With your WebODM experiments, maybe slow the flight down and get more overlap with the images. Try small experiments with that to see. Oh, by the way, is your RUclips Icon the Laughing Man Logo? I have that on my discord server. 😀
@@AZ-Drone Yes its laughing man. I didn't do a 70` test yet but 90` worked much better for ortho. One interesting thing I discovered is that you can upload a DJI generated video (even h265) + its corresponding SRT file directly into webODM and it will process it with the geo data. If you don't have the SRT, the ortho is pretty much trash since it has no sense of scale. Oddly the point map/model look just fine.
What kind of hardware are you running WebODM on? Looking to use it to perform Multispectral Orthomaps, but my standard PC is simply incapable of doing so
I'm running a Mac Studio M1. It's several years old but still works with WebODM well. 32GB of RAM. I wish it had more storage but that's my only complaint on it.
I have just gotten back into this App. I'm keyed into the 'orthomosaics'...they can make some nice art. My issue is the outputs. I have the Air2S and love this drone. It produces, as you most likely know, a nice large 5464px x 3640px image. Even larger than your Enterprise I think. What I can't get to work is using a file this size with WebODM and expect it to work. I have to 'dumb down' the images to 1,000px on the long side to even hope I can get an output. I do admit to being a tad happy with my images with upwards of 350 images(becasue I'm nuts) but...what the hell. It's just computers doing 'their thing'...computing. I have a MBP M1 with 16GM and a 1TB HD. I think I have enough computer. Any advice is most welcome and thanks. FYI...I did purchase one of your classes a while back.
I actually reduce the size of my images going into my M1 Studio. The final file sizes can become huge if you don't reduce the image size. And processing with 350 images? That's getting really big if you don't resize. Is there a reason for wanting the super large final output? Also, did you specify your RAM and Disk size in the WebODM setup? If you didn't allocate enough ram that may be a problem too. On my setup (in Docker) I have 6 CPUs, 28GB of Ram, and 96 GB Disk Size
@@AZ-Drone Thank you so much for getting back...you're a real shining light. I will look into all these specs in a couple of days...I know I did nothing with my Docker's setup. As for why I'd like my orthomosaics large is that maybe people might like to spring for large prints. I live in farm and horse country and some of these farms at sunrise/sunset are beautiful. I'd like to be set up with offering to photograph that covers a twenty acre farm and make a 20 x30 print. There's art in this approach...I just need to 'do it'. Thanks so much.
@@AZ-Drone I'm baaaack...my Schwarzenegger impression is not so good. Regarding my wanting/needing of a high res orthomosaic image using full res files...I think I found the answer. After reading posts regarding excessive 'wavy' image rendering...just not clean let's say. I personally can make better panos(just a few images) with Lightroom than with WebODM. Someone mentioned trying this. Under options use 'fast-orthophoto'. I uploaded 179 full sized JPEGS compressed to 70% and it worked. No 'wavy' parts and tack sharp. My output for this example was 56" x 34" at 300ppi. For some people this can make incredible original wall art. I hope I shared something you even learned from.
Love to see a qGIS summary as well.
Appreciate the video Rich. Do you have a video or more detail on how to import a texture or obj file from webodm to qgis? I'm getting better with both programs but I'm a bit stumped here.
Not yet. Your question got me wondering about how you could import a texture or obj file, and I've been doing a little reading. I pulled up ChatGPT, and it looks like there is a way, but not working for me yet. If you'd like to do a little investigation as well, here is the question I asked the AI. "how to import a texture or obj file from webodm to qgis". ChatGPT came up with a suggestion, but like I said, not working for me yet.
Hi. Great videos.
You said that the model is not that great, as a hobbyist myself, do you mind expanding/explaining how it is different from other platforms model.
Thanks again for the great videos.
Plus one for this question. It seems that if some orbital are done the 3D Maps improoves.
WebODM does offer their 3D Model and Texture. Together the models coming out look "okay" but never high end like some other platforms. Pix4D, Drone Deploy, Maps Made Easy, and Metashape are a few examples of higher end modeling platforms. In the case of several, you can send clients directly to your models online. The resolution and detail surpass WebODM, and they offer many more import and export options. Here's the thing though, for practicing and learning about modeling WebODM offers a fair amount. But there's only so much Open Source platforms can offer.
Just answered your mail question on the previous comment. Thanks for commenting and engaging on this one!
Just answered your mail question on the previous comment. Thanks for commenting and engaging on this one!
@@AZ-Drone thank you for explaining.
I know you tend to use the autonomous piloting software to handle the missions, but I’m stuck with a mini 4 pro at the moment without sDK support so I have to dial in my own settings using waypoints and then used timed shots (usually every 3 seconds). My question is, when you’re doing missions to do orthos and 3D models, what is your gimbal angle at? Is it -90’ for ortho and maybe -45’ for models? Or will a 3d model improve having both? I’ve been experimenting with webODM the last few days and have had some issues with everything being wavy.
More often than not we're shooting at -90 as folks are very interested in the orthos. When I do shoot for 3D models normally I'll go for -70. With the M3E I have additional options with their Obliques. The demand for 3D models has been low in my area (disappointment). With your WebODM experiments, maybe slow the flight down and get more overlap with the images. Try small experiments with that to see. Oh, by the way, is your RUclips Icon the Laughing Man Logo? I have that on my discord server. 😀
@@AZ-Drone Yes its laughing man. I didn't do a 70` test yet but 90` worked much better for ortho. One interesting thing I discovered is that you can upload a DJI generated video (even h265) + its corresponding SRT file directly into webODM and it will process it with the geo data. If you don't have the SRT, the ortho is pretty much trash since it has no sense of scale. Oddly the point map/model look just fine.
Great video, I hope you are doing well!
Thanks! You too!
What kind of hardware are you running WebODM on? Looking to use it to perform Multispectral Orthomaps, but my standard PC is simply incapable of doing so
I'm running a Mac Studio M1. It's several years old but still works with WebODM well. 32GB of RAM. I wish it had more storage but that's my only complaint on it.
I have just gotten back into this App. I'm keyed into the 'orthomosaics'...they can make some nice art. My issue is the outputs. I have the Air2S and love this drone. It produces, as you most likely know, a nice large 5464px x 3640px image. Even larger than your Enterprise I think. What I can't get to work is using a file this size with WebODM and expect it to work. I have to 'dumb down' the images to 1,000px on the long side to even hope I can get an output. I do admit to being a tad happy with my images with upwards of 350 images(becasue I'm nuts) but...what the hell. It's just computers doing 'their thing'...computing. I have a MBP M1 with 16GM and a 1TB HD. I think I have enough computer. Any advice is most welcome and thanks. FYI...I did purchase one of your classes a while back.
I actually reduce the size of my images going into my M1 Studio. The final file sizes can become huge if you don't reduce the image size. And processing with 350 images? That's getting really big if you don't resize. Is there a reason for wanting the super large final output? Also, did you specify your RAM and Disk size in the WebODM setup? If you didn't allocate enough ram that may be a problem too. On my setup (in Docker) I have 6 CPUs, 28GB of Ram, and 96 GB Disk Size
@@AZ-Drone Thank you so much for getting back...you're a real shining light. I will look into all these specs in a couple of days...I know I did nothing with my Docker's setup. As for why I'd like my orthomosaics large is that maybe people might like to spring for large prints. I live in farm and horse country and some of these farms at sunrise/sunset are beautiful. I'd like to be set up with offering to photograph that covers a twenty acre farm and make a 20 x30 print. There's art in this approach...I just need to 'do it'. Thanks so much.
@@AZ-Drone I'm baaaack...my Schwarzenegger impression is not so good. Regarding my wanting/needing of a high res orthomosaic image using full res files...I think I found the answer. After reading posts regarding excessive 'wavy' image rendering...just not clean let's say. I personally can make better panos(just a few images) with Lightroom than with WebODM. Someone mentioned trying this. Under options use 'fast-orthophoto'. I uploaded 179 full sized JPEGS compressed to 70% and it worked. No 'wavy' parts and tack sharp. My output for this example was 56" x 34" at 300ppi. For some people this can make incredible original wall art. I hope I shared something you even learned from.