fix typo in Tokenizers.md

CONTRIBUTING.md

@@ -87,6 +87,7 @@ Checklist for releases:
 * [ ] increase versions in
   * `src/nominatim_api/version.py`
   * `src/nominatim_db/version.py`
+  * CMakeLists.txt
 * [ ] update `ChangeLog` (copy information from patch releases from release branch)
 * [ ] complete `docs/admin/Migration.md`
 * [ ] update EOL dates in `SECURITY.md`

ChangeLog

@@ -1,28 +1,3 @@
-5.0.0
- * increase required versions for PostgreSQL (12+), PostGIS (3.0+)
- * remove installation via cmake and debundle osm2pgsql
- * remove deprecated PHP frontend
- * remove deprecated legacy tokenizer
- * add configurable pre-processing of queries
- * add query pre-processor to split up Japanese addresses
- * rewrite of osm2pgsql style implementation
-   (also adds support for osm2pgsql-themepark)
- * reduce the number of SQL queries needed to complete a 'lookup' call
- * improve computation of centroid for lines with only two points
- * improve bbox output for postcode areas
- * improve result order by returning the largest object when other things are
-   equal
- * add fallback for reverse geocoding to default country tables
- * exclude postcode areas from reverse geocoding
- * disable search endpoint when database is reverse-only (regression)
- * minor performance improvements to area split algorithm
- * switch table and index creation to use autocommit mode to avoid deadlocks
- * drop overly long ways during import
- * restrict automatic migrations to versions 4.3+
- * switch linting from pylint to flake8
- * switch tests to use a wikimedia test file in the new CSV style
- * various fixes and improvements to documentation
-
 4.5.0
  * allow building Nominatim as a pip package
  * make osm2pgsql building optional

SECURITY.md

@@ -9,10 +9,10 @@ versions.
 
 | Version | End of support for security updates |
 | ------- | ----------------------------------- |
-| 5.0.x   | 2027-02-06
 | 4.5.x   | 2026-09-12                          |
 | 4.4.x   | 2026-03-07                          |
 | 4.3.x   | 2025-09-07                          |
+| 4.2.x   | 2024-11-24                          |
 
 ## Reporting a Vulnerability
 

docs/admin/Migration.md

@@ -9,15 +9,19 @@ the following steps:
 * Update the frontend: `pip install -U nominatim-api`
 * (optionally) Restart updates
 
+If you are still using CMake for the installation of Nominatim, then you
+need to update the software in one step before migrating the database.
+It is not recommended to do this while the machine is serving requests.
+
 Below you find additional migrations and hints about other structural and
 breaking changes. **Please read them before running the migration.**
 
 !!! note
     If you are migrating from a version <4.3, you need to install 4.3
-    and migrate to 4.3 first. Then you can migrate to the current
+    first and migrate to 4.3 first. Then you can migrate to the current
     version. It is strongly recommended to do a reimport instead.
 
-## 4.5.0 -> 5.0.0
+## 4.5.0 -> master
 
 ### PHP frontend removed
 
@@ -29,42 +33,6 @@ needed. It currently omits a warning and does otherwise nothing. It will be
 removed in later versions of Nominatim. So make sure you remove it from your
 scripts.
 
