Capturing Drone Imagery for High-Quality Gaussian Splats
A practical field guide to flying for 3D Gaussian Splatting (3DGS) reconstruction. This tutorial assumes you’ve flown photogrammetry missions before — if you have, most of what you know transfers, but the priorities shift in important ways.
Why 3DGS isn’t just photogrammetry with a different output
Both pipelines start the same way: you fly a drone and collect overlapping photos. From there, the workflows diverge:
- Photogrammetry optimizes for geometric accuracy. It produces meshes and orthomosaics. Lighting variance hurts but is recoverable through blending.
- 3DGS optimizes for photometric fidelity from arbitrary viewpoints. It bakes view-dependent appearance — specular highlights, subsurface effects, soft shadows — into a cloud of millions of anisotropic 3D Gaussians.
Three practical consequences flow from this:
- Lighting must be consistent across the entire capture. A splat trained on inconsistent lighting will produce “floaters” — wispy cloud-like Gaussians that try to reconcile irreconcilable views. Photogrammetry tolerates lighting drift; 3DGS does not.
- You need more views per surface, from more angles, than for photogrammetry. Because the model represents view-dependent appearance, every surface should be observed from a hemisphere of directions, not just from above and once obliquely.
- Underconstrained regions become artifacts, not just holes. Where photogrammetry produces a hole or low-poly patch, 3DGS hallucinates Gaussians that look correct from training views but break down when you move the camera off the captured trajectory.
Plan for these from the moment you walk onto the site.
Step 1: Pre-flight planning
Pick the right time of day
Diffuse, overcast light is the gold standard. It eliminates harsh shadows and the directional speculars that cause inconsistencies between orbit angles. If you must shoot in direct sun:
- Fly close to solar noon so shadow direction shifts least during the mission.
- Avoid golden hour unless you’re shooting for cinematic intent and accept the lighting will be baked into the splat.
- Never split a capture across changing light — finish in one continuous session, or re-fly the whole thing.
Survey the scene for failure modes
Walk or pre-fly the site and identify:
- Reflective surfaces — glass, polished metal, water. These violate multi-view consistency. The Gaussians in those regions will be unstable and the surrounding geometry often degrades. Plan extra coverage from multiple incident angles, or accept the artifact.
- Repetitive textures — uniform brick walls, parking lots, gravel, tile patterns. SfM struggles to find unambiguous feature matches. Add ground-level oblique passes and ensure varied incidence angles.
- Thin structures — wires, fences, antennae, leafless branches. These are notoriously hard for both SfM and 3DGS. Higher resolution and closer passes help; nothing fixes them entirely.
- Moving elements — vegetation in wind, traffic, water surfaces, people. Each moving object becomes a floater. Plan timing to minimize movement, and anticipate that some scene dynamics may need to be handled downstream.
- Sky-dominant regions — pure sky has no features. Frame so sky is incidental rather than the primary content of any image.
Choose your scene scale
The capture pattern depends on what you’re reconstructing:
- Single object or building — orbital coverage is primary
- Building cluster or campus — orbital + grid hybrid
- Open landscape or terrain — double-grid with oblique passes
- Tall structure (tower, monument, cliff) — perimeter orbits at multiple altitudes
- Wind turbine or rotating radial structure — multi-altitude orbits with a critical hub-level pass
These patterns are described below.
Step 2: Camera settings
Manual everything. Auto-exposure between frames is the single most common cause of bad splats. Even small EV shifts produce a flicker effect that 3DGS cannot resolve.
The settings that matter
| Setting |
Recommendation |
Why |
| Exposure mode |
Full manual |
Auto-exposure variance ruins photometric consistency |
| Shutter speed |
1/1000s minimum, 1/2000s preferred |
Eliminates motion blur. Drones move and vibrate; even 1/500s can blur fine detail at altitude |
| ISO |
Lowest you can while maintaining shutter |
Noise floor matters for SH coefficient quality |
| Aperture |
Fixed (most drone cameras have fixed aperture; honor it) |
If variable, lock at lens sweet spot (typically f/4–f/5.6) |
| White balance |
Manual / locked |
Auto WB drift causes color inconsistency between angles |
| Format |
RAW (DNG) if available, otherwise highest-quality JPEG |
RAW lets you correct exposure post-hoc and apply consistent processing across the set |
| Picture profile |
D-Log or flat profile if RAW unavailable |
Preserves dynamic range for downstream processing |
| Mechanical shutter |
Use it if your platform supports it |
Eliminates rolling-shutter distortion that confuses pose recovery |
Shutter speed math
To keep motion blur below one pixel, the rough rule is:
shutter_speed < (GSD) / (drone_speed)
At 5 m/s with a 2 cm GSD, that’s 0.02 / 5 = 0.004s → 1/250s minimum just for forward motion. Add gimbal vibration headroom and you’re at 1/1000s. Fly slower if you can’t push shutter higher.
Pre-process before handoff
If you’ve shot RAW, develop the entire set with identical settings before handing the data off — same exposure, same WB, same tone curve. Don’t auto-balance per-image. The whole point is photometric consistency.
Step 3: Flight patterns
Pattern A — Building or single structure
Open visualizer →
The workhorse pattern. Combine these passes:
- Nadir grid over the structure and surrounding ground at altitude H. Side and forward overlap ≥ 80%.
- Orbit ring at H₁ ≈ 1.5× structure height, gimbal pitched -45°. One photo every 5–10° of azimuth (so 36–72 photos per ring).
- Orbit ring at H₂ ≈ structure height, gimbal pitched -20° to -30°. Same azimuth density.
- Low orbit at H₃ ≈ ⅓ structure height, gimbal near horizontal (-5° to -15°), capturing the base, façades, and any overhangs.
- Detail orbits for ornamentation, antennae, recessed features — closer-in passes at varied gimbal angles.
Modern platforms with automated oblique mission modes will run variants of this for you. Manual flight is fine; just hit the rings systematically.
Pattern B — Open site or landscape
Open visualizer →
- Double-grid nadir at altitude H — fly a grid in one direction, then orthogonal. 80% overlap both axes.
- Oblique grid at altitude H, gimbal pitched -45°, in the same flight direction as one of the nadir grids. This is the single most important pass for splat quality on flat sites.
- Perimeter orbit(s) around the area of interest at the edges of the site, capturing the scene from outside-in.
If your scene has vertical features (buildings, trees, terrain breaks), add Pattern A around each.
Pattern C — Tall structure (tower, monument, cliff face)
Open visualizer →
Skip the grid. Fly:
- Concentric perimeter orbits at 4–6 altitudes, evenly spaced from base to slightly above the top.
- Vary radius between rings — alternate close and far so you capture both detail and context.
- Vary gimbal pitch per ring — top rings tilt down more, bottom rings tilt up more, middle rings closer to horizontal. The combined coverage gives you the hemisphere of viewing directions every part of the structure needs.
- One nadir pass over the top to capture the crown, plus one wide nadir over the base for ground context.
Pattern D — Single object (small subject)
Open visualizer →
For a sculpture, vehicle, or individual tree:
- Treat it as a sphere. Capture from a dome of viewpoints — three orbits at three pitch angles (-15°, -45°, -75°) is a reasonable minimum.
- Distance: close enough that the object fills 60–80% of the frame.
- Supplement with ground-level handheld or tripod shots if the bottom and undersides matter.
Pattern E — Wind turbine (or other rotating radial structure)
Open visualizer →
Wind turbines combine tall-structure capture with radial blade geometry. They are also the pattern with the most consequential safety constraints in this guide.
The blades MUST be locked stationary for the entire capture. Even slight rotation between frames poisons multi-view consistency catastrophically — far worse than wind-blown vegetation, because the moving objects are large, repetitive, and dominate the scene. Confirm rotor lock visually and with the operator before takeoff.
The “Y” position (one blade pointing straight up) is conventional and gives symmetric coverage. With the rotor locked in Y:
- Hub-level orbit at extended radius — the critical pass. Altitude = hub height. Radius ≥ 1.5× blade length to maintain safety clearance from the lower blade tips. Gimbal near horizontal (-5° to -10°), capturing the hub and the inner two-thirds of all three blades from the side.
- High orbit at altitude = hub height + 20%. Smaller radius (≈ 1× blade length, since you’re now above the upper blade tip). Gimbal -30° to -45°, capturing the top of the hub and the upper blade from above.
- Mid-tower orbit at altitude ≈ ½ hub height. Radius ≈ 1× blade length. Gimbal -10°, for the tower midsection.
- Low orbit at altitude ≈ ¼ hub height. Radius small (~0.5× blade length, well clear of the lower blade tips, which sweep at altitude = hub_height − blade_length). Gimbal +15° looking up, for the tower base and lower hub.
- Nadir pass directly over the hub at a comfortable vertical margin. Gimbal -90°. Captures the hub crown, sensors, and any wiring on top of the nacelle.
- Ground supplementation for foundation, connection box, transformer pad, and any access infrastructure.
Critical safety notes for wind turbines:
- The lower blades sweep a circle of radius = blade length, centered on the hub axis. Any drone path inside that circle below hub height is at catastrophic risk if the rotor releases. Treat this as a hard exclusion zone unless you are well above the upper blade tip.
- Wind speeds at hub height are routinely 2–3× ground level, even when the surface is calm. Check the weather model at hub elevation, not just at the launch point.
- Many operators have specific drone access protocols and may require shutdown coordination, lockout/tagout confirmation, and a spotter on site.
- If the turbine has aviation warning lights, flying near them at night risks blinding the camera with lens flare that 3DGS cannot reconstruct. Day capture only unless you’ve planned around the lights.
Step 4: Coverage rules of thumb
These are the heuristics worth internalizing. Use them as starting points and adjust based on results from your specific scenes:
- Overlap: 80% forward, 80% side, minimum. Photogrammetry guides often suggest 70/60. For 3DGS, push higher. The cost is more photos and longer processing; the benefit is fewer floaters.
- Every surface visible from at least 3 distinct viewing directions. Ideally more. If you can imagine standing at a point on the surface and looking outward, your captured camera positions should fill a meaningful arc of that hemisphere.
- Three altitudes minimum for any vertical structure.
- Both nadir and oblique passes. Nadir-only kills façade quality. Oblique-only kills roof/top quality.
- Don’t over-fly or hover. Rapid bursts at near-identical positions inflate the dataset without adding new information and can confuse pose recovery with degenerate baselines. If your platform shoots a burst, downsample to one per unique pose.
- Image count target: 200–800 for a single building, 1000–3000 for a small site, 3000+ for complex sites. Quality of pose distribution beats raw count, but 3DGS does benefit from more views than photogrammetry would need for the same scene.
Step 5: Ground supplementation
Aerial-only captures fail at the bottoms of structures and anywhere a roof, awning, or overhang occludes the view from above. For high-fidelity results — especially on buildings with façade detail — supplement with terrestrial capture:
- Walk the perimeter at human eye height with a phone or handheld camera, photographing every façade with significant overlap.
- Include 45° upward angles to catch the underside of overhangs and balconies.
- Matching camera intrinsics matters less than you’d expect — modern pose-recovery handles mixed cameras — but consistent lighting still matters. Capture ground and aerial in the same session under the same light.
This single addition often produces a larger quality jump than any flight-pattern tweak.
Step 6: Capture-side preparation
A few preparation tasks that pay off in final splat quality, all done before handing imagery to the Omniris 3D Splatting Pipeline:
- Cull blurry frames. Even one motion-blurred image can poison the neighborhood of feature matches around it. Use a sharpness metric (variance of Laplacian, or similar) and drop the bottom decile.
- Cull redundant poses. If you have ten near-identical hovering shots, keep one. Cluster by camera position and orientation, not just XYZ — pitch and yaw matter for what each frame actually saw.
- Consistent RAW development. If you shot RAW, develop the entire set with identical settings — exposure, white balance, tone curve. Per-image auto-balance defeats the photometric consistency you locked in at the camera.
- Verify EXIF and telemetry. Check that GPS position, altitude, gimbal angles, and timestamps are intact across the set. Missing or corrupted metadata creates work downstream.
Step 7: Quality assessment
After processing, evaluate the splat in a viewer and look specifically for:
- Floaters — wispy Gaussians in midair, especially near reflective surfaces, sky, or moving-object regions. Generally indicate inconsistent observations.
- View-dependent breakdown — the splat looks great from training-camera-like angles but degrades when you move the virtual camera off-trajectory. Indicates undersampled view directions.
- Soft edges or stretched Gaussians along façades — usually means insufficient close-in oblique coverage.
- Holes or low-density regions — surfaces undersampled or occluded in the input. Re-fly with closer passes targeting those areas.
- Alignment seams between aerial and ground data (if you supplemented) — usually fixable by re-running the joint pipeline on the merged set rather than aligning two separately-trained models.
If the splat fails any of these checks badly, the fix is usually in the capture, not the training. Re-fly with the gap in mind.
Quick reference: the field checklist
Pre-flight
□ Diffuse light or stable sun position
□ No precipitation, low wind
□ Manual exposure locked
□ Manual white balance locked
□ Shutter ≥ 1/1000s
□ RAW or highest-quality JPEG
□ Mechanical shutter enabled if available
□ Battery count: aerial pattern + ground supplement + 20% margin
Mission
□ Nadir grid (80%/80% overlap)
□ Oblique grid OR multi-altitude orbits (per scene type)
□ Low/horizontal pass for façades and undersides
□ Detail orbits for high-frequency features
□ Ground supplementation walk
Post-flight
□ Cull blurry frames
□ Cull redundant poses
□ Develop RAW with consistent settings
□ Verify metadata integrity
□ Hand off to Omniris 3D Splatting Pipeline
The single best habit you can build is treating the first capture of any new site as a calibration flight. Fly it, run a quick splat that night, and look at where it fails. Then fly the real mission knowing what your scene specifically needs more of. Capture quality compounds — a small improvement in coverage, lighting consistency, or sharpness pays off many times over in the final result.
References
Foundational research
- Kerbl, B., Kopanas, G., Leimkühler, T., Drettakis, G. 3D Gaussian Splatting for Real-Time Radiance Field Rendering. ACM Transactions on Graphics 42(4), SIGGRAPH 2023 (arXiv:2308.04079). The original 3DGS paper.
- Pan, L., Baráth, D., Pollefeys, M., Schönberger, J. L. Global Structure-from-Motion Revisited (GLOMAP). ETH Zurich / Microsoft, ECCV 2024 (arXiv:2407.20219). Background on modern global SfM, relevant to understanding what pose recovery requires of a capture.
Drone capture for 3DGS specifically
- Tang, J., Gao, Y., Yang, D., Yan, L., Yue, Y., Yang, Y. DroneSplat: 3D Gaussian Splatting for Robust 3D Reconstruction from In-the-Wild Drone Imagery. arXiv:2503.16964, 2025 (project page). Treatment of dynamic distractors and limited-view challenges in real drone scenes.
- Wu, C.-Y., Sun, Y.-C., Lee, C.-T., Hsu, C.-H. Optimally Planning Drone Trajectories to Capture 3D Gaussian Splatting Objects. MultiMedia Modeling (MMM) 2025, Springer LNCS 15522. Theoretical framework for view selection under drone resource constraints.
Field practice references
Note on heuristics
Several specific numbers in this guide — image count targets, the orbit altitude formulas (1.5× height, ⅓ height), the three-altitude minimum, and the camera settings table values — are heuristics drawn from drone photogrammetry practice and adjusted for 3DGS’s higher coverage requirements. They are starting points based on field experience, not figures from controlled studies. Calibrate them to your scenes.