tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
ijtiff vs nodbi
A side-by-side editorial comparison of ijtiff and nodbi — release velocity, themes, recent moves, and the top alternatives to consider.
ijtiff vs nodbi: at a glance
What is ijtiff?
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
ijtiff reads and writes TIFF files the way ImageJ writes them, which ordinary R TIFF readers get wrong — multi-channel, multi-frame, and unusual bit depths. The 3.1.x line is dominated by memory correctness in the C tag-handling layer, alongside dropping the large imager dependency from the display path. Cadence is sporadic, with multi-year gaps.
What is nodbi?
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.
ijtiff vs nodbi: editorial side-by-side
ijtiff
0.0ANALYTICS
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
◆ Current state
ijtiff reads and writes TIFF files the way ImageJ writes them, which ordinary R TIFF readers get wrong — multi-channel, multi-frame, and unusual bit depths. The 3.1.x line is dominated by memory correctness in the C tag-handling layer, alongside dropping the large imager dependency from the display path. Cadence is sporadic, with multi-year gaps.
◆ Where it's heading
Two threads run through the window. The C layer is being hardened — memory leaks in tag handling, buffer cleanup, PROTECT errors, validation of malformed files — which is the kind of work that surfaces when a package gets run against real-world files at volume. Separately, the R layer is shedding dependencies, with base graphics replacing imager for display. Both make the package cheaper and safer to depend on rather than more capable.
◆ Prediction
Expect continued C-level correctness work rather than format features, since three of the last three substantive releases were memory or compiler fixes.
nodbi
0.0ANALYTICS
One document API over six databases, and every release is spent absorbing their JSON engines' churn
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to ijtiff and nodbi
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 ijtiff or nodbi.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all ijtiff alternatives → · See all nodbi alternatives →
Recent activity from ijtiff and nodbi
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agonodbijsonb_tree adopted; $in string queries and duplicate _id handling fixed
- 1y agonodbiDuckDB version parsing and listfields fix
- 1y agonodbidocdb_query reworked for DuckDB 1.3.0
- 1y agoijtiffPROTECT-error and documentation fixes across 3.1.1-3.1.3
- 1y agonodbiNDJSON writing delegated to DuckDB's internal function
- 1y agoijtiffDrops the imager dependency; fixes tag-handling memory leaks
- 1y agonodbiQuery results get consistent column types; fast NDJSON import reaches SQLite and Postgres ⚡
- 1y agonodbiQuery and file-import speedups via newer DuckDB features
- 3y agoijtiffMoves to rlang::abort() and away from magrittr
- 3y agoijtiffFixes NEWS.md headings
- 5y agoijtiffCompatibility with libtiff using C99 stdint.h
- 5y agoijtiffQuiets pkg-config warnings; drops LazyData
Frequently asked questions
What is the difference between ijtiff and nodbi?
They serve adjacent needs but don't currently overlap on shipped themes. ijtiff 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.
Is ijtiff better than nodbi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ijtiff 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.
What are the best alternatives to ijtiff?
Top ijtiff alternatives in Analytics are ranked by recent ship velocity. Browse the "ijtiff alternatives" section above for the current picks, or visit /alternatives/ijtiff for the full list with editorial commentary on each.
What are the best alternatives to nodbi?
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.