Skip to content

Releases

Version 5.3.3

Choose a tag to compare

@lonvia lonvia released this 14 Oct 21:48
Immutable release. Only release title and notes can be modified.

This is a minor release which makes Nominatim compatible with the latest version of SQLAlchemy and fixes a couple of smaller issues:

  • fix display of rank 11 boundaries
  • do not search for countries when country restriction is in place
  • improve reverse geocoding near overlapping POIs
  • improve API parameter validation
  • restrict overlong query terms
  • improve escaping of API output
  • fix searching for POIs parented to unnamed streets (thanks @pawank925)
  • fix code-formatting for newer pygments version
  • CLI: make entrances work for reverse and lookup calls
  • fix reported parent street for TIGER results in reverse search

There are also updates for Hungarian abbreviations (thanks @Janjko) and address level handling in Slovakia.

One breaking change is that the debug view is no longer enabled by default as it may leak information about your server. To reenable debugging, set NOMINATIM_SERVE_DEBUG_OUTPUT=yes in your .env configuration.

If you are running Nominatim 5.3.x we recommend to update. Updating the software is sufficient, no migrations are necessary,

Version 5.3.2

Choose a tag to compare

@lonvia lonvia released this 19 Apr 09:05

This is a bug-fix release which fixes a non-null constraint error that may occur while running updates.

If you are running Nominatim 5.3.x with updates, it is strongly advised to update. Updating the software and migrating to the new version will be sufficient to make updates work again, if you have run into the constraint error. No database reimport is necessary.

Version 5.3.1

Choose a tag to compare

@lonvia lonvia released this 10 Apr 14:21

