owntracks / talk

Questions, talk about OwnTracks
30 stars 4 forks source link

Q: why isn't "created_at" in every payload? #157

Closed na-am closed 5 months ago

na-am commented 1 year ago

hi, i wonder why the payload doesn't have all the time "created_at" on location type: {"_type":"location","acc":15,"alt":528,"batt":69,"bs":1,"cog":317,"conn":"m","inregions":["x814"],"inrids":["5eb246"],"lat":47.xx4518,"lon":8.xx2206,"m":2,"p":95.761,"tid":"NE","tst":1680598958,"vac":1,"vel":0}

that happens when i change manually the location interval on my iPhone

thx na-am

jpmens commented 1 year ago

created_at identifies the time at which the message is constructed (vs. tst which is the timestamp of the GPS fix)

na-am commented 1 year ago

yes, i've a message/payload, but no created_at timestamp do you see the point? lat+lon w/o a timestamp i've to ignore for my database

jpmens commented 1 year ago

what is the value of "t" at that moment?

ckrey commented 1 year ago

“created_at” is only created if the timestamp of the fix differs”

jpmens commented 5 months ago

Closing as answered