qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of dggridR and gtfstools — 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.
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.
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.
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.
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 gtfstools.
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 dggridR alternatives → · See all gtfstools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — geospatial — within Analytics. dggridR and gtfstools 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 gtfstools 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 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.