Skip to main content

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 section above. The map is initially centered at India, with no text in the search box. Now you need to put in the address that you wish to geocode in the search box and then click on search. If the entered address is valid, a marker will appear on the map at the appropriate location.

    There is some level of error-handling done in this example using the status codes of the geocoding facility in Google Maps API. The status codes return several values depending upon whether the geocode was successful or not and whether any result was returned. The following image will show one such condition where the geocode was successful but did not return anything as the entered address was invalid.


    Some may find the above example a little complex, but the example is not complex at all, it is just that you need to understand the geocoding requests, responses, results and status codes. If anybody wants me to write in depth about the theory of the geocoding, then I will definitely try and write to explain the stuff in as simple language as possible. Till then...Keep mapping!

Recommended for You

Difference between word-break: break-all versus word-wrap: break-word

The 2 CSS properties word-break: break-all and word-wrap: break-word appear to work in the same way or generate the same output, but there is a slight difference between the 2 and we will be discussing these differences today.



    Take a look at the example above. The difference is quite evident, however I will try to explain it further.

word-break: break-all Irrespective of whether it’s a continuous word or many words, break-all breaks them up at the edge of the width limit even within the characters of the same word
word-wrap: break-word This will wrap long words onto the next line.break-word adjusts different words so that they do not break in the middle.
    So if you have many fixed-size spans which get content dynamically, you might just prefer using word-wrap: break-word, as that way only the continuous words are broken in between, and in case it’s a sentence comprising many words, the spaces are adjusted to get intact words (no break within a word).     In case you want to exp…

Onclick polygon

Yesterday we had a look at a simple polygon example. But that example was not exciting as it was all hard-coded with no user interaction and which means no fun! Today's example will deal with creating a polygon on the fly, i.e. an on-click polygon in action!

    The code for creating a polygon is very much similar to creating a polyline! The only difference is that you need to replace "Polyline" by "Polygon" in such examples. Let's head on to our code.


    The output of the above code can be viewed in the result section above. If you have any doubts or queries regarding the above code then please comment here or feel free to drop me a mail! Till then, happy mapping!

jQuery Mobile's Next Big Step

Spatial Unlimited changes to The UI Dev


After being hosted on blogger 😣 for the last 6 years 📆, this page has finally been moved to Github.io
This means a few things for you, dear reader!

You will be redirected to the new page shortly! ⏩ ⏩ ⏩


Once crapy HTML is now better looking Markdown! 😍 😍


The entire blog is a Github repo! 😍 😍


Spatial Unlimited is now The UI Dev 😍 😍


Get directions between different states in India

Having seen a simple hard coded directions example yesterday, today we will have a look at another simple example but not an hard coded one. In today's  example we will see the directions between different states in India. We have two simple list boxes stating Origin and Destination as lists of the states in India. You can select a state from either of the lists and then you will get the directions between the two selected cities.

    If you see yesterday's code and today's code you will find a lot of similarities and so  it would be easy to follow. The code will look lengthy, but it is just because of the list boxes code. So don't worry about the code, just go for it.


    The output of the above code will look as seen in the results section above. Hope you find this code helpful in understanding the directions services even further. Tomorrow, we will look at another - a bit complex example. Till then, happy mapping.
Note: The above code will not display any results …

Two maps on the same page - Side-by-side

How good I am feeling to post a code example after such a long time! It's been all "news" over the past so many posts! Well now that I am finally doing a code example, I am posting a very highly requested code sample. Placing two Google Maps on the same page (Now that's simple you would say!), but side by side. Now this is the thing that most people struggle with. Well, implementing the second part is also very simple, as you will see in today's code.

    Let's see the code. Here it is!



    The output of the above code will be as seen in the result section above.

    As most of you will realize, there are two maps, one centered at "Pune" and other at "Noida". Why I chose these two locations? Well, just like that!...The main issue of concern is how the maps appeared side-by-side and not one below the other as would be normal behavior of two "div" elements used in the same page. Now here is the trick! Check out the the first