HOME
          
LATEST STORY
U.S. journalists, the clock is ticking: January 31 is the deadline to apply for a Nieman Fellowship
ABOUT                    SUBSCRIBE
June 22, 2012, 1:05 p.m.
Reporting & Production

Google loosens its limits and pricing on Maps API

For news organizations the price of making interactive maps still depends on how much they use the tool.

Last year Google incited a tiny panic among newsroom developers after announcing plans to start charging bigger users of the Google Maps API. This is something of a concern to newsrooms, where Google Maps has become an essential reporting tool.

Today Google relaxed those restrictions. Under the revised plans, the price for exceeding 25,000 pageviews a day has gone from $4-$10 per 1,000 map views down to 50 cents per 1,000 map views. They’re also tossing out the distinction between regular maps and styled maps, which previously cost more.

Then and now Google has said that the API limits wouldn’t apply to most developers, only the bigger guys. It’s not altogether surprising they would announce the change on the eve of Google I/O, the company’s annual developer event. In today’s blog post on the change:

We’re beginning to monitor Maps API usage starting today, and, based on current usage, fees will only apply to the top 0.35% of sites regularly exceeding the published limits of 25,000 map loads every day for 90 consecutive days. We aren’t automating the application of these limits, so if your site consistently uses more than the free maps allowance we’ll contact you to discuss your options. Please rest assured that your map will not stop working due to a sudden surge in popularity.

For media companies there has been plenty of confusion about the Maps API, particularly the hows and whys of taking the API to the limit. Google maps are now a ubiquitous part of storytelling because of the app’s malleability, but also, frankly, because it’s free. There are crime maps, census maps, education maps — the list goes on. When the limit scare hit, there were immediate discussions over what other mapping solutions exist for news companies. This change, while keeping the limits in place, may alleviate news developers’ fears of getting a massive tab from Google.

Still, there are more questions, particularly about using maps with Google Fusion Tables, something news developers are particularly fond of. A Google spokesman told me feedback from developers led to the changes to pricing and API limits. Here’s a statement they provided:

Developers using the Fusion Tables interface to generate a map and then using the embed function to add that map to a web page aren’t subject to the Google Maps API usage limits at this time. Normal usage limits apply for developers using the FusionTablesLayer class of the Maps API v3 to add Fusion Tables content to their Maps API applications.

This is not the first time Google has tweaked the Maps API limits. In fall 2011 the company doubled back in an effort to clear up confusion, noting that sites would not be penalized for breaking the limit on one particularly high traffic day. Instead, a site would be subject to the usage pricing if it exceeded the map-views limit for 90 consecutive days. Google also said nonprofit organizations or people using the API “in the public interest” would be exempt from the new maps rules.

POSTED     June 22, 2012, 1:05 p.m.
SEE MORE ON Reporting & Production
SHARE THIS STORY
   
Show comments  
Show tags
 
Join the 15,000 who get the freshest future-of-journalism news in our daily email.
U.S. journalists, the clock is ticking: January 31 is the deadline to apply for a Nieman Fellowship
It’s a chance to spend a year at Harvard and change the shape of your career.
Newsonomics: How deep is the newspaper industry’s money hole?
Forget keeping up with the economy — what would it take for the newspaper business just to keep up with inflation? Even the “growth” areas are slowing down.
Don’t try too hard to please Twitter — and other lessons from The New York Times’ social media desk
The team that runs the Times’ Twitter accounts looked back on what they learned — what worked, what didn’t — from running @NYTimes in 2014.
What to read next
2499
tweets
Don’t try too hard to please Twitter — and other lessons from The New York Times’ social media desk
The team that runs the Times’ Twitter accounts looked back on what they learned — what worked, what didn’t — from running @NYTimes in 2014.
716From explainers to sounds that make you go “Whoa!”: The 4 types of audio that people share
How can public radio make audio that breaks big on social media? A NPR experiment identified what makes a piece of audio go viral.
705Q&A: Amy O’Leary on eight years of navigating digital culture change at The New York Times
“In 2007, as digital people, we were expected to be 100 percent deferent to all traditional processes. We weren’t to bother reporters or encourage them to operate differently at all, because what they were doing was the very core of our journalism.”
These stories are our most popular on Twitter over the past 30 days.
See all our most recent pieces ➚
Encyclo is our encyclopedia of the future of news, chronicling the key players in journalism’s evolution.
Here are a few of the entries you’ll find in Encyclo.   Get the full Encyclo ➚
Bayosphere
Examiner.com
Texas Tribune
Quartz
The Guardian
Baristanet
The Tyee
PolitiFact
Ars Technica
AOL
Detroit Free Press and Detroit News
Groupon