I'm using the API to retrieve a trip. this is the retrieved json data:
averageSpeed: 0.18790506666666665
deviceId: 28
deviceName: "CAL 749"
distance: 17.040000915527344
driverName: null
driverUniqueId: null
duration: 468000
endAddress: null
endLat: 20.6678096
endLon: -103.32899809999999
endOdometer: 8919950670.87
endPositionId: 450048
endTime: "2019-12-17T17:10:08.000+0000"
maxSpeed: 0.311015
spentFuel: 0
startAddress: null
startLat: 20.667840599999998
startLon: -103.3290413
startOdometer: 8919950653.83
startPositionId: 449902
startTime: "2019-12-17T17:02:20.000+0000"
For what I understand, everything that says "start" (e.g. startTime) is the data of the beginning of the trip and everything saying "end" (e.g. endTime) is the data of the end of the trip.
This is OK for startTime - endTime, startOdometer - endOdometer, however, this is not correct for startLat/startLon because when putting startLat/startLon in a map it doesn't represents the beginning of the trip but ratter it seems to be some other position in the whole trip. I can assure this because when visualizing in traccar, the beginning of the trip is actually position 0,0. I would expect StartLat/StartLon to be 0,0 but that is not the case, instead API is retrieving startLat: 20.667840599999998, startLon: -103.3290413
Is this the intended behaviour? is this a bug? Would help a lot to clarify this. Thank you.
I'm using the API to retrieve a trip. this is the retrieved json data:
averageSpeed: 0.18790506666666665
deviceId: 28
deviceName: "CAL 749"
distance: 17.040000915527344
driverName: null
driverUniqueId: null
duration: 468000
endAddress: null
endLat: 20.6678096
endLon: -103.32899809999999
endOdometer: 8919950670.87
endPositionId: 450048
endTime: "2019-12-17T17:10:08.000+0000"
maxSpeed: 0.311015
spentFuel: 0
startAddress: null
startLat: 20.667840599999998
startLon: -103.3290413
startOdometer: 8919950653.83
startPositionId: 449902
startTime: "2019-12-17T17:02:20.000+0000"
For what I understand, everything that says "start" (e.g. startTime) is the data of the beginning of the trip and everything saying "end" (e.g. endTime) is the data of the end of the trip.
This is OK for startTime - endTime, startOdometer - endOdometer, however, this is not correct for startLat/startLon because when putting startLat/startLon in a map it doesn't represents the beginning of the trip but ratter it seems to be some other position in the whole trip. I can assure this because when visualizing in traccar, the beginning of the trip is actually position 0,0. I would expect StartLat/StartLon to be 0,0 but that is not the case, instead API is retrieving startLat: 20.667840599999998, startLon: -103.3290413
Is this the intended behaviour? is this a bug? Would help a lot to clarify this. Thank you.