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
|`bars_visit_num`| The number of daily visits made by those with SafeGraph's apps to bar-related POIs in a certain region <br/> **Earliest date available:** 01/01/2019 |
103
+
|`bars_visit_prop`| The number of daily visits made by those with SafeGraph's apps to bar-related POIs in a certain region, per 100,000 population <br/> **Earliest date available:** 01/01/2019 |
104
+
|`restaurants_visit_num`| The number of daily visits made by those with SafeGraph's apps to restaurant-related POIs in a certain region <br/> **Earliest date available:** 01/01/2019 |
105
+
|`restaurants_visit_prop`| The number of daily visits made by those with SafeGraph's apps to restaurant-related POIs in a certain region, per 100,000 population <br/> **Earliest date available:** 01/01/2019 |
106
+
107
+
SafeGraph delivered the number of daily visits to U.S. POIs, the details of which
The number of POIs coded as bars is much smaller than the number of POIs coded as restaurants.
121
+
SafeGraph's Weekly Patterns data consistently lacks data on bar visits for Alaska, Delaware, Maine, North Dakota, New Hampshire, South Dakota, Vermont, West Virginia, and Wyoming.
122
+
For certain dates, bar visits data is also missing for District of Columbia, Idaho and Washington. Restaurant visits data is available for all of the states, as well as the District of Columbia and Puerto Rico.
123
+
124
+
### Lag
125
+
126
+
SafeGraph provided newly updated data for the previous week every Wednesday,
127
+
meaning estimates for a specific day are only available 3-9 days later. It may
128
+
take up to an additional day for SafeGraph's data to be ingested into the
129
+
COVIDcast API.
130
+
131
+
## Limitations
132
+
133
+
SafeGraph's Social Distancing Metrics and Weekly Patterns are based on mobile devices that are members of SafeGraph panels, which is not necessarily the same thing as measuring the general public. These counts do not represent absolute counts, and only count visits by members of the panel in that region. This can result in several biases:
134
+
135
+
***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.
136
+
***Demographic bias.** SafeGraph panels may not be representative of the local population as a whole. For example, [some research suggests](https://doi.org/10.1145/3442188.3445881) 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.
0 commit comments