51–60 of 265 posts
One thing I like about AWS is that all services have a pricing section. I am interested in the routing service ( https://cloud.google.com/maps-platform/routes/ ) but there is only a contact sales button, no public pricing info available.
https://cloud.google.com/maps-platform/pricing/sheet/ has pricing for routes.
Check out Mapbox for a nice alternative.
WOW, my costs are going to go from about $320 per month to $3,750 per month. Time to find a different solution! GULP!
Earlier quoted context omitted.
AWS seems to me to mostly be a way to configure and sell capacity on hardware. Amazon probably has a lot of fantastic data and software that isn't available outside the company.
AWS was one of the biggest profit centers for Amazon in several recent quarters. Why they don't monetize their GIS data yet is anyone's guess.
I find it very interesting that Google Maps has 1 billion Monthly Active Users compared to Facebook’s 2+ billion. Where is this huge difference coming from?
I find it very interesting that Google Maps has 1 billion Monthly Active Users compared to Facebook’s 2+ billion. Where is this huge difference coming from?
Not a native English speaker and also not that well versed when it comes to marketing talk, but what exactly does "$200 monthly free credit" mean? (from this page: https://cloud.google.com/maps-platform/user-guide/pricing-ch... ). Do you get a sort of voucher with which you'll be able to use Google Maps services worth $200 each month? Will Google automatically start billing you once you surpass that quota? I'm in the…
Is there a documentation somehere describing which requests will degrade and how?
> Beginning on June 11, 2018, you’ll need to enable billing with a credit card and have a valid API key for all projects. This will give you the ability to scale easily with less downtime and fewer performance issues. In addition, we’re simplifying our 18 individual APIs into three products: Maps, Routes, and Places. > Also, in June 2016 we announced that we would stop supporting keyless usage, meaning any request th…
Since google admits that 98% of current users will continue to incur 0 cost this is simply a blatant way of getting a real name associated with their user data.
I was able to get on a desktop and find the pricing page. Here's a link:
Earlier quoted context omitted.
Are all those loads needed? In other words, how often do people interact with them? (Figuring how often they look at them is even more effort.) This kind of changes usually are made to discourage inefficient use of the API, which could be delayed until specific events happen: scrolling, mouseover, timer, etc. I'm not saying that's necessarily your case.
I can probably lower the loads somewhat, but I use other maps services too (street view, etc.) and this $200 free credit seems like for all of the services combined monthly, so one does not get a $200 free credit for each service and costs will quickly add up.
I see that the limit you mention is for dynamic maps. Somewhere else, they say "Requests for Dynamic Maps and Dynamic Street View (Street View Panoramas) will be billed at a higher rate than requests for Static Maps and Static Street View. Dynamic Maps and Street View images respond to user input; the Static versions do not."
I imagine that this is an incentive for developers to use static maps (which you could replace with dynamic ones when the user clicks or hovers on them). If you used static maps alone, that's 300K loads per month, or $480. You would deduct the $200 credit, for a $280 bill, but then pay full price for all the other services. I can see how that adds up quickly...
> If you are currently using an API key, please read the email we sent you on May 1st, which provides a high-level estimate of whether your future bill will change. Did anyone actually get this mail? I am using a key and even got a receipt yesterday but did not get this mail about pricing changes (user from Germany). Edit: Wow. I am currently using Places Radarsearch for a side project which currently has a (generous…
The pricing/limit changes are very aggressive. It's hard to believe they don't affect 98% of current users according to them.