When you start talking about fusing/correlating/combining data, time becomes very important. If systems are using different time sources, it is important to know that. If they are supposed to be synced to the same source, it is important to know if one is drifting. I see a utcSync flag in the individual track report. This may be accomplishing what I am describing, although the description is lacking. It is also not necessary to send this with every track report (at least not for any reason I can think of). Time does not drift very quickly, so putting this status in a periodic status message should be sufficient and save bandwidth.
When you start talking about fusing/correlating/combining data, time becomes very important. If systems are using different time sources, it is important to know that. If they are supposed to be synced to the same source, it is important to know if one is drifting. I see a utcSync flag in the individual track report. This may be accomplishing what I am describing, although the description is lacking. It is also not necessary to send this with every track report (at least not for any reason I can think of). Time does not drift very quickly, so putting this status in a periodic status message should be sufficient and save bandwidth.