fix(geocode): keep a nearby whole-name match as the last choice, and document the region rule

A query with a comma counted as "place, region", so a nearby place whose
own name has a comma ("Bed, Bath & Beyond") no longer won the nearby pass
and the unbiased pass could fly to a namesake far away. Its whole-name
match is now kept as the last choice, after the region checks of both
passes. CURRENT-STATE describes the place-region rule.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
quanticsoul4772andClaude Opus 5.5 committed 2026-10-25 17:07:46 -07:00
1 parent 7775f6007d
commit 91769d74b8
3 files changed
+41 -6

No files matched your search

+5 -1
View File
@@ -5191,7 +5191,11 @@ HTTP refusals and outages remain retryable. Searches share a 12-second total
deadline, with Photon requests capped at six seconds each. Caller/application
cancellation stops retries and late cache writes. Replacing a location search
cancels the previous lookup; disposing its controls cancels the active lookup. Photon uses a soft proximity bias, up to five
candidates, and an unbiased retry for name mismatches. Invalid/wrapped bounds
candidates, and an unbiased retry for name mismatches. A "place, region" query
only accepts a candidate named exactly for the place whose city, county, state,
country or country code (or USA/UK) contains the region; nearby results that
fail that check are retried unbiased, and a nearby place whose whole name is the
query (one with a comma in it) is the last choice. Invalid/wrapped bounds
are omitted rather than framing the wrong part of the globe.
### Map Stack Switcher (June 2026)