Google warns that rate limits, overage fees are coming to Maps API
arstechnica.com
arstechnica.com
While Google isn't exactly doing that here, it's coming awfully close.
I worked as the support engineer for the Google Maps API starting in 2007, in the early days of the API. We didn't think about monetization then. But then the GFC happened, and all over Google, there was a bigger emphasis on monetization -- basically every product had to eventually monetize. We experimented with different types of ads, but as it turns out, map-based advertising is difficult -- it's hard to know why a user is looking at a particular map, it's hard to get advertisers to geo-locate their ads accurately, it's hard to squish ads on a map without adding clutter, etc. While we continued to experiment with ads, we started talking about "ala carte" pricing, letting developers pay-per-view, per-geocode, etc, as a form of monetization.
That was about the time I left Google, when the monetization strategy was still unclear. It looks like they managed to implement ala carte from the technical perspective and decided to introduce it. Though it is a harsh reality check for developers who are already using the Maps API on popular free websites, I think its probably for the best. If I was given the choice between no Maps API at all, a Maps API with (not-so-relevant) ads, and a Maps API with incremental pricing, I'd personally opt for the latter. And who knows, maybe map-based ads will become an option in the future for those who prefer that option.
And if the pricing doesn't work for your site, there are multiple open-source mapping libraries that could use some love to bring them up to par with the Google Maps API (both from the developer & user usability perspective). I mentioned some in this talk: http://www.slideshare.net/wuzziwug/open-maps-or-close-enough... ...but there have been a few new entries in the space since then.
(Note: As I no longer work for them, nothing I say should be taken as official word from Google.)
And Justin O'Bierne had some great blog posts on why Google Maps work so well from a usability perspective:
http://web.archive.org/web/20110130154705/http://www.41latit...
Sadly, he's taken down all of his posts.
The "Shark Week" ad that literally screamed at me at 11PM was the straw that broke my mental back. I immediately installed AdBlock.
Their main *.openstreetmap.org has Tile Usage Policies, but there are other companies that provide free serives, and you can also host it yourself, render your own map, and pay your own bills. The data & tool chain is entirely Open, so you are not at the mercy of anyone.
I'm using the GMaps API for geocoding addresses and in that regard it's the best one available, especially since it has a pretty high tolerance for spellings and non-standard address formats.
I'm not certain how many GMap implementations there are that exceed a 25k/day load, but my back-of-the-napkin guesstimation is <10% of all sites that use Google Maps.
But, those are exactly the sites that I want using my maps, instead of Yahoo or Bing or some other provider.
Unless there's something I'm missing, this seems penny-wise and pound-foolish.
I've been wondering for a long time when this would come- the processing (getting directions, geocoding, etc) and bandwidth (for map images) demands must be huge, with comparatively little payback.
It'll be interesting to see how many big operations pay up, and how many switch. To an extent switching might be futile- if Google can't afford to keep the maps offering free, do you really think Yahoo can?
I'm more thinking about the costs of developing the software and gathering the data. And also the perceived _value_ of the data, independent from its costs. Ever tried to buy the kind of data Google uses on their backend, with terms of use that would support the kind of services Google offers? Good luck--both with terms and then with pricing. Other companies have been charging a fortune for this data.
> It'll be interesting to see how many big operations pay up, and how many switch. To an extent switching might be futile- if Google can't afford to keep the maps offering free, do you really think Yahoo can?
Regardless of whether they can, with Google pulling back, don't you think Yahoo et al. will want to raise their prices?
- They will be expected to pay a fee of $4 per thousand loads in excess of the limit.
- The cap is set to 2,500 loads for styled maps that customize the presentation.
- After 25,000 loads, the overage fee for styled maps will bump up to $8 per thousand. "
That is no joke, a $4 - $8 CPM on map loads means your app has to be doing substantially better than that, which is NOT an easy enterprise.
They are giving you over 9 million requests a year for free. Its not unreasonable to expect the profit from that to help subsidize the excess,
$4-8/CPM is far more than most ad networks pay. Perhaps Google is deliberately trying to get rid of most major GMaps users. If they follow through on this, they will be successful.
The $10k/yr Enterprise licence works out to $27/day which breaks even with the incremental pricing at 58k visits/day.
That's $68 cpm.
With some pushback they increased it to 1M impressions a year, but it's still a bit ridiculous.
At least there are alternatives:
1) Yahoo maps
2) Bing maps
3) OpenStreetMap
4) Nokia Maps
5) Cloudmade
http://developer.mapquest.com/web/products/open/directions-s...
They are one of the poster children for early success and then resting on their laurels while the competition ate their lunch.
I'm not a small business owner, though, so I don't know how much one would generally pay for email, or how much $50/person/yr is compared to the rest of the business.
If you could mix and match free and non-free accounts this would work great, but you can't. Again, I'm talking about companies with razor thin margins where the technology side is not super important. What do they do now? They mainly use free gmail/live/yahoo accounts.
As things stand at the moment the company I'm working for is in exactly that boat of some staff depending on email, and others only needing to retrieve a single email on each day they're working. We're working around it right now by just getting them to give us their personal email address.
That probably won't scale long term, but for now it does the job, and if we get to the point of needing more then I may just throw together a quick and dirty mail server for the people who don't need the convenience of Google Apps syncing between devices for them.
Meanwhile, you seem to be making a snippy ("sorry") counter-argument that his calculations are failing to take into account that if he had that much money to spend, he would be underestimating the cost of his system administrators, which would cost more than that.
I am sorry, but I don't understand... you both seem to be agreeing with and arguing with his point, by claiming that something unrelated (the units don't even seem the same to me: money made per employee vs. money spent per administrator) was not taken into account.
But who knows? Maybe Google saw that most businesses use 15 or 20 email accounts, so if they offered something like that, they'd lose a lot of money.
Aren't the limits IP based? This page on Google's 'Geocoding Strategies' seems to say so: http://code.google.com/apis/maps/articles/geocodestrat.html#...
So as long as your call to the Maps API goes out client side, aren't you ok?
http://code.google.com/apis/maps/signup.html
So to avoid it in that sense you'd have to force every one of your clients to go grab an API key and input it.
http://groups.google.com/group/google-maps-js-api-v3-notify/...
Sounds like they're laying the ground work for v3 to use API keys again.
Google Maps API is still free! Just has a limit of 25k maps/day. That means pricing only affects the top 0.35% sites!
https://twitter.com/#!/GoogleMapsAPI/status/1296873737002762...
I quite like the Google Maps API but in my company we're just not able to pay for things with credit cards or in fact to pay for anything we don't know the cost of up-front (i.e. variable billing). We'll happily and routinely pay hundreds of millions to suppliers so long as we have a contract, of course.
This is no doubt more of an indictment of my employer's internal processes and policies rather than Google, but it does mean that the "standard" maps platform I built will have to be re-written to use another source of tile data etc.
But it does seem like this means I have some re-work to do :-(
It will take my company literally months to push through a contract for something like this. Google will be required to tender, alongside other comparable services. I just don't see that happening...
It's possible to get 50% discounts of the $4 price (if you do more that 100,000,000 per year)
Any contract we sign needs to be for a fixed price, rather than a variable amount. And amounts above a certain limit need to go out to competitive tender, which takes a long time. (I'm not sure Google or the other players in this space would even bother to tender anyway.)
So the only option remaining is to rebuild the mapping solution using another technology to ensure continuity of service.
Presuming you don't, perhaps you could find a way to get your superiors to think of things like map requests as akin to coffee or paperclips rather than a service or a piece of boxed software.
Do you have any insight into how large the volume of your map requests is?
http://www.google.com/enterprise/earthmaps/maps-compare.html
Unfortunately, they don't list pricing in an obvious way.
I don't know any big site that gets more than 10$ per 1000 pageviews with ads. It's insane!
EDIT: fill in the form you'll get the pricing... 10k$ upfront for 10MM views: http://www.google.com/support/enterprise/bin/request.py?cont...
EDIT: ok, so that's an order of magnitude difference from your first post. that's well below the CPM for the "overage" charge, but well over it if you take into account the 25k initial views per day. It still doesn't make sense if they are legitimately offering that as the better high-end option.
I don't want to go all ad-hominemy, but based on your "Google Maps is dead, long live OpenStreetMap!" comment, I'm going to go ahead and take your numbers with a gigantic grain of salt :)
I think I made a mistake with the figures. I just checked that email again and it says 10,000$ for 1 million page views per day for public facing deployments. What a shame.
Google is changing. They used to be startup friendly. Now they focus on internal startups, and with a switch of a button cut services to potential competing startups.
Google maps UI is by far better than Yahoo maps. That and the street view/bike maps/etc. are features that give it a nice edge over alternatives.
I guess this was inevitable. But maybe we can switch to a different maps API? Google is so smooth though.