Address mapping to wrong location

I had something similar happen.
I just dragged the marker to the right spot and saved the listing.
That fixed it.
We might just ask Vikas whether he can shed any light on this.

In my case the I think the problem is due to whatever the js does to select/validate the city and the mismatched locations are caused by Google not getting the correct city, or not being sent a city at all.

I’m finding it such a trial to set the city that I have disabled the js and I’m testing a simple droplist to make the city selection more straightforward.

That suits my site where I only have a dozen or so cities that are eligible to be listed and I don’t need/want users putting in other cities.

You could test the theory by logging the Google API requests vs the responses received.

I’ll let you know if my changes cause any matching problems.

There appears to be an issue with the API configuration for regions in general.

You mention this

The problem here is really down to the google api for mapping addresses, it’s not great with regions, anyone who wants to work with me to try and get this 100% let me know.

Thanks,

Stiofan

But the reality is regions can be geocoded in a number of ways and there is not realistically any universal approach that can be applied for every country in the world. Regions can and will be divided by political districts or states depending on the country level or ISO code.

From Google Developer Docs

region — The region code, specified as a ccTLD (“top-level domain”) two-character value. This parameter will only influence, not fully restrict, results from the geocoder. (For more information see Region Biasing below.

I have posted several times in the location manager forum about this issue and there is no response apart from to say its the Google API.

A more accurate statement would be that its not the Google API but the way that the data is coded in GD – working with Google Maps everyday as I do, its not Google that insists on the optional region geocoding for maps data – its GD. So the question is why?

I have had to totally abandon GD at this point as its impossible to set an accurate city or address as the API Region data its pulling is NOT configured correctly for most countries in Asia. Its not even possible to correctly set certain cities as these pull in inaccurate region data based on the political/admin districts.

If its that difficult at the backend, its not even an option to expect users to fiddle around with lat/lon, moving markers etc etc at the front end in the hope they can set an address

Possible suggestions to resolve this include:-
Prepopulating countries and cities only in GD
Making the Region Data optional as it is optional in Google just not GD
Configuring the Google Region API in GD for each country in the world to correctly match how the the city/region/country data is used

Would love to use GD but setting addresses correctly is a fundamental requirement in GD that for now may or may not work depending on your location

As Paolo pointed out, you can enter a full address into the address field and Google will find it. The problem is that the address is parsed to the GD fields and re-validated, incorrectly by Google.

Which is why I think an option to disable Google address validation might solve these sorts of problems?

Hi

Please see my post in the location manager forum. It is not possible to set street and city for several countries in Asia as the REgion data is automatically added to the city. The region data is added is not accurate and added in the wrong hierarchy.

E.g districts that are part of a city are added as the region data.

If you follow the example I added as a private post it can be easily replicated to troubleshoot. It includes the Wikipedia defined districts. You can also jump on google maps and try to add any of the places that crop up for hotels, bars etc

After 6 weeks of mentioning this we are now working with other directory themes. If you want to test any fixes you develop, please drop me a line.