Slashdot Mirror
Google Maps API Becomes 'More Difficult and Expensive' (govtech.com)
Government Technology reports:
On July 16, Google Maps is going to make it more difficult and expensive to use its API, which could make custom maps that rely on the service less sustainable or even unfeasible for the people who made them... First, Google Maps is requiring all projects to have an official API key in order to work. If a user doesn't have a key, the quality of the map will likely be reduced, or it could simply stop working. Second, API keys will only work if they are attached to somebody's credit card. Google will charge that card if users exceed a certain number of API requests, which is different for different services. Google will provide users a free $200 credit toward those costs each month...
There are a couple places where the changes might have more of an impact. One is in the civic hacking space, where people often work with government data to create niche projects that aim for low costs, or are free so that as many people as possible can use them... "I think that's what scares people a little bit, it certainly scares me, this thought of having this API out there and not knowing how many people are going to use it," said Derek Eder, founder of the civic tech company DataMade. "I don't want to suddenly get a bill for $1,000."
There's at least three Open Source alternatives, and Geoawesomeness.com lists nine more.
Slashdot reader Jiri_Komarek also points out that Google's move was good news for its competitor, MapTiler. "Since Google announced the pricing change the number of our users increased by 200%," said Petr Pridal, head of the MapTiler team. "We expect more people to come as they get their first bill from Google."
There are a couple places where the changes might have more of an impact. One is in the civic hacking space, where people often work with government data to create niche projects that aim for low costs, or are free so that as many people as possible can use them... "I think that's what scares people a little bit, it certainly scares me, this thought of having this API out there and not knowing how many people are going to use it," said Derek Eder, founder of the civic tech company DataMade. "I don't want to suddenly get a bill for $1,000."
There's at least three Open Source alternatives, and Geoawesomeness.com lists nine more.
Slashdot reader Jiri_Komarek also points out that Google's move was good news for its competitor, MapTiler. "Since Google announced the pricing change the number of our users increased by 200%," said Petr Pridal, head of the MapTiler team. "We expect more people to come as they get their first bill from Google."
I salute Google's desire to migrate their users to open-source mapping alternatives. They're not just paying lip service to the idea, they're putting their money where their mouth is.
Or foot, anyway...
Once you kill off all the map competitors, its only natural you would then raise prices.
After years of faithful map overlay on the local public University's weather map had to be replaced because of this shift by Google. https://atmos.washington.edu/w...
And where are you now?
-=This sig has nothing to do with my comment. Move along now=-
https://www.openstreetmap.org/...
They haven't killed competitors.
I can actually understand why they did something like this, although I would have suggested a rate limit on a 'free' tier instead.
An example is, I heard a complaint from a city public transport agency. They had a phone app using this, and were railing against the new charges.
Turns out their app, which people have open for planning routes, and sitting waiting for busses/trains/etc, is written insanely and was re-requesting EVERYTHING
every 5 seconds while the app was running, so they were generating millions of API calls, to service a few thousand users...
They were trying to make a big public fuss about this, claiming google was evil. Perhaps they should just fix their damn app.
Of course the new solution isnt great either, a rate controlled free tier would be sensible, plus clear ways to limit your total exposure.
But I suspect there are a hell of a lot of maps API 'apps' that are just as retarded, and that the traffic/cost has become huge enough that they decided to do something.