massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
Comparison · Infra & APIs
remap vs rollupTree
A side-by-side editorial comparison of remap and rollupTree — release velocity, themes, recent moves, and the top alternatives to consider.
remap vs rollupTree: at a glance
What is remap?
A regional-model smoother in long-term maintenance, four years past its last real feature.
remap fits separate models to geographic regions and blends their predictions into a continuous surface, using the min_n nearest observations so region boundaries do not show as discontinuities. The methodological work is finished — the last behavioural change landed in 2022, and everything since has been unit handling, compiler warnings, dependency compatibility and citation updates. The July release is one such patch.
What is rollupTree?
The recursive-computation engine under massProps grows the accessors its consumer needed
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
remap vs rollupTree: editorial side-by-side
remap
0.0INFRA · APIS
A regional-model smoother in long-term maintenance, four years past its last real feature.
◆ Current state
remap fits separate models to geographic regions and blends their predictions into a continuous surface, using the min_n nearest observations so region boundaries do not show as discontinuities. The methodological work is finished — the last behavioural change landed in 2022, and everything since has been unit handling, compiler warnings, dependency compatibility and citation updates. The July release is one such patch.
◆ Where it's heading
This is a stable academic package tracking its ecosystem rather than growing. The visible pattern is reactive maintenance: sf's 1.0.0 transition, ggplot2's size-to-linewidth rename, a gcc-UBSAN error on zero-point distance calculations, and now a check that distance matrices passed to remap() and predict() are converted to kilometres. Note that the feed's timestamps invert the version order — 0.3.1 is stamped seconds after 0.3.2 despite being the earlier release, so recency in this feed is not a reliable guide to sequence.
◆ Prediction
Nothing in these entries points to new capability. The realistic expectation is more of the same: a patch whenever sf, ggplot2 or a CRAN check surfaces an incompatibility, at roughly the observed cadence of one release every year or two.
rollupTree
0.0INFRA · APIS
The recursive-computation engine under massProps grows the accessors its consumer needed
◆ Current state
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
◆ Where it's heading
The package develops in response to its one visible consumer. The 0.4.0 accessors appeared in January 2026 and massProps switched to them thirteen days later; 0.4.1 then fixed missing column names in the setters, which is the kind of defect only real use surfaces. Before that, 0.3.0's default_validate_dag() extended validation past strict trees to directed acyclic graphs, widening what structures the engine will accept.
◆ Prediction
On the established pattern the next release will be whatever massProps needs next, discovered by using it. A DAG validator suggests non-tree structures are in scope, but nothing in these notes says that path is being pushed further.
Alternatives to remap and rollupTree
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 remap or rollupTree.
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
GeoThinneR
Spatial thinning grows a result object, and the API breaks to make room for it
See all remap alternatives → · See all rollupTree alternatives →
Recent activity from remap and rollupTree
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoremapDistance matrices now converted to kilometres automatically
- 6mo agorollupTreeMissing column names in the new row setters
- 6mo agorollupTreeRow-level get and set accessors by key and by id
- 1y agorollupTreeMinor vignette improvements
- 1y agorollupTreeBadges and GitHub Actions added to the README
- 1y agorollupTreedefault_validate_dag() extends validation past strict trees
- 1y agoremapCitation updated to the R Journal article
- 1y agoremapUBSAN fix, parallel patch and sf search-path independence
- 3y agoremappredict() can return an upper bound on combined standard errors
- 5y agoremapRegions without observations no longer break the prediction surface
Frequently asked questions
What is the difference between remap and rollupTree?
They serve adjacent needs but don't currently overlap on shipped themes. remap and rollupTree 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 remap better than rollupTree?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. remap and rollupTree 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 remap?
Top remap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "remap alternatives" section above for the current picks, or visit /alternatives/remap for the full list with editorial commentary on each.
What are the best alternatives to rollupTree?
Top rollupTree alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rollupTree alternatives" section above for the current picks, or visit /alternatives/rolluptree for the full list with editorial commentary on each.