rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
Comparison · Analytics
biocro vs CatastRoNav
A side-by-side editorial comparison of biocro and CatastRoNav — release velocity, themes, recent moves, and the top alternatives to consider.
biocro vs CatastRoNav: 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 CatastRoNav?
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.
biocro vs CatastRoNav: 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.
CatastRoNav
0.0ANALYTICS
Navarre's cadastre client finally reaches feature parity with its bigger Spanish sibling.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect the next releases to track new Navarre service endpoints as they are published, and to inherit whatever maintenance pattern CatastRo adopts next.
Alternatives to biocro and CatastRoNav
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 CatastRoNav.
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 CatastRoNav alternatives →
Recent activity from biocro and CatastRoNav
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoCatastRoNavBuildings, addresses and WMS layers arrive in 1.0.0 ⚡
- 6mo agobiocroCompiler warning blocking Linux builds fixed
- 8mo agobiocroC++ root finders added; Ci calculation moved off fixed-point iteration ⚡
- 1y agobiocroMaintenance respiration module; SLA split into swappable methods
- 2y agoCatastRoNavATOM parcel retrieval and a caching system
- 2y agobiocroFirst CRAN-accepted release after a 20 MB to 5 MB cut
- 2y agobiocroDESCRIPTION date refreshed for CRAN submission
- 2y agobiocroCI workflow debugging tag, not a release
- 3y agoCatastRoNavGeometry validity fix for returned sf objects
- 3y agoCatastRoNavFirst release opens the Navarre cadastre to R
Frequently asked questions
What is the difference between biocro and CatastRoNav?
They serve adjacent needs but don't currently overlap on shipped themes. biocro and CatastRoNav 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 CatastRoNav?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. biocro and CatastRoNav 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 CatastRoNav?
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.