n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of CatastRo and stringi — 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.
stringi has spent two years on build hardening since its Unicode 15.1 reset.
stringi is the ICU-backed string engine under a large share of R's text handling. Since the 1.8.1 reset in late 2023 — which bundled ICU 74.1, dropped Solaris, and raised the compiler floor — every subsequent release has been build and portability maintenance: PROTECT-stack fixes, Windows build errors, compiler warnings. The 1.8.8 release in July 2026 continues that pattern by dropping the configure script's C++11 fallback.
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.
stringi is the ICU-backed string engine under a large share of R's text handling. Since the 1.8.1 reset in late 2023 — which bundled ICU 74.1, dropped Solaris, and raised the compiler floor — every subsequent release has been build and portability maintenance: PROTECT-stack fixes, Windows build errors, compiler warnings. The 1.8.8 release in July 2026 continues that pattern by dropping the configure script's C++11 fallback.
The package has reached feature stability and is maintained as infrastructure. Releases arrive when a toolchain, platform, or check regime changes, not when users ask for capability. The two-and-a-half year gap between 1.8.1's Unicode bump and anything comparable suggests the next directional move will again be an ICU bundle refresh rather than new API surface.
The next release is most likely another build-time fix or an ICU bundle update to a newer Unicode version; the entries show no in-progress feature work.
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 stringi.
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 stringi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. stringi 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. stringi 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 stringi alternatives in Analytics are ranked by recent ship velocity. Browse the "stringi alternatives" section above for the current picks, or visit /alternatives/stringi-r for the full list with editorial commentary on each.