RFOXiA LogoRFOXiA Club
← Back to DevHub

MultiNav Pro+ GNSS - how does 1.5m accuracy hold up under tree canopy?

Brittany ThompsonJune 15, 2026
So I'm building a trail mapping device - basically a handheld unit that logs a GPX track while hiking, and I want the path to actually look like the trail and not some wobbly mess 10 meters off in every direction. The MultiNav Pro+ GNSS with 1.5m accuracy spec sounds really promising for this, but the thing is, most of the trails I'm testing on are pretty heavily wooded. Like, thick deciduous canopy, not just light tree cover. I know GNSS accuracy specs are almost always tested in open-sky conditions and I'm just wondering if anyone has actually run this module through anything with real foliage overhead.</TITLE>
 
My concern is that under heavy canopy, signal attenuation from the leaves and branches is gonna reduce the number of visible satellites, and when you're only locking onto 4 or 5 birds instead of 10+, that 1.5m figure probably goes out the window. What I don't know is *how far* out the window. Are we talking 3-4 meters which is still workable for trail mapping, or does it degrade to something like 8-10m where the track just looks garbage? The 18Hz fix rate is actually super relevant here because I'm hoping the high update rate helps smooth things out even when individual fixes are noisier.
 
Also wondering if pairing the sensors module into the mix helps at all in this scenario - like if the accelerometer and gyro can provide some dead reckoning to fill in the gaps during really bad signal moments. I'm guessing that's more of a software fusion problem than something the hardware handles natively, but curious if anyone's already gone down that road with these modules. Any real-world canopy testing data would be awesome, even rough anecdotal stuff is useful at this point.
💬 1 replies👍 0 likes👁 0 views

💬 Want to join this discussion?

Join the Community on RFOXiA Club →

Replies

AdamJune 15, 2026
@Brittany Thompson good question and honestly a really practical one — canopy is where GNSS gear lives or dies for trail applications.
 
The honest answer is that under thick deciduous canopy you're probably looking at 3-6 meters on average, with occasional spikes worse than that during really dense patches or terrain features that cut your sky view down even further. The 1.5m spec is open-sky CEP, so yeah, that's not what you're getting in the woods — but 3-6m is actually still workable for trail mapping if you're not trying to distinguish between two parallel trails 5 meters apart. Your GPX track will look like a trail, not a random walk. The 18Hz rate genuinely does help here because you're averaging more frequent noisy fixes rather than fewer noisy fixes — the noise tends to be somewhat random so the higher sample rate gives your post-processing more to work with.
 
The IMU dead reckoning idea is solid but you're right that it's a software fusion problem, not something that happens natively on the hardware. The sensors module gives you the raw accelerometer and gyro data, but fusing that with GNSS into something like a Kalman filter is work you'd have to implement yourself. It's not trivial, but it's also not a PhD project — there are open implementations you could adapt. The bigger practical issue is that IMU dead reckoning drifts pretty fast on foot (unlike a vehicle with a wheel encoder to anchor it), so it's more useful for bridging a 2-3 second signal dropout than compensating for sustained canopy attenuation over a 10 minute stretch.
 
One thing that helps more than people expect in dense canopy is just raising the antenna position — even a few extra centimeters of clearance on a chest or shoulder mount vs. waist level changes your sky view meaningfully. Worth experimenting with before going deep on sensor fusion.

💬 Want to join this discussion?

Join the Community on RFOXiA Club →