← Back to home
Comparison · Infra & APIs

bcdata vs PINstimation

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

Shared themes:r-package

bcdata vs PINstimation: at a glance

FeaturebcdataPINstimation
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesopen-data, spatial-data, api-client, cql-queriesmarket-microstructure, finance, informed-trading, r-package
Last editorial update6h ago1h 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 PINstimation?

A market-microstructure toolkit that keeps adding estimators as the papers land.

PINstimation estimates probability-of-informed-trading models — PIN, multilayer PIN, adjusted PIN and VPIN — from trade and quote data, and handles the trade classification and aggregation that feeds them. The current 0.2.0 adds ivpin(), a maximum-likelihood variant of VPIN from Ke and Lin (2017). The package's early history is compressed into a single hour of backfilled tags in October 2022, so version order there does not track release order.

Read the full PINstimation trajectory →

bcdata vs PINstimation: 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
PINstimation
INFRA · APIS
0.0

A market-microstructure toolkit that keeps adding estimators as the papers land.

◆ Current state

PINstimation estimates probability-of-informed-trading models — PIN, multilayer PIN, adjusted PIN and VPIN — from trade and quote data, and handles the trade classification and aggregation that feeds them. The current 0.2.0 adds ivpin(), a maximum-likelihood variant of VPIN from Ke and Lin (2017). The package's early history is compressed into a single hour of backfilled tags in October 2022, so version order there does not track release order.

◆ Where it's heading

Each release tracks the literature: a Bayesian PIN estimator from Griffin et al., an improved VPIN from Ke and Lin, initial-parameter generation realigned to Ersan and Ghachem. The other steady thread is data handling — matrix inputs so the estimators compose with rolling windows, user-specified aggregation frequencies, and now quote leads as well as lags. The three-year gap between 0.1.2 and 0.2.0 makes this a slow, publication-paced package rather than an actively developed one.

◆ Prediction

On this pattern the next release adds whatever estimator the authors publish next, since two of the three feature releases here implement a specific paper. Nothing in the entries points to a change in the package's structure.

Alternatives to bcdata and PINstimation

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

See all bcdata alternatives → · See all PINstimation alternatives →

Recent activity from bcdata and PINstimation

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

  1. 1mo agobcdataGeometry predicate filters no longer rejected by the server
  2. 6mo agobcdataleaflet.extras dependency dropped for WMS legends
  3. 8mo agoPINstimationPINstimation 0.2.0
  4. 1y agobcdataSearch and listing functions return complete results again
  5. 1y agobcdataHardened against failing WMS and WFS capability requests
  6. 3y agobcdataJSON resources readable; organization listing helpers added
  7. 3y agoPINstimationPINstimation v0.1.2
  8. 3y agobcdatafilter() now requires local() for locally-evaluated calls
  9. 3y agoPINstimationPINstimation v0.1.1
  10. 3y agoPINstimationPINstimation v0.0.1-beta
  11. 3y agoPINstimationPINstimation v0.1.0

Frequently asked questions

What is the difference between bcdata and PINstimation?

Both compete on the same themes — r-package — within Infra & APIs. bcdata and PINstimation 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 PINstimation?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bcdata and PINstimation 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 PINstimation?

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