Merge branch 'main' into samehkhamis/rail-and-hud-cleanup

This commit is contained in:
Sameh Khamis authored and GitHub committed 2026-11-18 23:33:51 -08:00
commit 6502028fbe
9 files changed
+296 -35

No files matched your search

+8 -2
View File
@@ -966,7 +966,8 @@ the fleet set loaded at startup, so opening a card fetches no model.
country and Wikidata id. `src/data/wikidataCities.js` reads it on the first
lookup and answers `nearestCity` (the largest city within 12 km, else the
nearest within 60 km), `citiesAround`, `findPlace` ("Paris, France", or the
nearest namesake within 150 km of the view, else the largest) and
nearest namesake within 150 km of the view, else the largest; asked to, it
counts the smaller places of the detail tiles near the view too) and
`countryName`. Names match without case or accents ("lodz" finds Łódź). The
app never calls Wikidata; `scripts/build-wikidata-cities.mjs` rebuilds the
pack and fails if well-known cities are missing or a known grouping such as
@@ -8257,7 +8258,12 @@ clears them but the browser's own site data. Setting `PHOTON_URL`
empty turns the suggestions off along with it. Small places come from the
bundled Wikidata packs and are never looked up online; a small place with
the name of a city within 3 km in the same country is that city, and only
the city is listed. At most 64 detail tiles are kept in memory, the least
the city is listed. A place named in "villages near …" is the nearest of
that name within 150 km of the view, small places included, so a village in
view comes before a bigger namesake far away; with none near, the largest
city of the name. Small places are looked for within 500 km at most, so a
lookup asked for a wider radius reads only the detail tiles around its
centre (the search box asks for 150 km at most). At most 64 detail tiles are kept in memory, the least
recently used dropped first.
### Place-search providers