@@ -34,90 +34,16 @@ discrete difference of `cumulative_counts`, and assume that the
3434problem, because there there is only one county with a nonzero
3535` cumulative_count ` on January 22nd, with a value of 1.
3636
37- For deriving ` incidence ` , we use the estimated 2019 county population values
38- from the US Census Bureau. https://www.census.gov/data/tables/time-series/demo/popest/2010s-counties-total.html
37+ For deriving ` incidence ` , we use the estimated 2019 county population estimates
38+ from the [ US Census Bureau] ( https://www.census.gov/data/tables/time-series/demo/popest/2010s-counties-total.html ) .
3939
4040## Exceptions
4141
42- At the County (FIPS) level, we report the data _ exactly_ as JHU reports their
43- data, to prevent confusing public consumers of the data.
44- The visualization and modeling teams should take note of these exceptions.
45-
46- ### New York City
47-
48- New York City comprises of five boroughs:
49-
50- | Borough Name | County Name | FIPS Code |
51- | -------------------| -------------------| ---------------|
52- | Manhattan | New York County | 36061 |
53- | The Bronx | Bronx County | 36005 |
54- | Brooklyn | Kings County | 36047 |
55- | Queens | Queens County | 36081 |
56- | Staten Island | Richmond County | 36085 |
57-
58- ** Data from all five boroughs are reported under New York County,
59- FIPS Code 36061.** The other four boroughs are included in the dataset
60- and show up in our API, but they should be uniformly zero. (In our population
61- file under static folder, the population from all five boroughs are also
62- assigned to FIPS Code 36061 only. The populatio for the rest of the counties
63- are set to be 1.)
64-
65- All NYC counts are mapped to the MSA with CBSA ID 35620, which encompasses
66- all five boroughs. All NYC counts are mapped to HRR 303, which intersects
67- all five boroughs (297 also intersects the Bronx, 301 also intersects
68- Brooklyn and Queens, but absent additional information, I am leaving all
69- counts in 303).
70-
71- ### Kansas City, Missouri
72-
73- Kansas City intersects the following four counties, which themselves report
74- confirmed case and deaths data:
75-
76- | County Name | FIPS Code |
77- | -------------------| ---------------|
78- | Jackson County | 29095 |
79- | Platte County | 29165 |
80- | Cass County | 29037 |
81- | Clay County | 29047 |
82-
83- ** Data from Kansas City is given its own dedicated line, with FIPS
84- code 70003.** This is how JHU encodes their data. However, the data in
85- the four counties that Kansas City intersects is not necessarily zero.
86-
87- For the mapping to HRR and MSA, the counts for Kansas City are dispersed to
88- these four counties in equal proportions.
89-
90- ### Dukes and Nantucket Counties, Massachusetts
91-
92- ** The counties of Dukes and Nantucket report their figures together,
93- and we (like JHU) list them under FIPS Code 70002.** Here are the FIPS codes
94- for the individual counties:
95-
96- | County Name | FIPS Code |
97- | -------------------| ---------------|
98- | Dukes County | 25007 |
99- | Nantucket County | 25019 |
100-
101- For the mapping to HRR and MSA, the counts for Dukes and Nantucket are
102- dispersed to the two counties in equal proportions.
103-
104- The data in the individual counties is expected to be zero.
105-
106- ### Mismatched FIPS Codes
107-
108- Finally, there are two FIPS codes that were changed in 2015, leading to
109- mismatch between us and JHU. We report the data using the FIPS code used
110- by JHU, again to promote consistency and avoid confusion by external users
111- of the dataset. For the mapping to MSA, HRR, these two counties are
112- included properly.
113-
114- | County Name | State | "Our" FIPS | JHU FIPS |
115- | -------------------| ---------------| -------------------| ---------------|
116- | Oglala Lakota | South Dakota | 46113 | 46102 |
117- | Kusilvak | Alaska | 02270 | 02158 |
118-
119- Documentation for the changes made by the US Census Bureau in 2015:
120- https://www.census.gov/programs-surveys/geography/technical-documentation/county-changes.html
42+ To prevent confusing public consumers of the data, we report the data as closely
43+ as possible to the way JHU reports their data, using the same County FIPS codes.
44+ Nonetheless, there are a few exceptions which should be of interest to the
45+ visualization and modeling teams. These exceptions can be found at the [ JHU Delphi
46+ Epidata API documentation page] ( https://cmu-delphi.github.io/delphi-epidata/api/covidcast-signals/jhu-csse.html#geographical-exceptions ) .
12147
12248## Negative incidence
12349
@@ -129,26 +55,3 @@ to County Y, County X may have negative incidence.
12955
13056Because the MSA and HRR numbers are computed by taking population-weighted
13157averages, the count data at those geographical levels may be non-integral.
132-
133- ## Counties not in our canonical dataset
134-
135- Some FIPS codes do not appear as the primary FIPS for any ZIP code in our
136- canonical ` 02_20_uszips.csv ` ; they appear in the ` county ` exported files, but
137- for the MSA/HRR mapping, we disburse them equally to the counties with whom
138- they appear as a secondary FIPS code. The identification of such "secondary"
139- FIPS codes are documented in ` notebooks/create-mappings.ipynb ` . The full list
140- of ` secondary, [mapped] ` is:
141-
142- ```
143- SECONDARY_FIPS = [ # generated by notebooks/create-mappings.ipynb
144- ('51620', ['51093', '51175']),
145- ('51685', ['51153']),
146- ('28039', ['28059', '28041', '28131', '28045', '28059', '28109',
147- '28047']),
148- ('51690', ['51089', '51067']),
149- ('51595', ['51081', '51025', '51175', '51183']),
150- ('51600', ['51059', '51059', '51059']),
151- ('51580', ['51005']),
152- ('51678', ['51163']),
153- ]
154- ```
0 commit comments