qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of CatastRoNav and gtfstools — 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.
gtfstools stopped guarding its own object model and started accepting everyone else's.
gtfstools reads, edits, filters and validates GTFS public transport feeds in R on a data.table backend. Since 1.3.0 it accepts GTFS objects produced by other packages such as gtfsio and tidytransit, converting them through an as_dt_gtfs() generic. Validation runs MobilityData's canonical validator, now supported through v6.0.0.
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.
gtfstools reads, edits, filters and validates GTFS public transport feeds in R on a data.table backend. Since 1.3.0 it accepts GTFS objects produced by other packages such as gtfsio and tidytransit, converting them through an as_dt_gtfs() generic. Validation runs MobilityData's canonical validator, now supported through v6.0.0.
The package built out a wide function surface first — filters, geometry conversion, speed and duration calculations — then turned outward. Delegating validation to MobilityData's validator and accepting other packages' objects both trade self-sufficiency for a position inside the wider GTFS ecosystem. Deprecations are handled slowly, with old behaviour left as the default for a release or more.
Expect continued validator version tracking and further completion of the deprecation cycle around filter_by_stop_id()'s full_trips behaviour.
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 gtfstools.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
See all CatastRoNav alternatives → · See all gtfstools 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 gtfstools 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 gtfstools 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 gtfstools alternatives in Analytics are ranked by recent ship velocity. Browse the "gtfstools alternatives" section above for the current picks, or visit /alternatives/gtfstools-r for the full list with editorial commentary on each.