censusxy 1.1.1

• Address issue with OpenBLAS on CRAN checks

censusxy 1.1.0

• Expand support for parallel processing to Windows and the process has been streamlined so that Unix and Windows platforms now use the same workflow internally. This workflow change was motivated by a bug with macOS 12.4.
• Dependencies that are listed under Imports have been expanded since all operating systems now use the same packages to facilitate parallel processing.
• R version 3.4 is now the minimum version supported
• Miscellaneous documentation updates
• We’ve made some internal changes to ensure that API issues fail gracefully
• Documentation improvements have been made to clarify the main vignette

censusxy 1.0.1

• Fix issue related to current vintages and benchmarks in options.R that changed due to the 2020 Decennial Census

censusxy 1.0.0

Version 1.0.0 brings breaking changes, but adds a ton of new functionality. * Full support for all Census Bureau Geographic Tools * The syntax of cxy_geocode() has changed slightly to facilitate new options * Non-Standard Evaluation (NSE) has been removed * censusxy now only has 1 dependency * Parallel support added for Unix Platforms

censusxy 0.1.3

• The cxy_geocode() function now includes an option fill_na, which is enabled by default. Two fields in the original implementation of the package, cxy_quality and cxy_match, were returned as empty strings when no match was identified. Now, by default, they will both be returned with NA values when there is no match. If you want to return to the original behavior, simply set fill_na = FALSE in your function call.

censusxy 0.1.2

• Address CRAN policy concerns with how temporary files are saved and removed when uploading batches of addresses to the Census Bureau’s website

censusxy 0.1.1

• CRAN release version of the software.
• Corrected tense shifts in description paragraph in DESCRIPTION, README.Rmd, and index.Rmd
• Other minor updates to pkgdown site and README.Rmd

censusxy 0.1.0

• Added a NEWS.md file to track changes to the package.
• Add initial package infrastructure and functionality.
• Enable continuous integration and code coverage testing of package.
• Build pkgdown site.