thereabout

Thereabout is a self-hosted replacement for Google Location History. It can import your existing Google Location History and visualise it as a heatmap on Google Maps.

Features

• Load existing Google Location History ("Records.json") when exported via Google Takeout.
  • Geolocate country for each entry locally.
  • Store the imported data in mariaDB.
• Visualise your location history as a heatmap on Google Maps
  • Filter by date range: custom, YTD, 1 year, 5 years, full history
• Visualise a specific day as a polygon line on Google Maps
  • Locate the first or any entry on the map
  • Highlight the entry your cursor is hovering over
  • List all location entries for the given day and show the selected entry as a marker on the map
  • Open Google Photos on the selected day
  • CRUD
    • Create new entries via API or in the UI
    • Read all entries for a specific day, visualised as a path on the map
    • Update an existing entry by changing its location the map via drag & drop
    • Delete: existing entries, either one by one or in bulk
• Geocoding: Search for any location on Google Maps
• Statistics
  • Number of countries visited
  • Number of days spent abroad
  • Detailed list of countries visited with first/last visit, days spent
• Endpoint to add new location entries continuously , e.g. via Home Assistant
  • Support for Overland for more accurate tracking independent of HA
  • One-Click configuration button for Overland
• Deploy the application via Docker Compose
• GitHub Build Pipeline
• Configuration page
  • Upload Google Records.json from the frontend

Roadmap

• Reverse Geolocation
  • Ability to reverse geolocate points with place & POI information
  • Persist geolocated POIs so that they can be re-used
  • Tag days based on locations visited, e.g. home, work etc.
• Convenience features
  • centralised UI header
  • integration tests
  • improved db security: configurable password & improved docker file that doesn't allow access from outside by default
  • trips
    • trips speed improvement
    • trips search
    • trip line for whom was travelled with
  • versioning
    • versioned docker releases
    • see version in configuration
  • jump to google calendar directly from day view
  • show search results in main page as list
  • disable delete when nothing is selected
  • store selected day as url parameter
  • round edges of google maps integration
  • store user details
    • birthdate, name, home country
  • show weeks of life with country flags
  • add more tooltips
• Day overview page
  • Integrate Google Photos API (low prio)
  • Weather
  • Major locations visited
  • calculate distance travelled in a day
• Statistics:
  • km travelled
  • yearly: total km travelled, countries visited, ...
• Security: User Login & secure endpoints
• Export location history as json
• Endpoint/Integration with OpenAI, e.g. ask "Where was I in November 2023?",
• Add support to load other dated data into Thereabout, e.g. chatlogs, temperature for location, weather to make a more comprehensive view of a specific day
• InMemory TestDB for integration tests
  • test for CRUD operations

Bugs

• It's possible to trigger multiple imports resulting in duplicated records
• Timezones are weird & annoying as always... need to decide how to deal with viewing data from different time zones

Why

Google sadly has decided to discontinue Google Location History / Timeline for the web as you can read here. It's still available on device, but in my opinion it's fairly clunky to interact with it on a small screen and secondly it is also no longer possible to easily export the local location history. Especially being unable to export my location data is a no-go for me, as Google has been known to kill various projects/features.. see the Google graveyard. Since there is no good alternative that does what I want I've decided to develop my own self-hosted location history.

Security & privacy implications

Thereabout runs locally and does not upload your location data to the internet. It does however require the use of a Google Maps API Key to load the Map. Google may be able to track your usage of Google Maps.

Please beware that Thereabout is not intended to be run on the public internet. Either run it fully locally or behind a authorization server such as Authelia. Thereabout itself does not have a login solution at this time and is not intended as a multi-tenant application. Any user with access can see all data, including your Google Maps API key.

How to continue adding data

See the Swagger UI for the API documentation under http://localhost:9050/swagger-ui/index.html. There is an endpoint to add new location data. You can use this endpoint to add new location data from Home Assistant with Node RED or some other automation tool.

Usage

1. Clone the repository or download the docker-compose.yml file
2. Get a Google Maps API Key from the Google Cloud Console
3. Open the configuration page via /configuration and upload your Google Location History file (Records.json)
4. Add the Google Maps API Key to the docker-compose.yml file & run it.

export home assistant location data via influx

from(bucket: "homeassistant/autogen")
  |> range(start: 2022-01-01)
  |> filter(fn: (r) => r._measurement == "state" and r._field == "longitude" or r._field == "latitude" )