With the Geo Maps feature in PRTG, it is possible to integrate Google Maps into the PRTG web interface. Are there any limitations that apply when using this Google service?
Important notice: In order to use Google Maps in PRTG Network Monitor v13 or later, you need to acquire a new API key for Google Maps API v3! See this article for more information.
Google limits the use of its Static Maps API to avoid exhaustive use. PRTG uses this API to display Geo Maps in the web interface. Thus, the API restrictions apply to all PRTG users using the Geo Maps feature.
Quote: Use of the Google Static Maps API is subject to a query limit of 1000 unique (different) image requests per viewer per day. If quota should be exceeded, the following image will be displayed instead of a Geo Map:
However, in every day usage of PRTG you will usually not reach this limit. Limits are reset every 24 hours.
For more information please see Static Maps API V2 Developer Guide, section "Usage Limits".
We just upgraded to PRTG 8, and it seem that we already have reached 1000 different image request. The text above says requests per viewer, what does that mean?
"frognkommune" asks: The text above says requests per viewer, what does that mean?
We simply do not know, Google doesn't tell us in detail. But it seems that they reset the counters every 24 hours. For more information please see Static Maps API V2 Developer Guide, section "Usage Limits".
Have you considered the option of using the Bing maps API instead, or perhaps make it an option within the application which map source to use? I say this because while Google has more up-to-date aerial imagery(which you don't presently support anyway), Bing has more up-to-date address location matching information. For my area, to even get close I have to manually enter Lat/Long geocode locations. On that note, since I have to do that, is it possible to use a alternate label for the location. For example, use a string in the Location field with the ability to encode a Google(or Bing) location search string with a alternate label. Something like:
123 Main St, Some City, Some State/Country [Home Office]
The address, or Lat/Long geocode, used by Google, the tag or reference in PRTG designated as "Home Office" and not the address or Lat/Long. PRTG could strip the  delimited varibles and use the information it contains to specify a friendly name.
For me, typing in: Postcode FriendlyName: allows geomaps to locate *and* display FriendlyName, so:
CR0 1XU Company HQ
Correctly locates the postcode, shows the map, marks it as
CR0 1XU Company HQ
Which doesn't explain it very well, but just try putting s friendly name after the Postcode and you will see what I mean.