Repository navigation
Trips and routes
Find Hub sightings arrive every few minutes to hours, with an accuracy of roughly 50 to 200 metres. A tag sitting at home can report ten times in a row from slightly different spots. Find+ turns that raw stream into something a person can read: where the tag stayed, when it travelled, and where nothing was seen.
Stays and trips are worked out from sparse, delayed sightings. Times are when a tag was seen, and distances are approximate straight lines, not the road driven.
- Stays. Consecutive sightings inside one circle for at least 10 minutes become one row with a fix count. The circle is the larger of 75 m and 1.5 times the sighting's own accuracy, measured from a running centre, so jitter inside the accuracy circle never starts a trip. A stay inside a saved place carries its name ("Home"); any other is an "Unnamed stop".
- Trips. The movement between two stays: start and end time and place, duration, an approximate straight-line distance, the number of sightings and the longest gap.
-
Gaps. "No sightings between 3:10 and 4:40." Shown whenever two sightings are more
than 60 minutes apart (change it with
gap_minutes). A gap is missing data, not proof the tag stayed put. -
Sightings that look wrong. Find+ scores every sighting. One that jumps far and
comes straight back (the tag "teleports" 2.5 km and returns within minutes), needs an
impossible speed, sits far from the sightings around it, or disagrees with the rest of
the same person's trackers is flagged. A flagged sighting stays in your history. It is
left out of stays, trips, person events and alerts, and the API lists it under
outlierswithreasons(codes such asaba_teleport) and a plain-wordssuspect_reason. Latest, timeline and export rows carrysuspectandsuspect_reasontoo. A flag is dropped when another sighting of the same tracker, or a sibling tracker, lands within 200 m of it. Two bad sightings in a row are kept: Find+ needs two neighbours that agree before it calls one wrong. Re-score after upgrading withfindplus db recompute-quality [--since DATE]. - One poll of delay. A sighting that jumps more than a kilometre (or faster than a brisk walk) with nothing after it yet is held back from place alerts until the next one arrives. So is one far from where the person's other trackers agree. If the next sighting confirms it, the alert follows one poll late but carries the held sighting's own time; if the tag jumps back, it never fires. If nothing arrives, the hold runs out after 12 minutes and the alert follows then. A real quick out-and-back with a single sighting at the far end (a missed exit and a U-turn) is flagged too, unless a second sighting or another of the person's trackers was there.
On the dashboard and the Person page a flagged sighting is drawn faintly in a dashed ring with the
reason on hover (a "Show sightings that look wrong" box hides them), and it adds nothing to a day's
distance. Why one is greyed out: see the FAQ. Re-score after an upgrade with findplus db recompute-quality.
findplus trips --date 2026-09-18 # table, one tracked device
findplus trips --device-id ID --days 3 --json
curl 'http://localhost:8647/api/trips?device_id=ID&date=2026-09-18'
The MCP server exposes the same answer as get_trips. Each device is segmented on its
own; devices are never merged. A locked app refuses the route like every other data route.
Off by default. Nothing is sent anywhere unless you set routing.endpoint to the base
URL of an OSRM-compatible server, for example your own OSRM or Valhalla-OSRM instance.
Find+ never ships a public demo server address.
Road routes are off unless you enter a routing server address. When one is set, the sightings of each trip you open are sent to that server to draw the path, so use a server you run yourself.
Set it with POST /api/settings/routing.endpoint and {"value": "http://127.0.0.1:5000"};
an empty value turns it off. GET /api/trips/route?device_id=ID&trip_id=T then asks the
server's /match service (falling back to /route) and returns a GeoJSON LineString:
Likely route between sparse sightings, not a record of the road driven.
If the server is unreachable, refuses, or finds no road, you get straight dashed segments between the sightings instead. At most 60 sightings are sent per trip.