datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of GSODR and parzer — release velocity, themes, recent moves, and the top alternatives to consider.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
GSODR fetches and tidies NOAA Global Surface Summary of the Day weather data for R. The 4.0.0 release made nearest_stations() return a data.table of full station metadata plus distance in kilometres rather than a character vector of station IDs, with a documented one-liner for anyone who only wanted the IDs. Nothing has shipped since March 2024.
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
parzer converts messy coordinate strings — degrees, minutes, seconds, assorted symbols, arbitrary whitespace — into decimal degrees. Development is slow and sporadic, with three-year gaps between releases, and the work splits between C++ performance in the internal scrub() path and a long tail of parsing bugs. The most recent release, 0.4.4, fixed two genuinely dangerous ones: a leading space could silently drop a negative sign, and an E in a longitude string returned NA while a W parsed fine.
GSODR fetches and tidies NOAA Global Surface Summary of the Day weather data for R. The 4.0.0 release made nearest_stations() return a data.table of full station metadata plus distance in kilometres rather than a character vector of station IDs, with a documented one-liner for anyone who only wanted the IDs. Nothing has shipped since March 2024.
The package is mature and its releases read as upkeep: refreshing the internal ISD history database, dropping dependencies in favour of base and curl, and hardening the download path against station-year combinations that do not exist. The 4.0.0 change fits the same pattern of returning more structure by default rather than making callers query twice.
The most likely next release is another internal station-history refresh; there is no signal of new data sources or analysis features in these entries.
parzer converts messy coordinate strings — degrees, minutes, seconds, assorted symbols, arbitrary whitespace — into decimal degrees. Development is slow and sporadic, with three-year gaps between releases, and the work splits between C++ performance in the internal scrub() path and a long tail of parsing bugs. The most recent release, 0.4.4, fixed two genuinely dangerous ones: a leading space could silently drop a negative sign, and an E in a longitude string returned NA while a W parsed fine.
The package has settled its scope — 0.4.1 explicitly rewrote the documentation to say it parses coordinates rather than validates them — and now moves only when someone finds a string it mishandles. Recent work has also been about shedding weight: Rcpp dependence reduced, the C++ requirement dropped from DESCRIPTION, suggested dependencies removed, and the vignette builder moved to Quarto. Maintainership passed to a new maintainer in 2022 and the package has stayed within rOpenSci.
The next release will most likely be another batch of parsing edge cases reported by users, since that is what every release since 0.2.0 has been. Nothing in these entries points to new functionality.
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 GSODR or parzer.
The messy-date parser rewrote its core in Rust and came out 300x faster.
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
R help pages translated on demand by whichever LLM you point it at.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all GSODR alternatives → · See all parzer alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. GSODR and parzer 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. GSODR and parzer 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 GSODR alternatives in Analytics are ranked by recent ship velocity. Browse the "GSODR alternatives" section above for the current picks, or visit /alternatives/gsodr for the full list with editorial commentary on each.
Top parzer alternatives in Analytics are ranked by recent ship velocity. Browse the "parzer alternatives" section above for the current picks, or visit /alternatives/parzer for the full list with editorial commentary on each.