ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
A side-by-side editorial comparison of tabular and usmapdata — release velocity, themes, recent moves, and the top alternatives to consider.
tabular went from clinical tables to complete TFL output in under two months.
tabular renders pre-summarised clinical tables, figures and listings to RTF, LaTeX, HTML, PDF, DOCX, Markdown and now Typst from one immutable verb pipeline, with no external SAS or Java runtime. It arrived in June 2026 as a CRAN submission candidate, added figure() a month later to cover the F in TFL, and has spent the 0.3.x line on speed, font resolution and toolchain diagnostics.
usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.
usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.
tabular renders pre-summarised clinical tables, figures and listings to RTF, LaTeX, HTML, PDF, DOCX, Markdown and now Typst from one immutable verb pipeline, with no external SAS or Java runtime. It arrived in June 2026 as a CRAN submission candidate, added figure() a month later to cover the F in TFL, and has spent the 0.3.x line on speed, font resolution and toolchain diagnostics.
The work is converging on backend parity — one spec should render the same wherever you emit it. Recent notes are almost entirely gap-closing between targets: bold column headers and page-width correction on LaTeX, cell margins on DOCX, group-separator blank rows re-expressed as discardable space so a page never ends on a stray gap, whitespace collapsing honoured on Typst. Diagnostics are keeping pace, with check_latex() probing through kpsewhich and check_typst() auditing the compiler and font chain.
With both toolchain checkers in place, the friction that remains is environmental rather than featural, and the notes point to further parity and packaging fixes rather than another backend. Whether Typst becomes the default PDF path instead of LaTeX is not something these notes settle.
usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.
The package has settled into a predictable rhythm — one shapefile vintage per year, with structural change rare and clustered. The two changes that mattered were data_year in 0.4.0, which turned a single-vintage dataset into a time series, and the tibble-to-data-frame switch in 0.6.0 that reduced what downstream callers have to depend on.
The stated policy — each year added going forward, previous years reachable through data_year — points to a 2026 vintage as the next release. Nothing in these notes suggests further change to the data model.
Other Infra & APIs 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 tabular or usmapdata.
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore declared its API stable with every survey design type covered.
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
See all tabular alternatives → · See all usmapdata alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. tabular and usmapdata are shipping at a similar cadence (velocity 2.5 vs 2.5, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tabular and usmapdata are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top tabular alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tabular alternatives" section above for the current picks, or visit /alternatives/tabular for the full list with editorial commentary on each.
Top usmapdata alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "usmapdata alternatives" section above for the current picks, or visit /alternatives/usmapdata for the full list with editorial commentary on each.