Skip to content
Branch: master
Go to file
Code

Latest commit

CathyAtkinson committed 2461b96 May 7, 2020
Create README.md
Added a readme to explain the new files added

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 

README.md

google-mobility-reports-data

Update

07/05/2020 Revised lookup tables and boundaries file have been provided in the geography folder to reflect the changes made in the published Google Mobility data in the separation of Nottingham and Nottinghamshire.

17/04/2020: Google now make this data available in csv format format, please source the data from there and note the additional documentation. There will be small differences between the data we have extracted up until now and that published, usually that is around +/- 1% due to rounding.

Introduction

Archive of data related to the Google Community Mobility Reports published 03/04/2020 and 10/04/2020.

This repository contains data extracted from Google Community Mobility Reports published on the 03/04/2020 and 10/04/2020, together with supporting boundaries based on the current UK administrative geography to allow mapping and linking with other sources of data.

Data

The latest data is available in Microsoft Office .xlsx format here, which includes the entire data extracted from the UK report, as well as other international reports. Other datasets include:

LATEST DATA 16/04/2020 (covers the period 29/02 - 11/04)

Original data (covers the period 16/02 - 29/03)

Headline data for all countries is available from Matt Kerlogue's repository

Background

The Data Science Campus has extracted the data from Google’s UK report, and other international reports, to make them publicly available to all. We developed this Python tool (mobius) to achieve this.

The insights are drawn from changes in visits and lengths of stay for different types of locations indexed against median levels, for the same day of the week, over the period 3rd January - 6th February 2020 (for the original data). Google uses aggregated, anonymized sets of data from users who have turned on the Location History setting (off by default). Google caution that the location accuracy and the understanding of categorized places will vary between regions and so advice against using it to compare changes between countries, or between regions with different characteristics (e.g. rural versus urban areas) - please see Google's documentation for more details.

trend-chart

Figure 1: UK trends chart from Google Community Mobility Reports published on the 03/04/2020.

Data and methodology cannot be QA’d directly by the Campus and is provided on an ‘as-is’ basis.

Python tool: Mobility Report Data Extractor (mobius)

Logo

The Data Science Campus has created a python tool (https://github.com/datasciencecampus/mobility-report-data-extractor) for extracting the data points from the graphs for Google Community Mobility Report PDFs. To use this tool, the PDF documents need to be converted to Scalable Vector Graphic (SVG) format. The Campus has converted all PDF documents to SVG documents for this tool. These SVG files are used in mobius to obtain a Comma Separated Value (CSV) file for each graph in the original report.

This repository contains the CSV files for all G20 countries for national and regional graphs.

Boundary data for the UK

The set of boundaries provided in the geopackage is draft, and has been created by ONS in order to promote information sharing and analysis of the effect of COVID19.

The boundaries have been tailored specifically to present ‘Community Mobility’ data (first published by Google on 3 April 2020) recast to administrative boundaries.

The data published by Google covers all of the UK based on the normal Government Statistical Service (GSS) assignment to 2019 administrative areas - with 3 exceptions. The Unitary Authorities of Bournemouth, Christchurch and Poole; and Telford and Wrekin are missing. In building the boundaries provided here we have assumed that Google have included data for these missing areas within Dorset and Shropshire. Although they do not reflect the current administrative geography we have made use of Ceremonial County versions of Dorset and Shropshire to ensure full geographic coverage of the UK. These boundaries do not reflect current administrative boundaries so care should be taken in how they are used and they should only be used to understand the results published by Google. Further versions of these boundaries may be made available if we are able confirm more details but they are provided here in the hope that they will be helpful to others.

Mid-year population estimates for the UK

The 2018 mid-year population estimates for the UK have been linked to the custom lookup created by ONS. A Standard Area Measurement based on those produced by ONS Geography has also been included for each area (calculated in hectares). This allows measures such as population density to be calculated. 

About

Archive of data extracted from the google community mobility reports

Topics

Resources

Releases

No releases published

Contributors 4

  •  
  •  
  •  
  •  
You can’t perform that action at this time.