vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of hereR and neonUtilities — release velocity, themes, recent moves, and the top alternatives to consider.
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
hereR wraps HERE's routing, isoline, traffic, weather and geocoding endpoints for R, returning sf objects. Development is steady and reactive: each release either adopts a transport mode, parameter or API version HERE has newly made available, or corrects a rate limit that was producing 429 errors in practice. The current release adds speed-limit control and five more isoline transport modes.
Two major versions shipped in a year, and this feed will not say what changed in either.
neonUtilities is the R toolkit NEON publishes for pulling and assembling its own observatory data — downloading data products through the NEON API, unzipping and stacking monthly packages into analysis-ready tables, and handling the awkward cases like eddy-covariance and airborne data. It reached 4.0.0 in June and 4.0.1 in July. What those releases contain is not recoverable from this feed: every recent entry is a one-line pointer saying the tag corresponds to a CRAN version, with the change log left in NEWS.md.
hereR wraps HERE's routing, isoline, traffic, weather and geocoding endpoints for R, returning sf objects. Development is steady and reactive: each release either adopts a transport mode, parameter or API version HERE has newly made available, or corrects a rate limit that was producing 429 errors in practice. The current release adds speed-limit control and five more isoline transport modes.
Two threads run through the whole history. One is coverage — new modes, tolls and currency, arrival times, speed limits — arriving in the package shortly after they appear in HERE's API. The other is defensive operational tuning, with request rates repeatedly lowered below HERE's documented limits because the documented limits do not hold up. 1.0.0 was the one moment the package had to move rather than choose, migrating traffic to v7 and weather to v3 and breaking three functions' output in the process.
Expect the next release to enable whatever HERE exposes next in routing or isolines, and to keep adjusting request rates empirically; the package's own design appears settled.
neonUtilities is the R toolkit NEON publishes for pulling and assembling its own observatory data — downloading data products through the NEON API, unzipping and stacking monthly packages into analysis-ready tables, and handling the awkward cases like eddy-covariance and airborne data. It reached 4.0.0 in June and 4.0.1 in July. What those releases contain is not recoverable from this feed: every recent entry is a one-line pointer saying the tag corresponds to a CRAN version, with the change log left in NEWS.md.
Release cadence has picked up sharply — 3.0.0 through 4.0.1 in under a year, against multi-year gaps before that — and two major-version bumps in that window normally imply breaking changes for anyone pinning the package in a reproducible workflow. Direction cannot be read from the entries themselves. The one substantive note in the feed is older and instructive about how this repository is used: a 2023 development tag that modified stackEddy() to avoid NEON API calls for internal processing pipelines, explicitly not for public use and never submitted to CRAN.
No prediction is supportable from these entries — they contain no description of any change. What can be said is that the 3.x-to-4.x jump and the tight 4.0.0-to-4.0.1 turnaround fit the usual shape of a major release followed by a fix, and anyone depending on the package should read NEWS.md rather than this feed.
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 hereR or neonUtilities.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
One paper, one release: the functional control chart package ships methods as they get published.
See all hereR alternatives → · See all neonUtilities alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. hereR and neonUtilities 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. hereR and neonUtilities 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.
Top hereR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "hereR alternatives" section above for the current picks, or visit /alternatives/herer for the full list with editorial commentary on each.
Top neonUtilities alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "neonUtilities alternatives" section above for the current picks, or visit /alternatives/neonutilities for the full list with editorial commentary on each.