I currently have coban units reporting every 45 seconds to our server. When reviewing the stored locations, you see that the GPS device is reporting optimally, every 45 seconds, but when reviewing the information history, the reports come out with repeated locations. When investigating, I observed that traccar takes the fixtime as the adjusted data for the generation of reports in the history, but when analyzing the behavior of this field I noticed that when the device reports the same longitude and latitude the fixtime fails and maintains the same time where the longitude and latitude. That is, when the device reports the same longitudes and latitudes for different periods, the fixed time adjusts them to the last time the location changed. It should be noted that the location is marked as valid, a situation that leads to a bad report, since it does not clearly show the reporting times that the GPS is reporting. I attach data images. This error is evident on all units.
Fix time is not calculated. It's reported by yout device.
I currently have coban units reporting every 45 seconds to our server. When reviewing the stored locations, you see that the GPS device is reporting optimally, every 45 seconds, but when reviewing the information history, the reports come out with repeated locations. When investigating, I observed that traccar takes the fixtime as the adjusted data for the generation of reports in the history, but when analyzing the behavior of this field I noticed that when the device reports the same longitude and latitude the fixtime fails and maintains the same time where the longitude and latitude. That is, when the device reports the same longitudes and latitudes for different periods, the fixed time adjusts them to the last time the location changed. It should be noted that the location is marked as valid, a situation that leads to a bad report, since it does not clearly show the reporting times that the GPS is reporting. I attach data images. This error is evident on all units.
