qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of gtfstools and watina — 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 groundwater database client that has started doing the domain analysis too
watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.
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.
watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.
The package is drifting from a database client toward a domain toolkit. Early releases fought the data layer — connection handling moved to inbodb, sorting semantics changed, defunct dbplyr calls worked around. Recent work assumes retrieval is solved and adds hydrochemical analysis on top, along with defensive handling for the physically impossible inputs that analysis exposes, such as zero conductivity in the warehouse.
Expect further chemistry analysis and plotting helpers rather than new retrieval functions, since that is where the newest release invested and where the accompanying vignette points.
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 watina.
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 watina alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. gtfstools and watina 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 watina 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 watina alternatives in Analytics are ranked by recent ship velocity. Browse the "watina alternatives" section above for the current picks, or visit /alternatives/watina-r for the full list with editorial commentary on each.