← Back to home
Comparison · Infra & APIs

bcdata vs trackeR

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

bcdata vs trackeR: at a glance

FeaturebcdatatrackeR
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesopen-data, spatial-data, api-client, cql-queriesfitness-tracking, gps-data, file-parsing, visualization
Last editorial update7h 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 trackeR?

Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.

trackeR reads GPS and fitness-tracker files in TCX, GPX and JSON form and turns them into session data, distribution and concentration profiles, and route plots. Feature work concentrated in the 1.5 series in 2019; the two releases since are corrective. The latest swaps the plot layout dependencies for patchwork and fixes plot_route() returning nothing.

Read the full trackeR trajectory →

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

Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.

◆ Current state

trackeR reads GPS and fitness-tracker files in TCX, GPX and JSON form and turns them into session data, distribution and concentration profiles, and route plots. Feature work concentrated in the 1.5 series in 2019; the two releases since are corrective. The latest swaps the plot layout dependencies for patchwork and fixes plot_route() returning nothing.

◆ Where it's heading

Recent releases track other people's changes: ggmap moving to Stadia maps, gridExtra giving way to patchwork, a cadence field being read into the wrong column. The 2019 entries are where the analysis surface was built out, with cumulative elevation gain, compressed file reading and elevation-noise thresholds, and it has not moved much since.

◆ Prediction

Expect the next release to be another compatibility or parsing fix rather than a new metric.

Alternatives to bcdata and trackeR

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

See all bcdata alternatives → · See all trackeR alternatives →

Recent activity from bcdata and trackeR

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. 11mo agotrackeRplot_route() fixed; plot layout moved to patchwork
  4. 1y agobcdataSearch and listing functions return complete results again
  5. 1y agobcdataHardened against failing WMS and WFS capability requests
  6. 2y agotrackeRTCX cadence bug fixed; m_per_min units and Stadia maps
  7. 3y agobcdataJSON resources readable; organization listing helpers added
  8. 3y agobcdatafilter() now requires local() for locally-evaluated calls
  9. 7y agotrackeRCompressed file reading and correct GPX power extraction
  10. 7y agotrackeRvertical_noise threshold for elevation gain
  11. 7y agotrackeRCumulative elevation gain added as a derived metric
  12. 7y agotrackeRFortify and print bugs fixed in summary objects

Frequently asked questions

What is the difference between bcdata and trackeR?

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

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

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