Context
Current raw Google Maps saved-list payloads can contain localized or partial address strings that are not reliable enough for country/address inference.
Examples observed:
- Monaco saved-list data still includes addresses ending in
モナコ, even when the final Google Maps URL is reloaded with hl=en.
- Okinawa saved-list data can include address tails such as
2 Chome−19−17 RS-ONE 1F, which should never be treated as country/address canonical data.
- Adding
hl=en to the final resolved https://www.google.com/maps/... URL changed page/runtime wrapper artifacts but did not change the parsed saved-list payload. The best-ranked placelist payload and extracted place list were unchanged for both Okinawa and Monaco.
Goal
When Maps API lookups are enabled, canonicalize place address data through the API instead of trusting the scraped saved-list address string.
Proposed behavior
For each enriched place, store both:
formatted_address_en: canonical address requested with English language preference.formatted_address_local: canonical address requested with the place/local language preference where available.- Optionally structured address components for country/admin/locality/postal code if available from the API response.
Use the canonical English address/components for site-level country and country-code inference. Preserve the local-language address for future translation/local display work.
Acceptance criteria
- Monaco resolves to English country metadata (
Monaco, MC) while retaining local address data separately if returned by the API.
- Okinawa resolves to Japan (
Japan, JP) and street/building fragments cannot become country names.
- Existing raw scraped
address remains available as source data, but generated display/search fields prefer canonical enriched addresses when present.
- Tests cover at least Monaco-style localized country tails and Okinawa-style street/postal fragments.
- The enrichment cache schema/versioning accounts for the new address fields so stale cache entries can be refreshed safely.
Notes
This should wait until Maps API lookups are intentionally enabled. The hl=en scraping experiment suggests URL language parameters alone are not sufficient for canonical address data.
Context
Current raw Google Maps saved-list payloads can contain localized or partial address strings that are not reliable enough for country/address inference.
Examples observed:
モナコ, even when the final Google Maps URL is reloaded withhl=en.2 Chome−19−17 RS-ONE 1F, which should never be treated as country/address canonical data.hl=ento the final resolvedhttps://www.google.com/maps/...URL changed page/runtime wrapper artifacts but did not change the parsed saved-list payload. The best-ranked placelist payload and extracted place list were unchanged for both Okinawa and Monaco.Goal
When Maps API lookups are enabled, canonicalize place address data through the API instead of trusting the scraped saved-list address string.
Proposed behavior
For each enriched place, store both:
formatted_address_en: canonical address requested with English language preference.formatted_address_local: canonical address requested with the place/local language preference where available.Use the canonical English address/components for site-level country and country-code inference. Preserve the local-language address for future translation/local display work.
Acceptance criteria
Monaco,MC) while retaining local address data separately if returned by the API.Japan,JP) and street/building fragments cannot become country names.addressremains available as source data, but generated display/search fields prefer canonical enriched addresses when present.Notes
This should wait until Maps API lookups are intentionally enabled. The
hl=enscraping experiment suggests URL language parameters alone are not sufficient for canonical address data.