The Google Maps .web services be an Google .services giving geographic information to your maps application. This guide serves just to present data basic to the majority of the distinctive services. Singular situated beneath:
· Google Maps Headings Programming interface
· Google Maps Separation Lattice Programming interface
· Google Maps Service Rise Programming interface
· Google Maps Geocoding Programming interface
· Google Maps Geolocation Programming interface
· Google Maps Streets Programming interface
· Google Maps Time Zone Programming interface
· Google Spots Programming interface Web Service
· Discover which Programming interface you require
Utilize the Programming interface picker to locate the correct Programming interface for your task.
More about the web services
The rest of this guide examines systems for setting up web service asks for and parsing the reactions. For specific documentation for each service, in any case, you should counsel the proper documentation.
What is a web service?
The Google Maps Service Programming interface gives these web services as an interface for asking for Maps Programming interface information from outer services and utilizing them inside your Maps applications. These services are intended to be utilized as a part of conjunction with a guide, according to the Permit Confinements in the Google Maps Service APIs Terms of Service.
These web services utilize HTTP solicitations to particular URLs, passing URL parameters as contentions to the services. By and large, these services return information in the HTTP ask for as either JSON or XML for parsing or potentially handling by your application.
A run of the mill web service ask for is for the most part of the accompanying structure: where service demonstrates the specific service asked for and yield shows the reaction arrange (typically json or xml).
Full documentation of each service is contained inside the specific designer guides for those services. Be that as it may, this guide serves to hold some normal practices helpful for setting up your web service demands and preparing your web service reactions.
HTTPS is required for all Maps Programming interface web service demands containing client information, or designer identifiers. Solicitations made over HTTP that incorporate touchy information might be rejected.
Building a Substantial URL
You may imagine that a “substantial” URL is plainly obvious, yet that is not exactly the situation. A URL entered inside an address bar in a program, for instance, may contain extraordinary characters the program needs to inside make an interpretation of those characters into an alternate encoding before transmission. By a similar token, any code that creates or acknowledges UTF-8 info may treat URLs with UTF-8 characters as “substantial”, however would likewise need to decipher those characters previously sending them out to a web server Google Maps Service This procedure is called URL-encoding.
We have to decipher unique characters since all URLs need to comply with the grammar indicated by the W3 Uniform Asset Identifier determination. As a result, this implies URLs must contain just an exceptional subset of ASCII characters: the commonplace alphanumeric images, and some held characters for use as control characters inside Google Maps Service The table underneath outlines these characters: When constructing a substantial URL, you should guarantee that it contains just those characters appeared previously. Adjusting a URL to utilize this arrangement of characters by and large prompts two issues, one of oversight and one of substitution: Characters that you wish to deal with exist outside of the above set. For instance, characters in outside