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
Ah ok thanks. This is what I was wondering.
Two follow-ups:
Can you specify multiple
COUNTRY_CODE
s? (and if so, is the methodenvironment: - COUNTRY_CODE=country_one - COUNTRY_CODE=country_two
or
environment: - COUNTRY_CODE=[country_one, country_two]
or something else?)
And is this something that can seemlessly be retroactively changed? For example, if I set
COUNTRY_CODE=au
and it works fine for Australia, but then I move to NZ, can I add (assuming the answer to my first question is yes) or change toCOUNTRY_CODE=nz
and have all the NZ locations work on the already-recorded data, even if I made that change to my configuration after I had been in NZ for a few months?Good question, afaik you can not enter multiple countries to Photon. I was hoping it would be possible but everything i saw was it is either on country or the whole world. But maybe you can have a look here: https://github.com/komoot/photon That is the service we are using.
I just took a really quick look at it, but under Importing data from Nominatim it says “
-country-codes
allows to filter the data to be imported by country. Set this to a comma-separated list of two-letter language codes.”That’s a different section from the Importing data from a JSON dump section, which is where it only mentions
-country-code
. But even that does seem to suggest it takes “all the parameters of an import from a Nominatim database”. So it seems like either the documentation for one of them is wrong, or both are lacking (because in fact both the singular and plural work).I think this is not exposed when running the Docker container. But let me check later when i have time what happens if i put another country in that variable
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.