The Location History Parser offers a straightforward and efficient solution for anyone looking to analyze their Google Takeout location history data.
Downloading processed data as a CSV file opens up various possibilities for deeper analysis. Users can leverage tools like Excel, ArcGIS, or any other data analysis software to explore their data further, perform spatial analysis, and create custom visualizations.
While the provided scripts cover common use cases, they can be easily modified to extract additional data points or to suit specific analytical needs. This flexibility makes the tool suitable for both casual users and data enthusiasts.
- Python 3.x
Try it yourself, hosted via streamlit. Live Site
This Streamlit application (app.py) allows users to process and visualize their Google Takeout location history data. Users can upload a ZIP file containing their location history JSON files, and the app will extract, process, and display the data in an interactive format. The processed data can be downloaded as a CSV file for further analysis. You must have the Semantic Location History file present in order for this to run successfully.
Run the Streamlit app
pip install -r requirements.txt
streamlit run app.py
This will launch a web-based UI where you can upload your Google Takeout location history ZIP file and interact with the processed data.
There are three scripts in this repo, semantic_location_parser.py
, records_location_parser.py
, and full_location_history_parser.py
.
Each file scans through the Takeouts directory and parses the Google location data.
The resulting csv files can be used in ArcGIS for spatial analysis and visualization. If you want to see your data visually fast, then convert the csv to a macro enabled .xlms
file and use Excel's mapping tool.
- Download and extract your Location History data from Google Takeout. Google will send you a link to download a
.zip
file. Unzip the file into a new directory. - Save the python scripts in the same folder that you extracted the Takeouts folder.
- Open a terminal/command prompt and navigate to the location of the script and the data.
- Run the script using the command
python semantic_location_parser.py
. - The resulting csv file will be saved in the same folder as the script and data with the name
semantic_location_history.csv
. - The steps are the same for each script.
Google Takeout Location History data consists of two types of data: raw location history data and semantic location history data.
E:.
| location_history_parser.py
|
\---Takeout
| archive_browser.html
|
\---Location History
| Records.json
| Settings.json
| Tombstones.csv
|
\---Semantic Location History
+---2022
| 2022_DECEMBER.json
| 2022_NOVEMBER.json
|
\---2023
2023_FEBRUARY.json
2023_JANUARY.json
The semantic_location_parser.py
script is used to parse Google Takeout Location History data into a csv file. The script can extract the timestamp
, address
, placeId
, name
, latitudeE7
and longitudeE7
values from the semantic location history data and store them in a csv file.
The semantic location history data is found in the Semantic Location History
folder and consists of more high-level and processed information compared to the raw location history data found in the records.json
file. This data is partitioned by year in different subfolders and by month in different JSON files. Inside each semantic JSON file we can find a single flat timelineObjects
array.
The records_location_parser.py
is used to pull the less refined location data that is collected. This data can be used to highlight what roads you traveled along rather than just what location you visited.
The full_location_history_parser.py
parses the same data as the semantic_location_parser.py
, but it also parses the records.json
file in the same script. The two files are appended together on the timestamp
, lat
, and lon
columns. It's not the best way to store this data and not adivsed to be used.
This data set will have the following columns:
epoch_time
: Useful for APIstimestamp
: sample start time from devicedate_str
: timestamp to datelat
: latitudinal coordinate. The values need to be divided by 107 to be in the expected range.lon
: logitudinal coordinate. The values need to be divided by 107 to be in the expected range.address
: Best guess address by Googleplaceid
: Google place idname
: Name of location if it existsalt
: altitudeactivity_type
: Most confident activity typeplatformtype
: Platform used to access Google servicesfile_path
: Which folder the data came fromsys_time
: Comes from thetimestamp
key in therecords.json
, unique.
The script only extracts specific values from the raw location history data and the semantic location history data and stores them in their respective csv files. If you need to extract additional information, you may need to modify the script accordingly.