Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google: report format changed #16

Closed
ActiveConclusion opened this issue Jun 12, 2020 · 3 comments · Fixed by #17
Closed

Google: report format changed #16

ActiveConclusion opened this issue Jun 12, 2020 · 3 comments · Fixed by #17

Comments

@ActiveConclusion
Copy link
Owner

Google added in a recent update two columns:

  1. iso_3166_2_code
  2. census_fips_code

I'm not sure that these attributes are useful, but some fixes needed to the script.

Also, Google added more regions.

@ActiveConclusion
Copy link
Owner Author

There are two significant changes in the last update (2020-07-27) of Google reports:

  1. Added metro_area column. It's one more administrative level, for metropolitan areas.
  2. Before this update, the second level of subregions (column sub_region_2) was used only for the US counties. Now, there are many countries for which data on this level were added.

Currently, I exclude data for the second level of subregions and metropolitan areas in this preprocessed Google Mobility report.

I think to add an extended version of the report with new data, but I haven't decided yet how to do it better.

@ActiveConclusion
Copy link
Owner Author

The raw Google Mobility report is stored in the ZIP archive in this repo now due to the large file size.

@ActiveConclusion
Copy link
Owner Author

After some time of reflection, I decided to make a breakdown of the data by geographic principle.
So, in the recent update, I added detailed reports for Brazil (a lot of data is available for them) and for the world regions (Europe, Asia+Africa, North and South America + Oceania). You can check new data here.
Also, I decided to merge the "metro area" column with "sub_region_1" because I don't see any advantages of having this column separately.
As Apple and Waze do not have that detailed data, I have no plans to merge the new Google data with them (I still haven't merged Waze data 😱)

I leave this issue open for some time for suggestions/comments about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant