Geo field problem

If you select a country first, the city lookup does not work ... it only works if no country is selected (at least her in my testing environment)

Improvements:

Please see the new google map features here

• option for "visual.refresh" in article view and map list template

• region localization for better accuracy in geocoding for non US locations

Added.

• region localization for better accuracy in geocoding for non US locations

Added

How was this added?

Sergey Romanov

• region localization for better accuracy in geocoding for non US locations

Added

I would also like to understand this. How can we test? what are the steps?

I though that visual.refresh already contain this feature inside somehow :)

For example, to use a Maps API application localized to the United Kingdom, add &region=GB to the tag as shown below:

<script type="text/javascript" src="/ https://maps.googleapis.com/maps/api/js?sensor=false& ;region=GB">

Ok. Added. There was already language=en now I added region.

Hmm .. you implemented it based on the language. I think there would be a better approach.

Just think of english language. It will be most of the time US or GB, regardless where you are.

I see a better implementation with a field parameter for the region. If it is not selected, it can fall back to the language detection.

Like in my case it will set the parameter to GB while i would like a different region.

Think of portuguese -- it can be south america or in europe. If the search is based on the language parameter you will have a preference for europe, while your location might be in south america. With the similarity of city names, you will get a lot of wrong hits....

But I tage region from current language. it should always conform to what user is using. Isnt it?

Not really ...

see example of portuguese ..

or in my case, i will get GB as region ...

as mentioned .. if there is a region set in the parameter then it should take it, otherwise with no set region, use the language region as you did already ...

anyway, not sooo important ...

It was just to implement the new setting in a more precise (at least in my opinion) way

I think you are right. Parameter is always better. Because it gives more controll to end user.

I only think that region is going in union with language. Example I have Russian language and in parameters I set GB. How that will work? Would region be RU? And if I set RU in parameters what is my sile multilingual? Then it will set RU region for English too.

What do you think?

The region feature sets a preference for the geocoding, For a language preference there is another parameter.

See here:

Language Localization

The Google Maps API uses the browser's preferred language setting when displaying textual information such as the names for controls, copyright notices, driving directions and labels on maps. In most cases, this is preferable; you usually do not wish to override the user's preferred language setting. However, if you wish to change the Maps API to ignore the browser's language setting and force it to display information in a particular language, you can add an optional language parameter to the tag when including the Maps API JavaScript code, specifying the language to use.

Taken from the link in the initial post above.

The region setting is just a "fine tune". If you use the country select in the entry form, it will not be relevant. It only becomes relevant, when you use the geocoding without a country selector, since it will use the default preference for US.

Overall the parameter is not really soooo important. Therefore my suggestion to use it optional. If no region parameter is set in the field parameter it will just follow the default behavior .. Either get it from the language or even ignore it.

The way it is now, can be misleading (but it might only affect the geocoding in some very isolated cases) ... Not a high priority ..

I see. I'll change it to parameter.