← Back to home
Comparison · Infra & APIs

bcmaps vs daedalus

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

bcmaps vs daedalus: at a glance

Featurebcmapsdaedalus
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesspatial-data, r-package, open-government, sfepidemic-modelling, health-economics, npi-policy, ode-solvers
Last editorial update1h ago1h 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 daedalus?

An epidemic-economic model teaching its interventions to react to the outbreak itself.

daedalus couples an infectious-disease model to sector-level economic costs, letting users test non-pharmaceutical interventions against both epidemic and fiscal outcomes. Over autumn 2025 the intervention layer went from a single fixed closure to sequential timed NPIs and then to closures that lift in response to the model's own instantaneous reproduction number. Alongside that, the cost functions were reworked so illness states map more carefully onto lost productivity.

Read the full daedalus trajectory →

bcmaps vs daedalus: 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.

D
daedalus
INFRA · APIS
0.0

An epidemic-economic model teaching its interventions to react to the outbreak itself.

◆ Current state

daedalus couples an infectious-disease model to sector-level economic costs, letting users test non-pharmaceutical interventions against both epidemic and fiscal outcomes. Over autumn 2025 the intervention layer went from a single fixed closure to sequential timed NPIs and then to closures that lift in response to the model's own instantaneous reproduction number. Alongside that, the cost functions were reworked so illness states map more carefully onto lost productivity.

◆ Where it's heading

The arc is toward a model that behaves like a policy simulator rather than a scenario calculator: interventions now have their own state machine, R_t is computed inside the ODE system, and event handling has been pulled out of the output object. Correction releases sit between the feature ones, including an indexing fix the maintainers flag as required for accurate projections. The versioning is patch-level but the changes are structural.

◆ Prediction

With R_t and the next-generation matrix now available in-model, the likely next step is richer response rules keyed to those quantities; the entries give no signal on when a stable 1.0 arrives.

Alternatives to bcmaps and daedalus

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

See all bcmaps alternatives → · See all daedalus alternatives →

Recent activity from bcmaps and daedalus

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

  1. 5mo agobcmapsCensus dissemination block layer added
  2. 9mo agodaedalusVersion bump for a symposium preview build
  3. 9mo agodaedalusInterventions now lift in response to live R_t
  4. 10mo agodaedalusWithin-sector contact scaling corrected to quadratic
  5. 10mo agodaedalusIllness-driven absence reworked in the cost model
  6. 10mo agodaedalusMultiple sequential time-limited closures
  7. 11mo agodaedalusState array indexing corrections; earlier projections unreliable
  8. 1y agobcmapsCoordinate conversion fixed where output rows could be misaligned
  9. 2y agobcmapsutm_convert handles mixed UTM zones in tabular data
  10. 2y agobcmapsterra-based elevation function replaces the raster one
  11. 2y agobcmapssp and raster support removed, leaving sf as the only output class
  12. 3y agobcmapsDeprecation warnings announce the coming sf-only release

Frequently asked questions

What is the difference between bcmaps and daedalus?

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

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

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