Update detection of visits and places #90

Closed
opened 2025-07-08 08:35:01 -04:00 by AtHeartEngineer · 0 comments

Originally created by @dgraf-gh on 5/31/2025

At the moment if a point is ingested, the LocationProcessingPipeline starts. Which is basically a good idea but the implementation is lackluster.

For example, a point is ingested and the app tries to detect staypoints in the last hour. Which is fine, after that we have a list of StayPoints which then gets converted into Visits with a SignificantPlace. Then another Job is started which merges visits on the timeline and stores them as ProcessedVisits. But now nobody is using the merged and hopefully better ProcessedVisits but the app is working on the raw visits. This is then used for calculating SignificantPlaces and Trips between Visits.

Change the code that first:

  • a visit does not have a place but only lat an long
  • detecting trips and significant places should only be triggered after we have processed visits
*Originally created by @dgraf-gh on 5/31/2025* At the moment if a point is ingested, the LocationProcessingPipeline starts. Which is basically a good idea but the implementation is lackluster. For example, a point is ingested and the app tries to detect staypoints in the last hour. Which is fine, after that we have a list of StayPoints which then gets converted into Visits with a SignificantPlace. Then another Job is started which merges visits on the timeline and stores them as ProcessedVisits. But now nobody is using the merged and hopefully better ProcessedVisits but the app is working on the raw visits. This is then used for calculating SignificantPlaces and Trips between Visits. Change the code that first: - a visit does not have a place but only lat an long - detecting trips and significant places should only be triggered after we have processed visits
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/reitti#90