webchem
Adding chemical databases with one hand while public ones close programmatic access with the other.
A side-by-side editorial comparison of chromer and giscoR — release velocity, themes, recent moves, and the top alternatives to consider.
A chromosome-count database client that only ever ships when the upstream API moves.
chromer is a thin R client for the Chromosome Counts Database. Every release in the past three years is maintenance: a new maintainer and licence change in 0.3, test-skipping when the upstream service is down in 0.4, and two separate releases whose entire content is that the database's URL changed again. The current 0.10 points at ccdb.tau.ac.il/services/.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.
chromer is a thin R client for the Chromosome Counts Database. Every release in the past three years is maintenance: a new maintainer and licence change in 0.3, test-skipping when the upstream service is down in 0.4, and two separate releases whose entire content is that the database's URL changed again. The current 0.10 points at ccdb.tau.ac.il/services/.
The package is functionally complete and externally driven — its release cadence is a record of the CCDB's hosting history rather than of any development plan. The defensive work in 0.4, which added an internal check for whether the database is down and skips tests accordingly, shows the maintainer treating upstream instability as the permanent condition rather than an incident.
The next release will most likely be triggered by another CCDB endpoint or format change; nothing in the history suggests new functionality is planned.
giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.
The package is decoupling itself from Eurostat's publication calendar. Historically each new GISCO vintage required a release that bumped default years and rebuilt an internal dataset; after 1.0.0 a user can call gisco_get_cached_db(update_cache = TRUE) and reach new data without waiting. The follow-up releases are consistent with a project in consolidation — fixing the cache it just introduced, exposing a timeout for slow downloads, and tidying internals.
With the database now self-updating, expect releases to shift toward download reliability and new GISCO endpoints rather than annual dataset bumps; the timeout option in 1.1.0 suggests large downloads are the current pain point.
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 chromer or giscoR.
Adding chemical databases with one hand while public ones close programmatic access with the other.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
Went from estimating felling dates to doing the crossdating that produces them.
See all chromer alternatives → · See all giscoR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci, r-package — within Analytics. chromer and giscoR 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. chromer and giscoR 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.
Top chromer alternatives in Analytics are ranked by recent ship velocity. Browse the "chromer alternatives" section above for the current picks, or visit /alternatives/chromer for the full list with editorial commentary on each.
Top giscoR alternatives in Analytics are ranked by recent ship velocity. Browse the "giscoR alternatives" section above for the current picks, or visit /alternatives/giscor for the full list with editorial commentary on each.