• 8 Posts
  • 115 Comments
Joined 3 years ago
cake
Cake day: July 17th, 2023

help-circle

  • Yeah, understanding the data beneath the point would help alot. The problem with that is that we first can not query some system for every point. And second, since the raw data is already jumping around alot, even if we could it is still way off.

    Commute tracking could be a way for the statistics. They need to improve a lot.

    For the logic to detect valid points, we basically do that already for the visit detection. I am quite happy with it right now. Maybe the second year of reitti will be focused on the trips. 😀

    Google did something like the confidence thing in their old timeline (Records.json) format. There for every path they had stored the confidence of the transportation mode.

    And finally the mobile app. I doubt it will come the next year but we never know. I would have some ideas like tracking bumps (smoother rides are propably a car or train, elevation above x meters is propably a plane and so on) and such things to have more confidence in the trip detection. Right now, there is an app for everyone available which can report into reitti. So there is no pressure. But I don’t know, I also did not thought about writing my own reverse geocoder but that also came out of a necessity to have some smaller hosting on a small vps.


  • otherwise a way to reclassify all trips between the same places via the same route at once would be great

    After thinking about this part a bit: I could add something like a rule system to reitti. I will do it either way since I am searching for a way to add notifications to reitti. One rule then could be, if there is a trip between place A and B, during the workweek between 07:00 and 09:00, re-classify this as train ride. But this would override then the walk to the trainstation. So the rule would need to be:

    • Trip between Place A and Place B
    • during workweek
    • between 07:00 and 09:00
    • trip is classified as driving

    -> switch it to transit

    Another idea: adding hints for the classification in the transportation mode setting. Like: during the workweek, between 07:00 and 09:00 it is more likely I take the train instead of the car. The classification could then pull that information in and decide based on the hints which one to choose


  • Hello! Thank you so much for your kind words, they really mean a lot! 😊

    I already have some ideas for improving transportation detection down the line. One option is understanding the track beneath the path, sort of a “reverse route planner”: we have the route and then figure out which mode of transport was used along it. Another idea is analyzing the movement pattern in more sophisticated ways. Train rides might be recognizable by their consistent speed with full stops in between (I’m no train operator, but in my mind they accelerate to max speed, cruise, then stop), whereas car rides tend to fluctuate more.

    I completely understand your point. Especially when switching between trains and cars, speed alone makes it really hard to pick the right mode. I’ll definitely keep working on improving this!

    As for your second point: there’s colota-forwarder, which can fan out GPS points from one system to multiple others. Maybe that would work for your use case? I don’t currently see reitti itself implementing something like that, as it would mean keeping up to date with other services’ APIs and reacting whenever they change.

    Thanks again for taking the time to share your thoughts.










  • I try to be active on both. Reddit has the reach, but I like the vibe of this community on Lemmy. It is so much calmer and friendlier.

    Over the last year, the community came up with some awesome ideas I incorporated into Reitti. It is easy to miss some of them. I try to add as much documentation as possible, but it is, on one side, hard to anticipate how users search for features and, on the other, not to miss some of them over time. Maybe it is a good idea to take some time and add all missing stuff since I am wrapping up the 5.0 release.

    If I remember correctly, data sharing came as a suggestion on my first post here on Lemmy. Over the last year, I refined that, and now users on the same instance can share their data. You are even able to connect to users on other instances of Reitti and finally share your data via magic links.

    I am really thankful for all the support Reitti gets, and the ideas of our users make a difference in how it is coming along.







  • So here are the commands to delete the data directly from the database. It would be best to stop reitti before that.

    You need to replace :start_time and :end_time with the actual timestamps in the form of ‘2025-05-31T03:19:13.000Z’

    -- Here we first delete the data
    DELETE FROM raw_location_points WHERE user_id = 1 AND timestamp >  :start_time AND timestamp < :end_time;
    DELETE FROM processed_visits WHERE user_id = 1 AND start_time < :end_time AND end_time > :start_time;
    DELETE FROM trips WHERE user_id = 1 AND start_time < :end_time AND end_time > :start_time;
    
    -- now we mark the last point before and the first point after the deleted range as unprocessed
    UPDATE raw_location_points SET processed = FALSE WHERE id IN (SELECT id FROM public.raw_location_points WHERE user_id = 1 AND timestamp < :start_time ORDER BY timestamp DESC LIMIT 1);
    UPDATE raw_location_points SET processed = FALSE WHERE id IN (SELECT id FROM public.raw_location_points WHERE user_id = 1 AND timestamp > :end_time ORDER BY timestamp LIMIT 1);
    

    The next time, data comes in these newly marked points will be processed with the incoming data and should fix up everything.

    Let me know if you need further help.

    In the upcoming release, you would be able to delete them by hand in the UI. But I am working on the final stretches until I can declare the first beta release.




  • Oh, thank you for that detailed explanation. Based on that, I think that Reitti is not a good fit for it. It is designed to capture your personal movements but will fail to do so if there are gaps in between or multiple devices log into the same account.

    Maybe Traccar would be a better fit. From my understanding, it is designed to capture multiple devices.

    But maybe the upcoming devices feature aligns Reitti more with your use case. This could/will also bring support for fragmented tracks on a device level. From there, nothing speaks against exporting that single track then.

    Cropping seems like a nice idea I could add to the, also upcoming, edit functionality.

    Thank you for the inspiration 🙏