fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of bbk and rdataone — release velocity, themes, recent moves, and the top alternatives to consider.
One R interface is absorbing the world's central bank data portals, one API at a time.
bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.
The R client for DataONE ships slow, correctness-focused maintenance
rdataone is the R client for the DataONE federated research-data network, handling authentication, upload and retrieval of data packages against member nodes. Recent work is concentrated on correctness in the upload path — rightsHolder persistence, public-read flags applied across all objects in a package, and edge cases in archive() — plus dependency trimming. The feed's version stamps are unreliable: 2.2.2 carries a later publication date than 2.3.0, which cites 2.2.2 as its own predecessor.
bbk began as a Bundesbank client and has become a single R interface to central bank statistics generally: the ECB, BIS, and the national banks of Switzerland, Canada, the UK, France, Spain, Austria, Sweden, Norway, Portugal, Japan, Poland, the Czech Republic, and now Brazil and Mexico. Each provider gets a consistent set of verbs — a data function, a dimension function for the dataflow structure, and provider-specific extras like PRIBOR or CZEONIA fixings. Response caching, data.table returns, and an updated_after argument for incremental retrieval are shared plumbing rather than per-provider features.
The expansion is steady and the integration work is what makes it more than a list of wrappers: arguments introduced for one provider get pushed to the others, dimension introspection is being generalised across dataflows, and the bug fixes in recent releases are almost all about the same class of problem — series with missing observations, unsupported frequency codes, or date/value misalignment breaking a parser written for a tidier feed. The maintainer ships the same infrastructure across their packages in lockstep; bbk 0.9.0 and the sibling treasury package's 0.5.0 landed identical opt-in caching within minutes of each other. Geography is the visible frontier, but consistency across an increasingly ragged set of upstream APIs is the actual work.
Expect more national central banks to be added on the same template, and the newer providers to be retrofitted with the dimension and updated_after functions the older ones already have.
rdataone is the R client for the DataONE federated research-data network, handling authentication, upload and retrieval of data packages against member nodes. Recent work is concentrated on correctness in the upload path — rightsHolder persistence, public-read flags applied across all objects in a package, and edge cases in archive() — plus dependency trimming. The feed's version stamps are unreliable: 2.2.2 carries a later publication date than 2.3.0, which cites 2.2.2 as its own predecessor.
This is long-cycle infrastructure maintenance, not feature development. Release intervals run to years, and the content is dominated by access-control correctness, CRAN compliance and TLS/platform fixes rather than new client capability. The one consistent thread is hardening how permissions and checksums survive a round trip to a member node.
Expect continued low-frequency releases driven by CRAN check failures and platform TLS changes, with any functional work staying in the upload and permissions path rather than the query surface.
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 bbk or rdataone.
Pattern fills for ggplot2, hardened against the ways users write sizes
gcube's recent releases are all packaging metadata, not simulation code
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
See all bbk alternatives → · See all rdataone alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. bbk and rdataone 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. bbk and rdataone 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 bbk alternatives in Analytics are ranked by recent ship velocity. Browse the "bbk alternatives" section above for the current picks, or visit /alternatives/bbk for the full list with editorial commentary on each.
Top rdataone alternatives in Analytics are ranked by recent ship velocity. Browse the "rdataone alternatives" section above for the current picks, or visit /alternatives/rdataone for the full list with editorial commentary on each.