tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
excluder vs USAboundaries
A side-by-side editorial comparison of excluder and USAboundaries — release velocity, themes, recent moves, and the top alternatives to consider.
excluder vs USAboundaries: at a glance
What is excluder?
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.
What is USAboundaries?
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
excluder vs USAboundaries: editorial side-by-side
excluder
0.0ANALYTICS
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
◆ Current state
excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.
◆ Where it's heading
The package is stable and its maintenance load comes from things it does not control: the {iptools} package leaving CRAN, {tidyselect} deprecating the .data pronoun, IP-geolocation tests breaking when the underlying address data shifts. Much of that work is about staying installable, not about better exclusions. Note that several of these entries were backfilled into the feed within the same two-minute window and are not in version order.
◆ Prediction
The next release will most likely be another dependency or CRAN-check response rather than a new exclusion criterion, following the pattern of the last three.
USAboundaries
0.0ANALYTICS
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
◆ Current state
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
◆ Where it's heading
For a data package the release cycle is the data vintage, and the 0.3.0 split into a separate data package was designed precisely so those refreshes would not require a code release. That the 2024 update still arrived as two package versions seven years later says the mechanism is being used sparingly. Nothing in the feed shows work on the API itself since us_cities() gained an sf return type and a states argument in 2018.
◆ Prediction
The next release is most likely another vintage refresh when the census data moves again, rather than new geographies or functions. The split of 0.5.0 and 0.5.1 suggests state boundaries are handled on a separate path from the rest and may lag again.
Alternatives to excluder and USAboundaries
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either excluder or USAboundaries.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all excluder alternatives → · See all USAboundaries alternatives →
Recent activity from excluder and USAboundaries
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9mo agoUSAboundariesState boundaries updated to the 2024 census vintage
- 10mo agoUSAboundariesCensus data refreshed to 2024, states excepted
- 1y agoexcluderInternet-dependent tests and examples made conditional
- 2y agoexcluderqualtrics_fetch2 dataset and tidyselect deprecation fixes
- 3y agoexcluderCRAN acceptance and graceful IP-lookup failure
- 3y agoexcluderdplyr 1.0.8 across()/is.na() compatibility fix
- 3y agoexcluderuse_labels(), rename_columns(), and orientation-agnostic resolution
- 3y agoexcluderSwaps iptools for ipaddress
- 8y agoUSAboundariesus_cities() returns sf and gains a states argument
- 9y agoUSAboundariesData split into a companion package; all boundaries become sf ⚡
- 9y agoUSAboundariesContemporary state, county and district boundaries added
Frequently asked questions
What is the difference between excluder and USAboundaries?
They serve adjacent needs but don't currently overlap on shipped themes. excluder and USAboundaries are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is excluder better than USAboundaries?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. excluder and USAboundaries are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to excluder?
Top excluder alternatives in Analytics are ranked by recent ship velocity. Browse the "excluder alternatives" section above for the current picks, or visit /alternatives/excluder for the full list with editorial commentary on each.
What are the best alternatives to USAboundaries?
Top USAboundaries alternatives in Analytics are ranked by recent ship velocity. Browse the "USAboundaries alternatives" section above for the current picks, or visit /alternatives/usaboundaries for the full list with editorial commentary on each.