← Back to home
Comparison · Infra & APIs

pakret vs usmap

A side-by-side editorial comparison of pakret and usmap — release velocity, themes, recent moves, and the top alternatives to consider.

pakret vs usmap: at a glance

Featurepakretusmap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesreproducible-documents, citations, bibtex, quartocartography, sf, data-packaging, fips
Last editorial update6h ago38m ago
WebsiteVisit →Visit →

What is pakret?

Package citation for R documents, quietly growing to meet Quarto.

pakret inserts citations for R packages into R Markdown and Quarto documents, resolving each package to a BibTeX entry and writing the .bib file that backs it. Version 0.3.1 adds support for Quarto's inline syntax and separator control when citing several packages in one inline chunk, following 0.3.0, which made the package create missing .bib files, preserve capitalisation in reference titles, and treat the version placeholder in citation templates as optional. Cadence is a handful of small releases a year.

Read the full pakret trajectory →

What is usmap?

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

Read the full usmap trajectory →

pakret vs usmap: editorial side-by-side

P
pakret
INFRA · APIS
0.0

Package citation for R documents, quietly growing to meet Quarto.

◆ Current state

pakret inserts citations for R packages into R Markdown and Quarto documents, resolving each package to a BibTeX entry and writing the .bib file that backs it. Version 0.3.1 adds support for Quarto's inline syntax and separator control when citing several packages in one inline chunk, following 0.3.0, which made the package create missing .bib files, preserve capitalisation in reference titles, and treat the version placeholder in citation templates as optional. Cadence is a handful of small releases a year.

◆ Where it's heading

Every release in this window removes a specific friction someone hit while writing a document. Bib files that had to exist beforehand now get created; single-letter package names like R and C stopped being lower-cased in titles; the package works when loaded after conflicted; citing many packages got faster; and version numbers became optional for documents where they are noise. The 0.3.1 Quarto support extends the same idea to the format its users are moving to. Nothing here is architectural, and nothing needs to be.

◆ Prediction

Expect continued alignment with Quarto as more of its syntax surfaces become relevant, and further refinement of how multi-reference packages resolve to a single entry, which the BibTeX type priority work in 0.2.0 started. The entries give no indication of a 1.0.

U
usmap
INFRA · APIS
0.0

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

◆ Current state

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

◆ Where it's heading

The package has separated what it draws from how it draws, and that separation is what makes the recent releases possible: annual map vintages ship in usmapdata without touching usmap, and Puerto Rico could be backfilled into every existing year at once. The remaining work is coverage and defaults rather than architecture, and the Puerto Rico exclusion default is already governed by an environment variable rather than a code change.

◆ Prediction

Expect the annual map vintage to keep arriving through usmapdata, with usmap itself changing only where a new territory or a projection default needs handling.

Alternatives to pakret and usmap

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 pakret or usmap.

See all pakret alternatives → · See all usmap alternatives →

Recent activity from pakret and usmap

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agopakretQuarto inline syntax supported; list separators configurable
  2. 8mo agopakretMissing .bib files created; capitalisation preserved
  3. 11mo agousmapPuerto Rico added across every usmap function and map year
  4. 1y agousmapdata_year parameter threaded through the plotting functions
  5. 1y agopakretMultiple .bib files supported within one document
  6. 1y agopakretCitations with pre-written keys now supported
  7. 1y agopakretbook entries used when no manual entry exists
  8. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  9. 2y agousmapMap data becomes sf; usmap_transform() returns geometry
  10. 2y agousmapDocumentation links updated
  11. 2y agousmapMap data extracted to a companion usmapdata package

Frequently asked questions

What is the difference between pakret and usmap?

They serve adjacent needs but don't currently overlap on shipped themes. pakret and usmap 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 pakret better than usmap?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. pakret and usmap 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to pakret?

Top pakret alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pakret alternatives" section above for the current picks, or visit /alternatives/pakret for the full list with editorial commentary on each.

What are the best alternatives to usmap?

Top usmap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "usmap alternatives" section above for the current picks, or visit /alternatives/usmap for the full list with editorial commentary on each.