Merge pull request #503 from dshemetov/fix_safegraph_docs

Docs update: move safegraph to inactive category

Author: krivard

docs/api/covidcast-signals/indicator-combination.md

@@ -20,7 +20,7 @@ calculated or composed by Delphi. It is not a primary data source.
 
 ## Statistical Combination Signals (Inactive)
 
-The NMF combination signals were deactivated on March 17, 2021. Documenation for
+The NMF combination signals were deactivated on March 17, 2021. Documentation for
 these signals is still available on the page for [inactive indicator-combination
 signals](indicator-combination-inactive.md).
 

docs/api/covidcast-signals/safegraph-inactive.md

@@ -0,0 +1,74 @@
+---
+title: SafeGraph
+parent: Inactive Signals
+grand_parent: COVIDcast Epidata API
+---
+
+# SafeGraph
+{: .no_toc}
+* **Source name:** `safegraph`
+* **Available for:** county, MSA, HRR, state (see [geography coding docs](../covidcast_geography.md))
+* **Time type:** day (see [date format docs](../covidcast_times.md))
+* **License:** [CC BY](../covidcast_licensing.md#creative-commons-attribution)
+
+This data source uses data reported by [SafeGraph](https://www.safegraph.com/)
+using anonymized location data from mobile phones. SafeGraph provides several
+different datasets to eligible researchers. We surface signals from two such
+datasets. This dataset is no longer updated after April 19th, 2021.
+
+## Table of Contents
+{: .no_toc .text-delta}
+
+1. TOC
+{:toc}
+
+## SafeGraph Social Distancing Metrics
+
+* **Earliest issue available:** June 20, 2020
+* **Number of data revisions since June 23, 2020:** 1
+* **Date of last change:** November 3, 2020
+
+Data source based on [social distancing
+metrics](https://docs.safegraph.com/docs/social-distancing-metrics).  SafeGraph
+provides this data for individual census block groups, using differential
+privacy to protect individual people's data privacy.
+
+Delphi creates features of the SafeGraph data at the census block group level,
+then aggregates these features to the county and state levels. The aggregated
+data is freely available through the COVIDcast API.
+
+For precise definitions of the quantities below, consult the [SafeGraph social
+distancing metric
+documentation](https://docs.safegraph.com/docs/social-distancing-metrics).
+
+| Signal | Description |
+| --- | --- |
+| `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 |
+| `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 |
+| `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 |
+| `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 |
+| `completely_home_prop_7dav` | Offers a 7-day trailing window average of the `completely_home_prop`. <br/> **Earliest date available:** 01/01/2019 |
+| `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 |
+| `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 |
+| `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 |
+
+After computing each metric on the census block group (CBG) level, we aggregate
+to the county-level by taking the mean over CBGs in a county to obtain the value
+and taking `sd / sqrt(n)` for the standard error, where `sd` is the standard
+deviation over the metric values and `n` is the number of CBGs in the county. In
+doing so, we make the simplifying assumption that each CBG contributes an iid
+observation to the county-level distribution. `n` also serves as the sample
+size. The same method is used for aggregation to states.
+
+SafeGraph's signals measure mobility each day, which causes strong day-of-week
+effects: weekends have substantially different values than weekdays. Users
+interested in long-term trends, rather than mobility on one specific day, may
+prefer the `7dav` signals since averaging over the preceding 7 days removes
+these day-of-week effects.
+
+### Lag
+
+SafeGraph provides this data with a three-day lag, meaning estimates for a
+specific day are only available three days later. It may take up to an
+additional day for SafeGraph's data to be ingested into the COVIDcast API.
+

docs/api/covidcast-signals/safegraph.md

@@ -13,65 +13,19 @@ grand_parent: COVIDcast Epidata API
 
 This data source uses data reported by [SafeGraph](https://www.safegraph.com/)
 using anonymized location data from mobile phones. SafeGraph provides several
-different datasets to eligible researchers. We surface signals from two such
-datasets.
+different datasets to eligible researchers. We currently surface signals from one such
+dataset.
 
-## Table of Contents
+## Table of contents
 {: .no_toc .text-delta}
 
 1. TOC
 {:toc}
 
-## SafeGraph Social Distancing Metrics
-
-* **Earliest issue available:** June 20, 2020
-* **Number of data revisions since June 23, 2020:** 1
-* **Date of last change:** November 3, 2020
-
-Data source based on [social distancing
-metrics](https://docs.safegraph.com/docs/social-distancing-metrics).  SafeGraph
-provides this data for individual census block groups, using differential
-privacy to protect individual people's data privacy.
-
-Delphi creates features of the SafeGraph data at the census block group level,
-then aggregates these features to the county and state levels. The aggregated
-data is freely available through the COVIDcast API.
-
-For precise definitions of the quantities below, consult the [SafeGraph social
-distancing metric
-documentation](https://docs.safegraph.com/docs/social-distancing-metrics).
-
-| Signal | Description |
-| --- | --- |
-| `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 |
-| `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 |
-| `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 |
-| `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 |
-| `completely_home_prop_7dav` | Offers a 7-day trailing window average of the `completely_home_prop`. <br/> **Earliest date available:** 01/01/2019 |
-| `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 |
-| `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 |
-| `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 |
-
-After computing each metric on the census block group (CBG) level, we aggregate
-to the county-level by taking the mean over CBGs in a county to obtain the value
-and taking `sd / sqrt(n)` for the standard error, where `sd` is the standard
-deviation over the metric values and `n` is the number of CBGs in the county. In
-doing so, we make the simplifying assumption that each CBG contributes an iid
-observation to the county-level distribution. `n` also serves as the sample
-size. The same method is used for aggregation to states.
-
-SafeGraph's signals measure mobility each day, which causes strong day-of-week
-effects: weekends have substantially different values than weekdays. Users
-interested in long-term trends, rather than mobility on one specific day, may
-prefer the `7dav` signals since averaging over the preceding 7 days removes
-these day-of-week effects.
-
-### Lag
-
-SafeGraph provides this data with a three-day lag, meaning estimates for a
-specific day are only available three days later. It may take up to an
-additional day for SafeGraph's data to be ingested into the COVIDcast API.
+## SafeGraph Social Distancing Metrics (Inactive)
 
+These signals were updated until April 19th, 2021, when Safegraph ceased updating the dataset.
+Documentation for these signals is still available on the [inactive Safegraph page](safegraph-inactive.md).
 
 ## SafeGraph Weekly Patterns
 
@@ -91,7 +45,7 @@ restaurants, etc.)  from SafeGraph's Weekly Patterns data at the 5-digit ZipCode
 level, then aggregates and reports these features to the county, MSA, HRR, and
 state levels. The aggregated data is freely available through the COVIDcast API.
 
-For precise definitions of the quantities below, consult the [SafeGraph Weekly 
+For precise definitions of the quantities below, consult the [SafeGraph Weekly
 Patterns documentation](https://docs.safegraph.com/docs/weekly-patterns).
 
 | Signal | Description |
@@ -131,4 +85,3 @@ SafeGraph's Social Distancing Metrics and Weekly Patterns are based on mobile de
 
 * **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.
 * **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.
-

docs/api/covidcast_changelog.md

@@ -43,13 +43,13 @@ Duplicate survey weights had corrupted historical figures for the following sign
   * `hrr`: 20200406-20200415, 20200430-20200506
   * `msa`: 20200408-20200414, 20200430-20200506
   * `state`: 20200408-20200416, 20200430-20200506
-  
-#### 20 November 2020  
 
-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. 
-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. 
+#### 20 November 2020
 
-As of Nov. 20th, the error has been corrected and all affected data reissued. 
+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.
+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.
+
+As of Nov. 20th, the error has been corrected and all affected data reissued.
 
 ### `hospital-admissions`
 #### 20 October 2020
@@ -63,7 +63,7 @@ We now include figures on Puerto Rico for all `jhu-csse` signals at the state le
 
 #### 1 September 2020
 
-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. 
+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.
 
 #### 7 October 2020
 
@@ -95,6 +95,10 @@ We went from a custom geo mapping file (for aggregating from zip->(county, msa,
 
 ### `safegraph`
 
+#### 19 April 2021
+
+The Safegraph social distancing metrics are no longer being updated. Weekly patterns are still available.
+
 #### 3 November 2020
 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.