### Installing the required packages
The Nominatim frontend is best run from its own virtual environment. If
-you have already created one for the database backend during
-[installation](Installation.md#Building-Nominatim), you can use that. Otherwise
+you have already created one for the database backend during the
+[installation](Installation.md#building-nominatim), you can use that. Otherwise
create one now with:
```sh
```
This is in particular useful when the database runs on a different server.
-See [Advanced installations](../admin/Advanced-Installations.md#importing-nominatim-to-an-external-postgresql-database) for details.
+See [Advanced installations](../admin/Advanced-Installations.md#using-an-external-postgresql-database) for details.
There are no other configuration options for the legacy tokenizer. All
normalization functions are hard-coded.
## Place identification
-The [details](NominatimAPI.md#nominatim_api.core.NominatimAPI.details) and
-[lookup](NominatimAPI.md#nominatim_api.core.NominatimAPI.lookup) functions
+The [details](NominatimAPI.md#nominatim_api.NominatimAPI.details) and
+[lookup](NominatimAPI.md#nominatim_api.NominatimAPI.lookup) functions
require references to places in the database. Below the possible
types for place identification are listed. All types are dataclasses.
@property
def config(self) -> Configuration:
- """ Provide read-only access to the [configuration](#Configuration)
+ """ Provide read-only access to the [configuration](Configuration.md)
used by the API.
"""
return self._async_api.config
local_name: Optional[str] = None
""" Place holder for localization of this address part. See
- [Localization](#localization) below.
+ [Localization](Result-Handling.md#localization) below.
"""