-### CMake building removed
-
-Nominatim can now only be installed via pip. Please follow the installation
-instructions for the current version to change to pip.
-
-### osm2pgsql no longer vendored in
-
-Nominatim no longer ships its own version of osm2pgsql. Please install a
-stock version of osm2pgsql from your distribution. See the
-[installation instruction for osm2pgsql](https://osm2pgsql.org/doc/install.html)
-for details. A minimum version of 1.8 is required. The current stable versions
-of Ubuntu and Debian already ship with an appropriate versions. For older
-installation, you may have to compile a newer osm2pgsql yourself.
-
-### Legacy tokenizer removed
-
-The `legacy` tokenizer is no longer enabled. This tokenizer has been superseded
-by the `ICU` tokenizer a long time ago. In the unlikely case that your database
-still uses the `legacy` tokenizer, you must reimport your database.
-
-### osm2pgsql style overhauled
-
-There are some fundamental changes to how customized osm2pgsql styles should
-be written. The changes are mostly backwards compatible, i.e. custom styles
-should still work with the new implementation. The only exception is a
-customization of the `process_tags()` function. This function is no longer
-considered public and neither are the helper functions used in it.
-They currently still work but will be removed at some point. If you have
-been making changes to `process_tags`, please review your style and try
-to switch to the new convenience functions.
-
-For more information on the changes, see the
-[pull request](https://github.com/osm-search/Nominatim/pull/3615)
-and read the new
-[customization documentation](https://nominatim.org/release-docs/latest/customize/Import-Styles/).
-
 ## 4.4.0 -> 4.5.0
 
 ### New structure for Python packages

docs/admin/Update.md

@@ -68,10 +68,10 @@ the update interval no new data has been published yet, it will go to sleep
 until the next expected update and only then attempt to download the next batch.
 
 The one-time mode is particularly useful if you want to run updates continuously
-but need to schedule other work in between updates. For example, you might
-want to regularly recompute postcodes -- a process that
-must not be run while updates are in progress. An update script refreshing
-postcodes regularly might look like this:
+but need to schedule other work in between updates. For example, the main
+service at osm.org uses it, to regularly recompute postcodes -- a process that
+must not be run while updates are in progress. Its update script
+looks like this:
 
 ```sh
 #!/bin/bash
@@ -109,19 +109,17 @@ Unit=nominatim-updates.service
 WantedBy=multi-user.target
 ```
 
-`OnUnitActiveSec` defines how often the individual update command is run.
-
-Then add a service definition for the timer in `/etc/systemd/system/nominatim-updates.service`:
+And then a similar service definition: `/etc/systemd/system/nominatim-updates.service`:
 
 ```
 [Unit]
 Description=Single updates of Nominatim
 
 [Service]
-WorkingDirectory=/srv/nominatim-project
-ExecStart=/srv/nominatim-venv/bin/nominatim replication --once
-StandardOutput=journald
-StandardError=inherit
+WorkingDirectory=/srv/nominatim
+ExecStart=nominatim replication --once
+StandardOutput=append:/var/log/nominatim-updates.log
+StandardError=append:/var/log/nominatim-updates.error.log
 User=nominatim
 Group=nominatim
 Type=simple
@@ -130,9 +128,9 @@ Type=simple
 WantedBy=multi-user.target
 ```
 
-Replace the `WorkingDirectory` with your project directory. `ExecStart` points
-to the nominatim binary that was installed in your virtualenv earlier.
-Finally, you might need to adapt user and group names as required.
+Replace the `WorkingDirectory` with your project directory. Also adapt user and
+group names as required. `OnUnitActiveSec` defines how often the individual
+update command is run.
 
 Now activate the service and start the updates:
 
@@ -142,13 +140,12 @@ sudo systemctl enable nominatim-updates.timer
 sudo systemctl start nominatim-updates.timer
 ```
 
-You can stop future data updates while allowing any current, in-progress
+You can stop future data updates, while allowing any current, in-progress
 update steps to finish, by running `sudo systemctl stop
 nominatim-updates.timer` and waiting until `nominatim-updates.service` isn't
-running (`sudo systemctl is-active nominatim-updates.service`).
-
-To check the output from the update process, use journalctl: `journalctl -u
-nominatim-updates.service`
+running (`sudo systemctl is-active nominatim-updates.service`). Current output
+from the update can be seen like above (`systemctl status
+nominatim-updates.service`).
 
 
 #### Catch-up mode
@@ -158,13 +155,13 @@ all changes from the server until the database is up-to-date. The catch-up mode
 still respects the parameter `NOMINATIM_REPLICATION_MAX_DIFF`. It downloads and
 applies the changes in appropriate batches until all is done.
 
-The catch-up mode is foremost useful to bring the database up to date after the
+The catch-up mode is foremost useful to bring the database up to speed after the
 initial import. Give that the service usually is not in production at this
 point, you can temporarily be a bit more generous with the batch size and
 number of threads you use for the updates by running catch-up like this:
 
 ```
-cd /srv/nominatim-project
+cd /srv/nominatim
 NOMINATIM_REPLICATION_MAX_DIFF=5000 nominatim replication --catch-up --threads 15
 ```
 
@@ -176,13 +173,13 @@ replication catch-up at whatever interval you desire.
     When running scheduled updates with catch-up, it is a good idea to choose
     a replication source with an update frequency that is an order of magnitude
     lower. For example, if you want to update once a day, use an hourly updated
-    source. This ensures that you don't miss an entire day of updates when
+    source. This makes sure that you don't miss an entire day of updates when
     the source is unexpectedly late to publish its update.
 
     If you want to use the source with the same update frequency (e.g. a daily
     updated source with daily updates), use the
-    once mode together with a frequently run systemd script as described above.
-    It ensures to re-request the newest update until they have been published.
+    continuous update mode. It ensures to re-request the newest update until it
+    is published.
 
 
 #### Continuous updates
@@ -200,3 +197,36 @@ parameters:
 
 The update application keeps running forever and retrieves and applies
 new updates from the server as they are published.
+
+You can run this command as a simple systemd service. Create a service
+description like that in `/etc/systemd/system/nominatim-updates.service`:
+
+```
+[Unit]
+Description=Continuous updates of Nominatim
+
+[Service]
+WorkingDirectory=/srv/nominatim
+ExecStart=nominatim replication
+StandardOutput=append:/var/log/nominatim-updates.log
+StandardError=append:/var/log/nominatim-updates.error.log
+User=nominatim
+Group=nominatim
+Type=simple
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Replace the `WorkingDirectory` with your project directory. Also adapt user
+and group names as required.
+
+Now activate the service and start the updates:
+
+```
+sudo systemctl daemon-reload
+sudo systemctl enable nominatim-updates
+sudo systemctl start nominatim-updates
+```
+
+

docs/customize/Import-Styles.md

@@ -60,7 +60,7 @@ The _main tags_ classify what kind of place the OSM object represents. One
 OSM object can have more than one main tag. In such case one database entry
 is created for each main tag. _Name tags_ represent searchable names of the
 place. _Address tags_ are used to compute the address hierarchy of the place.
-Address tags are used for searching and for creating a display name of the place.
+Address are used for searching and for creating a display name of the place.
 _Extra tags_ are any tags that are not directly related to search but
 contain interesting additional information.
 
@@ -76,7 +76,7 @@ in which category.
 
 The flex style offers a number of functions to set the classification of
 each OSM tag. Most of these functions can also take a preset string instead
-of a tag description. These presets describe common configurations that
+of a tag descriptions. These presets describe common configurations that
 are also used in the definition of the predefined styles. This section
 lists the configuration functions and the accepted presets.
 
@@ -95,7 +95,7 @@ Any other string is matched exactly against tag keys.
 takes a lua table parameter which defines for keys and key/value
 combinations, how they are classified.
 
-The following classifications are recognized:
+The following classifications are recognised:
 
 | classification  | meaning |
 | :-------------- | :------ |
@@ -133,7 +133,7 @@ the same.
     In this example an object with a `boundary` tag will only be included
     when it has a value of `administrative`. Objects with `highway` tags are
     always included with two exceptions: the troll tag `highway=no` is
-    deleted on the spot. And when the value is `street_lamp` then the object
+    deleted on the spot and when the value is `street_lamp` then the object
     must have a name, too. Finally, if a `landuse` tag is present then
     it will be used independently of the concrete value when neither boundary
     nor highway tags were found and the object is named.
@@ -143,7 +143,7 @@ the same.
 | Name   | Description |
 | :----- | :---------- |
 | admin  | Basic tag set collecting places and administrative boundaries. This set is needed also to ensure proper address computation and should therefore always be present. You can disable selected place types like `place=locality` after adding this set, if they are not relevant for your use case. |
-| all_boundaries | Extends the set of recognized boundaries and places to all available ones. |
+| all_boundaries | Extends the set of recognised boundaries and places to all available ones. |
 | natural | Tags for natural features like rivers and mountain peaks. |
 | street/default | Tags for streets. Major streets are always included, minor ones only when they have a name. |
 | street/car | Tags for all streets that can be used by a motor vehicle. |
@@ -229,7 +229,7 @@ in turn take precedence over prefix matches.
 | Name     | Description |
 | :-----   | :---------- |
 | metatags | Tags with meta information about the OSM tag like source, notes and import sources. |
-| name     | Non-names that actually describe properties or name parts. These names can throw off search and should always be removed. |
+| name     | Non-names that describe in fact properties or name parts. These names can throw off search and should always be removed. |
 | address  | Extra `addr:*` tags that are not useful for Nominatim. |
 
 
@@ -305,7 +305,7 @@ the database independently of the presence of other main tags.
 `set_name_tags()` overwrites the current configuration, while
 `modify_name_tags()` replaces the fields that are given. (Be aware that
 the fields are replaced as a whole. `main = {'foo_name'}` will cause
-`foo_name` to become the only recognized primary name. Any previously
+`foo_name` to become the only recognised primary name. Any previously
 defined primary names are forgotten.)
 
 !!! example
@@ -326,9 +326,9 @@ defined primary names are forgotten.)
 
 | Name     | Description |
 | :-----   | :---------- |
-| core     | Basic set of recognized names for all places. |
+| core     | Basic set of recognised names for all places. |
 | address  | Additional names useful when indexing full addresses. |
-| poi      | Extended set of recognized names for pois. Use on top of the core set. |
+| poi      | Extended set of recognised names for pois. Use on top of the core set. |
 
 ### Address tags
 
@@ -376,8 +376,8 @@ the fields are replaced as a whole.)
 
 | Name     | Description |
 | :-----   | :---------- |
-| core     | Basic set of tags needed to recognize address relationship for any place. Always include this. |
-| houses   | Additional set of tags needed to recognize proper addresses |
+| core     | Basic set of tags needed to recognise address relationship for any place. Always include this. |
+| houses   | Additional set of tags needed to recognise proper addresses |
 
 ### Handling of unclassified tags
 
@@ -514,7 +514,7 @@ Themepark topics offer two configuration options:
 
 The customization functions described in the
 [Changing recognized tags](#changing-the-recognized-tags) section
-are available from the theme. To access the theme you need to explicitly initialize it.
+are available from the theme. To access the theme you need to explicitly initialise it.
 
 !!! Example
     ``` lua
@@ -568,7 +568,7 @@ gazetteer output.
 
 ## Changing the style of existing databases
 
-There is usually no issue changing the style of a database that is already
+There is normally no issue changing the style of a database that is already
 imported and now kept up-to-date with change files. Just be aware that any
 change in the style applies to updates only. If you want to change the data
 that is already in the database, then a reimport is necessary.

docs/customize/Settings.md

@@ -336,7 +336,7 @@ NOMINATIM_TABLESPACE_SEARCH_INDEX
 NOMINATIM_TABLESPACE_OSM_DATA
 :    Raw OSM data cache used for import and updates.
 
-NOMINATIM_TABLESPACE_OSM_INDEX
+NOMINATIM_TABLESPACE_OSM_DATA
 :    Indexes on the raw OSM data cache.
 
 NOMINATIM_TABLESPACE_PLACE_DATA

docs/customize/Tokenizers.md

@@ -50,7 +50,7 @@ queries. This happens in two stages:
    as during the import process but may involve other processing like,
    for example, word break detection.
 2. The **token analysis** step breaks down the query parts into tokens,
-   looks them up in the database and assigns them possible functions and
+   looks them up in the database and assignes them possible functions and
    probabilities.
 
 Query processing can be further customized while the rest of the analysis

docs/develop/Tokenizers.md

@@ -27,7 +27,7 @@ into a database query to find the right place.
 It is the core task of the tokenizer to create, manage and assign the search
 tokens. The tokenizer is involved in two distinct operations:
 
-* __at import time__: scanning names of OSM objects, normalizing them and
+* __at import time__: scanning s of OSM objects, normalizing them and
   building up the list of search tokens.
 * __at query time__: scanning the query and returning the appropriate search
   tokens.
@@ -44,7 +44,7 @@ trigger is responsible to fill out all secondary tables with extra geocoding
 information. This part is written in PL/pgSQL.
 
 The tokenizer is involved in both parts. When the indexer prepares a place,
-it hands it over to the tokenizer to inspect the names and create all the
+it hands it over to the tokenizer to inspect the s and create all the
 search tokens applicable for the place. This usually involves updating the
 tokenizer's internal token lists and creating a list of all token IDs for
 the specific place. This list is later needed in the PL/pgSQL part where the

lib-lua/themes/nominatim/init.lua

@@ -425,7 +425,7 @@ function Place:write_row(k, v)
     if self.geometry == nil then
         self.geometry = self.geom_func(self.object)
     end
-    if self.geometry == nil or self.geometry:is_null() then
+    if self.geometry:is_null() then
         return 0
     end
 
@@ -608,9 +608,6 @@ function module.process_way(object)
 
         if geom:is_null() then
             geom = o:as_linestring()
-            if geom:is_null() or geom:length() > 30 then
-                return nil
-            end
         end
 
         return geom

lib-sql/functions/partition-functions.sql

@@ -17,6 +17,28 @@ CREATE TYPE nearfeaturecentr AS (
   centroid GEOMETRY
 );
 
+-- feature intersects geometry
+-- for areas and linestrings they must touch at least along a line
+CREATE OR REPLACE FUNCTION is_relevant_geometry(de9im TEXT, geom_type TEXT)
+RETURNS BOOLEAN
+AS $$
+BEGIN
+  IF substring(de9im from 1 for 2) != 'FF' THEN
+    RETURN TRUE;
+  END IF;
+
+  IF geom_type = 'ST_Point' THEN
+    RETURN substring(de9im from 4 for 1) = '0';
+  END IF;
+
+  IF geom_type in ('ST_LineString', 'ST_MultiLineString') THEN
+    RETURN substring(de9im from 4 for 1) = '1';
+  END IF;
+
+  RETURN substring(de9im from 4 for 1) = '2';
+END
+$$ LANGUAGE plpgsql IMMUTABLE;
+
 CREATE OR REPLACE function getNearFeatures(in_partition INTEGER, feature GEOMETRY,
                                            feature_centroid GEOMETRY,
                                            maxrank INTEGER)
@@ -37,12 +59,7 @@ BEGIN
              isguess, postcode, centroid
       FROM location_area_large_{{ partition }}
       WHERE geometry && feature
-        AND CASE WHEN ST_Dimension(feature) = 0
-                     THEN _ST_Covers(geometry, feature)
-                 WHEN ST_Dimension(feature) = 2
-                     THEN ST_Relate(geometry, feature, 'T********')
-                 ELSE ST_NPoints(ST_Intersection(geometry, feature)) > 1
-            END
+        AND is_relevant_geometry(ST_Relate(geometry, feature), ST_GeometryType(feature))
         AND rank_address < maxrank
             -- Postcodes currently still use rank_search to define for which
             -- features they are relevant.
@@ -125,16 +142,14 @@ BEGIN
 
   IF in_rank_search <= 4 and not in_estimate THEN
     INSERT INTO location_area_country (place_id, country_code, geometry)
-      (SELECT in_place_id, in_country_code, geom
-       FROM split_geometry(in_geometry) as geom);
+      values (in_place_id, in_country_code, in_geometry);
     RETURN TRUE;
   END IF;
 
 {% for partition in db.partitions %}
   IF in_partition = {{ partition }} THEN
     INSERT INTO location_area_large_{{ partition }} (partition, place_id, country_code, keywords, rank_search, rank_address, isguess, postcode, centroid, geometry)
-      (SELECT in_partition, in_place_id, in_country_code, in_keywords, in_rank_search, in_rank_address, in_estimate, postcode, in_centroid, geom
-       FROM split_geometry(in_geometry) as geom);
+      values (in_partition, in_place_id, in_country_code, in_keywords, in_rank_search, in_rank_address, in_estimate, postcode, in_centroid, in_geometry);
     RETURN TRUE;
   END IF;
 {% endfor %}

lib-sql/functions/utils.sql

@@ -348,6 +348,8 @@ CREATE OR REPLACE FUNCTION add_location(place_id BIGINT, country_code varchar(2)
   RETURNS BOOLEAN
   AS $$
 DECLARE
+  locationid INTEGER;
+  secgeo GEOMETRY;
   postcode TEXT;
 BEGIN
   PERFORM deleteLocationArea(partition, place_id, rank_search);
@@ -358,19 +360,18 @@ BEGIN
       postcode := upper(trim (in_postcode));
   END IF;
 
-  IF ST_Dimension(geometry) = 2 THEN
-    RETURN insertLocationAreaLarge(partition, place_id, country_code, keywords,
-                                   rank_search, rank_address, false, postcode,
-                                   centroid, geometry);
+  IF ST_GeometryType(geometry) in ('ST_Polygon','ST_MultiPolygon') THEN
+    FOR secgeo IN select split_geometry(geometry) AS geom LOOP
+      PERFORM insertLocationAreaLarge(partition, place_id, country_code, keywords, rank_search, rank_address, false, postcode, centroid, secgeo);
+    END LOOP;
+
+  ELSEIF ST_GeometryType(geometry) = 'ST_Point' THEN
+    secgeo := place_node_fuzzy_area(geometry, rank_search);
+    PERFORM insertLocationAreaLarge(partition, place_id, country_code, keywords, rank_search, rank_address, true, postcode, centroid, secgeo);
+
   END IF;
 
-  IF ST_Dimension(geometry) = 0 THEN
-    RETURN insertLocationAreaLarge(partition, place_id, country_code, keywords,
-                                   rank_search, rank_address, true, postcode,
-                                   centroid, place_node_fuzzy_area(geometry, rank_search));
-  END IF;
-
-  RETURN false;
+  RETURN true;
 END;
 $$
 LANGUAGE plpgsql;
@@ -393,21 +394,19 @@ DECLARE
   geo RECORD;
   area FLOAT;
   remainingdepth INTEGER;
+  added INTEGER;
 BEGIN
+
 --  RAISE WARNING 'quad_split_geometry: maxarea=%, depth=%',maxarea,maxdepth;
 
-  IF not ST_IsValid(geometry) THEN
-    RETURN;
-  END IF;
-
-  IF ST_Dimension(geometry) != 2 OR maxdepth <= 1 THEN
+  IF (ST_GeometryType(geometry) not in ('ST_Polygon','ST_MultiPolygon') OR NOT ST_IsValid(geometry)) THEN
     RETURN NEXT geometry;
     RETURN;
   END IF;
 
   remainingdepth := maxdepth - 1;
   area := ST_AREA(geometry);
-  IF area < maxarea THEN
+  IF remainingdepth < 1 OR area < maxarea THEN
     RETURN NEXT geometry;
     RETURN;
   END IF;
@@ -427,6 +426,7 @@ BEGIN
   xmid := (xmin+xmax)/2;
   ymid := (ymin+ymax)/2;
 
+  added := 0;
   FOR seg IN 1..4 LOOP
 
     IF seg = 1 THEN
@@ -442,13 +442,16 @@ BEGIN
       secbox := ST_SetSRID(ST_MakeBox2D(ST_Point(xmid,ymid),ST_Point(xmax,ymax)),4326);
     END IF;
 
-    secgeo := st_intersection(geometry, secbox);
-    IF NOT ST_IsEmpty(secgeo) AND ST_Dimension(secgeo) = 2 THEN
-      FOR geo IN SELECT quad_split_geometry(secgeo, maxarea, remainingdepth) as geom LOOP
-        IF NOT ST_IsEmpty(geo.geom) AND ST_Dimension(geo.geom) = 2 THEN
-          RETURN NEXT geo.geom;
-        END IF;
-      END LOOP;
+    IF st_intersects(geometry, secbox) THEN
+      secgeo := st_intersection(geometry, secbox);
+      IF NOT ST_IsEmpty(secgeo) AND ST_GeometryType(secgeo) in ('ST_Polygon','ST_MultiPolygon') THEN
+        FOR geo IN select quad_split_geometry(secgeo, maxarea, remainingdepth) as geom LOOP
+          IF NOT ST_IsEmpty(geo.geom) AND ST_GeometryType(geo.geom) in ('ST_Polygon','ST_MultiPolygon') THEN
+            added := added + 1;
+            RETURN NEXT geo.geom;
+          END IF;
+        END LOOP;
+      END IF;
     END IF;
   END LOOP;
 
@@ -464,22 +467,10 @@ CREATE OR REPLACE FUNCTION split_geometry(geometry GEOMETRY)
 DECLARE
   geo RECORD;
 BEGIN
-  IF ST_GeometryType(geometry) = 'ST_MultiPolygon'
-     and ST_Area(geometry) * 10 > ST_Area(Box2D(geometry))
-  THEN
-    FOR geo IN
-        SELECT quad_split_geometry(g, 0.25, 20) as geom
-        FROM (SELECT (ST_Dump(geometry)).geom::geometry(Polygon, 4326) AS g) xx
-    LOOP
-      RETURN NEXT geo.geom;
-    END LOOP;
-  ELSE
-    FOR geo IN
-        SELECT quad_split_geometry(geometry, 0.25, 20) as geom
-    LOOP
-      RETURN NEXT geo.geom;
-    END LOOP;
-  END IF;
+  -- 10000000000 is ~~ 1x1 degree
+  FOR geo IN select quad_split_geometry(geometry, 0.25, 20) as geom LOOP
+    RETURN NEXT geo.geom;
+  END LOOP;
   RETURN;
 END;
 $$

settings/address-levels.json

@@ -23,8 +23,8 @@
           "allotments" : 22,
           "neighbourhood" : [20, 22],
           "quarter" : [20, 22],
-          "isolated_dwelling" : [22, 25],
-          "farm" : [22, 25],
+          "isolated_dwelling" : [22, 20],
+          "farm" : [22, 20],
           "city_block" : 25,
           "mountain_pass" : 25,
           "square" : 25,

settings/icu_tokenizer.yaml

@@ -1,5 +1,4 @@
 query-preprocessing:
-    - step: split_japanese_phrases
     - step: normalize
 normalization:
     - ":: lower ()"
@@ -10,17 +9,16 @@ normalization:
     - "'nº' > 'no'"
     - "ª > a"
     - "º > o"
-    - "[[:Punctuation:][:Symbol:][\u02bc] - [-:]]+  > '-'"
+    - "[[:Punctuation:][:Symbol:]\u02bc]  > ' '"
     - "ß > 'ss'" # German szet is unambiguously equal to double ss
-    - "[^[:alnum:] [:Canonical_Combining_Class=Virama:] [:Space:] [-:]] >"
+    - "[^[:alnum:] [:Canonical_Combining_Class=Virama:] [:Space:]] >"
     - "[:Lm:] >"
     - ":: [[:Number:]] Latin ()"
     - ":: [[:Number:]] Ascii ();"
     - ":: [[:Number:]] NFD ();"
     - "[[:Nonspacing Mark:] [:Cf:]] >;"
-    - "[-:]?[:Space:]+[-:]? > ' '"
+    - "[:Space:]+ > ' '"
 transliteration:
-    - "[-:]  > ' '"
     - ":: Latin ()"
     - !include icu-rules/extended-unicode-to-asccii.yaml
     - ":: Ascii ()"

src/nominatim_api/query_preprocessing/split_japanese_phrases.py

@@ -1,61 +0,0 @@
-# SPDX-License-Identifier: GPL-3.0-or-later
-#
-# This file is part of Nominatim. (https://nominatim.org)
-#
-# Copyright (C) 2025 by the Nominatim developer community.
-# For a full list of authors see the git log.
-"""
-This file divides Japanese addresses into three categories:
-prefecture, municipality, and other.
-The division is not strict but simple using these keywords.
-"""
-from typing import List
-import re
-
-from .config import QueryConfig
-from .base import QueryProcessingFunc
-from ..search.query import Phrase
-
-MATCH_PATTERNS = [
-    r'''
-                (...??[都都道府県縣])            # [group1] prefecture
-                (.+?[市区區町村])              # [group2] municipalities (city/wards/towns/villages)
-                (.+)                         # [group3] other words
-                ''',
-    r'''
-                (...??[都都道府県縣])            # [group1] prefecture
-                (.+)                         # [group3] other words
-                ''',
-    r'''
-                (.+?[市区區町村])              # [group2] municipalities (city/wards/towns/villages)
-                (.+)                         # [group3] other words
-                '''
-]
-
-
-class _JapanesePreprocessing:
-
-    def __init__(self, config: QueryConfig) -> None:
-        self.config = config
-
-    def split_phrase(self, phrase: Phrase) -> Phrase:
-        """
-        This function performs a division on the given text using a regular expression.
-        """
-        for pattern in MATCH_PATTERNS:
-            result = re.match(pattern, phrase.text, re.VERBOSE)
-            if result is not None:
-                return Phrase(phrase.ptype, ':'.join(result.groups()))
-
-        return phrase
-
-    def __call__(self, phrases: List[Phrase]) -> List[Phrase]:
-        """Split a Japanese address using japanese_tokenizer.
-        """
-        return [self.split_phrase(p) for p in phrases]
-
-
-def create(config: QueryConfig) -> QueryProcessingFunc:
-    """ Create a function of japanese preprocessing.
-    """
-    return _JapanesePreprocessing(config)

src/nominatim_api/search/db_search_builder.py

@@ -433,7 +433,6 @@ PENALTY_WORDCHANGE = {
     BreakType.START: 0.0,
     BreakType.END: 0.0,
     BreakType.PHRASE: 0.0,
-    BreakType.SOFT_PHRASE: 0.0,
     BreakType.WORD: 0.1,
     BreakType.PART: 0.2,
     BreakType.TOKEN: 0.4

src/nominatim_api/search/geocoder.py

@@ -133,7 +133,7 @@ class ForwardGeocoder:
         """
         assert self.query_analyzer is not None
         qwords = [word for phrase in query.source
-                  for word in re.split('[-,: ]+', phrase.text) if word]
+                  for word in re.split('[, ]+', phrase.text) if word]
         if not qwords:
             return
 
@@ -146,7 +146,7 @@ class ForwardGeocoder:
             distance = 0.0
             norm = self.query_analyzer.normalize_text(' '.join((result.display_name,
                                                                 result.country_code or '')))
-            words = set((w for w in re.split('[-,: ]+', norm) if w))
+            words = set((w for w in norm.split(' ') if w))
             if not words:
                 continue
             for qword in qwords:

src/nominatim_api/search/icu_tokenizer.py

@@ -7,12 +7,10 @@
 """
 Implementation of query analysis for the ICU tokenizer.
 """
-from typing import Tuple, Dict, List, Optional, Iterator, Any, cast
+from typing import Tuple, Dict, List, Optional, NamedTuple, Iterator, Any, cast
 from collections import defaultdict
 import dataclasses
 import difflib
-import re
-from itertools import zip_longest
 
 from icu import Transliterator
 
@@ -36,30 +34,17 @@ DB_TO_TOKEN_TYPE = {
     'C': qmod.TokenType.COUNTRY
 }
 
-PENALTY_IN_TOKEN_BREAK = {
-     qmod.BreakType.START: 0.5,
-     qmod.BreakType.END: 0.5,
-     qmod.BreakType.PHRASE: 0.5,
-     qmod.BreakType.SOFT_PHRASE: 0.5,
-     qmod.BreakType.WORD: 0.1,
-     qmod.BreakType.PART: 0.0,
-     qmod.BreakType.TOKEN: 0.0
-}
 
-
-@dataclasses.dataclass
-class QueryPart:
+class QueryPart(NamedTuple):
     """ Normalized and transliterated form of a single term in the query.
         When the term came out of a split during the transliteration,
         the normalized string is the full word before transliteration.
         The word number keeps track of the word before transliteration
         and can be used to identify partial transliterated terms.
-        Penalty is the break penalty for the break following the token.
     """
     token: str
     normalized: str
     word_number: int
-    penalty: float
 
 
 QueryParts = List[QueryPart]
@@ -73,12 +58,10 @@ def yield_words(terms: List[QueryPart], start: int) -> Iterator[Tuple[str, qmod.
     total = len(terms)
     for first in range(start, total):
         word = terms[first].token
-        penalty = PENALTY_IN_TOKEN_BREAK[qmod.BreakType.WORD]
-        yield word, qmod.TokenRange(first, first + 1, penalty=penalty)
+        yield word, qmod.TokenRange(first, first + 1)
         for last in range(first + 1, min(first + 20, total)):
             word = ' '.join((word, terms[last].token))
-            penalty += terms[last - 1].penalty
-            yield word, qmod.TokenRange(first, last + 1, penalty=penalty)
+            yield word, qmod.TokenRange(first, last + 1)
 
 
 @dataclasses.dataclass
@@ -111,25 +94,25 @@ class ICUToken(qmod.Token):
         self.penalty += (distance/len(self.lookup_word))
 
     @staticmethod
-    def from_db_row(row: SaRow, base_penalty: float = 0.0) -> 'ICUToken':
+    def from_db_row(row: SaRow) -> 'ICUToken':
         """ Create a ICUToken from the row of the word table.
         """
         count = 1 if row.info is None else row.info.get('count', 1)
         addr_count = 1 if row.info is None else row.info.get('addr_count', 1)
 
-        penalty = base_penalty
+        penalty = 0.0
         if row.type == 'w':
-            penalty += 0.3
+            penalty = 0.3
         elif row.type == 'W':
             if len(row.word_token) == 1 and row.word_token == row.word:
-                penalty += 0.2 if row.word.isdigit() else 0.3
+                penalty = 0.2 if row.word.isdigit() else 0.3
         elif row.type == 'H':
-            penalty += sum(0.1 for c in row.word_token if c != ' ' and not c.isdigit())
+            penalty = sum(0.1 for c in row.word_token if c != ' ' and not c.isdigit())
             if all(not c.isdigit() for c in row.word_token):
                 penalty += 0.2 * (len(row.word_token) - 1)
         elif row.type == 'C':
             if len(row.word_token) == 1:
-                penalty += 0.3
+                penalty = 0.3
 
         if row.info is None:
             lookup_word = row.word
@@ -219,7 +202,7 @@ class ICUQueryAnalyzer(AbstractQueryAnalyzer):
 
         for row in await self.lookup_in_db(list(words.keys())):
             for trange in words[row.word_token]:
-                token = ICUToken.from_db_row(row, trange.penalty or 0.0)
+                token = ICUToken.from_db_row(row)
                 if row.type == 'S':
                     if row.info['op'] in ('in', 'near'):
                         if trange.start == 0:
@@ -259,24 +242,16 @@ class ICUQueryAnalyzer(AbstractQueryAnalyzer):
         wordnr = 0
         for phrase in query.source:
             query.nodes[-1].ptype = phrase.ptype
-            phrase_split = re.split('([ :-])', phrase.text)
-            # The zip construct will give us the pairs of word/break from
-            # the regular expression split. As the split array ends on the
-            # final word, we simply use the fillvalue to even out the list and
-            # add the phrase break at the end.
-            for word, breakchar in zip_longest(*[iter(phrase_split)]*2, fillvalue=','):
-                if not word:
-                    continue
+            for word in phrase.text.split(' '):
                 trans = self.transliterator.transliterate(word)
                 if trans:
                     for term in trans.split(' '):
                         if term:
-                            parts.append(QueryPart(term, word, wordnr,
-                                                   PENALTY_IN_TOKEN_BREAK[qmod.BreakType.TOKEN]))
+                            parts.append(QueryPart(term, word, wordnr))
                             query.add_node(qmod.BreakType.TOKEN, phrase.ptype)
-                    query.nodes[-1].btype = qmod.BreakType(breakchar)
-                    parts[-1].penalty = PENALTY_IN_TOKEN_BREAK[qmod.BreakType(breakchar)]
+                    query.nodes[-1].btype = qmod.BreakType.WORD
                 wordnr += 1
+            query.nodes[-1].btype = qmod.BreakType.PHRASE
 
             for word, wrange in yield_words(parts, phrase_start):
                 words[word].append(wrange)
@@ -297,7 +272,7 @@ class ICUQueryAnalyzer(AbstractQueryAnalyzer):
         """ Add tokens to query that are not saved in the database.
         """
         for part, node, i in zip(parts, query.nodes, range(1000)):
-            if len(part.token) <= 4 and part.token.isdigit()\
+            if len(part.token) <= 4 and part[0].isdigit()\
                and not node.has_tokens(i+1, qmod.TokenType.HOUSENUMBER):
                 query.add_token(qmod.TokenRange(i, i+1), qmod.TokenType.HOUSENUMBER,
                                 ICUToken(penalty=0.5, token=0,

src/nominatim_api/search/query.py

@@ -21,13 +21,7 @@ class BreakType(enum.Enum):
     END = '>'
     """ End of the query. """
     PHRASE = ','
-    """ Hard break between two phrases. Address parts cannot cross hard
-        phrase boundaries."""
-    SOFT_PHRASE = ':'
-    """ Likely break between two phrases. Address parts should not cross soft
-        phrase boundaries. Soft breaks can be inserted by a preprocessor
-        that is analysing the input string.
-    """
+    """ Break between two phrases. """
     WORD = ' '
     """ Break between words. """
     PART = '-'
@@ -122,7 +116,6 @@ class TokenRange:
     """
     start: int
     end: int
-    penalty: Optional[float] = None
 
     def __lt__(self, other: 'TokenRange') -> bool:
         return self.end <= other.start

src/nominatim_api/search/token_assignment.py

@@ -27,7 +27,6 @@ PENALTY_TOKENCHANGE = {
     qmod.BreakType.START: 0.0,
     qmod.BreakType.END: 0.0,
     qmod.BreakType.PHRASE: 0.0,
-    qmod.BreakType.SOFT_PHRASE: 0.0,
     qmod.BreakType.WORD: 0.1,
     qmod.BreakType.PART: 0.2,
     qmod.BreakType.TOKEN: 0.4

src/nominatim_api/version.py

@@ -8,4 +8,4 @@
 Version information for the Nominatim API.
 """
 
-NOMINATIM_API_VERSION = '5.0.0'
+NOMINATIM_API_VERSION = '4.5.0'

src/nominatim_db/clicmd/setup.py

@@ -122,16 +122,13 @@ class SetupAll:
 
         LOG.warning('Post-process tables')
         with connect(args.config.get_libpq_dsn()) as conn:
-            conn.autocommit = True
             await database_import.create_search_indices(conn, args.config,
                                                         drop=args.no_updates,
                                                         threads=num_threads)
             LOG.warning('Create search index for default country names.')
-            conn.autocommit = False
             country_info.create_country_names(conn, tokenizer,
                                               args.config.get_str_list('LANGUAGES'))
             if args.no_updates:
-                conn.autocommit = True
                 freeze.drop_update_tables(conn)
         tokenizer.finalize_import(args.config)
 
@@ -186,7 +183,6 @@ class SetupAll:
         from ..tools import database_import, refresh
 
         with connect(config.get_libpq_dsn()) as conn:
-            conn.autocommit = True
             LOG.warning('Create functions (1st pass)')
             refresh.create_functions(conn, config, False, False)
             LOG.warning('Create tables')

src/nominatim_db/tokenizer/icu_token_analysis.py

@@ -25,8 +25,6 @@ class ICUTokenAnalysis:
 
     def __init__(self, norm_rules: str, trans_rules: str,
                  analysis_rules: Mapping[Optional[str], 'TokenAnalyzerRule']):
-        # additional break signs are not relevant during name analysis
-        norm_rules += ";[[:Space:][-:]]+ > ' ';"
         self.normalizer = Transliterator.createFromRules("icu_normalization",
                                                          norm_rules)
         trans_rules += ";[:Space:]+ > ' '"

src/nominatim_db/version.py

@@ -55,7 +55,7 @@ def parse_version(version: str) -> NominatimVersion:
     return NominatimVersion(*[int(x) for x in parts[:2] + parts[2].split('-')])
 
 
-NOMINATIM_VERSION = parse_version('5.0.0-0')
+NOMINATIM_VERSION = parse_version('4.5.0-0')
 
 POSTGRESQL_REQUIRED_VERSION = (12, 0)
 POSTGIS_REQUIRED_VERSION = (3, 0)

test/bdd/db/import/rank_computation.feature

@@ -267,34 +267,3 @@ Feature: Rank assignment
           | object      | rank_search | rank_address |
           | N23:amenity | 30          | 30           |
           | N23:place   | 16          | 16           |
-
-    Scenario: Address rank 25 is only used for addr:place
-        Given the grid
-           | 10 | 33 | 34 | 11 |
-        Given the places
-          | osm | class | type    | name |
-          | N10 | place | village | vil  |
-          | N11 | place | farm    | farm |
-        And the places
-          | osm | class   | type        | name | geometry |
-          | W1  | highway | residential | RD   | 33,11    |
-        And the places
-          | osm | class   | type        | name | addr+farm | geometry |
-          | W2  | highway | residential | RD2  | farm       | 34,11    |
-        And the places
-          | osm | class | type  | housenr |
-          | N33 | place | house | 23      |
-        And the places
-          | osm | class | type  | housenr | addr+place |
-          | N34 | place | house | 23      | farm       |
-        When importing
-        Then placex contains
-          | object | parent_place_id |
-          | N11    | N10             |
-          | N33    | W1              |
-          | N34    | N11             |
-        And place_addressline contains
-          | object | address |
-          | W1     | N10     |
-          | W2     | N10     |
-          | W2     | N11     |

test/python/api/query_processing/test_split_japanese_phrases.py

@@ -1,34 +0,0 @@
-# SPDX-License-Identifier: GPL-3.0-or-later
-#
-# This file is part of Nominatim. (https://nominatim.org)
-#
-# Copyright (C) 2025 by the Nominatim developer community.
-# For a full list of authors see the git log.
-"""
-Tests for japanese phrase splitting.
-"""
-from pathlib import Path
-
-import pytest
-
-from icu import Transliterator
-
-import nominatim_api.search.query as qmod
-from nominatim_api.query_preprocessing.config import QueryConfig
-from nominatim_api.query_preprocessing import split_japanese_phrases
-
-def run_preprocessor_on(query):
-    proc = split_japanese_phrases.create(QueryConfig().set_normalizer(None))
-
-    return proc(query)
-
-
-@pytest.mark.parametrize('inp,outp', [('大阪府大阪市大阪', '大阪府:大阪市:大阪'),
-                                      ('大阪府大阪', '大阪府:大阪'),
-                                      ('大阪市大阪', '大阪市:大阪')])
-def test_split_phrases(inp, outp):
-    query = [qmod.Phrase(qmod.PhraseType.NONE, inp)]
-
-    out = run_preprocessor_on(query)
-
-    assert out == [qmod.Phrase(qmod.PhraseType.NONE, outp)]

test/python/tools/test_refresh.py

@@ -23,10 +23,14 @@ def test_refresh_import_secondary_importance_non_existing(dsn):
 
 def test_refresh_import_secondary_importance_testdb(dsn, src_dir, temp_db_conn, temp_db_cursor):
     temp_db_cursor.execute('CREATE EXTENSION postgis')
-    temp_db_cursor.execute('CREATE EXTENSION postgis_raster')
-    assert refresh.import_secondary_importance(dsn, src_dir / 'test' / 'testdb') == 0
 
-    assert temp_db_cursor.table_exists('secondary_importance')
+    if postgis_version_tuple(temp_db_conn)[0] < 3:
+        assert refresh.import_secondary_importance(dsn, src_dir / 'test' / 'testdb') > 0
+    else:
+        temp_db_cursor.execute('CREATE EXTENSION postgis_raster')
+        assert refresh.import_secondary_importance(dsn, src_dir / 'test' / 'testdb') == 0
+
+        assert temp_db_cursor.table_exists('secondary_importance')
 
 
 @pytest.mark.parametrize("replace", (True, False))
@@ -37,7 +41,8 @@ def test_refresh_import_wikipedia(dsn, src_dir, table_factory, temp_db_cursor, r
     # use the small wikipedia file for the API testdb
     assert refresh.import_wikipedia_articles(dsn, src_dir / 'test' / 'testdb') == 0
 
-    assert temp_db_cursor.table_rows('wikimedia_importance') > 0
+    assert temp_db_cursor.table_rows('wikipedia_article') > 0
+    assert temp_db_cursor.table_rows('wikipedia_redirect') > 0
 
 
 def test_recompute_importance(placex_table, table_factory, temp_db_conn, temp_db_cursor):