INFRA · APIS
France's national flood statistics, ported out of Fortran and into R.
Alternatives · developer tools
bcmaps alternatives
The best bcmaps alternatives in developer tools, ranked by Sparkpulse's velocity_score.
Updated Aug 18, 2026
Looking for the best alternatives to bcmaps? Sparkpulse tracks and ranks 12 alternatives in developer tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, bcmaps shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About 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.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to bcmaps
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
INFRA · APIS
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
INFRA · APIS
Fast design-based estimators for experiments, coasting on CRAN patches.
INFRA · APIS
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
INFRA · APIS
IP address vectors for R that hit 1.0 and then went quiet.
INFRA · APIS
A column-key toolkit for stitching decades of ecological field data into one table.
INFRA · APIS
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
INFRA · APIS
Bayesian luminescence dating that finally replaced its folder-structure input format.
INFRA · APIS
An epidemic-economic model teaching its interventions to react to the outbreak itself.
INFRA · APIS
A parallel-chain helper for bkmr that has settled into pure upkeep.
INFRA · APIS
A cancer driver prioritization package that ships rarely and mostly to stay installable
INFRA · APIS
A meteorology ggplot2 extension where the netCDF reader became the main event
bcmaps vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| bcmaps (baseline) | 0.0 | 0 | spatial-datar-packageopen-government | sp and raster support removed, leaving sf as the only output class |
| HydroPortailStats | 0.0 | 0 | hydrologyflood-frequencybayesian-statistics | Historical flood records enter the estimator via an HBay port |
| bsvarSIGNs | 0.0 | 0 | bayesian-statisticseconometricsstructural-var | Launch: sign, zero and narrative restrictions for bsvars |
| estimatr | 0.0 | 0 | causal-inferenceexperimentsrobust-standard-errors | — |
| ggdist | 0.0 | 0 | data-visualizationuncertaintybayesian-statistics | Blurred dotplots draw Monte Carlo error; weights reach every estimator |
| ipaddress | 0.0 | 0 | networkingip-addressesrcpp | 1.0.0 breaks the interface to make it vector-native |
| ltertools | 0.0 | 0 | data-harmonizationecologylter | — |
| finnts | 0.0 | 0 | forecastingtime-seriestidymodels | — |
| BayLum | 0.0 | 0 | bayesian-statisticsluminescence-datinggeochronology | One data-file function and a YAML config replace the folder layout |
| daedalus | 0.0 | 0 | epidemic-modellinghealth-economicsnpi-policy | Interventions now lift in response to live R_t |
| bkmrhat | 0.0 | 0 | bayesian-statisticsmcmcparallel-computing | — |
| driveR | 0.0 | 0 | cancer-genomicsbioinformaticsr-package | — |
| metR | 0.0 | 0 | meteorologyggplot2r-package | — |
The 12 best bcmaps alternatives, in depth
1. HydroPortailStats · velocity 0.0
France's national flood statistics, ported out of Fortran and into R.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Historical flood records enter the estimator via an HBay port”.
Where bcmaps leans on spatial data, r package and open government, HydroPortailStats focuses on hydrology, flood frequency and bayesian statistics.
HydroPortailStats and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full HydroPortailStats trajectory → · Compare bcmaps vs HydroPortailStats →
2. bsvarSIGNs · velocity 0.0
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Launch: sign, zero and narrative restrictions for bsvars”.
Where bcmaps leans on spatial data, r package and open government, bsvarSIGNs focuses on bayesian statistics, econometrics and structural var.
bsvarSIGNs and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full bsvarSIGNs trajectory → · Compare bcmaps vs bsvarSIGNs →
3. estimatr · velocity 0.0
Fast design-based estimators for experiments, coasting on CRAN patches.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where bcmaps leans on spatial data, r package and open government, estimatr focuses on causal inference, experiments and robust standard errors.
estimatr and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. ggdist · velocity 0.0
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Blurred dotplots draw Monte Carlo error; weights reach every estimator”.
Where bcmaps leans on spatial data, r package and open government, ggdist focuses on data visualization, uncertainty and bayesian statistics.
ggdist and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. ipaddress · velocity 0.0
IP address vectors for R that hit 1.0 and then went quiet.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0.0 breaks the interface to make it vector-native”.
Where bcmaps leans on spatial data, r package and open government, ipaddress focuses on networking, ip addresses and rcpp.
ipaddress and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. ltertools · velocity 0.0
A column-key toolkit for stitching decades of ecological field data into one table.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where bcmaps leans on spatial data, r package and open government, ltertools focuses on data harmonization, ecology and lter.
ltertools and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
7. finnts · velocity 0.0
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where bcmaps leans on spatial data, r package and open government, finnts focuses on forecasting, time series and tidymodels.
finnts and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
8. BayLum · velocity 0.0
Bayesian luminescence dating that finally replaced its folder-structure input format.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “One data-file function and a YAML config replace the folder layout”.
Where bcmaps leans on spatial data, r package and open government, BayLum focuses on bayesian statistics, luminescence dating and geochronology.
BayLum and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. daedalus · velocity 0.0
An epidemic-economic model teaching its interventions to react to the outbreak itself.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Interventions now lift in response to live R_t”.
Where bcmaps leans on spatial data, r package and open government, daedalus focuses on epidemic modelling, health economics and npi policy.
daedalus and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. bkmrhat · velocity 0.0
A parallel-chain helper for bkmr that has settled into pure upkeep.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where bcmaps leans on spatial data, r package and open government, bkmrhat focuses on bayesian statistics, mcmc and parallel computing.
bkmrhat and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. driveR · velocity 0.0
A cancer driver prioritization package that ships rarely and mostly to stay installable.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where bcmaps leans on spatial data, r package and open government, driveR focuses on cancer genomics, bioinformatics and r package.
driveR and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. metR · velocity 0.0
A meteorology ggplot2 extension where the netCDF reader became the main event.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where bcmaps leans on spatial data, r package and open government, metR focuses on meteorology, ggplot2 and r package.
metR and bcmaps have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Frequently asked questions
What are the best alternatives to bcmaps?
The top bcmaps alternatives we currently track in developer tools are HydroPortailStats, bsvarSIGNs, estimatr, ggdist, ipaddress, ranked by recent ship velocity.
How is this list of bcmaps alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare bcmaps directly with one of these alternatives?
Yes — every card has a "Compare with bcmaps" link to a side-by-side /compare page.