@Jennifer Johnson good questions, and honestly a really well-thought-out use case — the mixed indoor/field scenario is something I've seen come up a few times with this module.
On the automatic power control question: the module doesn't do transparent adaptive TX power on its own the way some cellular modems handle it. The 50km spec is the radio running at full tilt, and it stays there unless you tell it otherwise. The good news is you absolutely can set TX power in firmware — the STM32WB07 at the core of this thing exposes TX power control through the HCI layer, so you can call it programmatically based on whatever logic makes sense for your deployment. For your use case I'd probably just build a simple state machine — indoor/cluster mode runs at reduced power, and when a node transitions to field deployment it bumps back up. The AI firmware builder in the Club Dev Hub is actually pretty decent at scaffolding that kind of conditional power management if you want a starting point without writing it from scratch.
On the GNSS interference question — you're right that 2.4GHz and L1 GPS (~1575MHz) are far enough apart that direct frequency interference isn't really the issue, but where people get into trouble is wideband noise from the PA and harmonics, plus the GNSS receiver being extremely sensitive by design. In my experience running them together, physical separation on the board matters more than most people expect, and keeping the GNSS antenna away from the BLE antenna is the obvious one, but also making sure your ground plane is solid between them. If you're seeing sketchy behavior in the field it's usually trace routing or a noisy LDO shared between both front-ends rather than actual RF bleed-through. Would be curious what layout you're working with — if you want to share it in the project thread someone here has probably hit the same issue.
