← Back to home
Comparison · Infra & APIs

bcdata vs prova

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

bcdata vs prova: at a glance

Featurebcdataprova
SectorInfra & APIsInfra & APIs
Velocity score0.06.3
Sparks · 30d01
Top themesopen-data, spatial-data, api-client, cql-queriesr-packages, bayesian-inference, decision-analysis, api-consolidation
Last editorial update2h ago46m 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 prova?

prova adds expected-utility calculation on top of its Bayesian inference core.

prova does Bayesian nonparametric inference in R — probabilities through Pr() and qPr(), mutual information, quantile plots. Five releases in about two weeks renamed its central argument, collapsed two plotting functions into one, and then in v2.3.0 introduced exputility() for expected utilities and their revisability, with plot() and print() methods attached from the start.

Read the full prova trajectory →

bcdata vs prova: 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.

P
prova
INFRA · APIS
6.3

prova adds expected-utility calculation on top of its Bayesian inference core.

◆ Current state

prova does Bayesian nonparametric inference in R — probabilities through Pr() and qPr(), mutual information, quantile plots. Five releases in about two weeks renamed its central argument, collapsed two plotting functions into one, and then in v2.3.0 introduced exputility() for expected utilities and their revisability, with plot() and print() methods attached from the start.

◆ Where it's heading

Two arcs run in parallel. One compresses the API: learnt= became K=, flexiplot() and plotquantiles() merged into pplot(), and omitting arguments such as Y=, X= and K= got simpler. The other extends reach — mutualinfoF() for finite-domain variates, quantile accuracy reported alongside mutual information, and now a decision-theoretic layer sitting on the inference the package already did.

◆ Prediction

exputility() shipping with print() and plot() methods matches how the probability and mutual-information classes were treated, so utilities are likely to get the same class-based handling as they mature. The notes do not say whether decision analysis extends beyond expected utility.

Alternatives to bcdata and prova

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 prova.

See all bcdata alternatives → · See all prova alternatives →

Recent activity from bcdata and prova

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

  1. 13d agoprovaexputility() brings decision analysis into prova
  2. 20d agoprovaCumulative 2.x notes, plus hist() and mutual-information changes
  3. 23d agoprovalearnt= becomes K=; pplot() replaces two plot functions
  4. 27d agoprovaFix for pre-existing parallel clusters
  5. 28d agoprovaextraDistr dropped; mutual-information objects get a class
  6. 1mo agobcdataGeometry predicate filters no longer rejected by the server
  7. 6mo agobcdataleaflet.extras dependency dropped for WMS legends
  8. 1y agobcdataSearch and listing functions return complete results again
  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 prova?

They serve adjacent needs but don't currently overlap on shipped themes. prova is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 bcdata better than prova?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. prova is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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 prova?

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