rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of tidyBdE and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
A Banco de España CSV scraper just learned to query the bank's live statistics API.
tidyBdE pulls Banco de España macroeconomic series into tidy R data frames and ships ggplot2 scales in the bank's house colors. Its whole history ran on bulk CSV downloads; 0.7.0 adds bde_series_api_latest() and bde_series_api_load() to query the bank's Statistics web service directly, with wide and long output, metadata extraction and time-range validation. The same release reached 100% line coverage.
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.
tidyBdE pulls Banco de España macroeconomic series into tidy R data frames and ships ggplot2 scales in the bank's house colors. Its whole history ran on bulk CSV downloads; 0.7.0 adds bde_series_api_latest() and bde_series_api_load() to query the bank's Statistics web service directly, with wide and long output, metadata extraction and time-range validation. The same release reached 100% line coverage.
Most releases in this feed are the package chasing Banco de España's own churn — series identifiers change upstream and the indicator wrappers get repointed. The API functions break that pattern by removing the bulk-file dependency for the first time, and the new csv_manual vignette reads like documentation of the legacy path rather than the preferred one. The maintainer is applying the same cli, roxygen2 and AI-assisted refactor pass seen across their other Spanish open-data packages.
Expect the indicator wrappers to migrate onto the API functions, which would end the recurring identifier-tracking releases; the bde_ind_db documentation already carries the API series code alongside the CSV identifiers.
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 tidyBdE 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 tidyBdE alternatives → · See all tidytransit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — open-data — within Analytics. tidyBdE 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. tidyBdE 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 tidyBdE alternatives in Analytics are ranked by recent ship velocity. Browse the "tidyBdE alternatives" section above for the current picks, or visit /alternatives/tidybde 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.