345
submitted
2 weeks ago* (last edited 2 weeks ago)
by
danielgraf@discuss.tchncs.de
to
c/selfhosted@lemmy.world
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
Fuck yeah this is awesome! The detail of Immich integration is just the icing on top of an awesome cake!
How demanding is it on server resources? Am I likely to be able to run it on an old Raspberry Pi that's also running a couple of other relatively light tasks? How much storage does it end up using over time? I'm probably going to try and get it running either on my Pi or my Synology NAS, though the latter has had issues with Docker containers in the past depending on the container's dependencies...
I have no clue if a raspberry will handle it. There a a couple of services involved to make it fast, but they are then another burden like RabbitMQ. Which make ingesting data instantaneous but you need extra processing power to handle the queues. It all comes with a tradeoff.
For size, there is mainly the PostGIS DB. I just checked and my db is around 800 MB for roughtly 8 1/2 Years of data.
Photon (the reverse geocode enabled in the compose file) is another beast. For Germany it takes 14 GB of storage while running, if you let PARALLELL updates enabled you can double that every time the index is updated. But you can remove that from the compose file and rely on external Geocoders. It is described in https://github.com/dedicatedcode/reitti?tab=readme-ov-file#reverse-geocoding-options
Oh interesting. I've just read through that link, and I was assuming that something similar to the "external only" option would have been the only way it worked. More specifically, I thought it'd just store a list of historical points and display those on an OSM overlay. But it seems like even "external only" is much more involved than that.
What happens with self-hosted Photon if you specify a country, but then also visit another country? (I assume in hybrid mode it's as simple as "use Photon in your country, use Nominatim otherwise?)
But yeah, definitely sounds like a Pi is probably not gonna cut it. I'll have to see if my Synology can do it, or if the weird OS restrictions Synology imposes prevent it.
If you use Photon and only have your main country available, it will fallback to the configured external Geo-coding-services since Photon will not return a result then. So the order of execution is: