All Versions
17
Latest Version
Avg Release Cycle
193 days
Latest Release
911 days ago

Changelog History
Page 1

  • v3.5.2 Changes

    September 25, 2020

    🚀 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.

  • v3.5.1 Changes

    June 29, 2020

    🚀 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.

  • v3.5.0 Changes

    June 06, 2020

    🚀 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.

  • v3.4.2 Changes

    May 04, 2020

    🛠 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.

  • v3.4.1 Changes

    December 28, 2019

    🛠 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.

  • v3.4.0 Changes

    October 25, 2019

    🚀 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 vesion 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.

  • v3.3.1 Changes

    May 04, 2020

    🛠 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.

  • v3.3.0 Changes

    May 01, 2019

    📚 This latest release makes Nominatim more configurable in custom installations. There is a new reverse-only mode for imports where forward search is not needed. In addition it is now possible to configure which OSM tags are taken into account by Nominatim. This allows to describe exactly which types of objects should be found in your instance. There are a number of example configurations for frequent use cases which you might use as a starting point. For more information read the installation documentation.

    🛠 As usual there are also a number of bug fixes and minor improvements. Details can be found in the ChangeLog file.

    🚀 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. However, when updating from 3.0.x, a full database reimport is strongly recommended. Updating from older releases is only possible with a database reimport.

    🚀 This will be the last release to support PHP 5.x and PostgreSQL < 9.3.

  • v3.2.1 Changes

    May 04, 2020

    🛠 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.

  • v3.2.0 Changes

    August 26, 2018

    🚀 This release brings two new output formats and a complete rewrite of the reverse geocoding algorithms.

    📚 We have added two new output formats for all API endpoints: geojson and geocodejson. The latter also exports for the first time address details by OSM admin level, which may be a help for all that want to process specific address parts further. Refer to the new documentation on output formats for details.

    🏗 The reverse algorithm has been largely rewritten to deliver better results in sparsely populated areas and when looking for administrative entities (town, country etc.). For details refer to the original outline of the algorithm. The new algorithm will also ensure that reverse geocoding coordinates on a road only return results that reference that road. Previously it was possible to end up on a nearby building that belonged to another road.

    👀 Next to these two major changes, there are a number of bug fixes and code cleanup. For a more complete list of changes, see the ChangeLog file.

    🚀 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. However, when updating from 3.0.x, a full database reimport is strongly recommended. Updating from older releases is only possible with a database reimport.