tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of gtfstools and stockplotr — release velocity, themes, recent moves, and the top alternatives to consider.
gtfstools stopped guarding its own object model and started accepting everyone else's.
gtfstools reads, edits, filters and validates GTFS public transport feeds in R on a data.table backend. Since 1.3.0 it accepts GTFS objects produced by other packages such as gtfsio and tidytransit, converting them through an as_dt_gtfs() generic. Validation runs MobilityData's canonical validator, now supported through v6.0.0.
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.
gtfstools reads, edits, filters and validates GTFS public transport feeds in R on a data.table backend. Since 1.3.0 it accepts GTFS objects produced by other packages such as gtfsio and tidytransit, converting them through an as_dt_gtfs() generic. Validation runs MobilityData's canonical validator, now supported through v6.0.0.
The package built out a wide function surface first — filters, geometry conversion, speed and duration calculations — then turned outward. Delegating validation to MobilityData's validator and accepting other packages' objects both trade self-sufficiency for a position inside the wider GTFS ecosystem. Deprecations are handled slowly, with old behaviour left as the default for a release or more.
Expect continued validator version tracking and further completion of the deprecation cycle around filter_by_stop_id()'s full_trips behaviour.
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.
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 gtfstools or stockplotr.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
The glue package that makes R carry units and uncertainty through the same calculation.
A fish diet package whose release history is really a record of surviving rfishbase.
See all gtfstools alternatives → · See all stockplotr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gtfstools and stockplotr 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. gtfstools and stockplotr 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 gtfstools alternatives in Analytics are ranked by recent ship velocity. Browse the "gtfstools alternatives" section above for the current picks, or visit /alternatives/gtfstools-r for the full list with editorial commentary on each.
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.