rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of stockplotr and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
A stock-assessment plotting package is growing a table engine to match its figures.
stockplotr generates the figures and, since 0.8.0-beta, the tables that go into NOAA fisheries stock assessment reports. The 0.8.0 release swapped the table backend from flextable to gt and shipped table_landings() as the first table function; 0.9.0 exported it with an interface deliberately mirroring the plot functions. Alongside that, convert_output() moved in from the sister package asar so model output is standardized here rather than upstream.
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.
stockplotr generates the figures and, since 0.8.0-beta, the tables that go into NOAA fisheries stock assessment reports. The 0.8.0 release swapped the table backend from flextable to gt and shipped table_landings() as the first table function; 0.9.0 exported it with an interface deliberately mirroring the plot functions. Alongside that, convert_output() moved in from the sister package asar so model output is standardized here rather than upstream.
The package is consolidating the whole report-artifact pipeline in one place: standardize model output, then emit both figures and tables from the same long-format frame. Pulling convert_output() out of asar because stockplotr depended on it more heavily is the clearest signal of where the center of gravity now sits. Everything is still tagged beta, and the plot function count is growing faster than the table one.
More table_* functions built on the gt foundation are the obvious next step, matching the existing plot_* set; the 0.9.0 notes describe table_landings() as the first of a revamped family rather than a one-off.
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 stockplotr 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 stockplotr alternatives → · See all tidytransit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. stockplotr 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. stockplotr 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 stockplotr alternatives in Analytics are ranked by recent ship velocity. Browse the "stockplotr alternatives" section above for the current picks, or visit /alternatives/stockplotr-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.