← Back to home
Comparison · Analytics

ardlverse vs spanishoddata

A side-by-side editorial comparison of ardlverse and spanishoddata — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

ardlverse vs spanishoddata: at a glance

Featureardlversespanishoddata
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeseconometrics, panel-data, ardl, r-packagemobility-data, origin-destination, duckdb, open-data
Last editorial update48m ago1h ago
WebsiteVisit →Visit →

What is ardlverse?

An outside audit against Stata found seven errors in ardlverse's panel estimator, including regressions with no intercept.

A small R package for autoregressive distributed lag models, with only three releases on record. The first two were administrative — a CRAN version note and a Zenodo metadata update. The third, 2.0.0, is a correction release built entirely from an external audit of panel_ardl() against Stata's xtpmg, and it is the only entry here with substantive content.

Read the full ardlverse trajectory →

What is spanishoddata?

spanishoddata spent a year finding out its 2020-2021 data was quietly incomplete.

spanishoddata provides access to Spain's open mobility origin-destination datasets from the Ministry of Transport, converting them into DuckDB and parquet for analysis at scale. Nearly every release in this window is a data-fidelity fix rather than a feature: district-to-municipal reaggregation was wrong for the 2020-2021 vintage, literal 'NA' strings in the source CSVs broke DuckDB enum casting, and the Amazon S3 metadata bucket turned out to be truncated at March 2021, silently hiding data.

Read the full spanishoddata trajectory →

ardlverse vs spanishoddata: editorial side-by-side

A
ardlverse
ANALYTICS
0.0

An outside audit against Stata found seven errors in ardlverse's panel estimator, including regressions with no intercept.

◆ Current state

A small R package for autoregressive distributed lag models, with only three releases on record. The first two were administrative — a CRAN version note and a Zenodo metadata update. The third, 2.0.0, is a correction release built entirely from an external audit of panel_ardl() against Stata's xtpmg, and it is the only entry here with substantive content.

◆ Where it's heading

The package's direction is now set by verification against an established reference implementation rather than by feature work. The seven fixes bring panel_ardl() into strict alignment with the original Pesaran, Shin and Smith framework, and the most serious of them is structural: internal regressions used lm.fit(), which unlike lm() does not append an intercept, so every short-run regression across the PMG, MG and DFE estimators was forced through the origin. Design matrices now carry a column of ones and DFE reconstructs the grand-mean intercept to match standard fixed-effects output.

◆ Prediction

Expect the next releases to extend the same audit approach to the remaining estimators, since a package that has been validated against xtpmg on one function invites the same question about the rest.

S
spanishoddata
ANALYTICS
0.0

spanishoddata spent a year finding out its 2020-2021 data was quietly incomplete.

◆ Current state

spanishoddata provides access to Spain's open mobility origin-destination datasets from the Ministry of Transport, converting them into DuckDB and parquet for analysis at scale. Nearly every release in this window is a data-fidelity fix rather than a feature: district-to-municipal reaggregation was wrong for the 2020-2021 vintage, literal 'NA' strings in the source CSVs broke DuckDB enum casting, and the Amazon S3 metadata bucket turned out to be truncated at March 2021, silently hiding data.

◆ Where it's heading

The package is in a trust-building phase. The pattern across 0.2.1 through 0.2.6 is the maintainers repeatedly discovering that upstream metadata and the package's own aggregation were misrepresenting what data existed, then fixing it and adding a check so it surfaces next time. That is now backed by infrastructure: comprehensive unit tests plus weekly live-data runs on GitHub workers that alert maintainers when the upstream ministry changes something. The last feature release sits outside the six-entry window, which is itself the story.

◆ Prediction

Expect continued upstream-tracking fixes as the ministry's API and S3 layout shift, with the experimental quick-access and checksum functions the most likely candidates for promotion to stable.

Alternatives to ardlverse and spanishoddata

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 ardlverse or spanishoddata.

See all ardlverse alternatives → · See all spanishoddata alternatives →

Recent activity from ardlverse and spanishoddata

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoardlverseSeven panel_ardl fixes after an audit against Stata's xtpmg
  2. 2mo agospanishoddataRedirected district files identified in v1 metadata
  3. 2mo agospanishoddataS3 metadata truncation at March 2021 bypassed via XML feed
  4. 4mo agospanishoddataLiteral NA strings no longer break DuckDB casting
  5. 4mo agospanishoddataLarge urban area zones can be reloaded again
  6. 5mo agoardlverseZenodo metadata updated with ORCID
  7. 5mo agoardlverseardlverse v1.1.3
  8. 5mo agospanishoddatatime_slot column removed; test coverage goes live-weekly
  9. 1y agospanishoddataDistrict-to-municipal reaggregation corrected for 2020-2021

Frequently asked questions

What is the difference between ardlverse and spanishoddata?

Both compete on the same themes — r-package — within Analytics. ardlverse and spanishoddata 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 ardlverse better than spanishoddata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ardlverse and spanishoddata 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 ardlverse?

Top ardlverse alternatives in Analytics are ranked by recent ship velocity. Browse the "ardlverse alternatives" section above for the current picks, or visit /alternatives/ardlverse-r for the full list with editorial commentary on each.

What are the best alternatives to spanishoddata?

Top spanishoddata alternatives in Analytics are ranked by recent ship velocity. Browse the "spanishoddata alternatives" section above for the current picks, or visit /alternatives/spanishoddata for the full list with editorial commentary on each.