A tables-listings-graphs package that reached CRAN and then went quiet.
USAboundaries alternatives
The best USAboundaries alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to USAboundaries? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, USAboundaries shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About 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.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to USAboundaries
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
USAboundaries vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| USAboundaries (baseline) | 0.0 | 0 | geospatialcensus-datasf | Data split into a companion package; all boundaries become sf |
| tidytlg | 0.0 | 0 | clinical-trialstablesr-package | — |
| Tplyr | 0.0 | 0 | clinical-trialstablestraceability | 1.0.0 introduces the traceability metadata framework |
| rlistings | 0.0 | 0 | clinical-trialslistingspagination | — |
| hoardr | 0.0 | 0 | cachingr-packageropensci | — |
| gigs | 0.0 | 0 | growth-standardsneonatal-healthr-package | Conversion API rewritten around data frames and classify_growth() |
| riem | 0.0 | 0 | weather-dataapi-clientr-package | — |
| datasetjson | 0.0 | 0 | clinical-datacdiscjson | Dataset-JSON 1.1.0 support with a redesigned object model |
| ijtiff | 0.0 | 0 | imagingtiffr-package | — |
| tern | 0.0 | 0 | clinical-trialstablesr-package | Two dozen more analysis functions drop make_afun() |
| posteriordb | 0.0 | 0 | bayesianbenchmarkingreference-data | — |
| tinkr | 0.0 | 0 | markdownxmlr-package | First release: the extensible yarn R6 class |
| excluder | 0.0 | 0 | survey-datadata-cleaningr-package | — |
The 12 best USAboundaries alternatives, in depth
1. tidytlg · velocity 0.0
A tables-listings-graphs package that reached CRAN and then went quiet.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where USAboundaries leans on geospatial, census data and sf, tidytlg focuses on clinical trials, tables and r package.
tidytlg and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full tidytlg trajectory → · Compare USAboundaries vs tidytlg →
2. Tplyr · velocity 0.0
Tplyr made clinical summary tables explain where every number came from.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0.0 introduces the traceability metadata framework”.
Where USAboundaries leans on geospatial, census data and sf, Tplyr focuses on clinical trials, tables and traceability.
Tplyr and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. rlistings · velocity 0.0
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where USAboundaries leans on geospatial, census data and sf, rlistings focuses on clinical trials, listings and pagination.
rlistings and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full rlistings trajectory → · Compare USAboundaries vs rlistings →
4. hoardr · velocity 0.0
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where USAboundaries leans on geospatial, census data and sf, hoardr focuses on caching, r package and ropensci.
hoardr and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full hoardr trajectory → · Compare USAboundaries vs hoardr →
5. gigs · velocity 0.0
Gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Conversion API rewritten around data frames and classify_growth()”.
Where USAboundaries leans on geospatial, census data and sf, gigs focuses on growth standards, neonatal health and r package.
gigs and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. riem · velocity 0.0
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where USAboundaries leans on geospatial, census data and sf, riem focuses on weather data, api client and r package.
riem and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. datasetjson · velocity 0.0
Datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Dataset-JSON 1.1.0 support with a redesigned object model”.
Where USAboundaries leans on geospatial, census data and sf, datasetjson focuses on clinical data, cdisc and json.
datasetjson and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full datasetjson trajectory → · Compare USAboundaries vs datasetjson →
8. ijtiff · velocity 0.0
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where USAboundaries leans on geospatial, census data and sf, ijtiff focuses on imaging, tiff and r package.
ijtiff and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full ijtiff trajectory → · Compare USAboundaries vs ijtiff →
9. tern · velocity 0.0
Tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Two dozen more analysis functions drop make_afun()”.
Where USAboundaries leans on geospatial, census data and sf, tern focuses on clinical trials, tables and r package.
tern and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. posteriordb · velocity 0.0
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where USAboundaries leans on geospatial, census data and sf, posteriordb focuses on bayesian, benchmarking and reference data.
posteriordb and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full posteriordb trajectory → · Compare USAboundaries vs posteriordb →
11. tinkr · velocity 0.0
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “First release: the extensible yarn R6 class”.
Where USAboundaries leans on geospatial, census data and sf, tinkr focuses on markdown, xml and r package.
tinkr and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. excluder · velocity 0.0
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where USAboundaries leans on geospatial, census data and sf, excluder focuses on survey data, data cleaning and r package.
excluder and USAboundaries have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full excluder trajectory → · Compare USAboundaries vs excluder →
Frequently asked questions
What are the best alternatives to USAboundaries?
The top USAboundaries alternatives we currently track in analytics tools are tidytlg, Tplyr, rlistings, hoardr, gigs, ranked by recent ship velocity.
How is this list of USAboundaries alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare USAboundaries directly with one of these alternatives?
Yes — every card has a "Compare with USAboundaries" link to a side-by-side /compare page.