<blockquote style="border-left: 1px solid #aaa; margin: 10px 0; padding: 0 10px;"><p style="white-space: pre-wrap; word-wrap: break-word;">I think there is no constraint from a CPU/harware point of view to use float these days.</p></blockquote><p style="white-space: pre-wrap; word-wrap: break-word;">ok nice, then I'll move to float for the GAD latitude and longitude.</p><p style="white-space: pre-wrap; word-wrap: break-word;">Wondering whether the "uncertainty circle" should also move to float meters instead of the integer millimeters. The uncertainty circle that the SMLC wants to return usually moves in TA steps of 550m. But the definition of the uncertainty coding actually has nonlinear steps. Looking at the 256 codes representing distance in millimeters:</p><pre style="font-family: monospace,monospace; white-space: pre-wrap;">static uint32_t table_uncertainty_1e3[128] = {<br> 0, 1000, 2100, 3310, 4641, 6105, 7715, 9487, 11435, 13579, 15937, 18531, 21384, 24522, 27974, 31772, 35949,<br> 40544, 45599, 51159, 57274, 64002, 71402, 79543, 88497, 98347, 109181, 121099, 134209, 148630, 164494, 181943,<br> 201137, 222251, 245476, 271024, 299126, 330039, 364043, 401447, 442592, 487851, 537636, 592400, 652640, 718904,<br> 791795, 871974, 960172, 1057189, 1163908, 1281299, 1410429, 1552472, 1708719, 1880591, 2069650, 2277615,<br> 2506377, 2758014, 3034816, 3339298, 3674227, 4042650, 4447915, 4893707, 5384077, 5923485, 6516834, 7169517,<br> 7887469, 8677216, 9545938, 10501531, 11552685, 12708953, 13980849, 15379933, 16918927, 18611820, 20474002,<br> 22522402, 24775642, 27254206, 29980627, 32979690, 36278659, 39907525, 43899277, 48290205, 53120226, 58433248,<br> 64277573, 70706330, 77777964, 85556760, 94113436, 103525780, 113879358, 125268293, 137796123, 151576735,<br> 166735409, 183409950, 201751945, 221928139, 244121953, 268535149, 295389664, 324929630, 357423593, 393166952,<br> 432484648, 475734112, 523308524, 575640376, 633205414, 696526955, 766180651, 842799716, 927080688, 1019789756,<br> 1121769732, 1233947705, 1357343476, 1493078824, 1642387706, 1806627477,<br>};</pre><p style="white-space: pre-wrap; word-wrap: break-word;">In the end steps as large as 2km, even though having nonzero "precision" down to a millimeter.</p><p style="white-space: pre-wrap; word-wrap: break-word;">From a user perspective, having a float indicating meters is more SI unit typical and has less amount of confusing digits... or maybe even use km?</p><p><a href="https://gerrit.osmocom.org/c/libosmocore/+/20331">View Change</a></p><ul style="list-style: none; padding: 0;"></ul><p>To view, visit <a href="https://gerrit.osmocom.org/c/libosmocore/+/20331">change 20331</a>. To unsubscribe, or for help writing mail filters, visit <a href="https://gerrit.osmocom.org/settings">settings</a>.</p><div itemscope itemtype="http://schema.org/EmailMessage"><div itemscope itemprop="action" itemtype="http://schema.org/ViewAction"><link itemprop="url" href="https://gerrit.osmocom.org/c/libosmocore/+/20331"/><meta itemprop="name" content="View Change"/></div></div>
<div style="display:none"> Gerrit-Project: libosmocore </div>
<div style="display:none"> Gerrit-Branch: master </div>
<div style="display:none"> Gerrit-Change-Id: Ib9aee749cd331712a4dcdadfb6a2dfa4c26da957 </div>
<div style="display:none"> Gerrit-Change-Number: 20331 </div>
<div style="display:none"> Gerrit-PatchSet: 2 </div>
<div style="display:none"> Gerrit-Owner: neels <nhofmeyr@sysmocom.de> </div>
<div style="display:none"> Gerrit-Reviewer: Jenkins Builder </div>
<div style="display:none"> Gerrit-Reviewer: neels <nhofmeyr@sysmocom.de> </div>
<div style="display:none"> Gerrit-CC: laforge <laforge@osmocom.org> </div>
<div style="display:none"> Gerrit-CC: pespin <pespin@sysmocom.de> </div>
<div style="display:none"> Gerrit-Comment-Date: Mon, 05 Oct 2020 18:49:23 +0000 </div>
<div style="display:none"> Gerrit-HasComments: No </div>
<div style="display:none"> Gerrit-Has-Labels: No </div>
<div style="display:none"> Gerrit-MessageType: comment </div>