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

help-circle


  • 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 🙏





  • Sure, give it a try if it fits your case. Bear in mind that reitti is really designed to track your whole day and only your personal movement. It will happily create a visit if you upload two separate gpx file with a gap between them of a day or so. This is a feature to circumvent battery saving modes and missed tracking in the accompanying gps apps.

    It can work but it sounds like you would benefit from the devices feature in the next release (not counting bugfixes here) The plan would be to merge then all gps data (automatically or manual) into one timeline. So all data of all devices together can be your personal movement.


  • Hello, thank you for your feedback.

    In one of the next updates, editing functionality will be added. Perhaps I can also add a function to add points in between.

    For my use case, Reitti already does a lot of cleaning up unrealistic or too dense data. However, sometimes it is missing a point or two. Especially old Google Takeouts or timeline data are notoriously bad. So, sometimes in my data, I visited Jakarta according to Google. I have never been there. The idea is that I should be able to delete that point or move it somewhere else.

    This will come in one of the next releases. There is no timeframe right now, as I first need to do a little bit of planning, and to be honest, I need a break from coding for a week or so after putting the new map into Reitti over the last three months. I thought it would be easier, but there were a lot of quirks in Deck.gl and MapLibre.