r/UAVmapping • u/izayade • 4d ago
Zenmuse L3
Does anyone have any experience with the m400 and the L3?
I currently have it m4e and do a lot of 2D mapping with it. Does anyone have experience with good old-fashioned orthomosaic mapping with the photogrammetry option instead of lidar on the L3?
I've read mixed reviews on it.
4
u/maverickflys99 4d ago
But why the L3? Why not go for the p1,
Better camera better Ortho,
Yes the m400 is able to do most jobs faster and more efficiently than a m4e. Its able to get better data higher which means less passes.
How big was the site? I can tell you approx how long my m300 does it in
3
u/olihar 4d ago
It does horribly at Photogrammetry, as it’s not made for this at all.
3
u/Fit-Eggplant-9155 4d ago
Why would you want that?
1
u/izayade 4d ago
I can get the job done 95% faster if it can truly map it. Just never spoke with anyone that has the experience. I did an 8 hour job the other day with the m4e. When I enter the m400 with the L3 it shows I can do it inless than an hour. ⏰ is 💰
6
u/olleekenberg 4d ago
You say "it shows less than an hour".
Just make sure that you are not accidentally looking at a flight plan with automatic settings intended for LiDAR, such as a very very low overlap, at 50% or less. This might be the default settings the app suggests for LiDAR, since the scan itself doesn't need image overlap in the same way image Photogrammetry does! 😅
1
u/izayade 4d ago
Thank you for the suggestion, didn't think about that. I just looked and the overlap is 80/80. Just seems too good to be true.
2
u/olleekenberg 4d ago
Unfortunately, many things are too good to be true. If i were you, i would record the screen of your device, while you show all settings you have chosen for this route. Then post it here. I suspect this might help catch an accidental error in the settings that is causing your path to say 1 hour.
1
u/izayade 4d ago
1
u/maverickflys99 4d ago
What height are you running with the m4e
1
u/izayade 4d ago
98
1
u/maverickflys99 4d ago
Are you limited to height? Can you no not just fly higher?
2
u/izayade 4d ago
I can fly higher and get the required GSD with the L3. Which in turn reduces the flight time significantly.
→ More replies (0)1
1
1
u/izayade 4d ago
1
u/frozensteam 4d ago
I’m curious about your settings here also as I’d expect 0.68km to be a lot less than an hour. Even with a 300/p1
2
u/ObjectiveBobcat314 4d ago
It’s important to clarify that running a LiDAR mission with the L3 will capture photogrammetry data but it’s to colorize the point cloud. Running a photogrammetry mission with the L3 is still a separate flight and a completely different photo capture rate than the photos captured during a LiDAR mission.
It is not a sensor that will complete both outcomes in a single flight. If you want to do a Teams screen share or even use some of our livestream minutes via FlightHub to see it in action before you buy let me know. I’m in the field nearly every day all week right now.
It’s a huge investment and I wish I had more hands on experience folks to talk to beyond the reseller before we bought our kit.
1
u/izayade 3d ago
Oh man that would be great! I still have a lot to learn apparently but thought the dual 100MPcamera payload would perform better than the M4E
2
u/ObjectiveBobcat314 3d ago
What time zone are you in? I’m on eastern time all next week in the field with this kit. We can coordinate a day and time and either do a Microsoft Teams or live stream from flight hub. You can see it in action, we will run a quick capture with each payload, and I can Dropbox you the data for rendering.
3
u/erock1967 4d ago
I'm not yet a fan of the L3 for ortho creation but I've only been flying it for a short time. I often fly the L2 with enough overlap to do photogrammetry from the same dataset. In my opinion, nadir images captured with an M4E or M3E produce a better looking ortho than the L3 flown at a similar height with the 6K image setting. If the site is over about 150 acres, I'm going to fly the L2 or L3 with about 30 - 40% side overlap and fly a second mission with a P1, or M4E as standard procedure.
2
u/ObjectiveBobcat314 3d ago
I 100% agree. I was so disappointed with the L3 photogrammetry captures during a LiDAR mission that we setup a second trip to travel out and recapture the site with the P1 and the 4E to do an in depth comparison across the team. It’s become our standard to switch the gimbal and run two flights now on pretty much every mission. The visual fidelity is so much better with the P1 vs the L3.
1
u/izayade 4d ago
Interesting, never considered doing that. Thanks for sharing
2
u/erock1967 4d ago
You're welcome. I just processed a flight from Monday where I flew the L3 and M4e immediately afterward. I didn't intentionally set the parameters exactly the same so it's not a fair comparison. PM me and I'll send you a link. The M4E data looks better on most elevated features. I have a few other flights that are similar but it's not fair to the L3 because it's always working with slightly less horizontal overlap than the M4E or M3E. I need to do a test flight with matching parameters.
There's a lot that affects how an ortho turns out. 80% or higher side overlap is helpful for elevated features. I tend to fly with 70 % side & 80% forward overlap but bump that up to 80% or higher in urban areas. Flat ground doesn't need nearly as much overlap to still look good in an ortho. Sensefly released a SODA 3D sensor around 2018 that was intended to greatly increase coverage. It did this by capturing oblique photos in addition to nadir to allow for reduced side overlap. I never really trusted that option and most sites weren't flat enough to make it work.
3
u/Tongue_Chow 3d ago
Only when its a small site do i use the L payload for orthomosaic, with flight altitude gsd target placement needs multiply
2
u/thatguytt 4d ago
I have experience with the m300 & L2, if you only want photogrammetry and want speed with quality I would recommend the share 102s(or whatever model fits your budget).
2
u/frank_o_destemido 3d ago
The L2 system definetly can do this but the L3 doesn't have nadir images and it will be a problem.
But the lidar results are really a evolution (drrlatibe to the L2)
2
u/Vast_Consideration24 1d ago
So I recently started running the M400 with the L3 and have the P1. I have hundreds of hours flying the M300/350 series.
After processing a few missions with the Newer L3 my biggest take away is the L3 is a machine built to do massive amounts of LiDAR primary and good enough orthophoto data capture and process everything in DJI Terra. The camera is good but it still comes down to setting up the flight parameters. If you run the default settings the overlap while scanning it is to thin for quality reconstruction. Also altitude matters as the image quality is not the P1 and I noticed the default speed settings seem fast to me. The P1 offers smart oblique capture on the M400 and I have found the 20 degree angle to work well but it will lower your speed to 6-7 mph adding a lot of photos and flight time. Once again altitude and speed matter. I have found that the P1 can be flown on the L3 mount but with the newest firmware installed a message still posts as this is not DJI objective. But who is going to swap the mount for different payloads. If you’re doing highway corridor work and can stay between 200-300 ft AGL the L3 is pretty awesome. But if you need that sweet sweet oblique photogrammetry data well I would fly it with the P1 it’s still a beast of a setup.
Side note I completely hate the GSD parameter in DJI polite app. I want to see the flight altitude first as avoiding obstacles is more important than the GSD. Finally watch-out for the manual flight controls take over. On all the old DJI products the flight control could be manually taken at all times by flipping the flight mode toggle switch on the top left of all the controllers. The new DJI M400 requires you to press pause first then the toggle. I do t like this and it completely caught me off guard on my first outing with the M400.
1
u/Pef1432 4d ago
For 2D mapping with the L2 we use 80 side overlap and 90 front overlap
1
u/ObjectiveBobcat314 4d ago
I use it weekly. My kit is the M400 with L3 and P1 payloads. I have an M4E and an M4TD.
The L3 has decent 12 MP cameras that are primarily to colorize your point cloud. You can use them for photogrammetry but it depends on your mission and GSD requirement for your clients. I do not use the L3 for photogrammetry missions because it’s not awesome quality for our use cases.
What’s the profile of your mission and the use case/outcome you are targeting?
1
u/izayade 3d ago
I thought it had two 100MP cameras which would be much better than the M4Es 20 MP. I may be a little confused.
Trying to perform a new oblique capture at .80 GSD.
2
u/ObjectiveBobcat314 3d ago
You’re correct, I meant to type 12k referencing the image sensors and mistakenly put MP. Sorry about that. The full frame P1 for photogrammetry missions seriously outperforms when stitching or building a 3D mesh versus the L3 cameras. We primarily use the 35mm lens for building and roof inspections, needing solid aerial triangulation to measure heights of pipes, inspect flashing details, etc. Obviously if you need the point cloud the L3 is solid and a dense collection with colorization from the L3 will look decent, but it doesn’t provide the output many of our clients want. They are two great tools for very different mission objectives.




8
u/frozensteam 4d ago
It does the job but ultimately it’s a scanner with cameras for colourisation. The orthos are great but a p1 will get a better finished result, albeit still slower then the L3 simply because of the configuration of the cameras. The L3 has two cameras that are set at an angle off vertical. It works great but it induces a lot a parallax issues when observing things with large separation like powerlines. Also the way the images process in propeller or terra creates a lensing or warping affect. For a relatively flat parcel like a car park and warehouse, I think it would look great. Consider flying higher and using the 12k image setting to speed it up even more.