← Back to home
Comparison · Infra & APIs

bcmaps vs finnts

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

Shared themes:r-package

bcmaps vs finnts: at a glance

Featurebcmapsfinnts
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesspatial-data, r-package, open-government, sfforecasting, time-series, tidymodels, automl
Last editorial update1h ago59m ago
WebsiteVisit →Visit →

What is bcmaps?

BC's spatial data package finished its sf migration and went back to adding layers

bcmaps provides British Columbia spatial layers and boundary data to R users, pulling from the BC Data Catalogue. The disruptive work is behind it: version 2.0.0 removed sp and raster support outright, leaving sf as the only returned class, in response to the retirement of rgdal and rgeos. Since then releases have been additive and small - cded_terra() replacing the deprecated raster variant, utm_convert() for reconciling coordinates across UTM zones, and in 2.3.0 a census dissemination block layer plus a dependency bump that removes an indirect reliance on the soon-to-be-archived leaflet.extras.

Read the full bcmaps trajectory →

What is finnts?

Microsoft's automated forecasting framework, still mostly a one-maintainer effort.

finnts automates time-series forecasting end to end — feature engineering, model selection, hierarchical reconciliation — on a tidymodels backbone. Recent releases have concentrated on global models (one model fitted across many series) and on hierarchical reconciliation, which has needed repeated correction at weekly granularity. Release notes are auto-generated pull-request lists, so the detail lives in the PRs rather than in the changelog.

Read the full finnts trajectory →

bcmaps vs finnts: editorial side-by-side

B
bcmaps
INFRA · APIS
0.0

BC's spatial data package finished its sf migration and went back to adding layers

◆ Current state

bcmaps provides British Columbia spatial layers and boundary data to R users, pulling from the BC Data Catalogue. The disruptive work is behind it: version 2.0.0 removed sp and raster support outright, leaving sf as the only returned class, in response to the retirement of rgdal and rgeos. Since then releases have been additive and small - cded_terra() replacing the deprecated raster variant, utm_convert() for reconciling coordinates across UTM zones, and in 2.3.0 a census dissemination block layer plus a dependency bump that removes an indirect reliance on the soon-to-be-archived leaflet.extras.

◆ Where it's heading

The package has spent most of its recent history reducing what it depends on rather than growing. Layers moved from a companion data package to direct Data Catalogue downloads in 1.1.0, ending manual update cycles; the sp and raster removal followed a full release of deprecation warnings; the terra transition took the same staged path. The recent dependency bump for leaflet.extras is the same instinct applied early. Feature work now arrives one function or one layer at a time, at roughly one release a year.

◆ Prediction

Expect further individual layer additions on request, and a completion of the terra transition through removal of the deprecated cded_raster(), given the package's pattern of announcing removals a release ahead.

F
finnts
INFRA · APIS
0.0

Microsoft's automated forecasting framework, still mostly a one-maintainer effort.

◆ Current state

finnts automates time-series forecasting end to end — feature engineering, model selection, hierarchical reconciliation — on a tidymodels backbone. Recent releases have concentrated on global models (one model fitted across many series) and on hierarchical reconciliation, which has needed repeated correction at weekly granularity. Release notes are auto-generated pull-request lists, so the detail lives in the PRs rather than in the changelog.

◆ Where it's heading

Cadence is roughly annual and the commit history is almost entirely one maintainer, with occasional outside contributions. The direction across the last four releases is consolidation of the forecasting internals — multi-horizon models, feature selection, reconciliation fixes — rather than new surface for users. The changelogs themselves are unedited PR dumps, which makes the arc harder to read than the work probably warrants.

◆ Prediction

Hierarchical reconciliation has produced a bug fix in three of the last four releases, so the next one likely touches it again; nothing in the entries points to a specific new capability.

Alternatives to bcmaps and finnts

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 bcmaps or finnts.

See all bcmaps alternatives → · See all finnts alternatives →

Recent activity from bcmaps and finnts

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

  1. 5mo agobcmapsCensus dissemination block layer added
  2. 11mo agofinntsGlobal model updates and a weekly reconciliation fix
  3. 1y agobcmapsCoordinate conversion fixed where output rows could be misaligned
  4. 1y agofinntsMulti-horizon models, hierarchy drivers, Synapse 3.4 migration
  5. 2y agobcmapsutm_convert handles mixed UTM zones in tabular data
  6. 2y agofinntsARIMAX support and feature selection added
  7. 2y agobcmapsterra-based elevation function replaces the raster one
  8. 2y agobcmapssp and raster support removed, leaving sf as the only output class
  9. 3y agobcmapsDeprecation warnings announce the coming sf-only release
  10. 3y agofinntsdplyr 1.1.0 compatibility and a reconciliation fix

Frequently asked questions

What is the difference between bcmaps and finnts?

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

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

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

What are the best alternatives to finnts?

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