Mapping Mountain Fields with Neo 2 | Guide

META: Learn how to map mountain fields with the Neo 2 drone. Chris Park shares a step-by-step tutorial covering obstacle avoidance, D-Log, and ActiveTrack tips.

By Chris Park | Creator

TL;DR

Pre-flight sensor cleaning is non-negotiable before every mountain mapping session—dirty obstacle avoidance sensors can cause catastrophic failures at altitude.
The Neo 2's ActiveTrack and obstacle avoidance systems work together to navigate complex mountain terrain, but they require specific configuration for field mapping.
Shooting in D-Log color profile preserves critical shadow and highlight data across uneven mountain terrain where lighting shifts dramatically.
A structured flight plan using QuickShots and Hyperlapse modes can generate comprehensive orthomosaic-ready imagery in a single battery cycle.

Why Mountain Field Mapping Demands a Different Approach

Flat agricultural mapping is straightforward. Mountain field mapping is not. Elevation changes of 200–500 feet across a single plot create inconsistent ground sampling distances, unpredictable wind corridors, and lighting conditions that shift every 15–20 minutes as the sun moves behind ridgelines. The Neo 2 handles these challenges remarkably well—if you set it up correctly.

This tutorial walks through every step I take before, during, and after a mountain mapping flight. I've mapped terraced rice fields in Southeast Asia, vineyard plots in the Andes, and highland grazing pastures across the Appalachians. The workflow below is what I've refined across 70+ mountain mapping missions.

The Pre-Flight Cleaning Step Most Pilots Skip

Here's the step that separates safe mountain flights from disaster stories: cleaning every sensor on the Neo 2 before each flight.

Mountain environments are brutal on drone sensors. Morning dew leaves mineral deposits on downward-facing vision sensors. Trail dust coats the forward and backward obstacle avoidance arrays. Pollen, especially during spring mapping seasons, creates a thin film over infrared proximity sensors that degrades their detection range by as much as 30–40%.

My Sensor Cleaning Protocol

Forward and backward obstacle avoidance sensors: Wipe with a dry microfiber cloth first, then a single pass with a lens-safe cleaning wipe.
Downward vision sensors: Use a blower bulb to remove loose grit before wiping—dragging particles across these sensors scratches the glass.
Camera lens and gimbal housing: Clean the lens with a proper lens pen. Check for condensation inside the gimbal housing if temperatures dropped overnight.
Propeller inspection: Mountain debris nicks leading edges. Run your fingertip along each blade. Any roughness means replacement.
Battery contacts: Wipe gold contacts with a dry cloth. Corrosion from humidity increases internal resistance and reduces flight time by 2–3 minutes.

Pro Tip: I carry a small ziplock bag with a microfiber cloth, a lens pen, a blower bulb, and two lens-safe wipes. The entire cleaning process takes 90 seconds and has prevented at least three crashes that I know of—once the obstacle avoidance system failed to detect a wire fence because the forward sensors were fogged with morning condensation.

Step 1: Plan Your Flight Grid Before You Leave Home

Mountain mapping requires more planning than flatland work. Open your preferred mapping software and load a topographic layer of your target field. Note the following:

Elevation range: The difference between the lowest and highest points of the field.
Slope angle: Anything above 15 degrees requires adjusted overlap settings.
Sun position: Calculate where the sun will be during your flight window to minimize shadow inconsistency.
Wind corridors: Mountain valleys funnel wind. Check forecasts for wind speed at altitude, not ground level.

For the Neo 2, I set my mapping altitude relative to the highest point of the terrain, not the takeoff point. This ensures the minimum ground sampling distance stays consistent across the entire plot.

Step 2: Configure the Neo 2 for Mountain Terrain

Obstacle Avoidance Settings

The Neo 2's obstacle avoidance system is your safety net in mountain environments, but the default settings aren't optimized for mapping flights. Here's what I change:

Set obstacle avoidance to "Bypass" mode rather than "Brake." Braking mid-flight creates gaps in your mapping grid. Bypass mode routes around obstacles and returns to the planned path.
Increase the detection sensitivity to maximum. Mountain fields have fences, poles, trees, and power lines that standard sensitivity might detect too late.
Enable downward sensing even during automated flights. Terrain-following relies on these sensors functioning perfectly—which is why that pre-flight cleaning step matters so much.

Camera and Color Profile

Switch to D-Log immediately. Mountain fields present the most extreme dynamic range challenge in aerial mapping. One side of a terrace sits in full sun while the adjacent step falls in deep shadow. D-Log captures approximately 2–3 extra stops of dynamic range compared to the standard color profile, which preserves recoverable data in both highlights and shadows during post-processing.

Additional camera settings for mapping:

Shutter speed: No slower than 1/focal length × 2 to prevent motion blur.
ISO: Keep at 100–200. Mountain light is typically abundant.
White balance: Manual, set to the current conditions. Auto white balance shifts between frames and creates color inconsistency in stitched orthomosaics.
Image format: RAW only. Compressed formats discard the tonal data D-Log is designed to preserve.

Step 3: Execute the Mapping Flight

