simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
kde1d vs PurpleAir
A side-by-side editorial comparison of kde1d and PurpleAir — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
kde1d vs PurpleAir: at a glance
What is kde1d?
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
kde1d estimates univariate densities with local polynomial kernel methods, handling bounded, discrete and now zero-inflated variables through a single type argument, with the numerical work in a header-only C++ library usable outside R. Version 1.1.0 added the zero-inflated discrete-continuous mixture case and shipped a new C++ API as an explicit breaking change; 1.1.1 followed in June with auto-generated notes and no description.
What is PurpleAir?
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
PurpleAir is a small R client for the PurpleAir air quality sensor API, covering sensor queries, historical readings, and — more recently — finding a sensor on the local network by IP address and id. Authentication has been simplified to an environment variable only, with the redundant key argument removed. The package is maintained reactively, and most of what ships is correctness work on the queries it already makes.
kde1d vs PurpleAir: editorial side-by-side
kde1d
0.0ANALYTICS
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
◆ Current state
kde1d estimates univariate densities with local polynomial kernel methods, handling bounded, discrete and now zero-inflated variables through a single type argument, with the numerical work in a header-only C++ library usable outside R. Version 1.1.0 added the zero-inflated discrete-continuous mixture case and shipped a new C++ API as an explicit breaking change; 1.1.1 followed in June with auto-generated notes and no description.
◆ Where it's heading
The package has alternated between performance work and widening the class of data it accepts. The 1.0.0 release was the performance milestone — FFT-based estimation, a better integration algorithm for the p, q and r functions, deterministic jittering replacing randomness, and standalone C++ headers. The 1.1.0 release is the scope milestone, adding a third data type to the two it already handled. Releases come from the same maintainer as svines and cluster on shared dates, so changes in the underlying C++ surface across the vine and density stack tend to ship together.
◆ Prediction
With the C++ API deliberately reworked for standalone use at 1.1.0, further work most plausibly consolidates that interface rather than adding data types. What 1.1.1 actually changed is not readable from its body.
PurpleAir
0.0ANALYTICS
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
◆ Current state
PurpleAir is a small R client for the PurpleAir air quality sensor API, covering sensor queries, historical readings, and — more recently — finding a sensor on the local network by IP address and id. Authentication has been simplified to an environment variable only, with the redundant key argument removed. The package is maintained reactively, and most of what ships is correctness work on the queries it already makes.
◆ Where it's heading
The recurring theme is time aggregation. Weekly, monthly and yearly average intervals were wrong and fixed in one release; the weekly average was wrong again and fixed in the next. For an air quality package that is not incidental — averaging window is what turns a stream of sensor readings into an exposure estimate, and downstream analyses inherit the error silently. The other thread is failing earlier and more clearly: explicit errors for spatial inputs the sensor query does not accept, better index parsing so malformed requests never reach the API, and handling for history calls that return nothing. Local sensor discovery is the one genuine capability addition, opening a path that does not depend on the cloud API at all.
◆ Prediction
On this record, further aggregation and input-validation fixes are the likeliest next releases; whether local network access grows past discovery into full local data retrieval is not something the entries indicate.
Alternatives to kde1d and PurpleAir
Other Analytics 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 kde1d or PurpleAir.
lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
ibis.iSDM
A raster-to-terra migration is the only readable change in a feed of merge notes.
anyflights
A nycflights13 generator whose recent work is all about the data being right.
vinereg
Conditional density and log-likelihood fill out a vine copula regression package.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
See all kde1d alternatives → · See all PurpleAir alternatives →
Recent activity from kde1d and PurpleAir
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoPurpleAirWeekly averages fixed again; API key argument dropped
- 10mo agoPurpleAirLocal sensor discovery, and averaging intervals corrected
- 1y agokde1dkde1d 1.1.1
- 1y agokde1dZero-inflated mixtures and a new standalone C++ API ⚡
- 1y agoPurpleAirBounding box sensor queries fixed
- 4y agokde1dBit-wise Boolean operations removed
- 5y agokde1ddkde1d() invisible output fixed
- 5y agokde1dValgrind false positive silenced
- 6y agokde1dqrng dependency dropped; undefined behaviour fixed
Frequently asked questions
What is the difference between kde1d and PurpleAir?
Both compete on the same themes — r-package — within Analytics. kde1d and PurpleAir 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 kde1d better than PurpleAir?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. kde1d and PurpleAir 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 Analytics products to evaluate alongside.
What are the best alternatives to kde1d?
Top kde1d alternatives in Analytics are ranked by recent ship velocity. Browse the "kde1d alternatives" section above for the current picks, or visit /alternatives/kde1d for the full list with editorial commentary on each.
What are the best alternatives to PurpleAir?
Top PurpleAir alternatives in Analytics are ranked by recent ship velocity. Browse the "PurpleAir alternatives" section above for the current picks, or visit /alternatives/purpleair for the full list with editorial commentary on each.