← Back to home
Comparison · Infra & APIs

bcdata vs rollupTree

A side-by-side editorial comparison of bcdata and rollupTree — release velocity, themes, recent moves, and the top alternatives to consider.

bcdata vs rollupTree: at a glance

FeaturebcdatarollupTree
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesopen-data, spatial-data, api-client, cql-queriesrecursive-computation, tree-structures, dag, engine-package
Last editorial update4h ago43m ago
WebsiteVisit →Visit →

What is bcdata?

The R gateway to B.C.'s data catalogue, mostly busy keeping pace with the servers behind it.

bcdata searches the British Columbia Data Catalogue and pulls records from it, including spatial layers retrieved through WMS and WFS with dplyr-style filtering translated into CQL queries sent to the server. The recent releases are small and corrective: 0.5.3 fixes malformed CQL generated by geometry predicates such as INTERSECTS, which the server had been rejecting outright, and 0.5.2 drops a leaflet extension dependency in favour of a base leaflet call. Cadence is a few releases a year.

Read the full bcdata trajectory →

What is rollupTree?

The recursive-computation engine under massProps grows the accessors its consumer needed

rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.

Read the full rollupTree trajectory →

bcdata vs rollupTree: editorial side-by-side

B
bcdata
INFRA · APIS
0.0

The R gateway to B.C.'s data catalogue, mostly busy keeping pace with the servers behind it.

◆ Current state

bcdata searches the British Columbia Data Catalogue and pulls records from it, including spatial layers retrieved through WMS and WFS with dplyr-style filtering translated into CQL queries sent to the server. The recent releases are small and corrective: 0.5.3 fixes malformed CQL generated by geometry predicates such as INTERSECTS, which the server had been rejecting outright, and 0.5.2 drops a leaflet extension dependency in favour of a base leaflet call. Cadence is a few releases a year.

◆ Where it's heading

Almost everything in this window is a response to something changing on the other side of the connection: a CKAN 2.9 upgrade that stopped search and listing functions returning complete results, WMS and WFS capability requests that cannot be relied on, dbplyr tightening the rules for local evaluation, and general catalogue-side churn. The package's own interface has been stable since the 0.4.0 change that required local() around locally-evaluated filter calls, and the work since has gone into keeping that stable interface working rather than extending it.

◆ Prediction

Expect the same pattern: targeted fixes as the catalogue and its CKAN, WMS and WFS layers change, with occasional dependency pruning of the kind 0.5.2 did. Nothing in these entries points toward a 0.6 or a change in what the package covers.

R
rollupTree
INFRA · APIS
0.0

The recursive-computation engine under massProps grows the accessors its consumer needed

◆ Current state

rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.

◆ Where it's heading

The package develops in response to its one visible consumer. The 0.4.0 accessors appeared in January 2026 and massProps switched to them thirteen days later; 0.4.1 then fixed missing column names in the setters, which is the kind of defect only real use surfaces. Before that, 0.3.0's default_validate_dag() extended validation past strict trees to directed acyclic graphs, widening what structures the engine will accept.

◆ Prediction

On the established pattern the next release will be whatever massProps needs next, discovered by using it. A DAG validator suggests non-tree structures are in scope, but nothing in these notes says that path is being pushed further.

Alternatives to bcdata and rollupTree

Other Infra & APIs 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 bcdata or rollupTree.

See all bcdata alternatives → · See all rollupTree alternatives →

Recent activity from bcdata and rollupTree

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agobcdataGeometry predicate filters no longer rejected by the server
  2. 6mo agorollupTreeMissing column names in the new row setters
  3. 6mo agobcdataleaflet.extras dependency dropped for WMS legends
  4. 6mo agorollupTreeRow-level get and set accessors by key and by id
  5. 1y agorollupTreeMinor vignette improvements
  6. 1y agorollupTreeBadges and GitHub Actions added to the README
  7. 1y agobcdataSearch and listing functions return complete results again
  8. 1y agorollupTreedefault_validate_dag() extends validation past strict trees
  9. 1y agobcdataHardened against failing WMS and WFS capability requests
  10. 3y agobcdataJSON resources readable; organization listing helpers added
  11. 3y agobcdatafilter() now requires local() for locally-evaluated calls

Frequently asked questions

What is the difference between bcdata and rollupTree?

They serve adjacent needs but don't currently overlap on shipped themes. bcdata and rollupTree 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 bcdata better than rollupTree?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bcdata and rollupTree 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to bcdata?

Top bcdata alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bcdata alternatives" section above for the current picks, or visit /alternatives/bcdata for the full list with editorial commentary on each.

What are the best alternatives to rollupTree?

Top rollupTree alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rollupTree alternatives" section above for the current picks, or visit /alternatives/rolluptree for the full list with editorial commentary on each.