I have experienced PosTime to be incorrect intermittently, the epoch time is occasionally a) correct (1-2 seconds delay) b) incorrect, approximately 121 seconds in the future c) incorrect, approximately 290 seconds in the future I have captured data using https request in JSON format with small time span, but still the epoch times in JSON data gets the static errors in b) and c) above, all PosTime data being consistently wrong for the same aircrafts (since it is just seconds after the first data collection). Has anyone else experienced the same problems? Any idea why this happens?
Someone is sending 100k aircraft reports to the servers. If you are using the JSON feed or TCP feed - some of the shit data is likely being transmitted through. Latest IP was in Germany - 193.124.136.126 Other Offenders sending spam data. 84.105.196.24 81.209.240.65 193.124.141.174 193.124.136.126 If more of this happen just send email or post here.
I experienced the same problem. When I look only at the position fields, I can draw a smooth trajectory which let me think that positions have been obtained on a regular basis (every 60s). But when I look at PosTimes, they greatly differ between 2 upates (45s, 78s, 39s, 57s, 81s....).
? JSON data? or from flight-data ... might be mlat of VRS feeder data being integrated. All it takes one turd to have their windows clock off by a few seconds and using VRS to throw blips in the data. also it's RF, it's not exact.
