rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of lineup2 and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
lineup2 ships once every few years, and 2026's release is a logo and a core-count tweak.
lineup2 provides distance-based tools for detecting sample mix-ups between related datasets — comparing rows and columns of two matrices to find swapped or mislabeled samples. Its visible history is four releases spread across six years, and the capability surface has barely moved since plot_sample() and the propdiff distance arrived in 0.4. Version 0.8 in July 2026 adds a package logo and redefines cores=0 to mean all-but-one core.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
lineup2 provides distance-based tools for detecting sample mix-ups between related datasets — comparing rows and columns of two matrices to find swapped or mislabeled samples. Its visible history is four releases spread across six years, and the capability surface has barely moved since plot_sample() and the propdiff distance arrived in 0.4. Version 0.8 in July 2026 adds a package logo and redefines cores=0 to mean all-but-one core.
This is a finished, single-purpose package in maintenance. The substantive changes across the whole window are plotting conveniences and one parallelism default; nothing in the entries points at new distance measures, new input formats, or expanded scope. The release cadence — five years between 0.6 and 0.8 — reads as a tool the author considers done.
Further releases are likely to stay small: a plotting option, a parallelism detail, or a check-farm fix. The entries give no signal of planned feature work.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
The package has settled into tracking an external standard, which is why the changelog reads as a sequence of spec conformance items rather than a roadmap. Parsing responsibility keeps shifting outward to gtfsio, and data sources have moved with the ecosystem, from the retired transitfeeds API to MobilityData. Router changes are rarer than reader changes but land in the same releases.
Further GTFS spec features are the safest expectation, with GTFS-Flex the likeliest area now that locations.geojson reading is in place.
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 lineup2 or tidytransit.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all lineup2 alternatives → · See all tidytransit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lineup2 and tidytransit 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. lineup2 and tidytransit 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 lineup2 alternatives in Analytics are ranked by recent ship velocity. Browse the "lineup2 alternatives" section above for the current picks, or visit /alternatives/lineup2-r for the full list with editorial commentary on each.
Top tidytransit alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytransit alternatives" section above for the current picks, or visit /alternatives/tidytransit-r for the full list with editorial commentary on each.