← Back to home
Comparison · Infra & APIs

bcdata vs smam

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

bcdata vs smam: at a glance

Featurebcdatasmam
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesopen-data, spatial-data, api-client, cql-queriesanimal-movement, stochastic-processes, state-space-models, rcpp
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 smam?

Animal-movement models in R, where new stochastic processes arrive years apart.

smam fits statistical models of animal movement, covering moving-resting processes with and without measurement error, moving-resting-handling, and moving-moving processes, with simulation, point estimation and variance estimation for each. The last three releases are pure upkeep: guarding Rf_error calls after an Rcpp update, a maintainer email change, and a compiler warning fix. The substantive work in this window is 0.7.0, which added estimate and vcov generics across all fit functions, and 0.6.0, which added the moving-moving process.

Read the full smam trajectory →

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

S
smam
INFRA · APIS
0.0

Animal-movement models in R, where new stochastic processes arrive years apart.

◆ Current state

smam fits statistical models of animal movement, covering moving-resting processes with and without measurement error, moving-resting-handling, and moving-moving processes, with simulation, point estimation and variance estimation for each. The last three releases are pure upkeep: guarding Rf_error calls after an Rcpp update, a maintainer email change, and a compiler warning fix. The substantive work in this window is 0.7.0, which added estimate and vcov generics across all fit functions, and 0.6.0, which added the moving-moving process.

◆ Where it's heading

This package grows by adding process models, and it does so rarely. Between the moving-moving process in 2021 and now, the only interface-level change has been the 0.7.0 generics that gave every fit function a common way to retrieve estimates and their covariance, which is consolidation of an accumulated collection rather than expansion of it. The three releases since are entirely reactive to toolchain and CRAN pressure, and they arrive in step with the maintainer's other package coga, which received the same Rcpp guard within twenty minutes on the same day.

◆ Prediction

Expect further releases to be CRAN and Rcpp maintenance unless a new movement process is published, which is what has historically prompted a minor version here. The generics added in 0.7.0 give any future process model a ready-made interface to slot into.

Alternatives to bcdata and smam

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

See all bcdata alternatives → · See all smam alternatives →

Recent activity from bcdata and smam

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

  1. 1mo agobcdataGeometry predicate filters no longer rejected by the server
  2. 5mo agosmamRcpp attributes regenerated to guard Rf_error calls
  3. 6mo agobcdataleaflet.extras dependency dropped for WMS legends
  4. 1y agobcdataSearch and listing functions return complete results again
  5. 1y agobcdataHardened against failing WMS and WFS capability requests
  6. 2y agosmamMaintainer email updated
  7. 2y agosmamCompiler format-security warning resolved
  8. 2y agosmamestimate and vcov generics unify all fit functions
  9. 3y agobcdataJSON resources readable; organization listing helpers added
  10. 3y agobcdatafilter() now requires local() for locally-evaluated calls
  11. 5y agosmamMoving-moving process added with simulation and estimation
  12. 5y agosmamVariance estimators adjusted; example dataset added

Frequently asked questions

What is the difference between bcdata and smam?

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

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

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