← Back to home
Comparison · Infra & APIs

bcdata vs emuR

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

Shared themes:r-package

bcdata vs emuR: at a glance

FeaturebcdataemuR
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesopen-data, spatial-data, api-client, cql-queriesspeech-science, phonetics, annotation, 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 emuR?

The R half of the EMU speech database system, fixing what was quietly broken.

emuR is the R interface to the EMU Speech Database Management System — loading annotated speech corpora, running hierarchical queries over annotation levels, extracting signal track data, and serving corpora to the EMU-webApp for browser-based annotation. It is at 2.6.0 on a slow cadence of roughly one release a year. Recent work has centred on the CRUD operations for annotation items and on widening what serve() can hand the web application.

Read the full emuR trajectory →

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

E
emuR
INFRA · APIS
0.0

The R half of the EMU speech database system, fixing what was quietly broken.

◆ Current state

emuR is the R interface to the EMU Speech Database Management System — loading annotated speech corpora, running hierarchical queries over annotation levels, extracting signal track data, and serving corpora to the EMU-webApp for browser-based annotation. It is at 2.6.0 on a slow cadence of roughly one release a year. Recent work has centred on the CRUD operations for annotation items and on widening what serve() can hand the web application.

◆ Where it's heading

The releases read as a package being brought up to the standard its own API implied. delete_itemsInLevel() shipped in 2.1.1 as a first version, was described in 2.5.0 as heavily flawed and now usable, and the create/update/delete family is still called ongoing work. Alongside that, the query engine was rewritten onto CTEs and the signal-processing layer is being opened past the bundled wrassp, starting with Matlab. Speed work recurs — SQLite transactions, prepared statements, on-the-fly caching — consistent with corpora outgrowing the original design.

◆ Prediction

Two threads are explicitly unfinished: the CRUD documentation and behaviour, described as ongoing, and the add_signalVia family, described as a draft starting with Matlab. Expect the next release to advance one of them rather than open new ground.

Alternatives to bcdata and emuR

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

See all bcdata alternatives → · See all emuR alternatives →

Recent activity from bcdata and emuR

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 agoemuRemuR 2.6.0
  4. 1y agoemuRemuR 2.5.1
  5. 1y agoemuRemuR 2.5.0
  6. 1y agobcdataSearch and listing functions return complete results again
  7. 1y agobcdataHardened against failing WMS and WFS capability requests
  8. 3y agoemuRemuR 2.4.0
  9. 3y agobcdataJSON resources readable; organization listing helpers added
  10. 3y agobcdatafilter() now requires local() for locally-evaluated calls
  11. 5y agoemuRemuR 2.3.0
  12. 5y agoemuRemuR 2.2.0

Frequently asked questions

What is the difference between bcdata and emuR?

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

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

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