Skip to main content

Geocoding - Region biasing

    Today we will have a look at a simple geocoding example wherein we will see the effects of region biasing on geocoding. First things first. What is region biasing in geocoding and why is it required; would be an obvious looking question here. The answer to this is pretty simple and straight. Region biasing means returning a geocoded address so that it falls in the region specified. Consider the example of the city named “Hyderabad” which is  present in India as well as Pakistan. Now, suppose that my target users are from India, then by using the region biasing property, the geocoder will always return the “Hyderabad” in India when a user enters a request for the same. I have taken the same example in the code, so that the region biasing geocoding concept would become much more clear.

    The code goes here…


    The code is pretty simple and does not need an explanation. The crux of the code lies in the following line of code.


    As you can see, the region property is set to “IN” which is a code for India. This is a hardcoded example, where the address to be geocoded is set to “Hyderabad”. Check out the line, var query = "Hyderabad". Now as the region is set to India the output that would be seen will be as seen in the result section above.

    Now change the region value to “PK”, i.e. Pakistan as,


    The output that you will see is as below:



    If you have any queries regarding the code feel free to leave a comment! Till the next Google Maps API v3 example…Keep mapping!

Comments

  1. I tried region=IN but still getting suggestions for outside india.
    I am using auto complete to show suggestion like google maps do

    ReplyDelete
    Replies
    1. Hi IndiaVote09.

      Could you let me know what were you looking for (geocoding) with region=IN?

      Please respond and I would be happy to check and revert!

      Regards,
      Shreerang.
      Like us on Facebook at https://www.facebook.com/pages/Spatial-Unlimited/185149371538692

      Delete

Post a Comment

Please leave your comments here...

Recommended for You

Form info window

         Today we will look at a Google Maps API v3 example to add a form in the information bubble! This is usually required when we wish to accept some data/information from the user! This data can be saved to a server in the form of an XML file or a database! The information can then be retrieved back at a later stage, when necessary!          In this example we will only look at form in the information bubble! The connectivity part with the server will be discussed in another post! So, today's code snippet is as seen below! <html> <head> <title> Google Maps API v3 - Adding marker and info window on Click and creating a form in the infowindow with the lat-lng information in it. </title> <script type="text/javascript" src="http://maps.google.com/maps/api/js?sensor=false"></script> <script type="text/javascript"> var map;    //When using ev...

India celebrates 62nd Republic Day

  India celebrates it's 62nd Republic day today! Wish you all a happy Republic Day!

Geocoding

    Geocoding is the process of converting addresses (like "Pune") into geographic coordinates (like latitude - 18.5193 and longitude - 73.8579), which you can use to place markers or position the map. The Google Maps API provides a geocoder class for geocoding addresses dynamically from user input. Accessing the Geocoding service is asynchronous, since the Google Maps API needs to make a call to an external server. For that reason, you need to pass a callback method to execute upon completion of the request. This callback method processes the result(s). To know more details about the geocoding requests, responses and results visit this link.     Understanding the geocoding requests, responses and results is very important for proper understanding and execution of any geocoding functionality in Google Maps API v3. Let us have a look at the following example...     The output of the above code will appear as seen in the results sectio...

Material UI, Google Polymer & Web Components

    Google introduced Material UI during the Google I/O a few days back. Since then the web is all abuzz with articles about material UI and what Polymer is and how these 2 fit together. In this article today, I will try and helps us all to get a better understanding of these new concepts.     So, let's start with Material UI first. Google has for long been trying to bridge the gap between the Web and the Android worlds with a unified user interface and Google's Material UI is a big step towards this. The new design philosophy is about dynamically adjusting the elements according to screen size, add more white space between elements, provide a lot of user feedback using animations, make use of bold UI colors and be flat and 3D about the design at the same time. Now that sounds really cool, isn't it? Well, actually it is and you will actually appreciate and enjoy it all the more when you watch the following video from this year's Google I/O.   ...

Google Map's Real-Time Traffic Layer...

    You can now check the traffic condition on the road before you leave for work, or a party or to your friend's place. Google's Traffic layer shows the traffic conditions in your area - LIVE!!! Live traffic data is available in major cities in the United States, France, Britain, Canada and Australia, with new cities and countries frequently added. The Google Maps API allows you to add real-time traffic information (where supported) to your maps using the TrafficLayer object. Traffic information is provided for the time at which the request is made. Consult this spreadsheet to determine traffic coverage support.     Let us now have a look at the Google Maps API - Trafiic Layer example. Copy the following code in a simple text file and save it as html. Click on this html file and it will open in your default browser. You will then see the traffic conditions in your area - LIVE...     The output of the above code looks as seen in the r...