← Back to home
Comparison · Analytics

enderecobr vs ggguides

A side-by-side editorial comparison of enderecobr and ggguides — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

enderecobr vs ggguides: at a glance

Featureenderecobrggguides
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesaddress-standardisation, brazil, rust, performanceggplot2, legends, r-package, bugfix-train
Last editorial update19m ago1h ago
WebsiteVisit →Visit →

What is enderecobr?

Brazilian address standardisation moves its core to Rust, betting on throughput over pure R

enderecobr standardises Brazilian address fields — street types, neighbourhoods, states, postcodes, house numbers — into consistent forms so records from different registries can be compared. It comes out of the ipeaGIT ecosystem and its API is a family of padronizar_* functions plus one padronizar_enderecos() that runs them together. The 0.5.0 release rewrote those standardisation functions in Rust with a documented speedup.

Read the full enderecobr trajectory →

What is ggguides?

Three releases in one day to make legend positioning finally do what the docs said.

ggguides is a helper layer over ggplot2's guide system, exposing legend placement and styling through small named functions instead of raw theme() calls. On 23 April 2026 it shipped 1.1.7, 1.1.8 and 1.1.9 within thirteen hours, each fixing a different path by which the justification argument silently did nothing. The common root cause is that ggplot2 3.5 split legend.justification into side-specific theme elements, and ggguides was still writing to the generic fallback.

Read the full ggguides trajectory →

enderecobr vs ggguides: editorial side-by-side

E
enderecobr
ANALYTICS
0.0

Brazilian address standardisation moves its core to Rust, betting on throughput over pure R

◆ Current state

enderecobr standardises Brazilian address fields — street types, neighbourhoods, states, postcodes, house numbers — into consistent forms so records from different registries can be compared. It comes out of the ipeaGIT ecosystem and its API is a family of padronizar_* functions plus one padronizar_enderecos() that runs them together. The 0.5.0 release rewrote those standardisation functions in Rust with a documented speedup.

◆ Where it's heading

Two years of releases were about control and correctness: new formato arguments letting callers choose state names or abbreviations, integers or characters for house numbers, and a run of fixes for numbers mangled by thousands separators. That work settled the semantics. With the behaviour pinned down, the Rust rewrite becomes the natural next move, and the release pairs it with new matching rules for the two messiest fields, neighbourhoods and street names.

◆ Prediction

The rewrite covers the standardisation functions specifically, so the remaining pure-R paths around them are the likely next targets, alongside continued rule additions for street and neighbourhood variants.

G
ggguides
ANALYTICS
0.0

Three releases in one day to make legend positioning finally do what the docs said.

◆ Current state

ggguides is a helper layer over ggplot2's guide system, exposing legend placement and styling through small named functions instead of raw theme() calls. On 23 April 2026 it shipped 1.1.7, 1.1.8 and 1.1.9 within thirteen hours, each fixing a different path by which the justification argument silently did nothing. The common root cause is that ggplot2 3.5 split legend.justification into side-specific theme elements, and ggguides was still writing to the generic fallback.

◆ Where it's heading

The package is in the phase where a wrapper meets the reality of the API it wraps. All three same-day releases are the same bug found in successive entry points: legend_inside(), then the four side functions, then legend_style(by = ). Along the way the fix work produced a real feature, a justification argument on the side legend functions. The pattern of a single reporter driving three consecutive releases suggests the surface is being audited rather than randomly patched.

◆ Prediction

Expect a consolidation release that audits the remaining theme elements ggguides writes to against ggplot2 3.5 semantics, rather than another single-path fix.

Alternatives to enderecobr and ggguides

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 enderecobr or ggguides.

See all enderecobr alternatives → · See all ggguides alternatives →

Recent activity from enderecobr and ggguides

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agoggguideslegend_style(by=) justification now reaches the whole-plot theme
  2. 3mo agoggguidesSide legend functions gain justification and target the right theme element
  3. 3mo agoggguideslegend_inside() justification now moves the legend as documented
  4. 7mo agoenderecobrStandardisation functions rewritten in Rust
  5. 8mo agoggguidesLegend reordering, key overrides and colorbar styling added
  6. 1y agoenderecobrNamespaced calls no longer error on internal warnings
  7. 1y agoenderecobrHouse numbers gain output format control, thousands-separator bug fixed
  8. 1y agoenderecobrStates can be standardised to full names or abbreviations
  9. 1y agoenderecobrAuthor added to package metadata
  10. 1y agoenderecobrStreet-type functions added and output columns given a naming convention

Frequently asked questions

What is the difference between enderecobr and ggguides?

Both compete on the same themes — r-package — within Analytics. enderecobr and ggguides 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 enderecobr better than ggguides?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. enderecobr and ggguides 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 enderecobr?

Top enderecobr alternatives in Analytics are ranked by recent ship velocity. Browse the "enderecobr alternatives" section above for the current picks, or visit /alternatives/enderecobr for the full list with editorial commentary on each.

What are the best alternatives to ggguides?

Top ggguides alternatives in Analytics are ranked by recent ship velocity. Browse the "ggguides alternatives" section above for the current picks, or visit /alternatives/ggguides for the full list with editorial commentary on each.