WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
L1centrality vs nominatimlite
A side-by-side editorial comparison of L1centrality and nominatimlite — release velocity, themes, recent moves, and the top alternatives to consider.
L1centrality vs nominatimlite: at a glance
What is L1centrality?
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
L1centrality implements L1 centrality and prestige for graphs, including group, local, and neighbourhood variants plus MDS-based visualization. The measure set has been stable since 0.3.0; the work since has gone into interfaces around it — S3 classes with print and summary methods, plot methods for every result class, and in 0.5.0 both multi-group evaluation and multicore computation for the local variant. The two releases since have been a warning-message pass and a typo pass.
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.
L1centrality vs nominatimlite: editorial side-by-side
L1centrality
0.0INFRA · APIS
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
◆ Current state
L1centrality implements L1 centrality and prestige for graphs, including group, local, and neighbourhood variants plus MDS-based visualization. The measure set has been stable since 0.3.0; the work since has gone into interfaces around it — S3 classes with print and summary methods, plot methods for every result class, and in 0.5.0 both multi-group evaluation and multicore computation for the local variant. The two releases since have been a warning-message pass and a typo pass.
◆ Where it's heading
The package has moved from defining measures to operationalizing them. 0.5.0 was the inflection: parallel local computation and list-valued group input both target users running these measures over many vertex sets or large graphs rather than illustrating them on one. The same release renamed weight_transform and eta to edge_weight_transform and vertex_weight, and added an explicit message when a distance matrix is received — the signature of a maintainer fielding the same misuse repeatedly.
◆ Prediction
The last two releases carry no functional change, so the near-term path is maintenance rather than new measures; a 0.6.0 would most likely extend parallelism beyond L1centLOC to the other computationally heavy variants.
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.
Alternatives to L1centrality and nominatimlite
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 L1centrality or nominatimlite.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all L1centrality alternatives → · See all nominatimlite alternatives →
Recent activity from L1centrality and nominatimlite
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoL1centralityTypo fixes only
- 2mo agonominatimliteInternal refactor with no public API change; minimum R now 4.1.0
- 3mo agoL1centralityWarning message wording updated
- 3mo agoL1centralityMulti-group prominence and multicore local centrality
- 5mo agonominatimliteSession caching and 1.2s throttling for API calls
- 7mo agonominatimliteMinor fixes to reverse geocoding functions
- 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
- 1y agoL1centralityHandles unnamed vertices; quantile type pinned
- 1y agonominatimliteDocumentation update
- 1y agoL1centralityS3 classes for all results, plus a Gini coefficient
- 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 L1centrality and nominatimlite?
They serve adjacent needs but don't currently overlap on shipped themes. L1centrality and nominatimlite 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 L1centrality better than nominatimlite?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. L1centrality and nominatimlite 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to L1centrality?
Top L1centrality alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "L1centrality alternatives" section above for the current picks, or visit /alternatives/l1centrality for the full list with editorial commentary on each.
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.