← Back to home
Comparison · Infra & APIs

bcdata vs tabular

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

bcdata vs tabular: at a glance

Featurebcdatatabular
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesopen-data, spatial-data, api-client, cql-queriesr-packages, clinical-trials, document-rendering, typst
Last editorial update2h ago45m 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 tabular?

tabular went from clinical tables to complete TFL output in under two months.

tabular renders pre-summarised clinical tables, figures and listings to RTF, LaTeX, HTML, PDF, DOCX, Markdown and now Typst from one immutable verb pipeline, with no external SAS or Java runtime. It arrived in June 2026 as a CRAN submission candidate, added figure() a month later to cover the F in TFL, and has spent the 0.3.x line on speed, font resolution and toolchain diagnostics.

Read the full tabular trajectory →

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

T
tabular
INFRA · APIS
2.5

tabular went from clinical tables to complete TFL output in under two months.

◆ Current state

tabular renders pre-summarised clinical tables, figures and listings to RTF, LaTeX, HTML, PDF, DOCX, Markdown and now Typst from one immutable verb pipeline, with no external SAS or Java runtime. It arrived in June 2026 as a CRAN submission candidate, added figure() a month later to cover the F in TFL, and has spent the 0.3.x line on speed, font resolution and toolchain diagnostics.

◆ Where it's heading

The work is converging on backend parity — one spec should render the same wherever you emit it. Recent notes are almost entirely gap-closing between targets: bold column headers and page-width correction on LaTeX, cell margins on DOCX, group-separator blank rows re-expressed as discardable space so a page never ends on a stray gap, whitespace collapsing honoured on Typst. Diagnostics are keeping pace, with check_latex() probing through kpsewhich and check_typst() auditing the compiler and font chain.

◆ Prediction

With both toolchain checkers in place, the friction that remains is environmental rather than featural, and the notes point to further parity and packaging fixes rather than another backend. Whether Typst becomes the default PDF path instead of LaTeX is not something these notes settle.

Alternatives to bcdata and tabular

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

See all bcdata alternatives → · See all tabular alternatives →

Recent activity from bcdata and tabular

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

  1. 27d agotabularTest-only fix for the CRAN macOS arm64 check
  2. 1mo agotabularTypst backend, check_typst(), and 11-24% faster rendering
  3. 1mo agobcdataGeometry predicate filters no longer rejected by the server
  4. 1mo agotabularfigure() completes the T, F and L of TFL output
  5. 2mo agotabularFirst release: clinical table rendering without SAS or Java
  6. 6mo agobcdataleaflet.extras dependency dropped for WMS legends
  7. 1y agobcdataSearch and listing functions return complete results again
  8. 1y agobcdataHardened against failing WMS and WFS capability requests
  9. 3y agobcdataJSON resources readable; organization listing helpers added
  10. 3y agobcdatafilter() now requires local() for locally-evaluated calls

Frequently asked questions

What is the difference between bcdata and tabular?

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

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

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