rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of CatastRoNav and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
Navarre's cadastre client finally reaches feature parity with its bigger Spanish sibling.
CatastRoNav wraps the Cadastre of Navarre, a Spanish region that publishes its own cadastral services separately from the national system. Until 1.0.0 the package could only fetch cadastral parcels via ATOM; it now retrieves buildings and addresses through ATOM as well and adds WMS INSPIRE layer access through catrnav_wms_get_layer(). The same release relicenses to GPL-2, moves requests to httr2 with retries and switches messaging to cli.
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.
CatastRoNav wraps the Cadastre of Navarre, a Spanish region that publishes its own cadastral services separately from the national system. Until 1.0.0 the package could only fetch cadastral parcels via ATOM; it now retrieves buildings and addresses through ATOM as well and adds WMS INSPIRE layer access through catrnav_wms_get_layer(). The same release relicenses to GPL-2, moves requests to httr2 with retries and switches messaging to cli.
The package is being pulled into line with CatastRo, the maintainer's national-cadastre client: same transport, same UTF-8 normalization strategy, same option names falling back to the CatastRo equivalents. Coverage has been gated by what the Navarre Cadastre actually publishes — 0.1.0 said outright that further ATOM capabilities would arrive when the regional service made them available, and 1.0.0 is that promise landing.
Expect the next releases to track new Navarre service endpoints as they are published, and to inherit whatever maintenance pattern CatastRo adopts next.
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 CatastRoNav 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 CatastRoNav alternatives → · See all tidytransit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CatastRoNav 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. CatastRoNav 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 CatastRoNav alternatives in Analytics are ranked by recent ship velocity. Browse the "CatastRoNav alternatives" section above for the current picks, or visit /alternatives/catastronav 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.