n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of CatastRo and rncl — release velocity, themes, recent moves, and the top alternatives to consider.
Spain's cadastre client spent 1.0.0 breaking its own cache to become a tidy, httr2-native package.
CatastRo pulls parcels, buildings, addresses and WMS map layers from the Spanish Cadastre into R. The 1.0.0 line rebuilt the codebase on httr2, reorganized the cache into topic-based subfolders and moved persistent storage from rappdirs to tools::R_user_dir(), a change that invalidates every pre-1.0.0 cache. The two releases since are documentation and an AI-assisted internal refactor.
A phylogenetics parser on life support, shipping only what CRAN's compilers demand.
rncl wraps the Nexus Class Library so R can read Newick and NEXUS tree files. Every release since 2016 has been custodial: 0.8.9 exists solely to pull upstream NCL changes so the bundled C++ compiles under the C++20 standard. No user-facing function has changed in close to a decade.
CatastRo pulls parcels, buildings, addresses and WMS map layers from the Spanish Cadastre into R. The 1.0.0 line rebuilt the codebase on httr2, reorganized the cache into topic-based subfolders and moved persistent storage from rappdirs to tools::R_user_dir(), a change that invalidates every pre-1.0.0 cache. The two releases since are documentation and an AI-assisted internal refactor.
The arc is consolidation, not expansion: the retrieval surface has been stable since 0.3.0 added street names to addresses, while the maintainer has spent the releases since standardizing transport, output types and messaging. All functions now return tibbles or sf objects with tibble data, and cli handles user-facing output. The same modernization is being applied across the maintainer's other Spanish-data packages.
Expect the next releases to stay in the 1.0.x patch range — documentation, cli wording and CRAN upkeep — unless the Cadastre publishes a new service worth wrapping.
rncl wraps the Nexus Class Library so R can read Newick and NEXUS tree files. Every release since 2016 has been custodial: 0.8.9 exists solely to pull upstream NCL changes so the bundled C++ compiles under the C++20 standard. No user-facing function has changed in close to a decade.
The release cadence tracks toolchain deprecations rather than user demand: gcc 12 removing binary_function in 2022, a deprecated Rcpp call in 2025, C++20 in 2026. The package is maintained as a stable parsing dependency for phylogenetics tooling, and the goal visible in these entries is keeping it installable, not extending it.
Expect the next release only when a compiler or CRAN policy change breaks the build again; nothing in these entries points to new parsing features.
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 CatastRo or rncl.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
collapse got a JSS paper and a 7x fmean speedup in the same release.
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
broadcast is filling in NumPy-style array broadcasting for R, operator by operator.
See all CatastRo alternatives → · See all rncl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rncl is currently shipping more aggressively (velocity 2.5 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rncl is currently shipping more aggressively (velocity 2.5 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.
Top CatastRo alternatives in Analytics are ranked by recent ship velocity. Browse the "CatastRo alternatives" section above for the current picks, or visit /alternatives/catastro for the full list with editorial commentary on each.
Top rncl alternatives in Analytics are ranked by recent ship velocity. Browse the "rncl alternatives" section above for the current picks, or visit /alternatives/rncl-r for the full list with editorial commentary on each.