← Back to home
Comparison · Infra & APIs

plssem vs usmap

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

plssem vs usmap: at a glance

Featureplssemusmap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesstructural-equation-modeling, partial-least-squares, multilevel-models, standard-errorscartography, sf, data-packaging, fips
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

What is plssem?

plssem took PLS-SEM into multilevel data, then spent two releases making the estimates trustworthy.

plssem is a young R implementation of partial least squares structural equation modelling, three CRAN releases old and shipping monthly. Its distinguishing work is the MC-PLS family — consistent PLS estimators the maintainer extended to mixed-effects designs in June — and the releases since have been about getting standard errors, admissibility and fit measures onto the same footing as the point estimates.

Read the full plssem 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 →

plssem vs usmap: editorial side-by-side

P
plssem
INFRA · APIS
0.0

plssem took PLS-SEM into multilevel data, then spent two releases making the estimates trustworthy.

◆ Current state

plssem is a young R implementation of partial least squares structural equation modelling, three CRAN releases old and shipping monthly. Its distinguishing work is the MC-PLS family — consistent PLS estimators the maintainer extended to mixed-effects designs in June — and the releases since have been about getting standard errors, admissibility and fit measures onto the same footing as the point estimates.

◆ Where it's heading

The pattern is capability first, inference second. Multilevel MC-PLSc and MC-OrdPLSc arrived in 0.1.2 together with Monte-Carlo delta-method standard errors and a Polyak-Juditsky extrapolation step; 0.1.3 then extended delta-method errors to redundant parameters and thresholds, optimized their computation, added a loglikelihood-based fit measure and generated dynamic bounds to keep MC-PLS solutions admissible. Admissibility recurs throughout — penalized inadmissible solutions in 0.1.1, variance lower bounds and negative residual variance handling in 0.1.3, and an option to drop inadmissible bootstraps rather than silently include them. The release notes are pull-request lists, so the reasoning behind each change stays in the repository.

◆ Prediction

The MIMIC mode and GLS estimator both landed in the most recent release without the standard-error and fit-measure work that followed earlier additions, so extending inference to cover them is the natural next step. Bootstrap defaults moving to 500 replications suggests runtime is a live constraint and further optimization is likely.

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

See all plssem alternatives → · See all usmap alternatives →

Recent activity from plssem and usmap

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

  1. 1mo agoplssemMIMIC mode, a GLS structural estimator and delta-method thresholds
  2. 2mo agoplssemMC-PLSc and MC-OrdPLSc extend to multilevel and mixed-effects models
  3. 3mo agoplssemParallel bootstrapping, kNN and mean imputation, higher-order constructs
  4. 11mo agousmapPuerto Rico added across every usmap function and map year
  5. 1y agousmapdata_year parameter threaded through the plotting functions
  6. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  7. 2y agousmapMap data becomes sf; usmap_transform() returns geometry
  8. 2y agousmapDocumentation links updated
  9. 2y agousmapMap data extracted to a companion usmapdata package

Frequently asked questions

What is the difference between plssem and usmap?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. plssem 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 plssem?

Top plssem alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "plssem alternatives" section above for the current picks, or visit /alternatives/plssem 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.