Rogue data points from past locations

I'm seeing occasional rogue points being collected by OT, significant distances away from my current location but recorded with reasonable accuracy. The weird part seems to be that these points to correspond to other locations I've been recently, though not duplicates of any past points.

Example data points

Here's a snippet of a one-time trip I did ~10 days ago (all recorded around 110-120m accuracy), as viewed in the OT frontend:

And here are two rogue points from yesterday while I was about 50km away (note that it's about 30m south of the previous data, but with the same recorded accuracy of ~120m):

Here's the real location with the two jumps away and back, along with a third to another different location I've also been recently:

These rogue points were both recorded with zero speed (at the real location I was moving 0-10km so they may have been correct at those times), and the device battery level fits with yesterday's data (as opposed to the location data it aligns with).

This has happened several times now, jumping to different cities as well as shorter distances within the same city when I've got regular activity there.

I'm not sure exactly where the problem actually lies, but I'm assuming it's on the Android capture side as this does seem to be a discrepency between OT and other location-collecting apps on the same device. I'm running μlogger in parallel (having intended to migrate to OT about a month ago) and that hasn't shown any discrepencies like I'm seeing here.

This smells like it's picked up a location from a lower-accuracy provider (e.g. network). Some other apps take a different approach to filtering these out, so I wonder if there's something that can be done in OT to achieve a similar effect.

Looking at the ulogger source, it seems like they discard network-provided locations if they receiuved a GPS location recently (beneath a threshold), which is a good idea!

I'll add in an option to allow people to do that and let's see if that helps.

feat: allow the user to hint that low-accuracy locations should be dr…

What's the recommemdet setting (e.g. used in ulogger)?

I configured it in OwnTracks with 300 and it provides a very good result to me. Thanks for implementing it!

I think it can be the solution for several open tickets like:
#1586
#2034

I've set discardNetworkLocationThresholdSeconds: 120 in v2.5.4 configuration management (not sure what a reasonable value is here) but it doesn't seem to have stopped these rogue points.

To be clear, they are being logged as source: network but claim high accuracy / low acc, which is way off (guessing that's the phone reporting that incorrectly though).

Example recorder logs

2025-10-24T09:10:11Z    *                       {"_type":"location","_id":"60d742de","acc":21,"alt":46,"batt":94,"bs":0,"cog":132,"conn":"m","created_at":1761297010,"lat":51.5xxxxxxx,"lon":-0.1xxxxxxx,"m":1,"source":"gps","tid":"ud","topic":"owntracks/user/device","tst":1761297011,"vac":34,"vel":3,"_http":true}
2025-10-24T09:10:31Z    *                       {"_type":"location","_id":"9f767ede","acc":22,"alt":53,"batt":94,"bs":0,"cog":0,"conn":"m","created_at":1761297034,"lat":52.yyyyyy,"lon":0.yyyyyyy,"m":1,"source":"network","tid":"ud","topic":"owntracks/user/device","tst":1761297031,"vac":3,"vel":0,"_http":true}
2025-10-24T09:10:31Z    *                       {"_type":"location","_id":"d981b7e4","acc":22,"alt":53,"batt":94,"bs":0,"cog":0,"conn":"m","created_at":1761297034,"lat":52.yyyyyy,"lon":0.yyyyyyy,"m":1,"source":"network","tid":"ud","topic":"owntracks/user/device","tst":1761297031,"vac":3,"vel":0,"_http":true}
2025-10-24T09:10:31Z    *                       {"_type":"location","_id":"cf593917","acc":22,"alt":53,"batt":94,"bs":0,"cog":0,"conn":"m","created_at":1761297110,"lat":52.yyyyyy,"lon":0.yyyyyyy,"m":1,"source":"network","t":"p","tid":"ud","topic":"owntracks/user/device","tst":1761297031,"vac":3,"vel":0,"_http":true}
2025-10-24T09:12:42Z    *                       {"_type":"location","_id":"ce4c55ba","acc":3,"alt":53,"batt":93,"bs":0,"cog":149,"conn":"m","created_at":1761297162,"lat":51.5zzzzzz,"lon":-0.1zzzzzz,"m":1,"source":"fused","tid":"ud","topic":"owntracks/user/device","tst":1761297162,"vac":4,"vel":4,"_http":true}

All of the 09:10:31 points report the same location about 50 miles away from my actual location.

feat: allow the user to hint that low-accuracy locations should be dr…

Navigation Menu

Repository navigation

Rogue data points from past locations #2053

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Rogue data points from past locations #2053

Description

Activity

growse commented on Aug 17, 2025

mar565 commented on Sep 2, 2025

Intenos commented on Sep 18, 2025

Terrance commented on Oct 25, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions