A practical wish list for a small private location-history server
Google’s cloud Timeline change has created a need for a way to keep phone location history searchable and visible. The goal is to combine live phone tracking with an older archive. Dawarich is the closest match on features, but it depends on Rails, , Redis, and Sidekiq, which usually means 4 to 5 and a fair amount of memory.
That feels too heavy for one phone sending only a few thousand GPS points per day. Reitti has a similar problem in Java and also needs plus RabbitMQ. GeoPulse looks newer and more polished, but it still needs and uses a BSL license with non-commercial limits to check.
OwnTracks Recorder is much lighter, but its interface feels dated and it cannot import , which is a key need. The desired tool is one small container or one executable, backed by a SQLite file, able to receive data from OwnTracks or GPSLogger, import Takeout history, show a heatmap, and show where the phone was on a chosen day. Multi-user support, sharing, and a separate are not needed.
Key points
- The need is a replacement for browsing personal location history after Google’s cloud Timeline change.
- Dawarich, Reitti, and GeoPulse fit parts of the use case but bring heavier database or service .
- OwnTracks Recorder is light, but it lacks import.
- The ideal setup is one small container or executable with SQLite storage, OwnTracks or GPSLogger input, Takeout import, heatmaps, and date-by-date browsing.
- Multi-user accounts, sharing features, and a companion are outside the needed scope.