qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of gtfstools and tidypolars — 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.
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
tidypolars lets you write dplyr and tidyr syntax against Polars DataFrames and LazyFrames. Its releases follow a fixed shape: raise the required polars version, add a handful of newly supported R functions and arguments, fix places where behaviour diverges from dplyr. Recent additions run from %notin% and as.integer() to .before/.after in mutate() and time zone handling in datetime parsing. Cadence is roughly every six to ten weeks and has not varied.
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.
tidypolars lets you write dplyr and tidyr syntax against Polars DataFrames and LazyFrames. Its releases follow a fixed shape: raise the required polars version, add a handful of newly supported R functions and arguments, fix places where behaviour diverges from dplyr. Recent additions run from %notin% and as.integer() to .before/.after in mutate() and time zone handling in datetime parsing. Cadence is roughly every six to ten weeks and has not varied.
Coverage is the whole strategy, and the target has been widening from dplyr into tidyr — unnest_longer_polars(), separate_longer_delim_polars() and separate_longer_position_polars() bring list-column and string-splitting verbs that have no Polars-idiomatic equivalent in the tidyverse dialect. The other consistent thread is fidelity: distinct() dropping unselected columns, summarize() dropping the last group, relocate() honouring tidy-select helpers, NULL in mutate() behaving as dplyr does. Each of these is a small breaking change made to match the reference rather than to differ from it.
The pattern of tracking the polars floor upward every release and following tidyverse changes closely — .by in fill() arrived when tidyr 1.3.2 shipped it — suggests the next releases continue mirroring new dplyr and tidyr arguments rather than adding a distinct capability.
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 tidypolars.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
See all gtfstools alternatives → · See all tidypolars 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 tidypolars 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 tidypolars 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 tidypolars alternatives in Analytics are ranked by recent ship velocity. Browse the "tidypolars alternatives" section above for the current picks, or visit /alternatives/tidypolars for the full list with editorial commentary on each.