rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of tidytransit and tmap — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Two years after a from-scratch rewrite, tmap is filling in the layers v4 promised.
tmap draws thematic maps in R across static and interactive modes. The 4.0 rewrite replaced the layer syntax with explicit visual variables, scales, legends and charts, and opened the package to extensions; the 4.x line since has been steady capability fill-in. The 4.4 release adds tm_circles with fixed unit-based radii, a blend argument on every layer, and hitboxes so small objects stay clickable in view mode.
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.
tmap draws thematic maps in R across static and interactive modes. The 4.0 rewrite replaced the layer syntax with explicit visual variables, scales, legends and charts, and opened the package to extensions; the 4.x line since has been steady capability fill-in. The 4.4 release adds tm_circles with fixed unit-based radii, a blend argument on every layer, and hitboxes so small objects stay clickable in view mode.
The extension mechanism introduced in 4.0 is where the interesting work is migrating: PMTiles support arrived through a separate experimental tmap.sources package, mode cycling became configurable via tmap_mode_pool() so packages like tmap.mapgl can register themselves, and shiny dispatch methods were added specifically to let other modes integrate. The core package is increasingly a rendering contract that satellite packages plug into.
Expect more rendering backends to land as sibling packages rather than in tmap itself, with the core continuing to absorb the dispatch and mode-management plumbing they need.
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 tidytransit or tmap.
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 tidytransit alternatives → · See all tmap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. tidytransit and tmap 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. tidytransit and tmap 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 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.
Top tmap alternatives in Analytics are ranked by recent ship velocity. Browse the "tmap alternatives" section above for the current picks, or visit /alternatives/tmap-r for the full list with editorial commentary on each.