2018-08-24 00:12:10 +03:00
|
|
|
# Basic Installation
|
|
|
|
|
2016-06-09 00:03:11 +03:00
|
|
|
This page contains generic installation instructions for Nominatim and its
|
|
|
|
prerequisites. There are also step-by-step instructions available for
|
|
|
|
the following operating systems:
|
|
|
|
|
2020-05-07 01:36:13 +03:00
|
|
|
* [Ubuntu 20.04](../appendix/Install-on-Ubuntu-20.md)
|
2018-08-24 22:33:24 +03:00
|
|
|
* [Ubuntu 18.04](../appendix/Install-on-Ubuntu-18.md)
|
2020-05-07 22:55:04 +03:00
|
|
|
* [CentOS 8](../appendix/Install-on-Centos-8.md)
|
2018-01-15 01:43:15 +03:00
|
|
|
* [CentOS 7.2](../appendix/Install-on-Centos-7.md)
|
2016-06-09 00:03:11 +03:00
|
|
|
|
|
|
|
These OS-specific instructions can also be found in executable form
|
|
|
|
in the `vagrant/` directory.
|
|
|
|
|
2018-02-21 20:31:16 +03:00
|
|
|
Users have created instructions for other frameworks. We haven't tested those
|
|
|
|
and can't offer support.
|
|
|
|
|
|
|
|
* [Docker](https://github.com/mediagis/nominatim-docker)
|
|
|
|
* [Docker on Kubernetes](https://github.com/peter-evans/nominatim-k8s)
|
|
|
|
* [Ansible](https://github.com/synthesio/infra-ansible-nominatim)
|
|
|
|
|
2018-08-24 00:12:10 +03:00
|
|
|
## Prerequisites
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2018-08-24 00:12:10 +03:00
|
|
|
### Software
|
2016-06-09 00:03:11 +03:00
|
|
|
|
|
|
|
For compiling:
|
|
|
|
|
|
|
|
* [cmake](https://cmake.org/)
|
2020-01-25 00:53:26 +03:00
|
|
|
* [expat](https://libexpat.github.io/)
|
|
|
|
* [proj](https://proj.org/)
|
|
|
|
* [bzip2](http://www.bzip.org/)
|
|
|
|
* [zlib](https://www.zlib.net/)
|
2021-03-22 03:46:46 +03:00
|
|
|
* [ICU](http://site.icu-project.org/)
|
2020-01-25 00:53:26 +03:00
|
|
|
* [Boost libraries](https://www.boost.org/), including system and filesystem
|
|
|
|
* PostgreSQL client libraries
|
2020-01-22 14:02:38 +03:00
|
|
|
* a recent C++ compiler (gcc 5+ or Clang 3.8+)
|
2016-06-09 00:03:11 +03:00
|
|
|
|
|
|
|
For running Nominatim:
|
|
|
|
|
2021-04-01 15:37:20 +03:00
|
|
|
* [PostgreSQL](https://www.postgresql.org) (9.3+ will work, 11+ strongly recommended)
|
2020-09-17 16:11:01 +03:00
|
|
|
* [PostGIS](https://postgis.net) (2.2+)
|
2021-01-15 12:38:28 +03:00
|
|
|
* [Python 3](https://www.python.org/) (3.5+)
|
2021-02-25 19:36:31 +03:00
|
|
|
* [Psycopg2](https://www.psycopg.org) (2.7+)
|
2021-02-10 13:15:21 +03:00
|
|
|
* [Python Dotenv](https://github.com/theskumar/python-dotenv)
|
2021-03-01 11:07:49 +03:00
|
|
|
* [psutil](https://github.com/giampaolo/psutil)
|
2021-03-03 19:48:14 +03:00
|
|
|
* [Jinja2](https://palletsprojects.com/p/jinja/)
|
2021-03-22 03:46:46 +03:00
|
|
|
* [PyICU](https://pypi.org/project/PyICU/)
|
2019-05-21 14:55:16 +03:00
|
|
|
* [PHP](https://php.net) (7.0 or later)
|
2016-06-09 00:03:11 +03:00
|
|
|
* PHP-pgsql
|
2017-06-01 20:34:16 +03:00
|
|
|
* PHP-intl (bundled with PHP)
|
2021-02-24 19:21:45 +03:00
|
|
|
* PHP-cgi (for running queries from the command line)
|
2016-06-09 00:03:11 +03:00
|
|
|
|
|
|
|
For running continuous updates:
|
|
|
|
|
2021-02-10 13:15:21 +03:00
|
|
|
* [pyosmium](https://osmcode.org/pyosmium/)
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-17 10:54:46 +03:00
|
|
|
For dependencies for running tests and building documentation, see
|
|
|
|
the [Development section](../develop/Development-Environment.md).
|
2020-01-25 00:53:26 +03:00
|
|
|
|
2018-08-24 00:12:10 +03:00
|
|
|
### Hardware
|
2016-06-09 00:03:11 +03:00
|
|
|
|
|
|
|
A minimum of 2GB of RAM is required or installation will fail. For a full
|
2019-11-24 12:31:34 +03:00
|
|
|
planet import 64GB of RAM or more are strongly recommended. Do not report
|
|
|
|
out of memory problems if you have less than 64GB RAM.
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-12-08 10:57:46 +03:00
|
|
|
For a full planet install you will need at least 900GB of hard disk space.
|
2020-12-11 19:08:13 +03:00
|
|
|
Take into account that the OSM database is growing fast.
|
2020-12-08 10:57:46 +03:00
|
|
|
Fast disks are essential. Using NVME disks is recommended.
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2019-11-24 12:31:34 +03:00
|
|
|
Even on a well configured machine the import of a full planet takes
|
2020-12-08 10:57:46 +03:00
|
|
|
around 2 days. On traditional spinning disks, 7-8 days are more realistic.
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-16 00:51:25 +03:00
|
|
|
## Tuning the PostgreSQL database
|
2016-06-09 00:03:11 +03:00
|
|
|
|
|
|
|
You might want to tune your PostgreSQL installation so that the later steps
|
|
|
|
make best use of your hardware. You should tune the following parameters in
|
|
|
|
your `postgresql.conf` file.
|
|
|
|
|
2019-11-24 12:31:34 +03:00
|
|
|
shared_buffers = 2GB
|
|
|
|
maintenance_work_mem = (10GB)
|
|
|
|
autovacuum_work_mem = 2GB
|
|
|
|
work_mem = (50MB)
|
|
|
|
effective_cache_size = (24GB)
|
2016-06-09 00:03:11 +03:00
|
|
|
synchronous_commit = off
|
2016-08-04 23:17:05 +03:00
|
|
|
checkpoint_segments = 100 # only for postgresql <= 9.4
|
2019-11-24 12:31:34 +03:00
|
|
|
max_wal_size = 1GB # postgresql > 9.4
|
2016-06-09 00:03:11 +03:00
|
|
|
checkpoint_timeout = 10min
|
|
|
|
checkpoint_completion_target = 0.9
|
|
|
|
|
|
|
|
The numbers in brackets behind some parameters seem to work fine for
|
2019-11-24 12:31:34 +03:00
|
|
|
64GB RAM machine. Adjust to your setup. A higher number for `max_wal_size`
|
|
|
|
means that PostgreSQL needs to run checkpoints less often but it does require
|
|
|
|
the additional space on your disk.
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-01-22 14:02:38 +03:00
|
|
|
Autovacuum must not be switched off because it ensures that the
|
|
|
|
tables are frequently analysed. If your machine has very little memory,
|
|
|
|
you might consider setting:
|
|
|
|
|
|
|
|
autovacuum_max_workers = 1
|
|
|
|
|
|
|
|
and even reduce `autovacuum_work_mem` further. This will reduce the amount
|
|
|
|
of memory that autovacuum takes away from the import process.
|
|
|
|
|
2016-06-09 00:03:11 +03:00
|
|
|
For the initial import, you should also set:
|
|
|
|
|
|
|
|
fsync = off
|
|
|
|
full_page_writes = off
|
|
|
|
|
|
|
|
Don't forget to reenable them after the initial import or you risk database
|
2020-01-22 14:02:38 +03:00
|
|
|
corruption.
|
|
|
|
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-16 00:51:25 +03:00
|
|
|
## Downloading and building Nominatim
|
|
|
|
|
|
|
|
### Downloading the latest release
|
|
|
|
|
|
|
|
You can download the [latest release from nominatim.org](https://nominatim.org/downloads/).
|
|
|
|
The release contains all necessary files. Just unpack it.
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-16 00:51:25 +03:00
|
|
|
### Downloading the latest development version
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-16 00:51:25 +03:00
|
|
|
If you want to install latest development version from github, make sure to
|
|
|
|
also check out the osm2pgsql subproject:
|
|
|
|
|
|
|
|
```
|
|
|
|
git clone --recursive git://github.com/openstreetmap/Nominatim.git
|
|
|
|
```
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-16 00:51:25 +03:00
|
|
|
The development version does not include the country grid. Download it separately:
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-05-13 11:13:15 +03:00
|
|
|
```
|
2020-09-16 00:51:25 +03:00
|
|
|
wget -O Nominatim/data/country_osm_grid.sql.gz https://www.nominatim.org/data/country_grid.sql.gz
|
|
|
|
```
|
|
|
|
|
|
|
|
### Building Nominatim
|
|
|
|
|
|
|
|
The code must be built in a separate directory. Create the directory and
|
|
|
|
change into it.
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-16 00:51:25 +03:00
|
|
|
```
|
|
|
|
mkdir build
|
|
|
|
cd build
|
2020-05-13 11:13:15 +03:00
|
|
|
```
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-16 00:51:25 +03:00
|
|
|
Nominatim uses cmake and make for building. Assuming that you have created the
|
|
|
|
build at the same level as the Nominatim source directory run:
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-09-16 00:51:25 +03:00
|
|
|
```
|
|
|
|
cmake ../Nominatim
|
|
|
|
make
|
2021-02-10 13:15:21 +03:00
|
|
|
sudo make install
|
|
|
|
```
|
|
|
|
|
|
|
|
Nominatim installs itself into `/usr/local` per default. To choose a different
|
|
|
|
installation directory add `-DCMAKE_INSTALL_PREFIX=<install root>` to the
|
|
|
|
cmake command. Make sure that the `bin` directory is available in your path
|
|
|
|
in that case, e.g.
|
|
|
|
|
|
|
|
```
|
|
|
|
export PATH=<install root>/bin:$PATH
|
2020-09-16 00:51:25 +03:00
|
|
|
```
|
2016-06-09 00:03:11 +03:00
|
|
|
|
2020-06-20 04:48:07 +03:00
|
|
|
Now continue with [importing the database](Import.md).
|