been there·
done that

• Timeline.json exported from Google Maps on an Android phone (the current format).
• Timeline export from an iPhone (Google Maps for iOS).
• Google Takeout files from before Timeline moved to phones: Records.json (raw GPS points) and Semantic Location History (one file per month). Load them together with Timeline.json and the app uses the best of each.
• Dawarich: an export from the Points page (GeoJSON or GPX, as the ZIP Dawarich gives you or unzipped), or the whole account export from Export my data. Trips and stays are worked out from its GPS points, with your visits' names and Dawarich's transport types when the account export has them.
• Strava: the account export ZIP, or single .gpx, .tcx or .fit files. Load them from Settings → Load Strava export once your Timeline is in. Each activity replaces the Timeline trip it covers and keeps its sport.

Flights don't need a file of their own: they come from Timeline, and long jumps Timeline missed are recognised as flights too. You can load several files at once, or a whole folder.

Android

1. Open Settings → Location → Location services → Timeline.
2. Tap Export Timeline data and save Timeline.json.

iPhone

1. In Google Maps, tap your profile picture, then Settings → Personal content.
2. Tap Export Timeline data and save the file.

Older Google Takeout

If you downloaded Location History from takeout.google.com before Google moved Timeline onto phones, load Records.json and the files in Semantic Location History. Takeout no longer offers new ones.

Dawarich

1. On the Points page, pick the dates and choose Export as GeoJSON (or GPX). Download the ZIP from the Exports page and load it as it is.
2. Or, for everything with your visits and transport types, use Export my data in Dawarich's settings and load that ZIP.

Strava

1. On strava.com open Settings → My Account → Download or Delete Your Account and request your archive.
2. Strava emails a ZIP. Load it as it is; only the activity files inside are read, so photos don't slow it down.

• Saved in your browser. Your last import is kept in this browser's storage, so the app opens with it next time.
• Trips are cleaned up. Bad GPS jumps, stale start and end points, time parked counted as driving and places Google moved are fixed, and loose GPS points become trips. Fixed trips are flagged in their details.
• Local times and countries come from time zone data and country borders built into the app, so they work offline.
• CO₂ is estimated per trip from its distance and transport, with the UK government's 2025 averages.
• The only things fetched from the internet are the map tiles (Esri) and the map library. Add the app to your home screen and it opens offline.

This project

BT•DT is free to use, copy and change for non-commercial purposes, as long as you credit the original: “Based on BT•DT by BlueHair (www.bluehair.co)”. It is licensed under CC BY-NC 4.0; the code is on GitHub. The BlueHair name and logo are not part of the license.

Built with

• Leaflet, the map library BSD 2-Clause
• Map tiles from Esri and its data providers Esri terms of use
• Country borders from Natural Earth Public domain
• Towns and cities from GeoNames CC BY 4.0
• Airports from OurAirports Public domain
• Time zone names from the IANA tz database Public domain
• CO₂ factors from the UK government's conversion factors Open Government Licence v3.0
• Fonts: Bricolage Grotesque and IBM Plex, via Google Fonts SIL Open Font License

BT•DT is a hobby project, made for fun and for my own travels. It is vibe coded: built by describing what I wanted to an AI (Claude) rather than writing the code by hand. Expect rough edges, and check anything important against your own records.