rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of deeptime and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
A geologic-time plotting layer that outgrew time axes and became a geology rendering toolkit.
deeptime extends ggplot2 with geological time scales, radial deep-time coordinates and phylogeny-aware geoms, and since 2.0.0 it also renders standardized FGDC/USGS geologic patterns as ggplot2 fills. The current 2.4.0 release adds geom_text_clade() for labeling clades on radial phylogenies and repairs long-standing coord_trans_xy() and scale-placement edge cases.
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.
deeptime extends ggplot2 with geological time scales, radial deep-time coordinates and phylogeny-aware geoms, and since 2.0.0 it also renders standardized FGDC/USGS geologic patterns as ggplot2 fills. The current 2.4.0 release adds geom_text_clade() for labeling clades on radial phylogenies and repairs long-standing coord_trans_xy() and scale-placement edge cases.
The package is converging on two jobs: being the canonical R renderer for stratigraphic drawing conventions, and keeping pace with ggplot2's own churn. A sustained deprecation program — gggeo_scale(), coord_geo_polar(), getScaleData(), now disparity_through_time() — is trimming the surface down to coord_geo(), coord_geo_radial() and the pattern functions. Roughly half of each recent release is ggplot2 4.0 compatibility work.
Expect disparity_through_time() and coord_geo_polar() to be removed outright in the next major version, and further geoms aimed at annotating radial phylogenies.
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 deeptime 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 deeptime 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. deeptime 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. deeptime 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 deeptime alternatives in Analytics are ranked by recent ship velocity. Browse the "deeptime alternatives" section above for the current picks, or visit /alternatives/deeptime-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.