Neighbour lists that look tidy until the rain starts
In mixed hill and valley coverage, a neighbour list is a weather-sensitive object. Dry-season drive tests follow the road. Rain changes which faces actually hear each other. Foliage holds water; a side-lobe that was a footnote in August becomes a interferer in April.
We ask for the list as exported, not as redrawn on a slide. Missing neighbours show up as HO failure spikes toward a face that is geographically close and radio-silent in the table. Extra neighbours show up as brief attempts toward a face that never answers.
The quality walkthrough does not retune the list. It marks which HO relations failed in the look-back window and whether those hours coincide with rain gauges or with a known floodplain. Operations can then decide whether to walk the relation in the wet or to leave it until the next planned swap.
Customer-care tickets that say ‘call drops on the bypass’ are useful when they name a time. They are weak when they name only a road. Map the ticket to a sector after you have the hour, not before. Otherwise you will retune the wrong face because the bypass sits under two sites.
Georgia’s mountain roads make this concrete: a single valley can be served by a ridge site and a lower face that only become mutual neighbours when the cloud base drops. A dictionary session that treats ‘neighbour’ as a static planning object will fight the radio desk every spring.