Location Ambiguity about firmware HOT 10 CLOSED

PRthis feature is at #3248, and support in the Python app is at meshtastic/python#487 If anyone is interested in these features, and wants to test, I'd be very interested to hear how that goes.
Full precision for a channel is 32, and at 0 location data is fully disabled for the given channel.

from firmware.

@dougle03 It's already in the iOS and Android app source code, and will roll out with the next release of both. It's not in the web app yet, but I expect that to happen before too long.

from firmware.

I like this, but it's also probably best changed in the firmware repo and then implemented in the various UIs

from firmware.

Are you not able to reduce location accuracy in android settings? This is an option for any app using location on iOS.

from firmware.

Are you not able to reduce location accuracy in android settings? This is an option for any app using location on iOS.

Not reliably. In some areas it will still be very accurate, depending on local cell and wifi networks.

But you're assuming I'm not using my phone gps for anything else, like navigation.

This function is built in to APRS equipped hand held ham radios as I've described it, with ambiguity based on lat.long decimal places, and it is very effective. It's lso used in android apps which interact with APRS radios.

from firmware.

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/adjustable-gps-precision-for-privacy/9513/3

from firmware.

I've started work on this. Currently using a binary bitmask, so we just set the bits of precision.

from firmware.

Will we see this in the web and Android app? - Perhaps for security purposes ambiguity over position should be the default with the option to increase accuracy.

from firmware.

Is this only for cellular device GPS forwarding or also for the hardware GPS on a node? I'm hoping it's for both so we can anonymize a little bit but still show the general location.

from firmware.

@Firworksyt it's both now. We've added the code in the firmware routine that generates location packets. So regardless of the source, the location gets protected.

from firmware.