{{ searchResult.published_at | date:'d MMMM yyyy' }}

Loading ...
Loading ...

Enter a search term such as “mobile analytics” or browse our content using the filters above.

No_results

That’s not only a poor Scrabble score but we also couldn’t find any results matching “”.
Check your spelling or try broadening your search.

Logo_distressed

Sorry about this, there is a problem with our search at the moment.
Please try again later.

The Google Maps API is probably one of the most popular APIs out there, and it's not hard to understand why. There are countless applications to which mapping functionality can be applied.

For developers and businesses looking for powerful mapping functionality, the free Google Maps API has been a godsend. But earlier this year, Google announced that it would be implementing usage limits for the Maps API, and on Wednesday, it followed through.

Going forward, those using the Maps API will be limited to 25,000 map loads per day, or 2,500 map loads per day when the Styled Maps feature is applied. Anyone exceeding these limits can either reduce usage, pay fees for excess usage above the limits or purchase a Maps API Premier license.

The fees for excess usage range from $4 to $10 per 1,000 excess map loads. For instance, a user of the JavaScript Maps API v3 will pay $4 for every 1,000 map loads above 25,000., while a use of the same API with Styled Maps will pay $4 for every 1,000 map loads above 2,500 and $8 for every 1,000 map loads above 25,000.

"For very popular sites," Google notes, "Maps API Premier is likely to be a more cost effective option." That makes sense, particularly for free, consumer-oriented websites that can't stay under the limits. After all, generating more than $4 to $10 CPM in, say, ad revenue for every 1,000 pageviews that add to excess page loads may be a tall order.

The good news is that Google won't be enforcing its new limits until 2012, but needless to say, some Maps API users probably won't be happy with the changes in the first place.

And therein lies the rub: there's no doubt that the Google Maps API offers a considerable amount of value, but unlike companies that launch their APIs on a paid basis, Google tends to find itself implementing revenue models after giving the farm away for free.

That could be smart, 'bait and switch' is devious lock-in strategy if your users can't easily turn to a competitor, but it also comes with risk.

Google's AppEngine pricing changes didn't go over too well, and while there's a very good chance the limits and fees for the Maps API won't cause a huge backlash because its position in the market is stronger, Google probably shouldn't make a habit of launching new offerings without clear pricing models beforehand if it wants developers and businesses to trust it as a platform provider.

Patricio Robles

Published 28 October, 2011 by Patricio Robles

Patricio Robles is a tech reporter at Econsultancy. Follow him on Twitter.

2392 more posts from this author

Comments (2)

Terry Chisholm

Terry Chisholm, Manager of Digital Services at Pulse Group

The only restriction I was aware of previously was the geotagging bit, that converts an address to a latitude and longitude feature. Now they are restricting the rest of the service as well?

Hope Bing make their API easier to convert from google maps api. I like their bird's eye maps better anyways!

almost 5 years ago

Terry Chisholm

Terry Chisholm, Manager of Digital Services at Pulse Group

OMG! Just seen that the starting price is $10,000 per year! Shocking!!!!
http://www.google.com/enterprise/earthmaps/maps-faq.html

almost 5 years ago

Comment
No-profile-pic
Save or Cancel
Daily_pulse_signup_wide

Enjoying this article?

Get more just like this, delivered to your inbox.

Keep up to date with the latest analysis, inspiration and learning from the Econsultancy blog with our free Daily Pulse newsletter. Each weekday, you ll receive a hand-picked digest of the latest and greatest articles, as well as snippets of new market data, best practice guides and trends research.