Skip Navigation
Introducing reitti: a selfhosted alternative to Google Timeline
  • Hi ada,

    yes, this will impact the visit calculation. Visits are calculated in building clusters of at least 5 points in a range of 100m over a duration of at least 5 minutes. If there is only one point logged for example at work or home, Reitti is not able to detect when you left it because every point is just an instant in time and does not carry any duration information with it.

    The more points we have to calculate Visits the more accurate it will be. I personally have set up GPSLogger to log every 30 seconds no matter how far I travelled but with at least 40m of accuracy.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • Hi LazyToad,

    it depends. Reitti on its own does not import any pictures. It only shows fetches them from Immich. For that to work it needs the geolocation where the image was taken in the exif data. You need to check if your expected image has this data in Immich. If it is available it shoud be displayed on the map if you select the day the picture was taken.

    Does it show the location in Immich? You can verify this if you open the image in Immich and let it display the Info.

    If it is showing, then it still could be that it is a bug in Reitti. Feel free to open an issue then :)

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • Cool, thanks for the feedback.

    For: 1: There should be something about downloading in the Photon logs. You can check with docker compose logs photon. I do not remember how long it took to download the index for Germany, but it was noticeable. It depends a lot on how you are connected to the internet and then how long it takes to extract the index.

    2: You should also see that in the log of Photon. If the default does not work reliably, you can create an account on Geoapify; it is free, and you get 3000 reverse geocode requests per day. I personally have Photon for DE and then the default service and additional Geoapify.

    3: Yeah, I was also thinking about that. In the end, a per-user setting and then the overlay should be disabled, but it could take a while until I can get to it.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • I am glad it worked out for you in importing the first file. I am still puzzled why it took that long.

    For the new format, did you have Android or iOS? With the timeline export from Google Maps on iOS, we can not do anything at the moment because there is actually no raw data in it. Only information like you stayed in this timeframe at that point and you traveled between these points. It's actually a little bit funny that it aggregates to the same data Reitti uses in the end.

    If you are on Android, it could also be a bug when importing that file. I only had a small one from one of my accounts to test. If you mind creating a bug report, I will have a look. If you do not want to attach the export file there, feel free to send it to daniel@dedicatedcode.com. I will have a look at it then privately. No problem.

    For the overlap in exports, it depends. If the points are the same, meaning they have the same timestamp, then Reitti will discard them. If not, they will be handled like every other new data and will end in recalculating visits and trips around that particular time.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • This process is not triggered by any external events.

    Every ten minutes, an internal background job activates. Its function is to scan the database for any RawLocationPoints that haven't been processed yet. These unprocessed points are then batched into groups of 100, and each batch is sent as a message to be consumed by the stay-detection-queue. This process naturally adds to the workload of that queue.

    However, if no new location data is being ingested, once all RawLocationPoints have been processed and their respective flags set, the stay-detection-queue should eventually clear, and the system should return to a idle state. I'm still puzzled as to why this initial queue (stay-detection-queue) is exhibiting such slow performance for you, as it's typically one of the faster steps.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • Thank you for testing Reitti. 🙏

    It depends on two key requirements for Reitti:

    1. First, it finds all photos from Immich taken on the day you selected.
    2. Then, it filters these photos based on the selected map bounds, using the embedded EXIF geolocation data (where the photo was shot).

    If the EXIF data does not contain geolocation information, we currently cannot display those photos because their placement on the map cannot be determined.

    Could you please verify in Immich if the expected photo has its location in the metadata? If it is available there, then the issue might lie in how Reitti is parsing that specific data.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • That's good, but I still question why it is so slow. If you receive these timeout exceptions more often, at some point the data will cease to be analyzed.

    I just re-tested it with multiple concurrent imports into a clean DB, and the stay-detection-queue completed in 10 minutes. It's not normal for it to take that long for you. The component that should take the most time is actually the merge-visit-queue because this creates a lot of stress for the DB. This test was conducted on my laptop, equipped with an AMD Ryzen™ 7 PRO 8840U and 32GB of RAM.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • Thanks for getting back to me. I can look into it. I don't think it's connected, but you never know.

    The data goes the same way, first to RabbitMQ and then the database. So it shouldn't matter, it's just another message or a bunch of them in the queue.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • Hmm, I had hoped you say something like a Raspberry PI :D

    But this should be enough to have it processed in a reasonable time. What I do not understand in the moment is, that the filesize should not affect it in any way. When importing it 100 Geopoints are bundled, send to RabbitMQ. From there we retrieve them, do some filtering and save them in the database. Then actually nothing happens anymore until the next processing run is triggered.

    But this than works with the PostGis DB and not with the file anymore. So the culprit should be there somewhere. I will try to insert some fake data into mine and see how long it takes if i double my location points.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • Thanks for the information. I will try to recreate it locally. In my testing I used a 600MB file and this took maybe 2 hours to process on my server. It is one of these ryzen 7 5825U. Since Reitti tries to do these analysis on multiple cores we start it with 4 to 16 Threads when processing. But the stay detection breaks when doing it that way, so it is locking per user to handle that. If now one of them takes a long time the others will break eventually. They will get resheduled 3 times until rabbitmq gives up.

    On what type of system do you run it?

    I will add some switches so it is configurable how many threads are opened and add some log statements to print out the duration it took for a single step.

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • It was not intentional but after bothering not about it because i had other things on my mind i got used to it and now like it the way it is.

    But for everyone who is bothered by that. If Reitti reaches 1k stars on Github I will add a switch to use a centered one 😊

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • Oh, i had the idea in mind what i want to create and than it was a matter of a couple of Google queries but in the end one of the LLM suggested a list of different names in foreign languages and reitti somehow sticked 😊

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • I had a similar setup with Home Assistant in the past so I understand your usecase. For Reitti to detect visits somewhat reliable it needs at least one datapoint of location data a minute. We build location clusters with minimum 5 points in 5 minutes. If HA tracks that often it should work. HA probably tracks more than that.

    I could add an integration that Reitti fetches the data from Home Assistant. Do you mind in creating a feature request?

  • Introducing reitti: a selfhosted alternative to Google Timeline
  • I looked at the docker image i am using in the docker-compose file and this only supports having a single country code. The actual reason can be found here: https://github.com/rtuszik/photon-docker/blob/3b63df49fbc0a77cafcbd6e6be2b8857c12b9143/start-photon.sh#L341C5-L342C7

    It is probably possible if you deploy photon on its own and then import the data somehow. But that is to much hassle for me, i think and hope that most of the use case is handled by the current solution. At least for most of the potential users. But I get the point if someone is traveling a lot between countries.

    If there is enough demand I could maybe try to create a PR for the Docker image to handle multiple country codes.

  • Introducing reitti: a selfhosted alternative to Google Timeline
    github.com GitHub - dedicatedcode/reitti

    Contribute to dedicatedcode/reitti development by creating an account on GitHub.

    GitHub - dedicatedcode/reitti

    Hey everyone!

    I'm excited to introduce Reitti, a location tracking and analysis application designed to help you gain insights about your movement patterns and significant places—all while keeping your data private on your own server.

    Core Capabilities:

    • Visit Tracking: Automatically recognizes and categorizes the places where you spend time, using customizable detection algorithms
    • Trip Analysis: Analyzes your movements between locations to understand how you travel whether by walking, cycling, or driving
    • Interactive Timeline: Visualizes all your past activities on an interactive timeline with map and list views that show visit duration, transport method, and distance traveled

    Photo Integration:

    • Connect your self-hosted Immich photo server to seamlessly display photos taken at specific locations right within Reitti's timeline. The interactive photo viewer lets you browse galleries for each place.

    Data Import Options:

    • Multiple Formats Supported: Reitti can import existing location data from GPX, GeoJSON, and Google Takeout (JSON) backups
    • (Near) Real-time Updates: Automatically receive location info via mobile apps like OwnTracks, GPSLogger or our REST API

    Customization:

    • Multi-geocoding Services: Configurable options to convert coordinates to human-readable addresses using providers like Nominatim
    • User Profiles: Customize individual display names, password management, and API token security under your own control

    Self-hosting:

    • Reitti is designed to be deployed on your own infrastructure using Docker containers. We provide configuration templates to set up linked services like PostgreSQL, RabbitMQ and Redis that keep all your location data private.

    Reitti is still early in development but has already developed extensive capabilities. I'd love to hear your feedback and answer any questions to tailor Reitti to meet the community's needs.

    Hope this sparks some interest!

    Daniel

    103
    InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DA
    danielgraf @discuss.tchncs.de
    Posts 1
    Comments 41