Monitor map loads and quota Updated!
You can monitor the use of your maps and check the status of your quota. The lower-left corner of the Maps Engine window shows you their current status, as in this example:
Quota usage as of 10/5 Public map loads:2% used Private map loads:18% used Storage:1% used
After you've added or deleted data, you'll see the new quota usage numbers within 2 to 10 minutes. The numbers refresh more slowly for bulk deletions than for other operations. This quota usage shows all map use, including API use. However, the graph shown in the "Published Map Analytics" section of the Maps Engine dashboard shows only Google Maps Engine use and does not reflect API use.
This article describes the map analytics displayed in the Maps Engine dashboard, how map loads are calculated, how storage is calculated, and what happens when you reach your quota. Map loads on Google properties, such as maps displayed as part of the Google Maps Engine public data program, will not incur any charge.
Maps Engine dashboard
The following image highlights the important parts of the Maps Engine dashboard. Note that the map list and accompanying usage graph show 10 pages at a time, but some of the usage totals are for the complete set of maps for this account (all pages).
How map loads are calculated
The map load calculation involves a number of factors, including a map's access control, the client used to view the map, and the number of layers viewed.
Public and private map loads
Public map loads occur when map viewers display or query published maps and layers that are shared as "Public on the web." (See Making data public.)
Private map loads occur when maps that are not shared as "Public on the web" are displayed. Maps Engine includes in this number the display of maps that have not yet been published (drafts) within Maps Engine. You might notice that the private map load number increases even before you've published maps, but this use by map editors is typically negligible in relation to your total quota.
What constitutes a map load
A map load is a unit of charge that triggers when a user displays a published map, using one of the Google interfaces described in How users can view your maps and Programmatic access to maps and layers.
These events cause Maps Engine to charge your account for one map load:
- A user views a map (by loading into a browser any of the URLs shown in the Access Links dialog, displayed when the user clicks ).
- A user views a layer, either because the layer is visible by default when the map appears or because the user explicitly chooses to view it. One map load is charged for each layer viewed.
- For WMS, one map load is charged for the
GetCapabilities()request (the initial request that is made only once), and one map load is charged for every
GetMap()request (one or more requests, based on panning and zooming). A single
GetMap()request can, based on client support, contain one to many layers, composited into a single request
- A user downloads a data source from Google Maps Engine.
- A Maps API application uses the visualization library's MapsEngineLayer class to request a layer in a Maps Engine map. One map load is charged for each layer requested.
- For every write request made by a Google Maps Engine API application, one map load is charged. Also, for every 10 read requests made by a Google Maps Engine API application, one map load is charged. See the Google Maps Engine API documentation.
The frequency at which Google applies the map load charge differs for public map loads and private map loads (in any of the supported clients):
- For public map loads, the charge occurs once per user session. A user can view the map until he or she closes the browser.
- For private map loads, the charge occurs once each time the user is authenticated. Authentication is valid for 60 minutes and re-authentication occurs automatically. Therefore, if a user views the map for 70 minutes, he or she is charged twice.
Here are some examples of map load charges:
- A map has four layers that are turned off by default but not locked. A viewer opens the map and turns on only two of the layers, leaving the others turned off. Your account is charged for three map loads, one for the map itself and one for each layer that the user views.
- A Maps API application uses the
MapsEngineLayerclass to render three Maps Engine layers. Each time someone opens the application to view the layers, your account is charged for four map loads, one for the enclosing map and one for each layer. If the content is access controlled, another four map loads are charged after 60 minutes.
- A GIS application uses WMS to connect to a map that has three layers visible. Maps Engine charges your account for one map load at the original connection request and one for every subsequent request. If the application requests each layer in a separate request, each layer counts as a map load, one per request. If the application splits up the map viewport into tiles and issues WMS requests for each tile, then each tile request would count as a map load.
How storage is calculated
The storage percentage indicates the amount of data that you've uploaded in relation to the total storage that you've purchased. The measurement is based on what you upload rather than the size of the uncompressed data, so if you can use a compressed format to upload, you'll conserve storage quota.
When you reach your quota
When you exceed your map load quota, Google stops serving your maps and responding to Google Maps Engine API queries. When you exceed your storage quota, Maps Engine no longer allows you to upload data.
Here's what to do when your quota has been exceeded:
- If you're a map editor, contact your Maps Engine administrator.
- If you're an administrator and want to buy additional quota, contact your Google sales representative. If you need an emergency service restoration, the Support team can help. Log into the Google Enterprise support portal and create a case, copying your sales representative if you have the appropriate name.