Drone Accessories

I'm going to be upfront here: I made a bunch of mistakes and the first dataset I brought home was basically garbage. So if you're just starting out with drone mapping like I am, maybe this saves you some frustration.

The Mission Planning Part

I used DJI Pilot 2 to set up the grid mission. The property is pretty flat with some tree lines along two sides, which I thought would make things easy. I set my altitude to 100 feet, which in hindsight was probably too low for the area I was covering, and I set my front and side overlap to 70% each. I'd read that 70/70 was a decent starting point for basic mapping so I went with that.

What I didn't think about was how long that was going to take. At 100 feet with 70% overlap on a 12-acre area, the mission ended up being longer than one battery. I only brought two batteries. I had to cut the grid short, come home, swap to my second battery, and then relaunch. When I stitched the photos later in Metashape, you could see exactly where I landed and came back - there was a seam in the orthomosaic that looked terrible and the point cloud got weird in that overlap zone.

Lesson one: plan your batteries before you go out. I should have either flown higher (maybe 200 feet) to cover the ground faster and reduce the photo count, or brought more batteries. I've since started plugging my mission into a calculator first to estimate flight time. There are a few free ones online and DJI Pilot 2 will also give you a rough estimate in the app, but I wasn't paying attention to it.

Ground Control Points - Or My Lack of Them

This is the big one. I didn't use any GCPs on my first attempt. I told myself the RTK GPS on the Mavic 3 Enterprise would be good enough and I didn't want to deal with the hassle of setting targets out. Big mistake, at least for what my neighbor actually needed.

The orthomosaic looked pretty good visually. Colors were decent, the fields were clear, tree lines showed up. But when I tried to pull any measurements out of it - distances, areas - they were off. Not by a crazy amount, but enough that I wouldn't feel comfortable handing this to someone making land decisions based on it.

I went back out a week later and this time I placed six GCP targets. I made my own out of painted plywood, just simple 18-inch crosses painted white and black. I put them around the perimeter of the property and one in the middle. I used a rented GPS unit from a local survey equipment place to get their coordinates - that part cost me about $80 for the day rental which felt like a lot but whatever, it was worth it for the learning experience.

The second dataset was dramatically better. Once I entered the GCP coordinates into Metashape and ran the alignment again, the absolute accuracy tightened up noticeably. I'm not going to pretend I'm producing survey-grade data here - I'm not a licensed surveyor and this was all just for learning - but the improvement was obvious and measurable.

Processing in Metashape

I'm still pretty new to Metashape. I've been using the trial version and I'll probably end up buying it eventually because it seems like the standard tool for this kind of work. The workflow I followed was pretty basic: add photos, align photos (I used medium quality to save time), build dense cloud, build mesh, build orthomosaic. For a 12-acre property I ended up with something like 400 photos on the second flight at 150 feet altitude with 75% front and 70% side overlap.

The processing took a few hours on my laptop, which is not a powerhouse. I've got a mid-range gaming laptop with a decent GPU but not anything crazy. Medium quality alignment took maybe 45 minutes and the dense cloud build took a couple hours. I let it run overnight on the second dataset.

The orthomosaic exported fine and I loaded it into QGIS to have a look. QGIS is free and honestly really powerful once you get the hang of it. I georeferenced the output, poked around with the layer styling, and was able to pull area measurements that matched what I was getting from manual calculation pretty closely. That felt like a real win.

What I'd Do Differently

A few things I'm taking into my next mission:

First, always calculate battery requirements before I leave the house. It sounds obvious but I genuinely just eyeballed it the first time and that cost me a good dataset.

Second, GCPs are worth the effort. Even if the drone has RTK, for anything that needs to be accurate, physical targets and surveyed coordinates make a real difference. I'm also going to look into setting up a permanent GCP or two on my own property so I have a known reference point for practice flights.

Third, bump up the overlap a little. I've been reading that for areas with a lot of vegetation or any terrain variation, going 80/80 is safer. It generates more photos and takes longer to process but the model quality improves and you get fewer holes in the point cloud.

Fourth - and this is something I keep seeing mentioned in the forums - fly in good lighting conditions. I did my first flight around noon on a bright day and the shadows from the tree lines caused some issues with the alignment in those areas. Overcast days are apparently better for mapping because the light is more even. I haven't had a chance to test this yet but I believe it.

Where I'm Going From Here

I want to do more of this. There's something really satisfying about taking a bunch of photos from a drone and turning them into something you can actually measure and analyze. My neighbor was happy enough with the second map that he's sharing it with his surveyor, which I thought was pretty cool even if it's not replacing actual survey work.

I'm thinking about trying a stockpile volume calculation next. There's a gravel operation not too far from here and I know the owner casually - I might reach out and see if I can do a demo flight just for practice. Volume measurement from drone data seems like a really practical application and I want to understand how well it actually works versus traditional methods.

Anyway, if you're just getting into drone mapping, hopefully some of this is useful. I'm definitely not an expert - obviously - but I'm learning and I'll keep posting about what I figure out.

A little background: I fly a DJI Mavic 3 Enterprise and I've been doing recreational flying for about two years. But lately I've been really interested in the mapping and surveying side of things. I've taken a few online courses, watched probably way too many YouTube videos about photogrammetry, and finally convinced a friend who owns a small piece of rural property to let me practice on his land. About 12 acres, mix of open field and some tree cover on the western edge. Perfect for a first attempt, I figured.

