What capture works best for drone mapping?
Use structured mapping passes rather than only cinematic flybys.
Drone capture plan
| Pass | How to fly | Why |
|---|---|---|
| Main orbit | Slow circle around the subject. | Side coverage. |
| High oblique pass | Camera angled down from above. | Roof and terrain coverage. |
| Low detail pass | Closer pass around important structures. | Improves inspection detail. |
| Grid or cross path | Slow crossing coverage. | Reduces gaps. |
| Transition pass | Connect important areas. | Better tours. |
| Review pass | Extra footage for weak zones. | Reduces artifacts. |
Which model should drone operators choose?
Use LiteV2 for validation, Cinematic for production, and Ultra for final maximum fidelity.
Drone model choice
| Model | Best for | Reason |
|---|---|---|
| LiteV2 | Testing flight coverage. | Fast validation. |
| Cinematic | Most commercial drone splats. | Balanced quality. |
| Ultra | Premium aerial reconstruction. | Maximum detail and high Gaussian target. |
| Physics mesh | Site geometry and simulation. | Adds geometry output. |
| Camera path | Flythroughs and tour rendering. | Preserves movement. |
| Background audio | Immersive location tours. | Adds atmosphere. |
Which drone mapping use cases fit Splatware?
Splatware fits buildings, roofs, construction sites, properties, landscapes, drone tours, and outdoor digital twins.
- Real estate exterior and site context.
- Construction progress documentation.
- Roof and facade capture.
- Commercial property walkthroughs.
- Aerial product or vehicle presentation.
- Tourism and location experiences.
- 360 drone scenes from Antigravity A1-style or Avata 360-style workflows.
What outputs matter for drone mapping?
Drone workflows often need more than the splat: point clouds, mesh, camera paths, virtual tours, renders, and downloads.
Drone outputs
| Output | Use case | Value |
|---|---|---|
| Hosted tour | Client/site review. | Easy sharing. |
| Point cloud | Technical inspection. | Structural understanding. |
| Dense mesh | Physics/collision/simulation. | Geometry output. |
| Camera path | Flythroughs and animation. | Presentation. |
| Rendered video | Marketing and reports. | No interactive viewer needed. |
| Downloads | Further processing. | Portable pipeline. |
What drone mapping mistakes should you avoid?
Avoid fast flight, one-orbit capture, missing roofs, no overlap, and untested huge models.
- Fly slow reconstruction passes before creative shots.
- Capture multiple heights.
- Avoid sudden yaw and motion blur.
- Use stable exposure.
- Test viewer performance before sharing.
- Keep a high-quality source and optimized web delivery version.
Frequently asked questions
Is Cinematic or Ultra better for drone mapping?
Cinematic is the best default; Ultra is best for maximum-fidelity final outputs and large detailed scenes.
Can Splatware use DJI drone footage?
Yes. Splatware can use drone media when the capture has enough overlap, sharpness, and coverage.
Can Splatware use 360 drone footage?
Yes. 360 drone workflows are useful for immersive aerial tours and spatial context.
Can Splatware create a drone virtual tour?
Yes. Drone splats can become hosted virtual tours and rendered flythroughs.
Can Splatware create point clouds from drone splats?
Splatware provides point cloud access as part of model output workflows.
Can Splatware provide dense mesh output for drone scenes?
Yes, dense mesh options can support geometry, physics, simulation, and downstream processing.
What Gaussian count is best for drone mapping?
Use lower counts for testing, medium counts for hosted tours, and higher counts for final high-fidelity exports.
What is the biggest drone capture mistake?
Flying cinematic-only footage without structured overlap is the biggest mistake.