rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
Comparison · Analytics
biocro vs CatastRo
A side-by-side editorial comparison of biocro and CatastRo — release velocity, themes, recent moves, and the top alternatives to consider.
biocro vs CatastRo: at a glance
What is biocro?
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
BioCro is a C++ crop growth simulator with an R interface, built from swappable modules for photosynthesis, respiration and development. Version 3.3.0 added multidimensional and one-dimensional root finders to the C++ source and put them to work immediately, replacing the fixed-point iteration used for intercellular CO2 with a Dekker root finder on the grounds that fixed-point iteration is known to be unstable there. Getting to that release also required moving from C++11 to C++17 and updating the bundled boost from 1.71 to 1.89.
What is CatastRo?
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.
biocro vs CatastRo: editorial side-by-side
biocro
0.0ANALYTICS
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
◆ Current state
BioCro is a C++ crop growth simulator with an R interface, built from swappable modules for photosynthesis, respiration and development. Version 3.3.0 added multidimensional and one-dimensional root finders to the C++ source and put them to work immediately, replacing the fixed-point iteration used for intercellular CO2 with a Dekker root finder on the grounds that fixed-point iteration is known to be unstable there. Getting to that release also required moving from C++11 to C++17 and updating the bundled boost from 1.71 to 1.89.
◆ Where it's heading
Two threads run together: the biology is being broken into finer interchangeable modules — separate maintenance respiration, alternative linear and logistic SLA methods, a direct development-index module — while the numerics underneath are being made solvable in general. The root finders are explicitly staged to move into the shared biocro/framework repository, so this is groundwork for other models rather than for this package alone.
◆ Prediction
More module-level alternatives that depend on simultaneous-equation solutions are the natural follow-on, and the root finders should migrate out to biocro/framework as the notes state.
CatastRo
0.0ANALYTICS
Spain's cadastre client spent 1.0.0 breaking its own cache to become a tidy, httr2-native package.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to biocro and CatastRo
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 biocro or CatastRo.
epikit
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
mutagen
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
broman
A statistician's personal toolbox, growing one plotting utility at a time
qtl
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all biocro alternatives → · See all CatastRo alternatives →
Recent activity from biocro and CatastRo
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoCatastRoAI-assisted internal refactor and cli message pass
- 3mo agoCatastRoDocumentation-only patch release
- 5mo agoCatastRo1.0.0 rebuilds on httr2 and invalidates every existing cache ⚡
- 6mo agobiocroCompiler warning blocking Linux builds fixed
- 8mo agobiocroC++ root finders added; Ci calculation moved off fixed-point iteration ⚡
- 1y agoCatastRoDocumentation and URL refresh
- 1y agobiocroMaintenance respiration module; SLA split into swappable methods
- 2y agoCatastRoCadastre service entry points updated
- 2y agobiocroFirst CRAN-accepted release after a 20 MB to 5 MB cut
- 2y agobiocroDESCRIPTION date refreshed for CRAN submission
- 2y agoCatastRohttr to httr2 migration, declared invisible to users
- 2y agobiocroCI workflow debugging tag, not a release
Frequently asked questions
What is the difference between biocro and CatastRo?
They serve adjacent needs but don't currently overlap on shipped themes. biocro and CatastRo 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.
Is biocro better than CatastRo?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. biocro and CatastRo 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.
What are the best alternatives to biocro?
Top biocro alternatives in Analytics are ranked by recent ship velocity. Browse the "biocro alternatives" section above for the current picks, or visit /alternatives/biocro-r for the full list with editorial commentary on each.
What are the best alternatives to CatastRo?
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.