This page is only for customers with the new version of the Google Maps APIs Premium Plan, which became available in January 2016.
Have the Premium Plan or a previous license?
To determine which license you have:
> In the Google Cloud Support Portal,
click Maps: Usage Report on the left.
> Does the ID at the top of the report have the following format?
gme-[company] & proj-[number] ([type])
If yes, you have the Premium Plan.
If no, you have a previous license
(Maps APIs for Work or Maps API for Business).
Introduction
With the Google Maps APIs Premium Plan, your application’s requests for APIs consume Maps APIs Credits, which you purchase annually. The following examples show how you to estimate annual Maps APIs Credits consumption for typical mapping applications: a simple real estate listings map and a more complex store locator.
To estimate your application’s credits consumption in these examples, consider the following:
- Your application’s user experience
- Which APIs your application uses
- A few implementation details
- How often your application is used
With this information, you can estimate of the number of credits your application will consume annually. To make your calculations easier, you can use the Google Maps APIs Premium Calculator.
Example 1: Real estate listings map
User experience
Agents in your real estate offices can view all of your company's active listings on a map on your internal web site. An agent can click a marker for a listing on the map to see an info window with details about the property from your database, including the listing agent, property address, square footage, a photo of the property, and a street view image. In the info window, the agent can click the "Get Directions" button, select their office location, and then view directions to the property.
Maps APIs used
| API | Features provided |
|---|---|
| Maps JavaScript API | Displays the map on the internal web page |
| Street View Static API | Provides the panoramic imagery in the info window |
| Geocoding API | Provides the latitude/longitude (lat/long) coordinates of the listing, using your database of property addresses |
| Directions API | Provides directions to the property |
Implementation details
- You have 30 offices in Colorado State, US, and approximately 3,000 agents.
- Your real estate database typically has about 25,000 active listings.
- You geocode your listings daily, using the Geocoding Web Service.
Agent usage assumptions
You estimate 3,000 daily visits to the listing map on your internal web site. For each visit, you estimate that:
- An agent views the info window for 5 properties.
- An agent requests directions for 1 property.
Calculation of Maps APIs Credits
Map loads usage
| API | Usage |
|---|---|
| Maps JavaScript API | 1 map load × 3,000 visitors × 1 credit = 3,000 credits |
| Street View Static API | 5 map loads × 3,000 visitors × 0.25 credits = 3,700 credits |
Total map loads: 3,000 + 3,750 = 6,750 requests per day × 365 days = 2,463,750 credits needed per year
Web service APIs usage
| API | Usage |
|---|---|
| Geocoding API | 25,000 geocodes per day |
| Directions API | 1 request × 3,000 visitors = 3,000 queries |
Total QPD: 25,000 + 3,000 = 28,000 QPD
QPD is below 100,000 free daily limit, so no additional credits are required.
Annual Maps APIs Credits required
2,463,750 credits for map loads + 0 credits for web services = 2,463,750 credits
Example 2: Store locator
User experience
Your customers can use the store locator on your web site or in a mobile app (Android/iOS) to find up to 50 of the nearest stores from a specific location. The customer enters their current location or any other starting point address or point of interest. As the customer begins typing in the starting point, the application automatically displays a list of matching addresses or place names. When the customer selects a place from the list, the map displays markers for 50 of the nearest stores from that place. The customer can then click a marker to see an info window with details about the store, including the address and hours of operation (from your stores database), the distance to the store, and a panoramic image of the location. The customer can then choose to get directions to the store.
Maps APIs used
| API | Features provided |
|---|---|
| Maps JavaScript API | Displays the map on the web site |
| Mobile SDKs (Android/iOS) | Displays the map on mobile devices |
| Street View Static API | Provides the static (non-interactive) panoramic imagery in the info window |
| Geocoding API | Provides the latitude/longitude (lat/long) coordinates of the store, using your list of store addresses |
| Distance Matrix API | Provides the distance and travel times between the starting point and the stores in your database; this information appears in the info window |
| Directions API | Provides directions to the store |
| Places API JavaScript library and Web Service |
|
Implementation details
Here are a few implementation details that affect your usage estimation:
- You have 1,500 stores worldwide.
- You geocode your 1,500 store locations once every 30 days, using the Geocoding Web Service.
- You use your database’s distance function to search all of your geocoded addresses to retrieve the nearest 50 stores from the visitor’s starting point.
- You call the Distance Matrix API to display the driving distance and times from the starting point to the 50 nearest stores retrieved by your database. By calculating the distances for only 50 stores, you keep the elements per request well below the 625 maximum.
Customer usage assumptions
You estimate 2,000 daily visits to the store locator: approximately 1,000 visits on the web site and 1,000 visits on mobile devices. For each visit, you estimate that:
- A customer types an average of 8 characters to find their starting point.
- A customer searches for 1 starting point and selects 1 starting point.
- A customer clicks an average of 2 markers to view the info window.
- A customer gets directions for 1 location.
Calculation of Maps APIs Credits
Map loads usage
| API | Usage |
|---|---|
| Maps JavaScript API | 1 map load × 1,000 visitors × 1 credit = 1,000 credits |
| Mobile SDK | 1 map load × 1,000 visitors × 1 credit = 1,000 credits |
| Street View Static API | 2 map loads × 2,000 visitors × 0.25 credits = 1,000 credits |
Total map loads: 1,000 + 1,000 + 1,000 = 3,000 requests per day × 365 days = 1,095,000 credits needed per year
Maps JavaScript/Web service APIs usage
| API | Usage |
|---|---|
| Geocoding API | 1,500 geocodes = 1,500 queries (per month) |
| Directions API | 1 request × 2,000 visitors = 2,000 queries |
| Distance Matrix API | 1 request × 2,000 visitors × 50 nearest stores = 100,000 elements |
Total QPD: 2,000 + 100,000 = 102,000 QPD
Total QPD overage: 102,000 - 100,000 free QPD = 2,000 QPD overage × .25 credits = 500 credits per day / 182,500 credits per year
Total QPD for geocoding: 1,500 × .25 credits = 375 credits per month / 4,500 credits per year
Total annual overage: 182,500 + 4,500 = 187,000 credits per year
Places API usage
| API | Usage |
|---|---|
| Place Autocomplete in the Places API | 1 searches × 8 characters per search × .1 credits = .8 × 2,000 visitors = 1,600 credits |
| Place Details in the Places API | 1 request × 2,000 visitors × 2 credits = 4,000 credits |
Total Places API usage: 1,600 + 4,000 = 5,600 requests per day / 2,044,000 credits per year
Annual Maps APIs Credits required
1,095,000 credits for map loads + 187,000 credits for QPD overage + 2,044,000 credits for Places requests = 3,326,000 credits