RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of filtro and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | filtro | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | feature selection, tidymodels, s7, filter methods | gis, esri-migration, offline-maps, field-data-capture |
| Last editorial update | 1h ago | 7h ago |
| Website | Visit → | — |
filtro moves to S7 and multiplies its feature-scoring methods in a single release.
filtro supplies feature-selection filter scores for the tidymodels stack. Version 0.2.0 adds five scoring methods — correlation, random forest importance, information gain, ROC AUC and cross tabulation — and moves the package from S3 to S7. It also gains a ranking layer: show_best_score_* and rank_best_score_* helpers for a single score, plus desirability-function helpers for optimising across several scores at once.
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
filtro supplies feature-selection filter scores for the tidymodels stack. Version 0.2.0 adds five scoring methods — correlation, random forest importance, information gain, ROC AUC and cross tabulation — and moves the package from S3 to S7. It also gains a ranking layer: show_best_score_* and rank_best_score_* helpers for a single score, plus desirability-function helpers for optimising across several scores at once.
The package is being built out on two axes at once — the catalogue of scores, and the machinery for choosing between them. The desirability functions are the more telling half, since they assume users will filter on several criteria rather than one. Adopting S7 while still pre-1.0 suggests the object model is being settled before the API is frozen.
Expect more scoring methods on the same S7 interface and a 1.0 release once the score and ranking APIs stop moving; the ranking helpers' naming is the most likely thing to change first.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
The direction is a full consolidation onto Esri. The legacy Google Maps engine is being retired on September 1 with automatic migration for anyone who hasn't switched, and Esri now carries Google's satellite and street basemaps so the imagery argument is neutralized. Underneath, the mobile SDK moved to ArcGIS 300.0.0 and ONNX on-device inference was dropped for a new INFERENCE format with labels.txt support. Offline is the second thread: downloadable layers can now be updated in place rather than deleted and recreated.
Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri feature parity work, with the MMPK layer and Photo FastFill early-access programs the most likely to graduate to general availability next.
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 filtro or Fulcrum.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all filtro alternatives → · See all Fulcrum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 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 Analytics products to evaluate alongside.
Top filtro alternatives in Analytics are ranked by recent ship velocity. Browse the "filtro alternatives" section above for the current picks, or visit /alternatives/filtro-r for the full list with editorial commentary on each.
Top Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.