fix(search): read hemisphere letters separated from the number (#1340)

Support spaced hemisphere coordinates while rejecting malformed numeric fragments and ambiguous component assignments. Include regression tests and runtime documentation.

Contribution by @rudycelekli.
This commit is contained in:
Rudy Mizrahi Celekli authored and GitHub committed 2026-10-24 23:39:51 -07:00
1 parent 5b8e6fbc38
commit b07352ea6a
4 files changed
+87 -6

No files matched your search

+6
View File
@@ -768,6 +768,12 @@ transports and cancellation through response parsing. Stop and application
teardown abort pending connections; reconnect requests a new client secret.
Microphone, radio handoff, tool schemas and default model behavior are preserved.
Coordinate search accepts whitespace-separated decimal degrees with prefix or
suffix hemisphere letters, including `40.7128 N 74.0060 W`. Components require
an actual separator and an unambiguous hemisphere assignment; malformed numeric
fragments and scientific notation fall through to geocoders instead of becoming
exact coordinate results.
Geospatial lookups are composed through `src/search`: forward/reverse geocoding,
text/nearby search and routing use configurable providers/endpoints. Annotation,
HUD and voice consumers share the configured service. Existing Google/Photon