← Back to home
Comparison · Infra & APIs

smam vs usmapdata

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

smam vs usmapdata: at a glance

Featuresmamusmapdata
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesanimal-movement, stochastic-processes, state-space-models, rcppr-packages, geospatial, census-data, cartography
Last editorial update3h ago1h 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 usmapdata?

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.

Read the full usmapdata trajectory →

smam vs usmapdata: 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
usmapdata
INFRA · APIS
2.5

usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to smam and usmapdata

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 usmapdata.

See all smam alternatives → · See all usmapdata alternatives →

Recent activity from smam and usmapdata

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

  1. 23d agousmapdata2025 Census shapefiles added
  2. 5mo agosmamRcpp attributes regenerated to guard Rf_error calls
  3. 0y agousmapdataPuerto Rico added across every map vintage
  4. 1y agousmapdataus_map() returns a data frame instead of a tibble
  5. 1y agousmapdata2024 Census shapefiles added
  6. 1y agousmapdatadata_year turns the package into a multi-vintage archive
  7. 2y agousmapdataMap data moves to 2023 shapefiles
  8. 2y agosmamMaintainer email updated
  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 usmapdata?

They serve adjacent needs but don't currently overlap on shipped themes. usmapdata is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is smam better than usmapdata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. usmapdata is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 usmapdata?

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.