osmextract
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
Comparison · Analytics
datefixR vs parzer
A side-by-side editorial comparison of datefixR and parzer — release velocity, themes, recent moves, and the top alternatives to consider.
datefixR vs parzer: at a glance
What is datefixR?
The messy-date parser rewrote its core in Rust and came out 300x faster.
datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.
What is parzer?
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.
datefixR vs parzer: editorial side-by-side
datefixR
0.0ANALYTICS
The messy-date parser rewrote its core in Rust and came out 300x faster.
◆ Current state
datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.
◆ Where it's heading
Two long arcs meet here. The first is localization: Russian, Indonesian, German, Spanish month abbreviations, and experimental Roman numeral months accumulated release by release, with full translation of user-facing messages treated as a goal rather than a bonus. The second is the migration off R for the parsing hot path — internals began moving to C++ around 1.3.1 before the Rust rewrite replaced that work entirely. The 2.0.1 regressions show the cost of that move, since behavior that was implicit in the R implementation had to be re-specified.
◆ Prediction
The Rust core is one release into stabilization and 2.0.1 was entirely regression repair, so expect further correctness fixes against pre-2.0.0 behavior before any new format support lands.
parzer
0.0ANALYTICS
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to datefixR and parzer
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 datefixR or parzer.
nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
poissonreg
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
S7
S7 has stopped adding surface and started proving it holds up against R itself.
torchvision
R's torchvision is porting PyTorch's vision stack one task at a time — instance segmentation just landed.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
See all datefixR alternatives → · See all parzer alternatives →
Recent activity from datefixR and parzer
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agodatefixRRust rewrite regressions repaired, silent NA casting stopped
- 11mo agodatefixRParsing core rewritten in Rust for a 300x speedup ⚡
- 1y agoparzerFixes dropped negative signs and mis-parsed E longitudes
- 1y agodatefixRIndonesian month names and translations added
- 2y agodatefixR'ene' and 'ener' recognized as January
- 3y agodatefixRRussian localization, Roman numeral months, Windows freeze fix
- 3y agodatefixRExcel leap-year offset and single-digit day fixes
- 4y agoparzerScope clarified: parsing, not coordinate validation
- 5y agoparzerFaster scrub(); works around non-UTF8 locales on Windows
- 5y agoparzerFixes factor conversion in parse_llstr() on older R
- 5y agoparzerparse_llstr() parses latitude and longitude from one string
- 6y agoparzerMore degree symbols recognised; NA handling fixed in C++
Frequently asked questions
What is the difference between datefixR and parzer?
They serve adjacent needs but don't currently overlap on shipped themes. datefixR 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.
Is datefixR better than parzer?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. datefixR 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.
What are the best alternatives to datefixR?
Top datefixR alternatives in Analytics are ranked by recent ship velocity. Browse the "datefixR alternatives" section above for the current picks, or visit /alternatives/datefixr for the full list with editorial commentary on each.
What are the best alternatives to parzer?
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.