Description
When the AI returns a very specific location string, Nominatim can't geocode it and no pin is dropped — the search silently succeeds on the AI side but produces no result on the map.
Steps to replicate
- Open a map block in the editor
- Type "Please tell me where Kafka's grave is" and hit Enter
- The AI returns a correct but overly specific string (e.g.
"Franz Kafka's Grave, New Jewish Cemetery, Prague, Czech Republic") — Nominatim finds nothing, no pin is dropped
Workaround: Ask at city level instead — "Please show me the city where Kafka's grave is" — which returns "Prague, Czech Republic" and drops the pin correctly.
Root cause
The system prompt instructs the AI to include "the location's name, the city and the country", which for a point-of-interest like a grave produces a string too specific for Nominatim to geocode. The fix would be tightening the system prompt to prefer city/country granularity over POI-level specificity.
Description
When the AI returns a very specific location string, Nominatim can't geocode it and no pin is dropped — the search silently succeeds on the AI side but produces no result on the map.
Steps to replicate
"Franz Kafka's Grave, New Jewish Cemetery, Prague, Czech Republic") — Nominatim finds nothing, no pin is droppedWorkaround: Ask at city level instead — "Please show me the city where Kafka's grave is" — which returns
"Prague, Czech Republic"and drops the pin correctly.Root cause
The system prompt instructs the AI to include "the location's name, the city and the country", which for a point-of-interest like a grave produces a string too specific for Nominatim to geocode. The fix would be tightening the system prompt to prefer city/country granularity over POI-level specificity.