STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
A side-by-side editorial comparison of rnpn and sdsfun — release velocity, themes, recent moves, and the top alternatives to consider.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
sdsfun collects spatial data science utilities — neighbour lists, spatial constrained clustering, discretization, dummy variable generation, geographical detector statistics and projection helpers — with the computationally heavy parts implemented in Rcpp. It was assembled quickly across late 2024, adding a function set roughly every three weeks, and has slowed since to a couple of releases a year. The most recent work is corrective: no longer initializing the RNG state at load, fixing matrix inputs misread as vectors, and clearing an Armadillo deprecation.
rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.
The package is being brought onto the current R stack and made honest about missing data, and those are the same project. Converting the -9999 sentinel to NA started in 1.3.0 for download functions and was extended to all columns in 1.4.1; the string "emptyvalue" got the same treatment. Beyond the migration, the feature additions are modest and specific to the domain, such as custom start and end dates for defining a phenometrics season.
With the dependency migration finished and sentinel handling now applied across all columns, the next releases most likely return to domain features and to fixes surfaced by the server side, which has already prompted work through migrations and backend moves. The removed progress indicator is an acknowledged regression that may come back.
sdsfun collects spatial data science utilities — neighbour lists, spatial constrained clustering, discretization, dummy variable generation, geographical detector statistics and projection helpers — with the computationally heavy parts implemented in Rcpp. It was assembled quickly across late 2024, adding a function set roughly every three weeks, and has slowed since to a couple of releases a year. The most recent work is corrective: no longer initializing the RNG state at load, fixing matrix inputs misread as vectors, and clearing an Armadillo deprecation.
This is infrastructure for a family of packages rather than an end-user tool, and the changelog says so directly — functions were added to support gdverse and sesp, and moran_test was migrated in from geocomplexity. That migration pattern is the defining move: capability consolidates here so the downstream packages can share it instead of each carrying its own copy. Growth has slowed as that consolidation completed, leaving correctness and dependency upkeep.
Given the package moves when its dependents need something, the next release most likely brings in another shared function or responds to a downstream requirement rather than following its own plan. Armadillo and CRAN check changes remain the reliable source of maintenance work.
Other Analytics 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 rnpn or sdsfun.
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. rnpn and sdsfun 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. rnpn and sdsfun 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 Analytics products to evaluate alongside.
Top rnpn alternatives in Analytics are ranked by recent ship velocity. Browse the "rnpn alternatives" section above for the current picks, or visit /alternatives/rnpn for the full list with editorial commentary on each.
Top sdsfun alternatives in Analytics are ranked by recent ship velocity. Browse the "sdsfun alternatives" section above for the current picks, or visit /alternatives/sdsfun for the full list with editorial commentary on each.