← Back to home
Comparison · Infra & APIs

remap vs tidyplots

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

remap vs tidyplots: at a glance

Featureremaptidyplots
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesspatial-modeling, geostatistics, r-packages, maintenance-modedata-visualization, r-package, ggplot2, scientific-publishing
Last editorial update3h ago1h ago
WebsiteVisit →Visit →

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.

Read the full remap trajectory →

What is tidyplots?

tidyplots keeps rebuilding its own foundations rather than layering around them.

tidyplots wraps ggplot2 in a pipe-driven API aimed at publication-ready scientific figures, trading grammar-of-graphics flexibility for a shorter path to a finished plot. It is at 0.4.0 after two years of frequent releases, and almost every one carries a breaking change — the most recent moved multi-panel layout off patchwork and onto ggplot2's own faceting. Statistical annotation, colour schemes and size control have each been reworked at least once.

Read the full tidyplots trajectory →

remap vs tidyplots: editorial side-by-side

R
remap
INFRA · APIS
0.0

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.

T
tidyplots
INFRA · APIS
0.0

tidyplots keeps rebuilding its own foundations rather than layering around them.

◆ Current state

tidyplots wraps ggplot2 in a pipe-driven API aimed at publication-ready scientific figures, trading grammar-of-graphics flexibility for a shorter path to a finished plot. It is at 0.4.0 after two years of frequent releases, and almost every one carries a breaking change — the most recent moved multi-panel layout off patchwork and onto ggplot2's own faceting. Statistical annotation, colour schemes and size control have each been reworked at least once.

◆ Where it's heading

The package is converging on ggplot2 rather than abstracting away from it: split_plot() now uses facet_wrap and facet_grid, as_tidyplot() was hard-deprecated on the grounds that converting a ggplot was never a good idea, and releases are timed against upstream ggplot2 versions. The other constant is the statistics surface, which has grown from basic error bars to paired and selected comparisons. Breaking changes are announced plainly and frequently, consistent with a package using 0.x to fix its shape before committing.

◆ Prediction

The patchwork removal is described as something that will eventually break dependent code, so the near-term work is likely completing that migration and settling the split_plot() parameters introduced alongside it. A 1.0 would signal the breaking-change cadence is ending, and nothing here indicates that yet.

Alternatives to remap and tidyplots

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

See all remap alternatives → · See all tidyplots alternatives →

Recent activity from remap and tidyplots

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

  1. 1mo agoremapDistance matrices now converted to kilometres automatically
  2. 7mo agotidyplotstidyplots 0.4.0
  3. 1y agotidyplotstidyplots 0.3.1
  4. 1y agotidyplotstidyplots 0.2.2
  5. 1y agotidyplotstidyplots 0.2.1
  6. 1y agoremapCitation updated to the R Journal article
  7. 1y agoremapUBSAN fix, parallel patch and sf search-path independence
  8. 1y agotidyplotstidyplots 0.2.0
  9. 1y agotidyplotstidyplots 0.1.2
  10. 3y agoremappredict() can return an upper bound on combined standard errors
  11. 5y agoremapRegions without observations no longer break the prediction surface

Frequently asked questions

What is the difference between remap and tidyplots?

They serve adjacent needs but don't currently overlap on shipped themes. remap and tidyplots 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 tidyplots?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. remap and tidyplots 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 tidyplots?

Top tidyplots alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tidyplots alternatives" section above for the current picks, or visit /alternatives/tidyplots for the full list with editorial commentary on each.