← Back to home
Comparison · Infra & APIs

FoRecoML vs nominatimlite

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

FoRecoML vs nominatimlite: at a glance

FeatureFoRecoMLnominatimlite
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, machine-learning, hierarchical-reconciliation, time-seriesr, geocoding, openstreetmap, nominatim
Last editorial update58m ago2d ago
WebsiteVisit →Visit →

What is FoRecoML?

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

Read the full FoRecoML trajectory →

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.

Read the full nominatimlite trajectory →

FoRecoML vs nominatimlite: editorial side-by-side

F
FoRecoML
INFRA · APIS
0.0

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

◆ Current state

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

◆ Where it's heading

This package is being built as a satellite, not a competitor. Adopting FoReco's exported new_foreco_class() constructor within days of that class appearing means FoRecoML results drop straight into the same print, summary, plot, and components methods as analytically reconciled ones — which is what makes machine-learning and classical reconciliation directly comparable in a single workflow. The 1.1.1 argument-validation work landed in the same minute as the equivalent change in FoReco, so the two are being maintained as one release train.

◆ Prediction

With the integration work done, the next release is more likely to add or expose machine-learning approaches than to keep reshaping output; the structured summary already enumerates features and trained models, which suggests inspection tooling is where attention has been.

N
nominatimlite
INFRA · APIS
0.0

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 FoRecoML 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 FoRecoML or nominatimlite.

See all FoRecoML alternatives → · See all nominatimlite alternatives →

Recent activity from FoRecoML and nominatimlite

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

  1. 1mo agoFoRecoMLStructured print and summary for fitted reconciliation models
  2. 1mo agoFoRecoMLAdopts FoReco's foreco class for all reconciliation output
  3. 2mo agonominatimliteInternal refactor with no public API change; minimum R now 4.1.0
  4. 3mo agoFoRecoMLMachine-learning forecast reconciliation arrives on CRAN
  5. 5mo agonominatimliteSession caching and 1.2s throttling for API calls
  6. 7mo agonominatimliteMinor fixes to reverse geocoding functions
  7. 1y agonominatimliteDocumentation update
  8. 2y agonominatimliteFix crash on long OSM IDs in address lookup
  9. 2y agonominatimliteStructured queries, local server support and JSONV2 output

Frequently asked questions

What is the difference between FoRecoML and nominatimlite?

They serve adjacent needs but don't currently overlap on shipped themes. FoRecoML 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 FoRecoML better than nominatimlite?

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

Top FoRecoML alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FoRecoML alternatives" section above for the current picks, or visit /alternatives/forecoml 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.