It would be great if we can set beacon's position ambiguity in case we don't want to broadcast precise location. It seems like the option is available in the backend API, and also mentioned in the doc, just not available to setup in frontend UI.
AFAIK, position ambiguity is only supported in regular position report format or mic-e format, not base91 compressed format. So maybe also add a toggle (that auto xors with position ambiguity toggle) for base91 compression.
(mic-e support for beacon would also be amazing, but it's a bit out of scope for this FR, should i split that into a separate issue or this will do?)
It would be great if we can set beacon's position ambiguity in case we don't want to broadcast precise location. It seems like the option is available in the backend API, and also mentioned in the doc, just not available to setup in frontend UI.
AFAIK, position ambiguity is only supported in regular position report format or mic-e format, not base91 compressed format. So maybe also add a toggle (that auto xors with position ambiguity toggle) for base91 compression.
(mic-e support for beacon would also be amazing, but it's a bit out of scope for this FR, should i split that into a separate issue or this will do?)