This release fixes an issue with updates of associatedStreet relations being unusably slow (see #4070).

If you are running Nominatim 5.3.0 with updates, please update to this latest release immediately. Updating the software and migrating to the new version will be sufficient to make updates work again. No database reimport is necessary.

Version 5.3.0

Choose a tag to compare

@lonvia lonvia released this 03 Apr 21:01

This release brings improvements to the computation of postcodes, interpolations and handling of associatedStreet relations. They all now have their separate processing tables making updates faster and more reliable. addr:interpolation is now also supported in conjunction with addr:housenumber.

The CLI tool has received a number of smaller updates: the layer parameter can now be used from the CLI search (thanks @Itz-Agasta), TIGER data can now be added even when the database is frozen (thanks @AyushDharDubey) and there is a new command to grant read rights to another user on the database (thanks @Itz-Agasta).

CI now also runs tests on Windows. We are still not officially supporting Windows but if you feel bold, please do try Nominatim out on Windows and report back issues.

There are a lot of smaller changes to improve performance and fix little glitches with the output. A complete list of all changes can as always be found in the Changelog.

If you are already using the Python frontend and pip installation method, then updating is straightforward. If not, it is strongly recommended that you update to version 4.5 first, switch frontend and installation code and then update to the newest Nominatim. As always, read through the migration guide before updating.

Many thanks to all the people who contributed to this release and haven't been mentioned yet: @harithilmi, @bgo-eiu, @kad-link, @jayaddison, @daishu0000, @vytas5. Also thanks to those who helped improving the documentation: @28Deepakpandey, @Aditya30ag, @AmmarYasser455, @jonas-endter-optimax-energy, @vai67

Version 5.2.0

Choose a tag to compare

@lonvia lonvia released this 29 Oct 10:40

This release adds support for returning entrances of buildings and areas to Nominatim. Entrances may help routers to find a better start and end point for your route. See the announcement blog post for details. Many thanks to @emlove for implementing this feature.

The forward query parser has been restructured and optimised, so that less SQL queries need to be send for a single search request. You should see a marked performance improvement especially around full address searches.

The osm2pgsql import style now makes sure to add always add any tags that Nominatim needs for internal processing. It is no longer necessary to add them manually in your custom style. This avoids bad surprises after a long import. If you have a line flex.add_for_extratags('required') in your custom style, then this will now throw an error. Simply remove the line and all will work as before.

There are a number of other smaller user-facing changes to this release:

A more complete list of changes can as always be found in the Changelog.

If you are already using the Python frontend and pip installation method, then updating is straightforward. If not, it is strongly recommended that you update to version 4.5 first, switch frontend and installation code and then update to the newest Nominatim. As always, read through the migration guide before updating.

Finally a big thank you to all the other contributors to this release: @Johannes-Andersen, @emmanuel-ferdman, @asharmalik19, @dave-meyer, @hasandiwan

Version 5.1.0

Choose a tag to compare

@lonvia lonvia released this 01 Apr 09:56

This release adds a pattern-based postcode parser to the query frontend. This means that postcodes no longer need to be present in the OSM database in order to be found. Any postcode that corresponds to the postcode format of a country will be recognised. The most notable use case here are US ZIP+4 postcodes.

The search algorithm has received a lot of minor tweaks, improving postcode search and search of complex addresses.

If you are using the geocodejson output format, then you can now get the extra information from extra OSM tags just like for the other output formats.

A more complete list of changes can be found in the Changelog.

If you are already using the Python frontend and pip installation method, then updating is straightforward. If not, it is strongly recommended that you update to version 4.5 first, switch frontend and installation code and then update to the newest Nominatim. As always, read through the migration guide before updating.

Many thanks to all the contributors to this release, especially the many first-time contributors: @shoorick, @IvanShift, @mhsrn21, @eumiro, @otbutz, @TuringVerified

Version 5.0.0

Choose a tag to compare

@lonvia lonvia released this 05 Feb 14:16

This release finishes the mutation of Nominatim into a Python package. The PHP frontend, bundled osm2pgsql and cmake build scripts have been removed, making Nominatim easier to install and maintain.

Also in this release, the osm2pgsql import style configuration has been largely be rewritten. If you are using one of the built-in styles, this will not make much of a difference. If you are maintaining your own custom style, however, this should become much easier. Have a look at the documentation of the pull request for an overview of the changes. The changes are backwards-compatible, so your old scripts will keep working for now.

Finally, Nominatim has a new hook for adding pre-processing functions for incoming search queries, allowing to apply custom filtering. The first filter to use this new functionality breaks up Japanese addresses into their parts. Many thanks to @miku0 for this code.

A more complete list of changes can be found in the Changelog.

If you are already using the Python frontend and pip installation method, then updating is straightforward. If not, it is strongly recommended that you update to version 4.5 first, switch frontend and installation code and then update to the new version 5.0. As always, read through the migration guide before updating.

Version 4.5.0

Choose a tag to compare

@lonvia lonvia released this 12 Sep 12:15

This release transforms Nominatim into a pure Python package and makes it available on pypi.org. Installing Nominatim now becomes as easy as pip install nominatim-db nominatim-api. The current release still supports the old way of building the source using cmake, so that you can still use your existing deployment code. Installation via pip will become the only mode of operation in the upcoming version 5.0. So please adapt your installation soon.

Other new features include the possibility to customize API output for web installations, a streamlined file format for wiki importances, improvements to ordering results according to how well address parts match and a more consistent assignment of countries in disputed areas.

A more complete list of changes can be found in the Changelog.

Updating from any version 4.x.x to the new release is straightforward. Please follow the instructions from the migration guide. Updating from older versions is possible but not recommended. Please note that the migration to 4.3.0 requires building a new index needed by the frontend. It is therefore not recommended to migrate while a machine is in active use.

This release marks the transition to the upcoming release 5.0. The following features are now deprecated and will be removed in the next release:

  • PHP frontend. Please switch to the newer Python frontend instead.
  • Legacy tokenizer. If your database still uses this tokenizer, you need to reimport using the ICU tokenizer
  • Installation via CMake. Switch to using pip install instead.
  • Bundeling of osm2pgsql. Use a stock osm2pgsql version 1.8 or higher. Ubuntu 24.04 and Debian >= 11 have appropriate packages. The packages of older Ubuntu version are too old and you need to compile a newer osm2pgsql from source.

This is also the last release to support PostgreSQL 9.6 and 10 as well as Postgis 2.x.

Version 4.4.1

Choose a tag to compare

@lonvia lonvia released this 20 Aug 15:15

This is a bug-fix release which fixes two issues with the update process:

  • Nominatim will no longer propagate changes around overly long ways. The ways will still be imported but no longer hold up the update process.
  • House numbers in address interpolations are restricted to a range of 0-999999. All other house numbers are silently ignored when building interpolations. This fixes an error where overly large house numbers result in a out-of-range error in Postgresql.

The release also resolves an Python module import error that appeared when SQLAlchemy 1.4 was installed together with Psycopg 3.

A more complete list of changes can be found in the Changelog.

Updating from any version 4.x.x to the new release is straightforward. Please follow the instructions from the migration guide. Updating from older versions is possible but not recommended. Please note that the migration to 4.3.0 requires building a new index needed by the frontend. It is therefore not recommended to migrate while a machine is in active use.

Version 4.4.0

Choose a tag to compare

@lonvia lonvia released this 07 Mar 15:34

This release brings many bug fixes and performance improvements for the new Python frontend introduced in the last version. It can now be considered stable and has become the frontend recommended to be used for new installations. You find deployment guides in the documentation.

A new feature in this release is experimental support for exporting a Nominatim database to SQLite. The SQLite database can then be used with the new Python frontend or when using the Nominatim library. For more information about this, watch the talk at SotM-EU 2023 or read the blog posts.

A more complete list of changes can be found in the Changelog. Many thanks to the external contributors @robbe-haesendonck (for imports without superuser rights), @lujoh (for a command for cleaning deleted relations) and @pawel-wroniszewski (for fixing postcode validation).

Updating from any version 4.x.x to the new release is straightforward. Please follow the instructions from the migration guide. Updating from older versions is possible but not recommended. Please note that the migration to 4.3.0 requires building a new index needed by the frontend. It is therefore not recommended to migrate while a machine is in active use.