phyloatlas
An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.
Comparison · Infra & APIs
nominatimlite vs projoint
A side-by-side editorial comparison of nominatimlite and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
nominatimlite vs projoint: at a glance
What is nominatimlite?
nominatimlite's real work was self-hosting and caching; 0.6.0 is an internal refactor with no API change
nominatimlite is a dependency-light R client for the Nominatim geocoding API, returning results as plain data frames or sf objects. The features that define it landed in 0.4.0 — structured queries, local Nominatim server support, and JSONV2 output — and 0.5.0 added session-scoped caching plus a 1.2-second inter-request delay to stay within the public API's usage policy. 0.6.0 in June 2026 changed no public behaviour.
What is projoint?
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
nominatimlite vs projoint: editorial side-by-side
nominatimlite
0.0INFRA · APIS
nominatimlite's real work was self-hosting and caching; 0.6.0 is an internal refactor with no API change
◆ Current state
nominatimlite is a dependency-light R client for the Nominatim geocoding API, returning results as plain data frames or sf objects. The features that define it landed in 0.4.0 — structured queries, local Nominatim server support, and JSONV2 output — and 0.5.0 added session-scoped caching plus a 1.2-second inter-request delay to stay within the public API's usage policy. 0.6.0 in June 2026 changed no public behaviour.
◆ Where it's heading
The package has settled. Recent effort goes to being a well-behaved API citizen and to internal consistency: 0.6.0 raised the minimum R to 4.1.0 and refactored URL construction, progress handling, coordinate validation and output preparation with AI assistance, explicitly leaving the public API untouched. That refactor is part of a sweep across the same maintainer's packages in the same weeks.
◆ Prediction
With the API surface stable and rate-limiting handled, future releases most likely track upstream Nominatim endpoint changes, as 0.4.0 did for v4.4.0. Nothing in the entries points to new query capabilities.
projoint
2.5INFRA · APIS
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
◆ Current state
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
◆ Where it's heading
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
◆ Prediction
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
Alternatives to nominatimlite and projoint
Other Infra & APIs 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 nominatimlite or projoint.
OpenLand
Land-change analysis in R that has spent six years defending one download link.
FoRecoML
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
FoReco
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
L1centrality
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
See all nominatimlite alternatives → · See all projoint alternatives →
Recent activity from nominatimlite and projoint
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
- 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
- 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
- 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
- 1mo agoprojointCitation metadata updated with the CRAN DOI
- 2mo agonominatimliteInternal refactor with no public API change; minimum R now 4.1.0
- 5mo agonominatimliteSession caching and 1.2s throttling for API calls
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
- 7mo agonominatimliteMinor fixes to reverse geocoding functions
- 1y agonominatimliteDocumentation update
- 2y agonominatimliteFix crash on long OSM IDs in address lookup
- 2y agonominatimliteStructured queries, local server support and JSONV2 output
Frequently asked questions
What is the difference between nominatimlite and projoint?
They serve adjacent needs but don't currently overlap on shipped themes. projoint is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is nominatimlite better than projoint?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. projoint is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to nominatimlite?
Top nominatimlite alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nominatimlite alternatives" section above for the current picks, or visit /alternatives/nominatimlite for the full list with editorial commentary on each.
What are the best alternatives to projoint?
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.