simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of anyflights and PurpleAir — release velocity, themes, recent moves, and the top alternatives to consider.
A nycflights13 generator whose recent work is all about the data being right.
anyflights builds nycflights13-style datasets for any US airport and year, downloading flight, weather, airline, airport, and plane tables and optionally packaging them. The four visible releases span 2022 to 2025 and are dominated by keeping those downloads working. The most recent fixes a timezone leak and gaps in hourly weather data.
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.
anyflights builds nycflights13-style datasets for any US airport and year, downloading flight, weather, airline, airport, and plane tables and optionally packaging them. The four visible releases span 2022 to 2025 and are dominated by keeping those downloads working. The most recent fixes a timezone leak and gaps in hourly weather data.
The function surface has been stable since 0.3; everything since concerns the fragility of the upstream sources. Broken URLs for airline data, download failures needing a session-timeout hint, planes data that stopped resolving, and weather values recorded only once an hour have each taken a release. Contributions come from teaching-adjacent users, which fits a package whose main use is generating course datasets.
Expect the next release to follow another upstream data-source change rather than to add a table or an argument.
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.
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.
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.
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 anyflights or PurpleAir.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
From a bundled hospital dataset to a live CMS API client.
See all anyflights alternatives → · See all PurpleAir alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package, data-quality — within Analytics. anyflights 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. anyflights 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.
Top anyflights alternatives in Analytics are ranked by recent ship velocity. Browse the "anyflights alternatives" section above for the current picks, or visit /alternatives/anyflights for the full list with editorial commentary on each.
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.