You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`completely_home_prop`| The fraction of mobile devices that did not leave the immediate area of their home (SafeGraph's `completely_home_device_count / device_count`) <br/> **Earliest date available:** 01/01/2019 |
47
+
|`full_time_work_prop`| The fraction of mobile devices that spent more than 6 hours at a location other than their home during the daytime (SafeGraph's `full_time_work_behavior_devices / device_count`) <br/> **Earliest date available:** 01/01/2019 |
48
+
|`part_time_work_prop`| The fraction of devices that spent between 3 and 6 hours at a location other than their home during the daytime (SafeGraph's `part_time_work_behavior_devices / device_count`) <br/> **Earliest date available:** 01/01/2019 |
49
+
|`median_home_dwell_time`| The median time spent at home for all devices at this location for this time period, in minutes <br/> **Earliest date available:** 01/01/2019 |
50
+
|`completely_home_prop_7dav`| Offers a 7-day trailing window average of the `completely_home_prop`. <br/> **Earliest date available:** 01/01/2019 |
51
+
|`full_time_work_prop_7dav`| Offers a 7-day trailing window average of the`full_time_work_prop`. <br/> **Earliest date available:** 01/01/2019 |
52
+
|`part_time_work_prop_7dav`| Offers a 7-day trailing window average of the`part_time_work_prop`. <br/> **Earliest date available:** 01/01/2019 |
53
+
|`median_home_dwell_time_7dav`| Offers a 7-day trailing window average of the `median_home_dwell_time`. <br/> **Earliest date available:** 01/01/2019 |
54
+
55
+
After computing each metric on the census block group (CBG) level, we aggregate
56
+
to the county-level by taking the mean over CBGs in a county to obtain the value
57
+
and taking `sd / sqrt(n)` for the standard error, where `sd` is the standard
58
+
deviation over the metric values and `n` is the number of CBGs in the county. In
59
+
doing so, we make the simplifying assumption that each CBG contributes an iid
60
+
observation to the county-level distribution. `n` also serves as the sample
61
+
size. The same method is used for aggregation to states.
62
+
63
+
SafeGraph's signals measure mobility each day, which causes strong day-of-week
64
+
effects: weekends have substantially different values than weekdays. Users
65
+
interested in long-term trends, rather than mobility on one specific day, may
66
+
prefer the `7dav` signals since averaging over the preceding 7 days removes
67
+
these day-of-week effects.
68
+
69
+
### Lag
70
+
71
+
SafeGraph provides this data with a three-day lag, meaning estimates for a
72
+
specific day are only available three days later. It may take up to an
73
+
additional day for SafeGraph's data to be ingested into the COVIDcast API.
|`completely_home_prop`| The fraction of mobile devices that did not leave the immediate area of their home (SafeGraph's `completely_home_device_count / device_count`) <br/> **Earliest date available:** 01/01/2019 |
47
-
|`full_time_work_prop`| The fraction of mobile devices that spent more than 6 hours at a location other than their home during the daytime (SafeGraph's `full_time_work_behavior_devices / device_count`) <br/> **Earliest date available:** 01/01/2019 |
48
-
|`part_time_work_prop`| The fraction of devices that spent between 3 and 6 hours at a location other than their home during the daytime (SafeGraph's `part_time_work_behavior_devices / device_count`) <br/> **Earliest date available:** 01/01/2019 |
49
-
|`median_home_dwell_time`| The median time spent at home for all devices at this location for this time period, in minutes <br/> **Earliest date available:** 01/01/2019 |
50
-
|`completely_home_prop_7dav`| Offers a 7-day trailing window average of the `completely_home_prop`. <br/> **Earliest date available:** 01/01/2019 |
51
-
|`full_time_work_prop_7dav`| Offers a 7-day trailing window average of the`full_time_work_prop`. <br/> **Earliest date available:** 01/01/2019 |
52
-
|`part_time_work_prop_7dav`| Offers a 7-day trailing window average of the`part_time_work_prop`. <br/> **Earliest date available:** 01/01/2019 |
53
-
|`median_home_dwell_time_7dav`| Offers a 7-day trailing window average of the `median_home_dwell_time`. <br/> **Earliest date available:** 01/01/2019 |
54
-
55
-
After computing each metric on the census block group (CBG) level, we aggregate
56
-
to the county-level by taking the mean over CBGs in a county to obtain the value
57
-
and taking `sd / sqrt(n)` for the standard error, where `sd` is the standard
58
-
deviation over the metric values and `n` is the number of CBGs in the county. In
59
-
doing so, we make the simplifying assumption that each CBG contributes an iid
60
-
observation to the county-level distribution. `n` also serves as the sample
61
-
size. The same method is used for aggregation to states.
62
-
63
-
SafeGraph's signals measure mobility each day, which causes strong day-of-week
64
-
effects: weekends have substantially different values than weekdays. Users
65
-
interested in long-term trends, rather than mobility on one specific day, may
66
-
prefer the `7dav` signals since averaging over the preceding 7 days removes
67
-
these day-of-week effects.
68
-
69
-
### Lag
70
-
71
-
SafeGraph provides this data with a three-day lag, meaning estimates for a
72
-
specific day are only available three days later. It may take up to an
73
-
additional day for SafeGraph's data to be ingested into the COVIDcast API.
25
+
## SafeGraph Social Distancing Metrics (Inactive)
74
26
27
+
These signals were updated until April 19th, 2021, when Safegraph ceased updating the dataset.
28
+
Documentation for these signals is still available on the [inactive Safegraph page](safegraph-inactive.md).
75
29
76
30
## SafeGraph Weekly Patterns
77
31
@@ -91,7 +45,7 @@ restaurants, etc.) from SafeGraph's Weekly Patterns data at the 5-digit ZipCode
91
45
level, then aggregates and reports these features to the county, MSA, HRR, and
92
46
state levels. The aggregated data is freely available through the COVIDcast API.
93
47
94
-
For precise definitions of the quantities below, consult the [SafeGraph Weekly
48
+
For precise definitions of the quantities below, consult the [SafeGraph Weekly
@@ -131,4 +85,3 @@ SafeGraph's Social Distancing Metrics and Weekly Patterns are based on mobile de
131
85
132
86
***Geographic bias.** If some regions have a greater density of SafeGraph panel members as a percentage of the population than other regions, comparisons of metrics between regions may be biased. Regions with more SafeGraph panel members will appear to have more visits counted, even if the rate of visits in the general population is the same.
133
87
***Demographic bias.** SafeGraph panels may not be representative of the local population as a whole. For example, [some research suggests](https://arxiv.org/abs/2011.07194) that "older and non-white voters are less likely to be captured by mobility data", so this data will not accurately reflect behavior in those populations. Since population demographics vary across the United States, this can also contribute to geographic biases.
Copy file name to clipboardExpand all lines: docs/api/covidcast_changelog.md
+10-6Lines changed: 10 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -43,13 +43,13 @@ Duplicate survey weights had corrupted historical figures for the following sign
43
43
*`hrr`: 20200406-20200415, 20200430-20200506
44
44
*`msa`: 20200408-20200414, 20200430-20200506
45
45
*`state`: 20200408-20200416, 20200430-20200506
46
-
47
-
#### 20 November 2020
48
46
49
-
Due to a bug in our data processing system, estimates of the percentage of people reporting that they have been tested for COVID-19 calculated before October 8th were incorrect.
50
-
We incorrectly treated an answer of “no” as a missing response, which affected the `smoothed_tested_14d` and `smoothed_wtested_14d` signals from the `fb-survey` source.
47
+
#### 20 November 2020
51
48
52
-
As of Nov. 20th, the error has been corrected and all affected data reissued.
49
+
Due to a bug in our data processing system, estimates of the percentage of people reporting that they have been tested for COVID-19 calculated before October 8th were incorrect.
50
+
We incorrectly treated an answer of “no” as a missing response, which affected the `smoothed_tested_14d` and `smoothed_wtested_14d` signals from the `fb-survey` source.
51
+
52
+
As of Nov. 20th, the error has been corrected and all affected data reissued.
53
53
54
54
### `hospital-admissions`
55
55
#### 20 October 2020
@@ -63,7 +63,7 @@ We now include figures on Puerto Rico for all `jhu-csse` signals at the state le
63
63
64
64
#### 1 September 2020
65
65
66
-
NY Boroughs county FIPS (36005, 36047, 36061, 36081, 36085) are now split in proportion to the population of each county, instead of being reported in aggregate in FIPS 36061.
66
+
NY Boroughs county FIPS (36005, 36047, 36061, 36081, 36085) are now split in proportion to the population of each county, instead of being reported in aggregate in FIPS 36061.
67
67
68
68
#### 7 October 2020
69
69
@@ -95,6 +95,10 @@ We went from a custom geo mapping file (for aggregating from zip->(county, msa,
95
95
96
96
### `safegraph`
97
97
98
+
#### 19 April 2021
99
+
100
+
The Safegraph social distancing metrics are no longer being updated. Weekly patterns are still available.
101
+
98
102
#### 3 November 2020
99
103
We went from a custom geo mapping file (for aggregating from county->state) to a central geo file based on rigorously sourced US census data.
0 commit comments