My device sends JT808 data to the Traccar server. However, I sometimes notice that when displaying the trajectory, the track points are not connected in the actual driving order.
For example, given several coordinates in the correct chronological order:
gps_data_t0==> gps_data_t1==> gps_data_t2==> gps_data_t3==> gps_data_t4==> gps_data_t5,
the actual display shows the trajectory as:
gps_data_t0==> gps_data_t4==> gps_data_t5==> gps_data_t1==> gps_data_t2==> gps_data_t3.
Upon checking my MySQL database, I found that the records in the database are indeed stored in the order:
gps_data_t0==> gps_data_t4==> gps_data_t5==> gps_data_t1==> gps_data_t2==> gps_data_t3.
I suspect that the trajectory display follows the record order in the database.
The original JT808 data includes a devicetimefield which is correctly sequential according to the trajectory and time. It is estimated that poor communication signals may cause the device to report to the Traccar server out of the real trajectory or devicetimeorder. Alternatively, upon arrival at the Traccar server, factors like server load or other reasons might cause the data to be written to the database out of sequence.
Could you consider modifying this or adding a configuration option so that saving to the database and trajectory display are based on devicetimeinstead?
Have you looked at the fix time?
My device sends JT808 data to the Traccar server. However, I sometimes notice that when displaying the trajectory, the track points are not connected in the actual driving order.
For example, given several coordinates in the correct chronological order:
gps_data_t0==> gps_data_t1==> gps_data_t2==> gps_data_t3==> gps_data_t4==> gps_data_t5,
the actual display shows the trajectory as:
gps_data_t0==> gps_data_t4==> gps_data_t5==> gps_data_t1==> gps_data_t2==> gps_data_t3.
Upon checking my MySQL database, I found that the records in the database are indeed stored in the order:
gps_data_t0==> gps_data_t4==> gps_data_t5==> gps_data_t1==> gps_data_t2==> gps_data_t3.
I suspect that the trajectory display follows the record order in the database.
The original JT808 data includes a devicetimefield which is correctly sequential according to the trajectory and time. It is estimated that poor communication signals may cause the device to report to the Traccar server out of the real trajectory or devicetimeorder. Alternatively, upon arrival at the Traccar server, factors like server load or other reasons might cause the data to be written to the database out of sequence.
Could you consider modifying this or adding a configuration option so that saving to the database and trajectory display are based on devicetimeinstead?