if i drag it, will it change the coordinates in SQL?

I’m in Australia and for fun, I typed in 809 Southbridge Street, Auburn and pressed the set address button and it mapped to “Bridge Street , Ourimba” but kept the street address as 809 Southbridge Street.

Once I had typed in 809 Southbridge Street I couldn’t get the address field to update by moving the icon on the map either?

Seems if the Suburb and Postcode don’t match the Set Address button will produce unpredictable locations?

Thanks,

Stiofan

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.

Would all the GD functionality still work so long as there was a valid Lat and Lon for a listing?

It might solve a few problems being created in different parts of the world by different address formats?

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