qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
Comparison · Analytics
ggdemetra vs tidytransit
A side-by-side editorial comparison of ggdemetra and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
ggdemetra vs tidytransit: at a glance
What is ggdemetra?
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
What is tidytransit?
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.
ggdemetra vs tidytransit: editorial side-by-side
ggdemetra
0.0ANALYTICS
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
◆ Current state
ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.
◆ Where it's heading
The package has been steadily completing its coverage of the seasonal adjustment output surface: component extractors and autoplot methods in 0.2.3, SI ratio plotting in 0.2.5, then two releases of corrections to make SI ratios behave under TRAMO-SEATS jSA models and when no seasonal component is exported. Alongside that, the naming is being tidied — y_forecast() became raw(), and init_ggplot() shortened the setup boilerplate. This reads as a package approaching the edge of its intended scope and spending its effort on correctness.
◆ Prediction
Two consecutive releases fixing SI ratios under TRAMO-SEATS suggest that code path is the least settled part of the package, so further corrections there are the most likely next move. The entries give no indication of new model families or plot types being planned.
tidytransit
0.0ANALYTICS
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Further GTFS spec features are the safest expectation, with GTFS-Flex the likeliest area now that locations.geojson reading is in place.
Alternatives to ggdemetra and tidytransit
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 ggdemetra or tidytransit.
constants
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
austraits
The R client for AusTraits spends its releases chasing the dataset it reads.
fossilsim
A fossil-record simulator that quietly grew a trait-evolution engine.
tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
tern.mmrm
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all ggdemetra alternatives → · See all tidytransit alternatives →
Recent activity from ggdemetra and tidytransit
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agotidytransitIn-seat transfers supported in raptor() and travel_times()
- 11mo agotidytransitstop_group_distances() no longer ignores the by parameter
- 1y agotidytransitlocations.geojson reading; specs parsed from the GTFS reference
- 2y agoggdemetrasiratio() fix when TRAMO-SEATS exports no seasonal component
- 2y agoggdemetraraw() replaces y_forecast(); new init_ggplot() helper
- 2y agoggdemetraRe-tagged moments later as 0.2.7
- 2y agotidytransitfare_media_id added to fare_products spec
- 3y agotidytransitinterpolate_stop_times() added; router updated
- 3y agotidytransitDuplicated primary key check improved
- 3y agoggdemetraSI ratio plotting functions land
- 5y agoggdemetrats2df() conversion helper and geom_outlier date fix
- 6y agoggdemetrageom_arima no longer recomputes the model
Frequently asked questions
What is the difference between ggdemetra and tidytransit?
They serve adjacent needs but don't currently overlap on shipped themes. ggdemetra 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.
Is ggdemetra better than tidytransit?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggdemetra 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.
What are the best alternatives to ggdemetra?
Top ggdemetra alternatives in Analytics are ranked by recent ship velocity. Browse the "ggdemetra alternatives" section above for the current picks, or visit /alternatives/ggdemetra for the full list with editorial commentary on each.
What are the best alternatives to tidytransit?
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.