The Mission Planning Part

I used DJI Pilot 2 for mission planning, which integrates pretty smoothly with the . Setting up the grid mission wasn't too bad once I figured out the interface. My big mistake number one was overlap settings. I had read that 70-75% front overlap and 60-65% side overlap is a reasonable starting point for most mapping work. I looked at that and thought, yeah but more is better right? So I cranked front overlap to 85% and side overlap to 80%.

What happened? My 12-acre site turned into a mission that generated over 800 images. Processing that in Agisoft Metashape on my laptop took the better part of five hours and nearly crashed the thing twice. My friend's field did not need 800 photos. Somewhere around 400 probably would have done the job fine and saved me an afternoon of staring at a progress bar. Lesson learned: more overlap means more images means way more processing time and storage. There's a balance and I was nowhere near it.

Ground Control Points — I Kind Of Sorta Did These

This is the part I'm most embarrassed about. I knew ground control points were important. I'd watched the videos. I understood in theory that without GCPs your map might look great but the absolute accuracy is going to be off, sometimes by a lot. I set out five targets — just printed these black and white checkerboard squares I found a template for online — and I placed them around the field.

What I did not do: use an actual survey-grade GPS to record their coordinates. I used my phone's GPS. My phone GPS. Which, in open sky conditions, is maybe accurate to three or four meters on a good day.

So my orthomosaic looks visually really nice. But when I checked it against known reference points? There were some offsets that were... not great. I'm not going to put a number on it because I think I also made mistakes in how I imported the GCP coordinates into Metashape, so it's a compounding error situation. The point is, if you're doing this for anything that actually matters — anything where someone needs real-world accuracy — you need real-world accurate GCP coordinates. Phone GPS is not that.

I've since been looking into renting a RTK GPS unit for my next attempt. Some survey equipment rental places do short-term rentals which makes it more accessible for someone like me who isn't doing this commercially yet.

The Actual Flight

The flight itself was the most straightforward part, weirdly. Once the mission was loaded it was pretty much hands-off. I launched, the drone went and did its thing in a nice back-and-forth lawnmower pattern, and landed itself. Total flight time was maybe 22 minutes. Wind was light, maybe 8 mph, which was fine. I flew at 80 meters AGL and set my speed to around 8 m/s.

One thing I didn't anticipate: the tree line on the western edge. The automated mission doesn't really account for obstacles in any meaningful way on this hardware — it's not doing terrain following or anything like that. The trees are only about 10 meters tall so at 80 meters I had plenty of clearance, but it did make me think about how I'd handle terrain that's more variable. Something to dig into for future missions.

I also forgot to check that my camera settings were locked down before the mission started. The drone adjusted exposure a couple times mid-flight as it crossed from the shadowed area near the trees back into full sun, and you can actually see slight brightness variations in some of the image tiles in the final orthomosaic. Going forward I'm setting manual exposure or at minimum using the auto-exposure lock feature before I start the grid.

Processing in Metashape

I went with Agisoft Metashape Standard because the price point is way more manageable than some of the alternatives for someone just learning. The workflow is roughly: import photos, align photos, build dense cloud, build mesh, build orthomosaic. Each step builds on the last and any errors kind of cascade.

My photo alignment went well — Metashape aligned 792 of my 803 images which I thought was pretty good. The dense cloud looked really solid over the open field area. The tree canopy area was messier, which I've read is pretty typical. Vegetation with a lot of movement between shots is tough for photogrammetry.

The orthomosaic export I did at full resolution, which was another mistake in terms of file size. The TIFF came out at around 4GB. I don't have a GIS setup sophisticated enough to really work with that efficiently yet. I've been reading about QGIS which is free and apparently handles large rasters reasonably well with the right settings, so that's my next thing to figure out.

What I'd Do Differently

Looking back, here's my honest list:

• Drop the overlap to something more reasonable, probably 75% front and 65% side, and see if the results are still acceptable
• Borrow or rent an actual RTK GPS for GCPs — this is non-negotiable if accuracy matters at all
• Lock camera exposure before starting the mission
• Export the orthomosaic at a more manageable resolution until I have a proper GIS workflow set up
• Fly on a fully overcast day if possible — even lighting across the whole scene apparently makes a real difference

I've also started reading more about coordinate systems and datums because when I was trying to bring my orthomosaic into QGIS I ran into projection issues that I genuinely did not understand. That's a whole rabbit hole I'm just starting to go down.

Overall Thoughts

Honestly even with all the mistakes? I'm kind of hooked. There's something really satisfying about turning two hours of field work into a map you can actually measure things on and look at from above. Even my rough, GPS-phone-GCP orthomosaic shows my friend where his fence line sits relative to the tree canopy in a way he'd never really been able to visualize before. He seemed genuinely impressed, which made me feel better about the whole thing.

I've got another practice mission planned for next month on a slightly larger site, about 25 acres. I'll write that one up too. Hoping to have the RTK situation sorted by then and maybe a better handle on the QGIS side of things. We'll see.

If anyone else is starting out with mapping and has figured out the GCP workflow on a budget, I would genuinely love to hear how you're handling it. Drop something in the comments.