← Back to home
Comparison · Infra & APIs

bcdata vs radiatR

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

Shared themes:r-package

bcdata vs radiatR: at a glance

FeaturebcdataradiatR
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesopen-data, spatial-data, api-client, cql-queriescircular-statistics, animal-movement, r-package, shiny-app
Last editorial update1h 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 radiatR?

A circular-statistics toolkit for animal movement, shipped and then tightened in three weeks.

radiatR reads movement trajectories, plots them on circular axes, computes kinematics such as speed and path sinuosity, and runs the circular statistics that go with them, including tests of mean direction, symmetry and unimodality. It arrived as a first public release on 9 July 2026 with an accompanying Shiny app, and has had two releases since at roughly weekly intervals. The 0.1.x line is still setting its boundaries: 0.1.2 removes a loader dialect and makes previously silent data problems into errors.

Read the full radiatR trajectory →

bcdata vs radiatR: 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
radiatR
INFRA · APIS
2.5

A circular-statistics toolkit for animal movement, shipped and then tightened in three weeks.

◆ Current state

radiatR reads movement trajectories, plots them on circular axes, computes kinematics such as speed and path sinuosity, and runs the circular statistics that go with them, including tests of mean direction, symmetry and unimodality. It arrived as a first public release on 9 July 2026 with an accompanying Shiny app, and has had two releases since at roughly weekly intervals. The 0.1.x line is still setting its boundaries: 0.1.2 removes a loader dialect and makes previously silent data problems into errors.

◆ Where it's heading

Three releases in twelve days show a package hardening in public rather than accreting features. The direction of travel is toward refusing bad input instead of quietly working around it: non-finite coordinate rows now error by default rather than being dropped silently, combining Tracks objects rejects colliding trajectory ids and conflicting calibration metadata instead of merging them and discarding one side, and the Shiny app clears prior state before reading a new upload. The statistical surface is growing in parallel, but within the scope the first release already claimed.

◆ Prediction

Expect the remaining goodness-of-fit gap the notes name explicitly, Jones-Pewsey, to be filled in a later release, and the error-on-bad-input treatment to reach the parts of the loader it has not yet covered. A CRAN submission is the natural next step for a package this young, though nothing in these entries commits to one.

Alternatives to bcdata and radiatR

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

See all bcdata alternatives → · See all radiatR alternatives →

Recent activity from bcdata and radiatR

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

  1. 29d agoradiatRctrax loader dropped; bad coordinates now error by default
  2. 1mo agoradiatRWrapped-Cauchy and Pycke tests close two statistical gaps
  3. 1mo agobcdataGeometry predicate filters no longer rejected by the server
  4. 1mo agoradiatRFirst public release
  5. 6mo agobcdataleaflet.extras dependency dropped for WMS legends
  6. 1y agobcdataSearch and listing functions return complete results again
  7. 1y agobcdataHardened against failing WMS and WFS capability requests
  8. 3y agobcdataJSON resources readable; organization listing helpers added
  9. 3y agobcdatafilter() now requires local() for locally-evaluated calls

Frequently asked questions

What is the difference between bcdata and radiatR?

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

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

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