Version 3.7.0

This is a transitional release towards version 4 of Nominatim. It introduces major changes in the organisation of the code and how Nominatim should be installed:

• Nominatim can now be installed with make install. Keeping the source and build directories is no longer necessary.
• A new single nominatim command-line tool replaces the various functions of the PHP utility scripts.
• A new project directory collects configuration and installation-specific data for each Nominatim database.
• Configuration files switch to dotenv format.

This release still maintains the compatibility with the old scripts and structures to make an update of existing installations easier. The only exception is the configuration file format which needs to be converted on update. For more information about migrating from older 3.x.x versions, have a look at the Migration guide in the documentation.

Version 3.6.0

Work has continued on improving the address output of results. Administrative boundaries are no longer assigned a fixed type but their context is taken into account. This solves many issues we had with the urban/rural divide. addr:* tags are now fully taken into account when searching and when displaying the results of your search. Especially rural US will benefit from that.

The HTML output has been removed from the API. We have created a separate project nominatim-ui which implements the former debugging interface as a simple javascript application. The documentation has hints on how to migrate to nominatim-ui should you need the HTML output on your own installation.

A full list of changes can be found as usual in the Changelog.md.

If you want to update from 3.x.x, there is a database migration path described in the migration guide. However note that migration to 3.6.0 is rather extensive and you can only benefit from the improved addressing after a full reimport. Migrating from 3.1.0 can be done simply by following the migration guide nonetheless. When updating from 3.0.x, a full database reimport is strongly recommended. Updating from older releases is only possible with a database reimport.

Version 3.5.2

This is a maintenance release which fixes a couple of issues with the new Ubuntu 20.04 release. For a detailed list of changes see Changelog.md.

Nominatim 3.5.x installations can be updated directly without changes to the database. Make sure to run ./utils/setup.php --create-functions --enable-diff-updates after setting up the new release to apply all changes to the SQL code. For upgrading from older versions please consult the migration guide.

Version 3.5.1

This bug-fix release fixes two important issues with osm2pgsql:

• osm2pgsql might get stuck during updates when running with Postgresql 12
• osm2pgsql might hang when processing extremely complex multipolygons

All users should update to this latest version when they run regular updates on their database or plan to import new data that includes North America. Nominatim 3.5.0 installations can be updated directly without changes to the database. For upgrading from older versions please consult the migration guide.

Version 3.5.0

This release brings improvements to how address ranks are computed and place nodes and boundaries are linked. You can now expect better results in the classification of address details. It is now also possible to have country-specific address ranking to account for local deviations.

Thanks to last years Google Summer of Code, the Wikipedia ranking has been improved. It is now based on a recent Wikipedia dump with a lot more pages and Nominatim can also take into account Wikidata tags when linking.

The code has seen more restructuring. The C indexer has been replaces by a simplified Python script and we have started to split up the larger SQL functions into more readable chunks.

A full list of changes can be found as usual in the Changelog.md.

If you want to update from 3.x.x, there is a database migration path described in the migration guide. Migrating from 3.1.0 can be done without problems. When updating from 3.0.x, a full database reimport is strongly recommended. Updating from older releases is only possible with a database reimport.

Release 3.4.2

This is a bugfix release which fixes an important security vulnerability in the website code.

The /details endpoint fails to properly sanitize user input and uses it as is in an SQL query. This allows an attacker to inject arbitrary SQL code including querying and updating the database.

All installations still running a 3.4.x release should update to this new version. No changes to the database are necessary. Simply download and build the new version, copy over your settings/local.php file and point your webserver to the new version.

Release 3.3.1

This is a bugfix release which fixes an important security vulnerability in the website code.

The /details endpoint fails to properly sanitize user input and uses it as is in an SQL query. This allows an attacker to inject arbitrary SQL code including querying and updating the database.

All installations still running a 3.3.0 release should update to this new version. No changes to the database are necessary. Simply download and build the new version, copy over your settings/local.php file and point your webserver to the new version.

Release 3.2.1

This is a bugfix release which fixes an important security vulnerability in the website code.

The /details endpoint fails to properly sanitize user input and uses it as is in an SQL query. This allows an attacker to inject arbitrary SQL code including querying and updating the database.

All installations still running a 3.2.0 release should update to this new version. No changes to the database are necessary. Simply download and build the new version, copy over your settings/local.php file and point your webserver to the new version.

Release 3.4.1

This is a bugfix release for the bundled osm2pgsql. It fixes two important bugs:

• Nominatim updates might hang due to a race between deletion and insertion of objects.
• Address points might get lost in the Nominatim database when they are updated in OpenStreetMap.

This release also fixes a typo in the supplied import style files (see #1606 (comment)). If you have custom style files then you might have to fix this typo as well.

Databases running on 3.4.0 can be updated to the new release without any special provisions. If you run regular updates, you should consider a full reimport at some point to get back the missing address points.

If you want to update from 3.x.x, there is a database migration path described in the migration guide. Migrating from 3.1.0 can be done without problems. When updating from 3.0.x, a full database reimport is strongly recommended. Updating from older releases is only possible with a database reimport.

Release 3.4.0

This release brings some improvements to the internal database structure that further reduce the size of the database. It also contains a fix for osm2pgsql where the import sometimes runs out of memory, especially when no flatnode files are used. If you plan to import a new database without flatnode files, an upgrade is strongly recommended.

As usual, there are some smaller improvements to documentation and the search algorithm. Details can be found in Changelog.md.

Please note that starting with this version PostgreSQL >= 9.3, PostGIS >= 2.2 and PHP >= 7.0 are required.

If you want to update from 3.x.x, there is a database migration path described in the migration guide. Migrating from 3.1.0 can be done without problems. When updating from 3.0.x, a full database reimport is strongly recommended. Updating from older releases is only possible with a database reimport.