← Back to home
Comparison · DevOps

Nominatim vs SU2

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

Nominatim vs SU2: at a glance

FeatureNominatimSU2
SectorDevOpsDevOps
Velocity score0.00.0
Sparks · 30d00
Top themesgeocoding, openstreetmap, python-package, postcodescfd, adjoint-optimization, multiphysics, turbulence-models
Last editorial update3h ago2h ago
WebsiteVisit →Visit →

What is Nominatim?

The geocoder finished becoming a Python package, then got back to matching addresses

Nominatim releases a minor version every few months with fast hotfixes when an update path breaks. The 4.5-to-5.0 span was structural — becoming a pip-installable Python package, then removing the PHP frontend, bundled osm2pgsql and cmake scripts outright. Since then the work has returned to geocoding quality: a pattern-based postcode parser, building entrances in results, a restructured forward query parser, and separate processing tables for postcodes, interpolations and associatedStreet relations.

Read the full Nominatim trajectory →

What is SU2?

SU2 is growing from an aerodynamics solver into a coupled multiphysics optimizer

SU2 ships two or three releases a year under the same Harrier codename it has used since 8.0, each one a long list of contributed features rather than a single theme. The multiphysics work is the clearest thread: thermal expansion and centrifugal forces reached the FEA solver in 8.2.0, a coupled thermoelasticity solver followed, and 8.5.0 declares that coupling fully functional and adds its adjoint. Turbulence modelling gets steady attention in parallel, most recently a grey-area mitigation strategy for detached-eddy simulation.

Read the full SU2 trajectory →

Nominatim vs SU2: editorial side-by-side

N
Nominatim
DEVOPS
0.0

The geocoder finished becoming a Python package, then got back to matching addresses

◆ Current state

Nominatim releases a minor version every few months with fast hotfixes when an update path breaks. The 4.5-to-5.0 span was structural — becoming a pip-installable Python package, then removing the PHP frontend, bundled osm2pgsql and cmake scripts outright. Since then the work has returned to geocoding quality: a pattern-based postcode parser, building entrances in results, a restructured forward query parser, and separate processing tables for postcodes, interpolations and associatedStreet relations.

◆ Where it's heading

With the packaging migration finished, the project is optimizing the two things operators actually feel — how fast a search resolves and whether continuous OSM updates keep flowing. The 5.3.0 split into dedicated processing tables was explicitly about making updates faster and more reliable, and the two hotfixes that followed within a fortnight show how tightly that path is watched. Query-side work is trending toward recognizing input that is not in the database at all, as the postcode parser does.

◆ Prediction

Expect continued query-parser and update-pipeline optimization rather than new output types, since that is where every release since 5.0.0 has concentrated.

S
SU2
DEVOPS
0.0

SU2 is growing from an aerodynamics solver into a coupled multiphysics optimizer

◆ Current state

SU2 ships two or three releases a year under the same Harrier codename it has used since 8.0, each one a long list of contributed features rather than a single theme. The multiphysics work is the clearest thread: thermal expansion and centrifugal forces reached the FEA solver in 8.2.0, a coupled thermoelasticity solver followed, and 8.5.0 declares that coupling fully functional and adds its adjoint. Turbulence modelling gets steady attention in parallel, most recently a grey-area mitigation strategy for detached-eddy simulation.

◆ Where it's heading

Two directions are visible in the contribution pattern. Adjoint capability is being extended to each new physics as it lands, which matters because gradient-based design optimization is what distinguishes SU2 from a general-purpose solver — a coupled solver without an adjoint is only half the feature. Meanwhile the numerics substrate is being reworked underneath: FGCRODR replacing GMRES for Newton-Krylov adjoints, PaStiX 6, multigrid tuning, better default compiler flags, and an early GPU port of the FGMRES solver contributed through Google Summer of Code. Machine learning enters narrowly, through data-driven and physics-informed fluid models rather than as a general capability.

◆ Prediction

The GPU work so far covers one linear solver and is still labelled experimental, so the plausible next step is extending it to more of the solve rather than a new physics module. Expect the adjoint-follows-physics pattern to continue with whatever coupling lands next.

Alternatives to Nominatim and SU2

Other DevOps 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 Nominatim or SU2.

See all Nominatim alternatives → · See all SU2 alternatives →

Recent activity from Nominatim and SU2

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

  1. 3mo agoSU2SU2 8.5.0 completes thermoelastic coupling and adds its adjoint
  2. 3mo agoNominatim5.3.2 fixes a non-null constraint error during updates
  3. 4mo agoNominatim5.3.1 restores usable update speed for associatedStreet relations
  4. 4mo agoNominatim5.3.0 gives postcodes and interpolations their own processing tables
  5. 7mo agoSU2SU2 8.4.0 adds the FGCRODR solver and SST roughness boundaries
  6. 9mo agoNominatim5.2.0 returns building entrances and cuts SQL round-trips
  7. 11mo agoSU2SU2 8.3.0 lands a CUDA port of FGMRES and RBF mesh deformation
  8. 1y agoSU2SU2 8.2.0 adds a coupled thermoelasticity solver and PINN fluid models
  9. 1y agoNominatim5.1.0 recognizes postcodes that aren't in the OSM data
  10. 1y agoNominatim5.0.0 removes the PHP frontend, bundled osm2pgsql and cmake
  11. 1y agoSU2SU2 8.1.0 adds solid-to-solid conjugate heat transfer and custom inlets
  12. 2y agoSU2SU2 8.0.1 adds actuator-disk BEM, fixes CoDiPack adjoint locking

Frequently asked questions

What is the difference between Nominatim and SU2?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Nominatim and SU2 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 DevOps products to evaluate alongside.

What are the best alternatives to Nominatim?

Top Nominatim alternatives in DevOps are ranked by recent ship velocity. Browse the "Nominatim alternatives" section above for the current picks, or visit /alternatives/nominatim for the full list with editorial commentary on each.

What are the best alternatives to SU2?

Top SU2 alternatives in DevOps are ranked by recent ship velocity. Browse the "SU2 alternatives" section above for the current picks, or visit /alternatives/su2 for the full list with editorial commentary on each.