mice
mice can finally predict, not just estimate, from multiply imputed data.
Comparison · Infra & APIs
bcdata vs GeoThinneR
A side-by-side editorial comparison of bcdata and GeoThinneR — release velocity, themes, recent moves, and the top alternatives to consider.
bcdata vs GeoThinneR: at a glance
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.
What is GeoThinneR?
Spatial thinning grows a result object, and the API breaks to make room for it
GeoThinneR removes spatially redundant occurrence records before species distribution modelling. Version 2.0.0 restructured it around a GeoThinned S3 class with print, summary, plot and trial-accessor methods, replacing the bare logical vectors earlier versions returned, and reorganised the methods into three named strategies — distance, grid and precision — with the search algorithm as a separate argument. The two releases since have added a priority system for choosing which of several tied points to drop.
bcdata vs GeoThinneR: editorial side-by-side
bcdata
0.0INFRA · APIS
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.
GeoThinneR
0.0INFRA · APIS
Spatial thinning grows a result object, and the API breaks to make room for it
◆ Current state
GeoThinneR removes spatially redundant occurrence records before species distribution modelling. Version 2.0.0 restructured it around a GeoThinned S3 class with print, summary, plot and trial-accessor methods, replacing the bare logical vectors earlier versions returned, and reorganised the methods into three named strategies — distance, grid and precision — with the search algorithm as a separate argument. The two releases since have added a priority system for choosing which of several tied points to drop.
◆ Where it's heading
The package is moving from a function that returns an answer to a tool that returns something you can interrogate. Multiple thinning trials are first-class — you can ask for the largest, fetch a specific one, summarise one — and the recent work is about making the choice among tied candidates controllable rather than random. Dependency discipline runs alongside: the R-tree method was dropped when its package was not on CRAN, and spatial coverage degrades to NA rather than failing when s2 is missing.
◆ Prediction
The priority mechanism now covers all three strategies and the last release was an overflow fix in the local kd-tree path at large sizes, so scale is where the pressure is. More work on the distance methods at large N is the likelier next step than another strategy.
Alternatives to bcdata and GeoThinneR
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 GeoThinneR.
PINstimation
A market-microstructure toolkit that keeps adding estimators as the papers land.
nzilbb.vowels
A vowel-analysis package trimming dependencies after an email address got it archived.
emuR
The R half of the EMU speech database system, fixing what was quietly broken.
BAS
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all bcdata alternatives → · See all GeoThinneR alternatives →
Recent activity from bcdata and GeoThinneR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agobcdataGeometry predicate filters no longer rejected by the server
- 5mo agoGeoThinneRInteger overflow in local kd-tree grid assignment
- 6mo agobcdataleaflet.extras dependency dropped for WMS legends
- 8mo agoGeoThinneRPriority-based tie-breaking across all thinning methods
- 1y agoGeoThinneRGeoThinned result objects and a reorganised method surface ⚡
- 1y agoGeoThinneRR-tree thinning removed with its off-CRAN dependency
- 1y agobcdataSearch and listing functions return complete results again
- 1y agobcdataHardened against failing WMS and WFS capability requests
- 3y agobcdataJSON resources readable; organization listing helpers added
- 3y agobcdatafilter() now requires local() for locally-evaluated calls
Frequently asked questions
What is the difference between bcdata and GeoThinneR?
They serve adjacent needs but don't currently overlap on shipped themes. bcdata and GeoThinneR 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 GeoThinneR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bcdata and GeoThinneR 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 GeoThinneR?
Top GeoThinneR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GeoThinneR alternatives" section above for the current picks, or visit /alternatives/geothinner for the full list with editorial commentary on each.