I'm using uLogger to upload my positions on PhoneTrack and I noticed crazy speed values reported on tooltips (I'm not driving at 200kph in round-abouts...)
I checked the data from the database and they are fine. Please have a look to the enclosed screenshots.
ISSUE: uLogger uploads speed in Km/hour, while Traccar uploads speed in m/second.
uLogger values are 3.6x too high, as the database is in meters/sec
uLogger(m/sec) = uLogger(kph)x1000/3600 = uLogger(kph)/3.6
Speed is 55.8kph in database, which seems ok (and not 200.880kph as displayed on the map)
I can provide more values for debug if needed (prior and next points values)
BTW, the statistics panel is also reporting wrong values (top speed above 360kph and average speed of 230kph... not bad )
I manually updated the database table and divided all speed values by 3.6 and now the speeds are fine on the map.
Fix is still needed for newly acquired values.
In Ulogger case, speed was multiplied by 3.6 when received by PhoneTrack... It's been fixed and pushed to master. Could you update to latest master branch state and confirm the speed is now correct (for newly logged points) ?
I will check the modification today and keep you updated.
I modified yesterday the issue description to explain the 3.6 ratio:
m/second = km/hour x (1000m / 3600sec) = km/hour x 3.6
I have two suggestions to improve the server :
I noticed also that uLogger can also log the GPS accuracy (in meters),
and which is not currently logged by Phonetrack
There should be a way to filter incoming positions (ignore new position
if we are almost at the same place ---> a "minimum distance" parameter)
You're wrong about the speed unit sent by Ulogger. It sends it in m/s and there was a wrong conversion (*3.6) done by PhoneTrack when receiving positions from Ulogger. It has been removed as i said before. Nothing has to be done to speed value on points sent by Ulogger.
This is off-topic but :
i can check how accuracy is named in Ulogger logging queries and store it
"minimum distance" is a logger-related feature. PhoneTrack stores whatever is sent to it. Most (all ?) of the logging apps have that parameter.
My mistake, uLogger does upload accuracy (in meters) while Traccar doesn't (accuracy stored = 0 in database)
uLogger has the location source (GPS, network) which is interesting for filtering, while Traccar
By the way, I'm not synced with the trunk (Phonetrack installed by NextCloud repository) so I manually patched the logcontroller.php and it works
Btw a huge benefit of using git to get latest development version is that you cannot make mistakes or forget to apply changes on one file. It just works. Don't hesitate to delete PhoneTrack folder and clone the repository to try latest version. Then you can simply disable the app, delete the clone and install it again with Nextcloud web interface. I wrote a few snippets to explain those manipulations.