v1.6.2

Flurry of recent releases since the county --> COG switch

cwi 1.6.2

Edit xwalk---there were still more FIPS codes to update with their COG-based versions. The data frame now includes COG-based codes for block groups, tracts, towns, and PUMAs.

cwi 1.6.1

Bump ACS-related defaults to 2022

cwi 1.6.0

MINOR BREAKING CHANGE: This update corresponds to the 2022 ACS data release, which is the first to use COGs instead of counties. Because COGs have different FIPS codes, town and tract FIPS codes (but apparently not block groups) have changed to match. The bulk of their code digits stay the same, but the portion signifying the county changed, e.g. 09009140101 is now 09170140101. To deal with that without breaking too much code, there are a few changes to the package:

• Neighborhood lookup tables (bridgeport_tracts, etc) have the previous county-based FIPS codes in the column geoid, and the new COG-based FIPS codes in the column geoid_cog.
• xwalk now has columns for COG-based town and tract FIPS codes, in addition to the previous county-based ones.
• Calling multi_geo_acs with counties = "all" (the default) will get you COGs, but multi_geo_decennial will get you counties, because the switch was not retroactive.
• The names of COGs returned by multi_geo_acs and used for names in the regions list are the ones the Census Bureau uses. Unfortunately, these aren't all the ones the state uses. For that, I've added a function fix_cogs, which replaces common names for them with the ones the state lists somewhat officially, e.g. Capitol COG is in the census data, Capitol Region COG is what the state usually uses but probably not always.
• Finally, the part that doesn't come up often but will break: previously the multi_geo_* functions took neighborhood names, weights, and GEOIDs as bare column names, with defaults (name, weight, and geoid, respectively). These now have to all be given as strings (i.e. in quotation marks), and geoid no longer has a default. This is to deal with the fact that some calculations will now need the neighborhood lookup tables' geoid columns, and some will need geoid_cog. This only matters when you're including neighborhoods in function calls.

cwi 1.4.0

cwi 1.4.0

• MINOR BREAKING CHANGE: multi_geo_decennial now defaults to 2020. Because the 2020 decennial uses a different summary file code from previous years, the default sumfile argument, if used with 2010, will lead to an error.
• 2020 decennial variables are now available in decennial_vars20. The 2010 ones are still in decennial_vars10.
• A new data frame, cb_avail, has the years, programs (ACS vs decennial), and dataset codes (SF1, ACS5, DHC, etc.) available from the Census Bureau's API.
• The function dh_scaffold was poorly named and not a great fit for the aims of this project. It's been moved to {stylehaven}; find it there as scaffold_project.
• Minor improvements to some warnings and other messages.

cwi 1.3.0

• Add COGs to xwalk along with function for reconciling names

cwi 1.2.0

• Update defaults to 2021 where applicable: multi_geo_acs, adj_inflation base year, label_acs.
• Replace acs_vars20 with acs_vars21.
• multi_geo_decennial now takes "pl" as a possible value for summary file, since the full 2020 Decennial data still aren't out.

cwi 1.1.3

• Add regional councils of governments to regions list. Connecticut adopted these in 2022 to replace counties. Definitions from CTOPM here.
• Add vignette on regions since there's so many of them now

cwi 1.1.2

• Start handling updated MSA definitions—not sure that any datasets actually use these yet
• Add rescale option to sub_nonanswers—its default won't change any existing code

cwi 1.1.1

Bugfix: occupational codes have larger groups and smaller groups. One larger group (Healthcare Practitioners and Technical Occupations) was mislabeled so it was marked as being under Education, Legal, Community Service, Arts, and Media Occupations.

cwi 1.1.0

Some updates to 2020

• 2020 ACS 5-year data are finally out, so acs_vars19 has been replaced by acs_vars20, and multi_geo_acs now uses 2020 as the default. Some examples & vignette code have been updated to match.
• Decennial census data aren't out yet and won't be for some time, so decennial-related things still default to 2010.

cwi 1.0.0

Major exciting overhaul! This was the first time I felt like enough of this package is flexible and well thought out to consider it a real release. A lot of the changes are under the hood--I split a lot of functions into slimmed-down main "caller" functions and multiple task-focused "helper" functions, making it easier to maintain the package, add or modify features, and use the same code for multiple tasks.

User-facing updates

• Moved from base messages to cli for cleaner and clearer messaging (printouts on what fetch functions are getting, limitations to function calls, etc)
• Better handling of Census API calls to better deal with how very often their servers are busted
• Metadata: several behind-the-scenes datasets that set limits of functions' API calls are now expanded to not just be limited to Connecticut--includes qwi_industry and laus_trend.
• Added a table of occupation codes for main occupation groups
• Better documentation for many functions

Breaking changes

• I've never liked the levels for the multi_geo_* functions--I don't really remember why I made these plural, but they're now singular. So a column that would have been e.g. "1_state", "2_counties", "3_towns" will now be "1_state", "2_county", "3_town". This might break filtering you've done by level.
• Renamed one function: acs_quick_map --> quick_map

To do

• Update to 2020 ACS and Decennial defaults

cwi 0.4.4

• Add handling for reading crosstab weights placed in headers alongside data rather than in a separate table (e.g. for 2021).

cwi 0.4.0

• Rewrote neighborhood weights with the 2020 redistricting block boundaries. Dropped the block group table that was only done for New Haven, and changed the name of nhv_tracts to new_haven_tracts to match those for other cities.
• QWI API is working again, but payroll data is missing from their database.

cwi 0.3.1

• Minor behind-the-scenes updates

cwi 0.2.0

• Added finished versions of read_xtab, read_weights, xtab2df, and collapse_n_wt for working with DataHaven Community Wellbeing Survey crosstabs—see vignettes
• Added add_logo with built-in DataHaven logo
• Bug fixes in sub_nonanswers, xwalk