r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of naijR and nodbi — release velocity, themes, recent moves, and the top alternatives to consider.
naijR is assembling the Nigerian reference data R analysts otherwise hand-code every time.
naijR packages Nigeria-specific data and utilities for R: state and Local Government Area names, choropleth mapping, and phone-number repair. The newest release adds `ngdist`, a UNDP-sourced distance matrix covering road distances between all 37 state capitals, with `ng_distance()` for pairwise lookup in kilometres or miles. The spatial foundation was rebased on sf in 0.6.0, retiring the rgdal-era code.
One document API over six databases, and every release is spent absorbing their JSON engines' churn
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
naijR packages Nigeria-specific data and utilities for R: state and Local Government Area names, choropleth mapping, and phone-number repair. The newest release adds `ngdist`, a UNDP-sourced distance matrix covering road distances between all 37 state capitals, with `ng_distance()` for pairwise lookup in kilometres or miles. The spatial foundation was rebased on sf in 0.6.0, retiring the rgdal-era code.
The package keeps converting local knowledge into checked data structures. LGA names shared between states got `disambiguate_lga()` with interactive selection; misspellings in the original reference document were corrected; mobile numbers with inconsistent separators, or with the letter O typed for zero, get repaired rather than rejected. Each addition targets a specific way Nigerian administrative or contact data breaks generic tooling, which is a narrower and more durable brief than most country packages take on.
With a distance matrix now in place alongside the boundary and naming data, the plausible next step is more derived geography of the same kind rather than new utility functions, though the entries do not say which dataset is next.
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
Two threads dominate. The first is performance, pursued backend by backend: fast direct NDJSON import moved from DuckDB-only to SQLite and PostgreSQL, query refactors chasing each DuckDB release, and the removal of expensive tree-walking where a cheaper path exists. The second is making results predictable — consistent column types, version checks on the database backend, clearer messages when a Postgres database does not exist yet or when column names contain the dots nodbi reserves for JSON paths.
Given that most recent releases are triggered by DuckDB and RSQLite version changes, the next one likely follows the same pattern — adopting a new JSON function or working around a slow one. The duplicate-_id handling added in 0.14.0 suggests NDJSON ingestion edge cases are the current active area.
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 naijR or nodbi.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. naijR and nodbi 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. naijR and nodbi 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 naijR alternatives in Analytics are ranked by recent ship velocity. Browse the "naijR alternatives" section above for the current picks, or visit /alternatives/naijr for the full list with editorial commentary on each.
Top nodbi alternatives in Analytics are ranked by recent ship velocity. Browse the "nodbi alternatives" section above for the current picks, or visit /alternatives/nodbi for the full list with editorial commentary on each.