When using "NamedPointLookup" , all entries in the location database get matches for alternative spellings from geonames.org
However, if a city has dashes in its name like 'La Roche-sur-Yon' or space like "La Roche sur Yon", NamedPointLookup does not often return a correct result.
Workaround exists like https://support.qlik.com/articles/000060042 and https://community.qlik.com/t5/Qlik-GeoAnalytics-Documents/How-to-improve-the-lookup-accuracy/ta-p/15...
But we cannot modify the data entered by users into data sources and it is not possible to modify the script every day when a new data source about a city name is not exactly what "NamedPointLookup" expected to detect the GPS coordinates.
Thus, I suggest an improvement of "NamedPointLookup" to detect at least a space or dash character entered into a city name. (for example), thus obtain a sufficient quality of detection of city's GPS coordinates,