Hello and thank you. I have no idea how an app gets onto Yunohost. But I have now seen that you can nominate an app to be packaged, and someone put Reitti in it. Wishlist Reitti, but it seems they have some restrictions on who can vote for it.
Maybe there is another way to get it on, like a generic Docker thing. If that is a way, I am more than happy to assist.
Hello! If you ask me personally. I am happy with how reitti is working today. It suits my own movement patterns well enough, but everyone is different, so your mileage may certainly vary. I am improving it step by step though, so it should keep getting better over time.
On a general comparison with dawarich: I honestly do not know enough about it anymore to give you a fair assessment. I know they have a comparison on their website, but as with all of these, it is not completely correct. That is simply the nature of such comparisons, and it is also why I will not make one myself. After all, I would be hopelessly biased.
So here is my suggestion: if you have Docker and some gpx files handy (you can export them straight from dawarich), spin up an instance with docker-compose and throw the gpx files at it. See how it goes and whether it fits your needs. If it does not, no worries at all, just shut it down and never think about it again. Or maybe come back and give some feedback. 🙂
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:
-> 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.
That’s exactly the use case someone reported recently.
Right now, you can press a button on an individual image in Reitti if it’s aligned by time rather than location. And if you’ve got multiple images and you’re feeling brave (in other words, you trust Reitti 😄), there’s also a button to do it all at once from the gallery in the map bubbles.
Give it a try, and let me know how it goes! If anything needs tweaking, I’m happy to adjust it. Happy to hear feedback either way!
Hi Jolly, that is an awesome question, and I did not give it much thought. At the moment, there is no search on that data. Even displaying it is hard since you have to open the dialog again.
Right now, it is more like a “gathering phase.” You can collect the data, and we will figure out how this can be used. My main motivation, and I repeat myself for the last three major releases, is to enhance the memories feature with more context. Maybe, if the technique ever becomes feasible for the average homelab, we could generate more personal memories by incorporating some local LLM with the additional information of the tags and descriptions. This currently breaks because there is no single multilingual LLM that works well.
But I like the idea of searching through that data. This could be a nice addition; feel free to create a discussion on GitHub. I really like having multiple views on these topics. The device feature would not have existed if there had been no discussion about it. I always refused it before because it would not fit.
Since the data there is really open and quite free in its structure, I already have some ideas, like putting the songs I heard through Plex, scrobbled through MultiScrobble, into Reitti. That way, I could see what I listened to at that moment. For whatever reason, that sounds like an awesome idea, maybe for a side show when creating a memory of our trips.
Thank you for your kind words. That really warms my heart. 🙏
Give it a try. As an avid timeline user in the past (before the major hiccup last year), I am proud to say that in my experience it works even better than Google Timeline, which, to be honest, I never thought I’d be able to say out loud. Last time I checked, the new timeline was a disaster.
I am happy to hear that.
I fixed the link and it should be resolved in a couple of minutes. I used the wrong one and never tested that command.
Thank you for coming back with that. That really helps :)
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.
You can get data via HTTP into reitti. Registering reitti on a MQTT broker also works.
Thank you for the info. I will check the command.
Dev of reitti here 👋
Reitti allows sharing data like live location between users. If you use the owntracks app, you would even see all users, which share their location woth you, directly in the app.
Else you can see them in reitti directly with their latest known location.
Yes, then it is propably better to wait instead of deleting the data in that way.
When everything goes right we have one or two weeks till the first beta version. Stay tuned 😉
Oh, and please create a backup before that. You never know :)
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.
Hello @KToomey,
thank you for your kind words.
There is currently no official way of removing a day worth of data. You can however delete it directly from the database and issue a recalculation.
I will come back later and tell you the commands. Currently I have some family business to do :)
I personally mainly use GPSLogger on my phone. I had one problem with it but this is remedied in V136 of it and now it can use the HTTP File Upload which brings the battery usage down a lot. So in my experience this works really well. There is also an autoconfig button. You can open the Integrations Settings page on your phone and press the button. This will configure GPSLogger so you do not have to enter the address and the auth token by hand.
I would check the settings afterwards. I have set mine to not report anything with more than 25m accuracy. And upload the data once an hour.