|
1 |
| -# Patterns Dataset in Safegraph Mobility Data |
| 1 | +# Weekly Patterns Dataset in SafeGraph Mobility Data |
2 | 2 |
|
3 |
| -We import Zip Code-level raw mobility indicators from Safegraph **Weekly |
| 3 | +We import Zip Code-level raw mobility indicators from SafeGraph **Weekly |
4 | 4 | Patterns** dataset, calculate functions of the raw data, and then aggregate
|
5 | 5 | he data to the county, hrr, msa and state levels.
|
6 | 6 |
|
7 | 7 | ## Brand Information
|
8 |
| -Safegraph provides daily number of visits to points of interest (POIs) in Weekly |
9 |
| -Patterns datasets which is documanted [here](https://docs.safegraph.com/docs/weekly-patterns). |
| 8 | +SafeGraph provides daily number of visits to points of interest (POIs) in Weekly |
| 9 | +Patterns datasets which is documented [here](https://docs.safegraph.com/docs/weekly-patterns). |
10 | 10 | Base information such as location name, address, category, and brand association
|
11 | 11 | for POIs are provided in **Places Schema** dataset which is documented [here]
|
12 |
| -(https://docs.safegraph.com/docs/places-schema). Safegraph does not update their |
| 12 | +(https://docs.safegraph.com/docs/places-schema). SafeGraph does not update their |
13 | 13 | list of POIs frequently but there does exist versioning issue. The release
|
14 | 14 | version can be found in `release-metadata` in Weekly Patterns dataset and there
|
15 |
| -are correspounding `brand_info.csv` provided in Places Schema dataset. To save |
| 15 | +are corresponding `brand_info.csv` provided in Places Schema dataset. To save |
16 | 16 | storage space, we do not download the whole Places Schema dataset, but only add
|
17 |
| -new necesary `brand_info.csv` in `./statics` with suffix YYYYMM(release version). |
| 17 | +new necessary `brand_info.csv` in `./statics` with suffix YYYYMM(release version). |
18 | 18 |
|
19 | 19 | ## Geographical Levels
|
20 | 20 | * `county`: reported using zero-padded FIPS codes (consistency with the
|
21 | 21 | other COVIDcast data)
|
22 |
| -* `msa`: reported using cbsa (consistent with all other COVIDcast sensors) |
| 22 | +* `msa`: reported using CBSA (consistent with all other COVIDcast sensors) |
23 | 23 | * `hrr`: reported using HRR number (consistent with all other COVIDcast sensors)
|
24 | 24 | * `state`: reported using two-letter postal code
|
25 | 25 |
|
26 | 26 | ## Metrics, Level 1 (`m1`)
|
27 |
| -* `bars_visit`: The number of visits to bars(places with naics code = 722410) |
28 |
| -* `restaurants_visit`: The number of visits to restaurants(places with naics |
| 27 | +* `bars_visit`: The number of visits to bars(places with NAICS code = 722410) |
| 28 | +* `restaurants_visit`: The number of visits to restaurants(places with NAICS |
29 | 29 | code = 722511)
|
30 | 30 |
|
31 | 31 | ## Metrics, Level 2 (`m2`)
|
32 |
| -* `num`: number of new deaths on a given week |
| 32 | +* `num`: number of visits in a given week |
33 | 33 | * `prop`: `num` / population * 100,000 (Notice the population here only includes
|
34 | 34 | population aggregated at Zip Code level. If there are no POIs for a certain
|
35 | 35 | Zip Code, the population there won't be considered.)
|
36 | 36 |
|
37 | 37 |
|
38 | 38 | ## API Key
|
39 | 39 |
|
40 |
| -We access the Safegraph data using an AWS key-secret pair which is valid |
| 40 | +We access the SafeGraph data using an AWS key-secret pair which is valid |
41 | 41 | until June 15, 2021. The AWS credentials have been issued under
|
42 |
| -@huisaddison's Safegraph Data Catalog account. |
| 42 | +@huisaddison's SafeGraph Data Catalog account. |
0 commit comments