3 This page contains generic installation instructions for Nominatim and its
4 prerequisites. There are also step-by-step instructions available for
5 the following operating systems:
7 * [Ubuntu 20.04](../appendix/Install-on-Ubuntu-20.md)
8 * [Ubuntu 18.04](../appendix/Install-on-Ubuntu-18.md)
9 * [CentOS 8](../appendix/Install-on-Centos-8.md)
11 These OS-specific instructions can also be found in executable form
12 in the `vagrant/` directory.
14 Users have created instructions for other frameworks. We haven't tested those
15 and can't offer support.
17 * [Docker](https://github.com/mediagis/nominatim-docker)
18 * [Docker on Kubernetes](https://github.com/peter-evans/nominatim-k8s)
19 * [Kubernetes with Helm](https://github.com/robjuz/helm-charts/blob/master/charts/nominatim/README.md)
20 * [Ansible](https://github.com/synthesio/infra-ansible-nominatim)
27 For larger installations you **must have** PostgreSQL 11+ and Postgis 3+
28 otherwise import and queries will be slow to the point of being unusable.
29 Query performance has marked improvements with PostgrSQL 13+ and Postgis 3.2+.
33 * [cmake](https://cmake.org/)
34 * [expat](https://libexpat.github.io/)
35 * [proj](https://proj.org/)
36 * [bzip2](http://www.bzip.org/)
37 * [zlib](https://www.zlib.net/)
38 * [ICU](http://site.icu-project.org/)
39 * [Boost libraries](https://www.boost.org/), including system and filesystem
40 * PostgreSQL client libraries
41 * a recent C++ compiler (gcc 5+ or Clang 3.8+)
43 For running Nominatim:
45 * [PostgreSQL](https://www.postgresql.org) (9.6+ will work, 11+ strongly recommended)
46 * [PostGIS](https://postgis.net) (2.2+ will work, 3.0+ strongly recommended)
47 * [Python 3](https://www.python.org/) (3.6+)
48 * [Python Typing Extensions](https://github.com/python/typing_extensions)
49 * [Psycopg2](https://www.psycopg.org) (2.7+)
50 * [Python Dotenv](https://github.com/theskumar/python-dotenv)
51 * [psutil](https://github.com/giampaolo/psutil)
52 * [Jinja2](https://palletsprojects.com/p/jinja/)
53 * [PyICU](https://pypi.org/project/PyICU/)
54 * [PyYaml](https://pyyaml.org/) (5.1+)
55 * [datrie](https://github.com/pytries/datrie)
56 * [PHP](https://php.net) (7.0 or later)
58 * PHP-intl (bundled with PHP)
59 * PHP-cgi (for running queries from the command line)
61 For running continuous updates:
63 * [pyosmium](https://osmcode.org/pyosmium/)
65 For dependencies for running tests and building documentation, see
66 the [Development section](../develop/Development-Environment.md).
70 A minimum of 2GB of RAM is required or installation will fail. For a full
71 planet import 64GB of RAM or more are strongly recommended. Do not report
72 out of memory problems if you have less than 64GB RAM.
74 For a full planet install you will need at least 900GB of hard disk space.
75 Take into account that the OSM database is growing fast.
76 Fast disks are essential. Using NVME disks is recommended.
78 Even on a well configured machine the import of a full planet takes
79 around 2 days. On traditional spinning disks, 7-8 days are more realistic.
81 ## Tuning the PostgreSQL database
83 You might want to tune your PostgreSQL installation so that the later steps
84 make best use of your hardware. You should tune the following parameters in
85 your `postgresql.conf` file.
88 maintenance_work_mem = (10GB)
89 autovacuum_work_mem = 2GB
91 effective_cache_size = (24GB)
92 synchronous_commit = off
94 checkpoint_timeout = 10min
95 checkpoint_completion_target = 0.9
97 The numbers in brackets behind some parameters seem to work fine for
98 64GB RAM machine. Adjust to your setup. A higher number for `max_wal_size`
99 means that PostgreSQL needs to run checkpoints less often but it does require
100 the additional space on your disk.
102 Autovacuum must not be switched off because it ensures that the
103 tables are frequently analysed. If your machine has very little memory,
104 you might consider setting:
106 autovacuum_max_workers = 1
108 and even reduce `autovacuum_work_mem` further. This will reduce the amount
109 of memory that autovacuum takes away from the import process.
111 For the initial import, you should also set:
114 full_page_writes = off
116 Don't forget to reenable them after the initial import or you risk database
120 ## Downloading and building Nominatim
122 ### Downloading the latest release
124 You can download the [latest release from nominatim.org](https://nominatim.org/downloads/).
125 The release contains all necessary files. Just unpack it.
127 ### Downloading the latest development version
129 If you want to install latest development version from github, make sure to
130 also check out the osm2pgsql subproject:
133 git clone --recursive https://github.com/openstreetmap/Nominatim.git
136 The development version does not include the country grid. Download it separately:
139 wget -O Nominatim/data/country_osm_grid.sql.gz https://www.nominatim.org/data/country_grid.sql.gz
142 ### Building Nominatim
144 The code must be built in a separate directory. Create the directory and
152 Nominatim uses cmake and make for building. Assuming that you have created the
153 build at the same level as the Nominatim source directory run:
162 The default installation no longer compiles the PostgreSQL module that
163 is needed for the legacy tokenizer from older Nominatim versions. If you
164 are upgrading an older database or want to run the
165 [legacy tokenizer](../customize/Tokenizers.md#legacy-tokenizer) for
166 some other reason, you need to enable the PostgreSQL module via
167 cmake: `cmake -DBUILD_MODULE=on ../Nominatim`. To compile the module
168 you need to have the server development headers for PostgreSQL installed.
169 On Ubuntu/Debian run: `sudo apt install postgresql-server-dev-<postgresql version>`
172 Nominatim installs itself into `/usr/local` per default. To choose a different
173 installation directory add `-DCMAKE_INSTALL_PREFIX=<install root>` to the
174 cmake command. Make sure that the `bin` directory is available in your path
178 export PATH=<install root>/bin:$PATH
181 Now continue with [importing the database](Import.md).