rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of dggridR and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
A discrete global grid generator grew cell traversal and became a usable spatial index.
dggridR builds discrete global grids — icosahedral tessellations of the Earth into equal-area hexagonal or triangular cells — by wrapping the DGGRID C++ engine. The 4.1.0 release adds dgneighbors, dgchildren and dgparent for moving between adjacent cells and across resolutions, plus dgpoints_to_cells and dgbin_points for mapping and aggregating point data into cells. New aperture 7 and mixed-aperture ISEA43H grid types arrive alongside them.
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.
dggridR builds discrete global grids — icosahedral tessellations of the Earth into equal-area hexagonal or triangular cells — by wrapping the DGGRID C++ engine. The 4.1.0 release adds dgneighbors, dgchildren and dgparent for moving between adjacent cells and across resolutions, plus dgpoints_to_cells and dgbin_points for mapping and aggregating point data into cells. New aperture 7 and mixed-aperture ISEA43H grid types arrive alongside them.
The package changed hands in effect as well as in code: the 4.0.0 engine update to DGGRID v9.0b and the first real test suite were contributed by Sebastian Krantz, who also maintains the upstream engine fork, and 4.1.0's feature burst followed two weeks later. The direction of that burst is unmistakable — away from generating grids for plotting and toward using them as an indexing structure that point data gets binned into and navigated through.
Expect the cell hierarchy functions to extend to non-hexagonal apertures and multi-level traversal, closing the remaining gaps against established global indexing systems.
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 dggridR 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 dggridR 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. dggridR 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. dggridR 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 dggridR alternatives in Analytics are ranked by recent ship velocity. Browse the "dggridR alternatives" section above for the current picks, or visit /alternatives/dggridr 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.