bittermelon
bittermelon is growing from binary bitmaps toward greyscale and color glyphs
Comparison · Analytics
ageproR vs CatastRo
A side-by-side editorial comparison of ageproR and CatastRo — release velocity, themes, recent moves, and the top alternatives to consider.
ageproR vs CatastRo: at a glance
What is ageproR?
ageproR spent two years chasing a moving file format, then added the recruitment models that justify the effort.
An R interface for building and validating AGEPRO input files — the configuration format for a fisheries stock projection program used in stock assessments. Releases come every few months and are dominated by one recurring problem: keeping up with the AGEPRO input file format, which has moved between VERSION 4.0 and VERSION 4.25 in both directions across this window. The package spends considerable effort on validation, version detection, and clear error messages when a file does not match.
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.
ageproR vs CatastRo: editorial side-by-side
ageproR
0.0ANALYTICS
ageproR spent two years chasing a moving file format, then added the recruitment models that justify the effort.
◆ Current state
An R interface for building and validating AGEPRO input files — the configuration format for a fisheries stock projection program used in stock assessments. Releases come every few months and are dominated by one recurring problem: keeping up with the AGEPRO input file format, which has moved between VERSION 4.0 and VERSION 4.25 in both directions across this window. The package spends considerable effort on validation, version detection, and clear error messages when a file does not match.
◆ Where it's heading
The version-format churn is settling. Release 0.7.1 reverted the default back to VERSION 4.0 as a bugfix, and 0.9.0 finally set 4.25 as current while retaining a 4.0 compatibility string and improving the detection messages — a resolution rather than another reversal. With that stabilising, the substantive work has been the recruitment model coverage added in 0.8.0, which brought autocorrelated lognormal error structures into the package for the first time. Naming has been converging too, with output_stock_summary and summary_output_flag renamed to auxiliary variants to match the AGEPRO-GUI specification.
◆ Prediction
Expect the remaining recruitment models to be filled in against the AGEPRO specification, and the version handling to stay on 4.25 now that both formats are supported and validated rather than swapped.
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 ageproR 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 ageproR or CatastRo.
epiworldR
epiworldR is a thin R shell whose releases track the C++ simulator underneath it
watina
A groundwater database client that has started doing the domain analysis too
inbospatial
A thin R wrapper over Flemish geospatial services, adding one standard at a time
Fluent Bit
Fluent Bit keeps two lines alive while the 5.x branch quietly opens 5.1.
OpenCTI
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
See all ageproR alternatives → · See all CatastRo alternatives →
Recent activity from ageproR and CatastRo
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoCatastRoAI-assisted internal refactor and cli message pass
- 2mo agoageproRwrite_inp option flag detection fixed after 0.8.0 dependency changes
- 3mo agoCatastRoDocumentation-only patch release
- 5mo agoCatastRo1.0.0 rebuilds on httr2 and invalidates every existing cache ⚡
- 6mo agoageproRAGEPRO VERSION 4.25 becomes the default format, with 4.0 kept compatible
- 1y agoageproRFour recruitment models added, including autocorrelated lognormal error ⚡
- 1y agoageproRagepro_inp_model initialisation aligned with the other model classes
- 1y agoCatastRoDocumentation and URL refresh
- 1y agoageproRVersion string read from line 1; invalid recruitment data blocks export
- 1y agoageproRInput file format reverted to VERSION 4.0 as a bugfix
- 2y agoCatastRoCadastre service entry points updated
- 2y agoCatastRohttr to httr2 migration, declared invisible to users
Frequently asked questions
What is the difference between ageproR and CatastRo?
They serve adjacent needs but don't currently overlap on shipped themes. ageproR 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 ageproR better than CatastRo?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ageproR 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 ageproR?
Top ageproR alternatives in Analytics are ranked by recent ship velocity. Browse the "ageproR alternatives" section above for the current picks, or visit /alternatives/agepror-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.