The reason for which the plugin uses lat/long details store in the db and not obtained from google is quite simple. Let`s say we have a site with 200 properties...and we want to find out what properties are close to the current one. If we get the details from google, we have to select 200 properties from db, ask google for the lat/long details for all of them based on address, then perform the radius calculations (based on a math formula) and display only X properties that are nearby the current one. This approach is totally unacceptable when it comes to resource usage.
Instead, we use the lat/long details stored in the db in property details and select just X properties that are located close to the current property and display them. Simple and way faster.
Yes, the "space in language" problem also happens with the standard Joomla template.
Please provide a link where I can see this.