X-Git-Url: https://git.openstreetmap.org./nominatim.git/blobdiff_plain/5b20fa7e38d81d0a7e63aaf3c64c3ab80916ff38..5f6fe6cab769ad4d305264788ccb268eaeff91f1:/docs/admin/Migration.md?ds=inline diff --git a/docs/admin/Migration.md b/docs/admin/Migration.md index 917d3785..21bbb51a 100644 --- a/docs/admin/Migration.md +++ b/docs/admin/Migration.md @@ -8,6 +8,30 @@ SQL statements should be executed from the PostgreSQL commandline. Execute ## 3.5.0 -> master +### Change of layout of search_name_* tables + +The table need a different index for nearest place lookup. Recreate the +indexes using the following shell script: + +```bash +for table in `psql -d nominatim -c "SELECT tablename FROM pg_tables WHERE tablename LIKE 'search_name_%'" -tA | grep -v search_name_blank`; +do + psql -d nominatim -c "DROP INDEX idx_${table}_centroid_place; CREATE INDEX idx_${table}_centroid_place ON ${table} USING gist (centroid) WHERE ((address_rank >= 2) AND (address_rank <= 25)); DROP INDEX idx_${table}_centroid_street; CREATE INDEX idx_${table}_centroid_street ON ${table} USING gist (centroid) WHERE ((address_rank >= 26) AND (address_rank <= 27))"; +done +``` + +### Removal of html output + +The debugging UI is no longer directly provided with Nominatim. Instead we +now provide a simple Javascript application. Please refer to +[Setting up the Nominatim UI](../Setup-Nominatim-UI) for details on how to +set up the UI. + +The icons served together with the API responses have been moved to the +nominatim-ui project as well. If you want to keep the `icon` field in the +response, you need to set `CONST_MapIcon_URL` to the URL of the `/mapicon` +directory of nominatim-ui. + ### Change order during indexing When reindexing places during updates, there is now a different order used @@ -15,15 +39,24 @@ which needs a different database index. Create it with the following SQL command ```sql CREATE INDEX idx_placex_pendingsector_rank_address - ON placex USING BTREE (rank_address, geometry_sector) where indexed_status > 0; + ON placex + USING BTREE (rank_address, geometry_sector) + WHERE indexed_status > 0; ``` You can then drop the old index with: ```sql -DROP INDEX idx_placex_pendingsector +DROP INDEX idx_placex_pendingsector; ``` +### Unused index + +This index has been unused ever since the query using it was changed two years ago. Saves about 12GB on a planet installation. + +```sql +DROP INDEX idx_placex_geometry_reverse_lookupPoint; +``` ### Switching to dotenv @@ -46,6 +79,16 @@ follows: * download the new Wikipedia tables as described in the import section * reimport the tables: `./utils/setup.php --import-wikipedia-articles` * update the functions: `./utils/setup.php --create-functions --enable-diff-updates` + * create a new lookup index: +```sql +CREATE INDEX idx_placex_wikidata + ON placex + USING BTREE ((extratags -> 'wikidata')) + WHERE extratags ? 'wikidata' + AND class = 'place' + AND osm_type = 'N' + AND rank_search < 26; +``` * compute importance: `./utils/update.php --recompute-importance` The last step takes about 10 hours on the full planet. @@ -101,7 +144,7 @@ The new format is ### Natural Earth country boundaries no longer needed as fallback -``` +```sql DROP TABLE country_naturalearthdata; ``` @@ -127,27 +170,37 @@ following command: The reverse algorithm has changed and requires new indexes. Run the following SQL statements to create the indexes: -``` +```sql CREATE INDEX idx_placex_geometry_reverse_lookupPoint - ON placex USING gist (geometry) - WHERE (name is not null or housenumber is not null or rank_address between 26 and 27) - AND class not in ('railway','tunnel','bridge','man_made') - AND rank_address >= 26 AND indexed_status = 0 AND linked_place_id is null; + ON placex + USING gist (geometry) + WHERE (name IS NOT null or housenumber IS NOT null or rank_address BETWEEN 26 AND 27) + AND class NOT IN ('railway','tunnel','bridge','man_made') + AND rank_address >= 26 + AND indexed_status = 0 + AND linked_place_id IS null; CREATE INDEX idx_placex_geometry_reverse_lookupPolygon ON placex USING gist (geometry) WHERE St_GeometryType(geometry) in ('ST_Polygon', 'ST_MultiPolygon') - AND rank_address between 4 and 25 AND type != 'postcode' - AND name is not null AND indexed_status = 0 AND linked_place_id is null; + AND rank_address between 4 and 25 + AND type != 'postcode' + AND name is not null + AND indexed_status = 0 + AND linked_place_id is null; CREATE INDEX idx_placex_geometry_reverse_placeNode ON placex USING gist (geometry) - WHERE osm_type = 'N' AND rank_search between 5 and 25 - AND class = 'place' AND type != 'postcode' - AND name is not null AND indexed_status = 0 AND linked_place_id is null; + WHERE osm_type = 'N' + AND rank_search between 5 and 25 + AND class = 'place' + AND type != 'postcode' + AND name is not null + AND indexed_status = 0 + AND linked_place_id is null; ``` You also need to grant the website user access to the `country_osm_grid` table: -``` +```sql GRANT SELECT ON table country_osm_grid to "www-user"; ``` @@ -155,7 +208,7 @@ Replace the `www-user` with the user name of your website server if necessary. You can now drop the unused indexes: -``` +```sql DROP INDEX idx_placex_reverse_geometry; ``` @@ -184,8 +237,8 @@ CREATE INDEX idx_postcode_geometry ON location_postcode USING GIST (geometry); CREATE UNIQUE INDEX idx_postcode_id ON location_postcode USING BTREE (place_id); CREATE INDEX idx_postcode_postcode ON location_postcode USING BTREE (postcode); GRANT SELECT ON location_postcode TO "www-data"; -drop type if exists nearfeaturecentr cascade; -create type nearfeaturecentr as ( +DROP TYPE IF EXISTS nearfeaturecentr CASCADE; +CREATE TYPE nearfeaturecentr AS ( place_id BIGINT, keywords int[], rank_address smallint,