<comment>Estimate calculation source identifier. In multi-function engines like HPE, calculations can be handled by various calculation functions. This source identifier
provides an analytical characterization that enbles a deeper understanding of how the data is processed. Identifiers can include terms like 'hybrid', 'agnss', 'celldb', 'ecid',
tdoa, rf-base1, rf-base2, slame, etc. Terms are not constant and may be substantially different across systems using this XID struct. </comment>
tdoa, rf-base1, rf-base2, slam, etc. Terms are not constant and may be substantially different across systems using this XID struct. </comment>
<comment>The last observation type used to create the estimate. In multi-type observables, multiple estimates will be generated with the last estimate usually indicating the last estimate use.
If estimated simultaneously, then the obstype will be the dominant observations (one with the most obversations and/or least uncertainty). If there is no dominance, then the observation
type is 'undefined'</comment>
type is 'undefined'.</comment>
</elem>
<elemname="tic"type="uint32">
<comment>Tic count of the estimate. For single transaction sessions, the tic count is always 0. For multi-transaction sessions, the tic-count will be monotonic increasing.</comment>
Optional descriptive floor label if available. Floor labels are useful to provide a floor specifier not readily indexed like floor number. Examples include
'Lobby', 'Parking 1', 'Parking 2', 'Mezzannine 1', '12', '14', 'Observation Deck', etc. In cases, where the result is between floors, the floor label may
'Lobby', 'Parking 1', 'Parking 2', 'Mezzannine 1', '12', '14', 'Observation Deck', etc. In cases where the result is between floors, the floor label may
specify a compound label such as 'P1/P2' if supported.
