Thanks for your quick reply.
Yes I am sure I evaluate the correct fields.
some php code:
....
$request_body = file_get_contents('php://input');
$data = json_decode($request_body, true);
$unixtime = $data['when'];
$lat = $data['where_lat'];
$lon = $data['where_lon'];
$vel = $data['body']['velocity'];
$bearing = $data['body']['bearing'];
....
and then standard code that I also use in different applications (eg to forward JSON locations from a LORA network to my traccar server):
...
curl_setopt($ch, CURLOPT_URL, "http://127.0.0.1:5055/?id=$id&lat=$lat&lon=$lon&
timestamp=$unixtime&speed=$vel&bearing=$bearing");
...
So I receive the un-altered JSON message generated on the note(card/hub) side in my php script. JSON decode it, convert it into a PHP array, and pick the pieces that I am interested in.
Please note that the overlaying arrows in the posted picture change direction, so the $data[‘body’][‘bearing’] value changes, just not the where_lon and where_lat values. Per sync that is.
What I find interesting though is that velocity and bearing are contained within the body of the JSON message, while where_lat and where_lon are a level higher, (together with tower information).
I hope my ignorance is being excused, but I was kinda expecting latitude and longitude to be part of the body of the ‘file’ - together with bearing and velocity - and not part of the transmission information - a level higher.
I cannot find any documentation about the data format either. Maye somebody can point me to it, please.
