Google Maps API (server-side) limits

Asked

Viewed 430 times

2

I am designing a system in PHP, which will access the Google Maps Geocoding API via URL (Curl).

This system will be sold to different clients. All sold systems will be on the same server.

Each system/client will have its own Key (API Key).

PROBLEM:

The Google Maps API has access limit by Key. The Google Maps API will be accessed by several different Keys, however, coming from the same IP. Because of this, can Google understand a fraud? Because apparently, it looks like someone is using multiple Keys in a single app, trying to bypass the access limit?

1 answer

1

I believe that this issue is more legal than programming. Since just reading the terms will find this information.

I don’t even know if I should answer and I don’t know if the information here will be correct, the ideal would be to contact Google or read more slowly all the terms of Google Maps. I just looked for some topics I thought you mentioned about using keys.


"The Google Maps API has Key Access Limit. The Google Maps API will be accessed by several different Keys"

If your intention is just to "bypass" the limit, ie circumventing the limit using multiple keys this is clearly a violation of the terms of Google:

Quota Limits are enforced on a Unique project Basis, and you may not take any action to circumvent quota Limits. For example, you may not create Multiple Projects to compound and exceed quota Limits.

You can hire bigger limits and not have that worry. The Google limit is per application and not per customer, so you are a single application and it makes no sense that you have more than one key.

In addition, not all Google Maps features need keys, as mentioned here.

This is clearly defined here:

No use Beyond transaction Limits and Usage policies. If your Maps API Implementation generates a high volume of transactions, Google reserves the right to set transaction Limits, as described in the Maps Apis Documentation here. Google also reserves the right to set other Usage policies in the Documentation from time to time. If you want to Engage in use Outside These transaction Limits or Usage policies, you can Purchase more Usage Capacity through the Maps API Standard pricing plan, or you can contact the Google Maps options to address your needs. Google may decline your request, or condition Acceptance on your Agreement to Additional Terms and/or charges for that use.

If each key has 2500 calls and you own 10 keys automatically you are able to make more calls than the limit, after all now you can make 25000 plus all keys.


Google has restrictions on commercial use as mentioned:

However, not all commercial uses are allowed. For example, if your site meets any of the following criteria, you should purchase the appropriate license from Google Maps Apis Premium Plan:

Your website is only available to paying customers. Your website only can be accessed from your company or your intranet. Your application is related to business expedition, fleet management, tracking of business assets or similar activities.

So if this is the case you will have to migrate to the "Premium Plan" mentioned above, which will no longer make sense in having multiple keys.

This is also defined in:

No Asset-tracking unless you have Purchased the applicable Enterprise License. Unless you have Purchased an applicable Premium Plan or Maps Apis for Work Icense that expressly Permits you to do so, you will not use the Service or Content for Commercial Asset-tracking or in Maps API Implementations Whose Primary purpose is to assess Vehicle Insurance Risks:

Commercial Asset-tracking includes Dispatch, Fleet management, and Maps API Implementations that track your (or your end users') Assets (for example, private or Commercial Transportation Applications, including taxi and Vehicle-for-hire Applications).

Non-commercial Asset-tracking implementations include Applications used for a non-commercial purpose (for example, a free, publicly Accessible Maps API Implementation that displays real-time public Transit or other Transportation status information or that Allows end users to share real-time Location with others).



Sources:

  1. https://developers.google.com/maps/faq
  2. https://developers.google.com/maps/terms#section_10_4
  • No, I have no intention of crossing the line, on the contrary, my doubt is to avoid future problems. But I was upset that Google did not allow to put different systems on the same server, because by using the same IP, could arise problems.

  • But what would be the problem of using a single key, rather than using several different keys?

  • Because each client system is independent, but will be on the same hosting server. It would be unfair that because of 1 client who used the system a lot, the others are also blocked to use the map of their respective system

  • The correct is for every customer to have his key.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.