← Back to home
Comparison · Analytics

enderecobr vs TrialEmulation

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

Shared themes:r-package

enderecobr vs TrialEmulation: at a glance

FeatureenderecobrTrialEmulation
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesaddress-standardisation, brazil, rust, performancecausal-inference, target-trial-emulation, duckdb, maintenance
Last editorial update17m 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 TrialEmulation?

Target trial emulation held steady by dependency maintenance, not new methods.

TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.

Read the full TrialEmulation trajectory →

enderecobr vs TrialEmulation: 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.

T0.0

Target trial emulation held steady by dependency maintenance, not new methods.

◆ Current state

TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.

◆ Where it's heading

The package is being kept installable rather than extended. Its dependency surface, duckdb for storage, parglm for fitting, testthat for checks, generates most of the release traffic, and CRAN archiving parglm forced two separate releases three months apart to fully excise it. The version numbering, still in the 0.0.4.x range after years, suggests the maintainers do not consider the API settled enough to promote.

◆ Prediction

Further releases will most likely be triggered by upstream dependency changes; the entries give no signal on when methodological work resumes.

Alternatives to enderecobr and TrialEmulation

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 TrialEmulation.

See all enderecobr alternatives → · See all TrialEmulation alternatives →

Recent activity from enderecobr and TrialEmulation

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

  1. 4mo agoTrialEmulationDocumentation references to the archived parglm removed
  2. 7mo agoTrialEmulationparglm dependency dropped after CRAN archiving
  3. 7mo agoenderecobrStandardisation functions rewritten in Rust
  4. 9mo agoTrialEmulationTest fixes for updated testthat, plus link updates
  5. 9mo agoTrialEmulationCompatibility fixes ahead of testthat 3.3.0
  6. 1y agoTrialEmulationTests updated for duckdb 1.3.0 sampling; R 4.1 now required
  7. 1y agoTrialEmulationTests updated for duckdb 1.2.0 sampling changes
  8. 1y agoenderecobrNamespaced calls no longer error on internal warnings
  9. 1y agoenderecobrHouse numbers gain output format control, thousands-separator bug fixed
  10. 1y agoenderecobrStates can be standardised to full names or abbreviations
  11. 1y agoenderecobrAuthor added to package metadata
  12. 1y agoenderecobrStreet-type functions added and output columns given a naming convention

Frequently asked questions

What is the difference between enderecobr and TrialEmulation?

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

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

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