Importing and Updating the Database
The following instructions explain how to create a Nominatim database from an OSM planet file and how to keep the database up to date. It is assumed that you have already successfully installed the Nominatim software itself, if not return to the installation page.
Configuration setup in settings/local.php
The Nominatim server can be customized via the file
in the build directory. Note that this is a PHP file, so it must always
start like this:
without any leading spaces.
There are lots of configuration settings you can tweak. Have a look
settings/default.php for a full list. Most should have a sensible default.
If you plan to import a large dataset (e.g. Europe, North America, planet),
you should also enable flatnode storage of node locations. With this
setting enabled, node coordinates are stored in a simple file instead
of the database. This will save you import time and disk storage.
Add to your
Replace the second part with a suitable path on your system and make sure the directory exists. There should be at least 40GB of free space.
Downloading additional data
Wikipedia can be used as an optional auxiliary data source to help indicate the importance of osm features. Nominatim will work without this information but it will improve the quality of the results if this is installed. This data is available as a binary download:
cd $NOMINATIM_SOURCE_DIR/data wget https://www.nominatim.org/data/wikipedia_article.sql.bin wget https://www.nominatim.org/data/wikipedia_redirect.sql.bin
Combined the 2 files are around 1.5GB and add around 30GB to the install size of nominatim. They also increase the install time by an hour or so.
NOTE: you'll need to download the Wikipedia rankings before performing the initial import of the data if you want the rankings applied to the loaded data.
Nominatim can use postcodes from an external source to improve searches that involve a UK postcode. This data can be optionally downloaded:
cd $NOMINATIM_SOURCE_DIR/data wget https://www.nominatim.org/data/gb_postcode_data.sql.gz
Initial import of the data
Important: first try the import with a small excerpt, for example from Geofabrik.
Download the data to import and load the data with the following command:
./utils/setup.php --osm-file <data file> --all [--osm2pgsql-cache 28000] 2>&1 | tee setup.log
--osm2pgsql-cache parameter is optional but strongly recommended for
planet imports. It sets the node cache size for the osm2pgsql import part
-C parameter in osm2pgsql help). As a rule of thumb, this should be
about the same size as the file you are importing but never more than
2/3 of RAM available. If your machine starts swapping reduce the size.
Computing word frequency for search terms can improve the performance of forward geocoding in particular under high load as it helps Postgres' query planner to make the right decisions. To recompute word counts run:
This will take a couple of hours for a full planet installation. You can also defer that step to a later point in time when you realise that performance becomes an issue. Just make sure that updates are stopped before running this function.
If you want to be able to search for places by their type through special key phrases you also need to enable these key phrases like this:
./utils/specialphrases.php --wiki-import > specialphrases.sql psql -d nominatim -f specialphrases.sql
Note that this command downloads the phrases from the wiki link above.
Installing Tiger housenumber data for the US
Nominatim is able to use the official TIGER address set to complement the OSM house number data in the US. You can add TIGER data to your own Nominatim instance by following these steps:
Install the GDAL library and python bindings and the unzip tool
sudo apt-get install python-gdal unzip
sudo yum install gdal-python unzip
Get preprocessed TIGER 2017 data and unpack it into the data directory in your Nominatim sources:
cd Nominatim/data wget https://nominatim.org/data/tiger2017-nominatim-preprocessed.tar.gz tar xf tiger2017-nominatim-preprocessed.tar.gz
Import the data into your Nominatim database:
Enable use of the Tiger data in your
Apply the new settings:
./utils/setup.php --create-functions --enable-diff-updates --create-partition-functions
The entire US adds about 10GB to your database.
You can also process the data from the original TIGER data to create the SQL files, Nominatim needs for the import:
Get the TIGER 2017 data. You will need the EDGES files (3,234 zip files, 11GB total).
wget -r ftp://ftp2.census.gov/geo/tiger/TIGER2017/EDGES/
Convert the data into SQL statements:
./utils/imports.php --parse-tiger <tiger edge data directory>
Be warned that this can take quite a long time. After this process is finished,
the same preprocessed files as above are available in
There are many different possibilities to update your Nominatim database.
The following section describes how to keep it up-to-date with Pyosmium.
For a list of other methods see the output of
Installing the newest version of Pyosmium
It is recommended to install Pyosmium via pip. Run (as the same user who will later run the updates):
pip install --user osmium
Nominatim needs a tool called
pyosmium-get-updates, which comes with
Pyosmium. You need to tell Nominatim where to find it. Add the
following line to your
The path above is fine if you used the
--user parameter with pip.
user with your user name.
Setting up the update process
Next the update needs to be initialised. By default Nominatim is configured to update using the global minutely diffs.
If you want a different update source you will need to add some settings
settings/local.php. For example, to use the daily country extracts
diffs for Ireland from geofabrik add the following:
// base URL of the replication service @define('CONST_Replication_Url', 'https://download.geofabrik.de/europe/ireland-and-northern-ireland-updates'); // How often upstream publishes diffs @define('CONST_Replication_Update_Interval', '86400'); // How long to sleep if no update found yet @define('CONST_Replication_Recheck_Interval', '900');
To set up the update process now run the following command:
It outputs the date where updates will start. Recheck that this date is what you expect.
The --init-updates command needs to be rerun whenever the replication service is changed.
The following command will keep your database constantly up to date:
(Note that even though the old name "import-osmosis-all" has been kept for compatibility reasons, Osmosis is not required to run this - it uses pyosmium behind the scenes.)
If you have imported multiple country extracts and want to keep them up-to-date, have a look at the script in issue #60.