GeoWind2Plan: Mission-Time 3D Urban Wind Prediction for Energy-Efficient UAV Planning
Shaoxiang Qin, Yucheng Zhao, Fuyuan Lyu, Di Zhou, Jiachen Yao, Xue Liu, Anima Anandkumar, Liangzhu Leon Wang, Xiongye Xiao
NeurIPS 2026 (Spotlight)
cs.AI, cs.RO
2026-09-29
A geometry-conditioned neural operator predicts corridor-local 3D urban wind in about 3 seconds versus 8 hours for CFD, cutting UAV headwind energy 12.7% versus wind-agnostic planning and recovering 86% of CFD-reference savings.
Urban UAV energy depends on more than path length. Buildings reshape ambient wind into spatially varying 3D flow: speed-up through street canyons, slow wakes behind towers, redirected flow around dense clusters. Propulsion energy tracks air-relative velocity, so the geometrically shortest route can be the costliest one. Wind-aware planning therefore needs building-resolved 3D wind, and CFD is the natural source, yet one simulation solves one city under one inflow boundary condition. Change the wind direction or speed and you rerun it; a high-resolution 1.2 km urban case takes about 8 hours, while urban missions last minutes to tens of minutes. Prior energy-aware planners mostly assumed a wind field was already on hand, or used a single wind vector or a height-only profile, discarding the horizontal structure that drives energy cost.
GeoWind2Plan takes three inputs: a background wind vector, 3D building geometry, and a start-goal pair.
The wind predictor is a localized FNO (a neural operator that learns input-function-to-PDE-solution maps) conditioned on occupancy, SDF, and multi-directional distance features, applied to shared 45×45×45 patches. It trains on roughly twenty 1.2 km CFD cases in about 7 hours on a single V100.
The design goal is decision-useful wind, not pointwise CFD reconstruction: trajectories are planned on predicted wind and evaluated under high-fidelity CFD wind.
Evaluation covers four held-out 1.2 km blocks and one 3 km block, 256 missions each, default inflow 4 m/s. Baselines are zero wind and a height-only profile; the CFD field serves as the oracle (planning directly on the true field). Energy is reported in Wh/km; on block A across all wind angles, the oracle sits at 12.3, wind-agnostic at 13.3, and this method at 12.5.
| Setting | Method | Energy overhead vs oracle |
| 8 m/s headwind | agnostic / profile / ours | +41.0% / +18.9% / +7.6% |
| 3 km block, all angles | agnostic / profile / ours | +14.6% / +3.8% / +2.5% |
Averaged over the four 1.2 km blocks, savings over wind-agnostic planning reach 6.9% in tailwind, 12.7% in headwind, and 4.5% in crosswind, recovering 87.9%, 85.7%, and 75.0% of the oracle's savings. Stronger wind raises the value of local 3D structure. Trajectories adapt systematically: higher and faster in tailwind, lower and slower in headwind, with lateral bending that matches the CFD reference. Narrowing the corridor to 10% barely changes energy, but planning fails when a building taller than 120 m spans the corridor and blocks all feasible paths.
This is the first framework coupling wind-conditioned, building-resolved 3D wind prediction with CFD-evaluated UAV energy planning at mission time. For urban logistics or inspection fleets, it removes the need for a precomputed city-wide wind library: a 3-second wind field recovers 75% to 88% of what oracle planning would save, as a pure software gain with no hardware changes. The more transferable idea is the decision-level evaluation protocol: a surrogate's worth is measured by downstream trajectory energy under the true field, not pointwise error.
The absolute savings of 5% to 13% are moderate, but they cost nothing in hardware and still matter for range-constrained vehicles.
Stated by the authors: the model uses time-averaged fields, so turbulence-induced power fluctuations and turbulence safety risks are out of scope, and background wind is assumed fixed during a mission, with no replanning under time-varying inflow. The speed-rescaling error grows to 11.2% at 8 m/s, and thermally stratified or gusty inflow is untested.
Reading closely: training uses about twenty CFD cases, which the authors call the main bottleneck, and generalization to irregular real-city geometry is unverified. All ground truth comes from the CityFFD solver, evaluation reuses the same energy model, and no real flight data backs the numbers. The oracle is a same-optimizer CFD-reference planner, not a certified global optimum.