Aerospike
Aerospike shipped a coordinated CVE train across four release branches in one afternoon
Comparison · DevOps
Nominatim vs GeoTools
A side-by-side editorial comparison of Nominatim and GeoTools — release velocity, themes, recent moves, and the top alternatives to consider.
Nominatim vs GeoTools: at a glance
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.
What is GeoTools?
GeoTools is migrating off dead Java imaging infrastructure that the whole GeoServer stack sits on
GeoTools runs three release branches at once — 33.x for Java 11, 34.x for Java 17, and now 35.0 — with the same GEOT ticket numbers appearing across all of them as fixes get backported. The 34.0 release in October 2025 made Java 17 the stable line; 35.0 in June 2026 is the structural one, migrating the raster core to ImageN, moving to Jakarta EE 10 and Jackson 3, and dropping the H2-based indexes and gt-jdbc-h2 entirely. Cloud-native formats are the other active area: GeoParquet, PMTiles and DGGS support have all arrived within the last year.
Nominatim vs GeoTools: editorial side-by-side
Nominatim
0.0DEVOPS
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.
GeoTools
0.0DEVOPS
GeoTools is migrating off dead Java imaging infrastructure that the whole GeoServer stack sits on
◆ Current state
GeoTools runs three release branches at once — 33.x for Java 11, 34.x for Java 17, and now 35.0 — with the same GEOT ticket numbers appearing across all of them as fixes get backported. The 34.0 release in October 2025 made Java 17 the stable line; 35.0 in June 2026 is the structural one, migrating the raster core to ImageN, moving to Jakarta EE 10 and Jackson 3, and dropping the H2-based indexes and gt-jdbc-h2 entirely. Cloud-native formats are the other active area: GeoParquet, PMTiles and DGGS support have all arrived within the last year.
◆ Where it's heading
The library is replacing foundations it can no longer maintain. Java Advanced Imaging has been unmaintained for well over a decade, and the move to ImageN — staged across 34.0's JAITools-to-JAI-Ext step and 35.0's full migration — is the exit from that dependency. The same pass removes H2, upgrades every JDBC driver in the tree, and standardises entity resolution across the library. Format work runs alongside it and points at object storage: GeoParquet with AWS credential-chain auth and covering-bbox filtering, PMTiles reading, curved geometries in GeoPackage.
◆ Prediction
With ImageN and Jakarta EE 10 landed in 35.0, expect the 35.x patches to be dominated by fallout from those migrations in the raster and mosaic paths, where the release already shows reprojection and overview-decimation bugs. The 33.x Java 11 branch is receiving only backports and looks close to retirement.
Alternatives to Nominatim and GeoTools
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 GeoTools.
Firebird
Firebird maintains three release branches at once and ships the same fixes to all of them
SU2
SU2 is growing from an aerodynamics solver into a coupled multiphysics optimizer
Psi4
Psi4 is closing the gap with ORCA on the methods that decide which code a lab installs
libosmium
libosmium is a stable OSM parsing library whose main work now is shedding old dependencies
OpenMM
OpenMM keeps opening new simulation domains while pushing more of the run onto the GPU
See all Nominatim alternatives → · See all GeoTools alternatives →
Recent activity from Nominatim and GeoTools
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoGeoToolsGeoTools 35.0 migrates to ImageN and Jakarta EE 10, drops H2 ⚡
- 2mo agoGeoToolsGeoTools 34.4 adds DefaultEntityResolver, fixes WFS connection leak
- 3mo agoNominatim5.3.2 fixes a non-null constraint error during updates
- 4mo agoNominatim5.3.1 restores usable update speed for associatedStreet relations
- 4mo agoNominatim5.3.0 gives postcodes and interpolations their own processing tables
- 5mo agoGeoToolsGeoTools 33.5 backports ImageMosaic PamDataset support
- 6mo agoGeoToolsGeoTools 34.2 adds AWS credential chain auth for GeoParquet on S3
- 7mo agoGeoToolsGeoTools 33.4 backports PostGIS and GeoPackage fixes to Java 11
- 9mo agoNominatim5.2.0 returns building entrances and cuts SQL round-trips
- 9mo agoGeoToolsGeoTools 34.0 makes Java 17 stable and adds a PMTiles datastore
- 1y agoNominatim5.1.0 recognizes postcodes that aren't in the OSM data
- 1y agoNominatim5.0.0 removes the PHP frontend, bundled osm2pgsql and cmake
Frequently asked questions
What is the difference between Nominatim and GeoTools?
They serve adjacent needs but don't currently overlap on shipped themes. Nominatim and GeoTools 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 GeoTools?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Nominatim and GeoTools 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 GeoTools?
Top GeoTools alternatives in DevOps are ranked by recent ship velocity. Browse the "GeoTools alternatives" section above for the current picks, or visit /alternatives/geotools for the full list with editorial commentary on each.