← Back to home
Comparison · Analytics

spanishoddata vs tidytransit

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

Shared themes:open-data

spanishoddata vs tidytransit: at a glance

Featurespanishoddatatidytransit
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmobility-data, origin-destination, duckdb, open-datar, transit, gtfs, routing
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

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 →

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.

Read the full tidytransit trajectory →

spanishoddata vs tidytransit: editorial side-by-side

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.

T
tidytransit
ANALYTICS
0.0

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

See all spanishoddata alternatives → · See all tidytransit alternatives →

Recent activity from spanishoddata and tidytransit

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

  1. 2mo agospanishoddataRedirected district files identified in v1 metadata
  2. 2mo agospanishoddataS3 metadata truncation at March 2021 bypassed via XML feed
  3. 4mo agospanishoddataLiteral NA strings no longer break DuckDB casting
  4. 4mo agospanishoddataLarge urban area zones can be reloaded again
  5. 5mo agospanishoddatatime_slot column removed; test coverage goes live-weekly
  6. 6mo agotidytransitIn-seat transfers supported in raptor() and travel_times()
  7. 11mo agotidytransitstop_group_distances() no longer ignores the by parameter
  8. 1y agospanishoddataDistrict-to-municipal reaggregation corrected for 2020-2021
  9. 1y agotidytransitlocations.geojson reading; specs parsed from the GTFS reference
  10. 2y agotidytransitfare_media_id added to fare_products spec
  11. 3y agotidytransitinterpolate_stop_times() added; router updated
  12. 3y agotidytransitDuplicated primary key check improved

Frequently asked questions

What is the difference between spanishoddata and tidytransit?

Both compete on the same themes — open-data — within Analytics. spanishoddata 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 spanishoddata better than tidytransit?

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

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.