← Back to home
Comparison · Analytics

hdnom vs tidytransit

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

Shared themes:r

hdnom vs tidytransit: at a glance

Featurehdnomtidytransit
SectorAnalyticsAnalytics
Velocity score5.00.0
Sparks · 30d00
Top themessurvival analysis, r, regularization, nomogramsr, transit, gtfs, routing
Last editorial update6h ago1h ago
WebsiteVisit →Visit →

What is hdnom?

hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to

hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.

Read the full hdnom 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 →

hdnom vs tidytransit: editorial side-by-side

H
hdnom
ANALYTICS
5.0

hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to

◆ Current state

hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.

◆ Where it's heading

The releases track two upstream pressures with no feature work of its own. glmnet is the larger one: its 4.1-9 change to how Cox cross-validation errors are normalized made lambda.1se select null models far more often, forcing hdnom to expose a rule argument and switch its examples to lambda.min. R-devel is the other, producing a steady trickle of strict-headers, deprecated-symbol and check-note fixes. The pattern is consistent — absorb the upstream change, default to whatever preserves existing behaviour, let users opt into the new one.

◆ Prediction

The cox.ties default is explicitly pinned to "breslow" to silence glmnet's migration warning, which is a deferral rather than a decision; expect a future release to flip that default to "efron" once glmnet completes the transition.

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

See all hdnom alternatives → · See all tidytransit alternatives →

Recent activity from hdnom and tidytransit

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

  1. 18d agohdnomhdnom 6.2.1
  2. 18d agohdnomhdnom 6.2.0 pins Cox tie handling ahead of glmnet's migration
  3. 6mo agotidytransitIn-seat transfers supported in raptor() and travel_times()
  4. 11mo agotidytransitstop_group_distances() no longer ignores the by parameter
  5. 1y agohdnomhdnom 6.1.0 exposes lambda selection after a glmnet normalization change
  6. 1y agotidytransitlocations.geojson reading; specs parsed from the GTFS reference
  7. 1y agohdnomhdnom 6.0.4
  8. 2y agohdnomhdnom 6.0.3
  9. 2y agotidytransitfare_media_id added to fare_products spec
  10. 3y agotidytransitinterpolate_stop_times() added; router updated
  11. 3y agotidytransitDuplicated primary key check improved
  12. 3y agohdnomhdnom 6.0.2

Frequently asked questions

What is the difference between hdnom and tidytransit?

Both compete on the same themes — r — within Analytics. hdnom is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is hdnom better than tidytransit?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hdnom is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to hdnom?

Top hdnom alternatives in Analytics are ranked by recent ship velocity. Browse the "hdnom alternatives" section above for the current picks, or visit /alternatives/hdnom 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.