OpenRepGrid
Repertory grids learn which pole is the preferred one — a data-model change, not another plot option.
A side-by-side editorial comparison of ipeaplot and trackeR — release velocity, themes, recent moves, and the top alternatives to consider.
An institutional chart theme whose recent releases are all vignette repair.
ipeaplot supplies Ipea's house style to ggplot2 — theme_ipea(), matching colour and fill scales, and export helpers that write the formats the institute's publications need. The feature line has been quiet since October, when save_ipeaplot() consolidated the format-specific savers. Both July releases exist to get the package building again, not to change it.
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
trackeR reads GPS and fitness-tracker files in TCX, GPX and JSON form and turns them into session data, distribution and concentration profiles, and route plots. Feature work concentrated in the 1.5 series in 2019; the two releases since are corrective. The latest swaps the plot layout dependencies for patchwork and fixes plot_route() returning nothing.
ipeaplot supplies Ipea's house style to ggplot2 — theme_ipea(), matching colour and fill scales, and export helpers that write the formats the institute's publications need. The feature line has been quiet since October, when save_ipeaplot() consolidated the format-specific savers. Both July releases exist to get the package building again, not to change it.
The package has been converging on a smaller, more uniform surface: separate save_eps() and save_pdf() helpers gave way to one save_ipeaplot() covering vector and raster formats with sensible defaults, and the Frutiger font dependency was dropped for a default sans-serif. What consumes releases now is downstream breakage — two consecutive patches in ten days, the second traced to geobr, both in vignettes rather than package code.
The palette line has grown one colour set at a time and is the most likely place for the next addition, but nothing in these entries commits to it. On current evidence the near term is more compatibility patching against the geobr and ggplot2 packages the vignettes depend on.
trackeR reads GPS and fitness-tracker files in TCX, GPX and JSON form and turns them into session data, distribution and concentration profiles, and route plots. Feature work concentrated in the 1.5 series in 2019; the two releases since are corrective. The latest swaps the plot layout dependencies for patchwork and fixes plot_route() returning nothing.
Recent releases track other people's changes: ggmap moving to Stadia maps, gridExtra giving way to patchwork, a cadence field being read into the wrong column. The 2019 entries are where the analysis surface was built out, with cumulative elevation gain, compressed file reading and elevation-noise thresholds, and it has not moved much since.
Expect the next release to be another compatibility or parsing fix rather than a new metric.
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 ipeaplot or trackeR.
Repertory grids learn which pole is the preferred one — a data-model change, not another plot option.
A categorical-variable selection package that publishes its full test logs as release candidates.
A dormant sample-size package woke up in 2025 with parallel backends and a three-release DOI farce.
A niche R package for author bylines that keeps sanding down the edges of academic metadata.
The REDCap API client finished its breaking cleanup and settled into CRAN-compliance mode.
The protist reference database keeps widening past the rRNA gene it was built on.
See all ipeaplot alternatives → · See all trackeR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ipeaplot and trackeR 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. ipeaplot and trackeR 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 ipeaplot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ipeaplot alternatives" section above for the current picks, or visit /alternatives/ipeaplot for the full list with editorial commentary on each.
Top trackeR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "trackeR alternatives" section above for the current picks, or visit /alternatives/tracker for the full list with editorial commentary on each.