rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of etn and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
etn stopped being an RStudio-server package and became something you can run anywhere.
etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.
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.
etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.
Two arcs run in parallel: widening access, and making room for non-acoustic data. The access work has been deliberate — an API-backed beta in 2024, then a stable release that picks the transport automatically and checks that a local etnservice install matches the deployed one, because the same query returning different results by transport would be worse than requiring the server. The Darwin Core export added in 2.1.0 points the same outward direction, moving data to OBIS and GBIF instead of keeping it in the ETN silo.
The cpod scope named in the 2.0.0 notes is the most likely next addition, now that the naming and the API transport are both in place to carry it.
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 etn 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 etn alternatives → · See all tidytransit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r, open-data — within Analytics. etn 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. etn 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 etn alternatives in Analytics are ranked by recent ship velocity. Browse the "etn alternatives" section above for the current picks, or visit /alternatives/etn-r 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.