compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
Comparison · Analytics
hubData vs topocast
A side-by-side editorial comparison of hubData and topocast — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
hubData vs topocast: at a glance
What is hubData?
The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
What is topocast?
New R package downscaling coarse climate rasters onto fine terrain, now five times cheaper per call.
topocast is a young R package — first released in June 2026 — that downscales coarse rasters onto fine terrain using moving-window regression, with the relationship expressed as a formula over layer names. Its defining implementation choice is summed-area tables, which make the cost of estimating coefficient grids independent of the window radius. Three releases in six weeks have taken it from first publication through real-workflow fixes to a substantial performance restructuring.
hubData vs topocast: editorial side-by-side
hubData
0.0ANALYTICS
The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.
◆ Current state
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
◆ Where it's heading
The package has largely finished adding surface and is now paying down the cost of sitting on top of Arrow and S3: ALTREP-backed columns escaping into user sessions, cloud hubs whose declared format differs from what is actually written, and metadata arrays parsing inconsistently. Each fix narrows the gap between what the storage layer does and what an R user expects. The performance-motivated default flip in 2.0.0 points the same way, prioritising large cloud hubs over conservative local behaviour.
◆ Prediction
Expect continued fixes at the Arrow and cloud boundary, particularly where declared hub configuration and actual stored format disagree, which has now produced defects twice.
topocast
2.5ANALYTICS
New R package downscaling coarse climate rasters onto fine terrain, now five times cheaper per call.
◆ Current state
topocast is a young R package — first released in June 2026 — that downscales coarse rasters onto fine terrain using moving-window regression, with the relationship expressed as a formula over layer names. Its defining implementation choice is summed-area tables, which make the cost of estimating coefficient grids independent of the window radius. Three releases in six weeks have taken it from first publication through real-workflow fixes to a substantial performance restructuring.
◆ Where it's heading
Development is being driven by running the package against real datasets — the second release names CHELSA and SRTM as the source of its three fixes — and the third is a direct response to multi-response calls repeating work. The arc is the ordinary one for a new method package: publish the method, then discover that real inputs have more responses, more coordinate-system edge cases, and more repeated structure than the initial design assumed. Coefficient grids being exposed as output suggests the local regression parameters, such as lapse rate, are as interesting to users as the downscaled values.
◆ Prediction
Expect continued work on multi-response and time-series throughput, and more coordinate-system and input-validation handling as the package meets further real climate datasets.
Alternatives to hubData and topocast
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 hubData or topocast.
nabla
nabla dropped its C++ engine to chase exact derivatives at any order.
snowflakeauth
Eight months from first release to keyring caching and workload identity.
kwb.geosalz
A research-project workflow package where the interesting work is in the plumbing.
cyclocomp
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
revdbayes
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
See all hubData alternatives → · See all topocast alternatives →
Recent activity from hubData and topocast
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agotopocastMulti-response calls stop repeating the coarse-to-target trip
- 1mo agohubDataCloud hubs declaring CSV no longer return an empty connection
- 2mo agotopocastCoefficient grids exposed and coarse predictors derived automatically
- 2mo agotopocastFirst release: terrain downscaling by moving-window regression
- 3mo agohubDatacollect_hub() returns plain vectors instead of ALTREP views
- 3mo agohubDataArray-valued metadata fields now parse as list columns
- 7mo agohubDatadate_col parameter for oracle output schemas
- 8mo agohubDataconnect_hub() skips file validation by default (breaking)
- 10mo agohubDataArrow schema conversion and validation utilities
Frequently asked questions
What is the difference between hubData and topocast?
Both compete on the same themes — r-package — within Analytics. topocast 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.
Is hubData better than topocast?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. topocast 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.
What are the best alternatives to hubData?
Top hubData alternatives in Analytics are ranked by recent ship velocity. Browse the "hubData alternatives" section above for the current picks, or visit /alternatives/hubdata for the full list with editorial commentary on each.
What are the best alternatives to topocast?
Top topocast alternatives in Analytics are ranked by recent ship velocity. Browse the "topocast alternatives" section above for the current picks, or visit /alternatives/topocast for the full list with editorial commentary on each.