← Back to home
Comparison · Infra & APIs

smam vs usmap

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

smam vs usmap: at a glance

Featuresmamusmap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesanimal-movement, stochastic-processes, state-space-models, rcppcartography, sf, data-packaging, fips
Last editorial update6h ago42m ago
WebsiteVisit →Visit →

What is smam?

Animal-movement models in R, where new stochastic processes arrive years apart.

smam fits statistical models of animal movement, covering moving-resting processes with and without measurement error, moving-resting-handling, and moving-moving processes, with simulation, point estimation and variance estimation for each. The last three releases are pure upkeep: guarding Rf_error calls after an Rcpp update, a maintainer email change, and a compiler warning fix. The substantive work in this window is 0.7.0, which added estimate and vcov generics across all fit functions, and 0.6.0, which added the moving-moving process.

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

smam vs usmap: editorial side-by-side

S
smam
INFRA · APIS
0.0

Animal-movement models in R, where new stochastic processes arrive years apart.

◆ Current state

smam fits statistical models of animal movement, covering moving-resting processes with and without measurement error, moving-resting-handling, and moving-moving processes, with simulation, point estimation and variance estimation for each. The last three releases are pure upkeep: guarding Rf_error calls after an Rcpp update, a maintainer email change, and a compiler warning fix. The substantive work in this window is 0.7.0, which added estimate and vcov generics across all fit functions, and 0.6.0, which added the moving-moving process.

◆ Where it's heading

This package grows by adding process models, and it does so rarely. Between the moving-moving process in 2021 and now, the only interface-level change has been the 0.7.0 generics that gave every fit function a common way to retrieve estimates and their covariance, which is consolidation of an accumulated collection rather than expansion of it. The three releases since are entirely reactive to toolchain and CRAN pressure, and they arrive in step with the maintainer's other package coga, which received the same Rcpp guard within twenty minutes on the same day.

◆ Prediction

Expect further releases to be CRAN and Rcpp maintenance unless a new movement process is published, which is what has historically prompted a minor version here. The generics added in 0.7.0 give any future process model a ready-made interface to slot into.

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

See all smam alternatives → · See all usmap alternatives →

Recent activity from smam and usmap

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

  1. 5mo agosmamRcpp attributes regenerated to guard Rf_error calls
  2. 11mo agousmapPuerto Rico added across every usmap function and map year
  3. 1y agousmapdata_year parameter threaded through the plotting functions
  4. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  5. 2y agousmapMap data becomes sf; usmap_transform() returns geometry
  6. 2y agosmamMaintainer email updated
  7. 2y agousmapDocumentation links updated
  8. 2y agousmapMap data extracted to a companion usmapdata package
  9. 2y agosmamCompiler format-security warning resolved
  10. 3y agosmamestimate and vcov generics unify all fit functions
  11. 5y agosmamMoving-moving process added with simulation and estimation
  12. 5y agosmamVariance estimators adjusted; example dataset added

Frequently asked questions

What is the difference between smam and usmap?

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

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

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