Using ActiveTrack for Perimeter Passes

Before running the automated grid, I fly a perimeter pass using ActiveTrack locked onto the field boundary. This accomplishes two things: it captures oblique-angle imagery of the field edges (critical for accurate 3D models), and it gives the Neo 2's systems a chance to register obstacles along the flight path.

ActiveTrack on the Neo 2 handles subject tracking with impressive tenacity, even when the "subject" is a fence line or tree row bordering the field. Lock onto a distinct visual feature at the field's edge and let the drone trace it.

Grid Pattern Execution

For slopes exceeding 10 degrees, increase your front overlap to 80% and side overlap to 70%. Standard 75/65 overlap settings work fine on flat ground but leave gaps on slopes where the effective ground coverage per image shrinks.

QuickShots for Reference Imagery

At each corner of the field, I trigger a QuickShots Dronie or Rocket sequence. These provide contextual reference imagery that helps orient the final map and serves as excellent supplementary content for client deliverables.

Hyperlapse for Progress Documentation

If you're mapping the same field across a growing season, capture a Hyperlapse sequence at a consistent waypoint during each visit. Over 4–6 visits, this creates a compelling time-lapse showing crop development, erosion patterns, or land-use changes. The Neo 2's Hyperlapse mode stabilizes footage effectively even in the 10–15 mph gusts common in mountain valleys.

Technical Comparison: Mountain Mapping Settings vs. Standard Settings

Parameter	Standard Flatland Setting	Mountain Field Setting (Neo 2)
Flight altitude reference	Takeoff point	Highest terrain point
Front overlap	75%	80–85%
Side overlap	65%	70–75%
Obstacle avoidance mode	Brake	Bypass
Detection sensitivity	Standard	Maximum
Color profile	Normal / Standard	D-Log
ISO range	100–400	100–200
White balance	Auto	Manual
Image format	JPEG or RAW	RAW only
Perimeter pass	Optional	Required
Ground control points	Every 500m	Every 200–300m

Expert Insight: The single biggest accuracy improvement I've made in mountain mapping wasn't a software upgrade or a new drone—it was switching from auto to manual white balance. Color inconsistency between frames confuses stitching algorithms, especially along shadow boundaries on sloped terrain. Manual white balance eliminated 60–70% of my stitching errors on terraced fields.

Step 4: Post-Processing Mountain Mapping Data

Import your D-Log RAW files into your stitching software. Apply a flat color correction that normalizes exposure across the set before stitching—this reduces artifacts along seam lines where shadow and sunlit frames meet.

Key post-processing steps:

Apply terrain-aware stitching if your software supports it. This uses the elevation data embedded in each image's metadata.
Generate a Digital Elevation Model (DEM) alongside the orthomosaic. Mountain fields demand elevation data for drainage analysis, erosion risk assessment, and planting optimization.
Export at native resolution. Downsampling before analysis discards the detail you worked to capture.

Common Mistakes to Avoid

Flying in standard color mode instead of D-Log: You'll clip highlights on sun-facing slopes and crush shadows on shaded slopes. This data is unrecoverable in post-processing.
Using ground-level wind forecasts: Wind at 150–300 feet above a mountain valley can be 2–3× stronger than ground-level readings. Always check altitude-specific forecasts.
Skipping the pre-flight sensor cleaning: Obstacle avoidance sensors degrade quietly. You won't know they're underperforming until the drone fails to detect an obstacle.
Setting altitude relative to takeoff point: On a field with 200 feet of elevation change, the drone will be dangerously close to the ground at the highest point or too far away at the lowest point. Reference the highest terrain point.
Running a single battery to zero: Mountain thermals and wind gusts increase power consumption. Land with at least 20% battery remaining—not the standard 15% you'd use on flat ground.
Ignoring the perimeter pass: Skipping oblique edge imagery produces 3D models that fall apart at field boundaries, exactly where erosion and drainage data matters most.

Frequently Asked Questions

Can the Neo 2's obstacle avoidance handle tree canopy near mountain fields?

The Neo 2 detects trees and branches reliably when sensors are clean and sensitivity is set to maximum. Thin branches under 1 cm diameter remain difficult for any vision-based system, so maintain a minimum 10-foot clearance from tree canopy edges. In bypass mode, the drone routes around detected obstacles and returns to the planned grid path automatically.

How many acres can the Neo 2 map on a single battery in mountain terrain?

Expect roughly 15–20 acres per battery at 80% front overlap with moderate wind. Flat terrain yields 25–30 acres under the same settings. The reduction comes from increased hover corrections against wind gusts and the higher overlap requirements. Carry at least 3–4 batteries for any mountain mapping session exceeding 40 acres.

Is D-Log necessary for every mountain mapping flight, or only on high-contrast days?

Use D-Log on every mountain flight regardless of weather conditions. Overcast days still produce significant luminance variation across sloped terrain. The additional dynamic range D-Log captures costs you nothing in flight time and consistently improves stitching accuracy. The only overhead is a slightly longer post-processing workflow—a worthwhile trade for data you can't recapture.

Ready for your own Neo 2? Contact our team for expert consultation.