pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of rsofun and usmap — release velocity, themes, recent moves, and the top alternatives to consider.
An ecosystem model starts tracking carbon isotopes and land-use change.
rsofun wraps the P-model and BiomeE vegetation models in R with Fortran cores, covering photosynthesis, water balance and forest demography, plus Bayesian calibration. The 5.1.0 release is the first in the window to widen what the models simulate rather than reorganise them. Before it, the history is renaming, cost-function rewrites and output-format consistency work.
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.
rsofun wraps the P-model and BiomeE vegetation models in R with Fortran cores, covering photosynthesis, water balance and forest demography, plus Bayesian calibration. The 5.1.0 release is the first in the window to widen what the models simulate rather than reorganise them. Before it, the history is renaming, cost-function rewrites and output-format consistency work.
The direction is from a calibration harness toward a model that can answer different questions: isotope fractionation now comes out of the P-model, BiomeE handles land use and land-use change, and forcing can be recycled when a simulation outruns its data. Version stamps are unreliable here, with a v5.0 tag carrying only a build fix and predating v4.4, so the arc reads better through content than through numbering.
The isotope work is explicitly unfinished, with a constant atmospheric signature standing in for daily d13c forcing, so the next likely step is accepting that as model input.
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.
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.
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.
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 rsofun or usmap.
The protist reference database keeps widening past the rRNA gene it was built on.
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
Conservation planning absorbs the literature's target-setting rules as code.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
State-panel tooling holding steady since its 2020 data and ergonomics release.
See all rsofun alternatives → · See all usmap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rsofun 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rsofun 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.
Top rsofun alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rsofun alternatives" section above for the current picks, or visit /alternatives/rsofun for the full list with editorial commentary on each.
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.