- This topic has 17 replies, 7 voices, and was last updated 3 years ago by
.
-
Posts
-
I just received a long email from Google and the gist of it is they are going to start charging for the API … they say my site – which exclusively uses Mappress to serve maps – will exceed the base $200 per month of “free” use of the API. But they don’t say by how much.
Wondering if this is blindsiding you as well, Chris – their deadline to start charging for use is June 11 – and how, perhaps, to tweak the maps to scale back calls to APIs?
Thanks, Sandra
Hi,
That message caught me by surprise as well. I assumed they were heading in that direction when they demanded the use of API keys, but I didn’t know when or if they would require billing info.
There’s unfortunately no way to reduce the API calls – MapPress already uses the API as sparingly as possible. One suggestion: if you show maps in post excerpts you might consider limiting them to just single-post detail pages.
Google does provide a ‘user guide’ that explains how to estimate your future billing:
https://cloud.google.com/maps-platform/user-guide/pricing-changes/
It looks like the first 28,000 maps are free. In months where your site gets heavy traffic and exceeds that free allowance, they show $7 per 1,000 map loads.
Any chance of amending the plugin to use a different base map (open street maps etc.). I’m using your plugin for mashups and I’ve calculated its going to cost me about $5000 per MONTH just for effectively displaying Google’s base map in the background.
I’m not bothered about directions or anything like that. An option just to use an alternative (perhaps when ticked would grey out Google Maps specific options would work?).
I realise its a pain for you, but would be a great business opportunity. There are going to be literally tens of thousands of people looking for an alternative over the next month.
We’ve got a month.
Yes, very disturbing to figure out what it will cost to keep maps on our website, which is a hiking website so of course maps are crucial.
For the month of April, which is not one of our busier months, Google says we had 130,703 requests of Maps Javascript API in 30 days, plus 1,577 of Directions API and 1,006 of Geocoding API.
Under the current plan, there was no charge for less than 25,000 map loads per 24 hours. Never a problem.
Under the new plan, the above would cost $732 per month. Much more than we earn off the website. Simply not viable.
So, an important question for you. Mashups are the most important feature of Mappress that we use on our website. If we do not insert mappress code in a post and show a static JPG trail map, but use mappress in the post to simply store the lat-lon of the post and then show it elsewhere as part of a mashup, that would not load the Javascript API on the post, correct?
We could replace our trail maps with static versions, but being able to show the locations of the trails together on a mashup map is still a crucial element for our website.
Hi,
I didn’t notice they’d changed from 25,000 free maps per day to 25,000 per month!
Static maps may help, since they have a 100,000 monthly free quota. Or, if your individual maps have only 1 POI, you could use the Google embed API (https://developers.google.com/maps/documentation/embed/guide) which seems to have virtually unlimited free usage.
I’m working on adding both of these options to MapPress as well. I’ll be out of the office until May 15, and it will take a few days after that.
Any updates, Chris? Checking in as I’m ripping Mappress code off most of our pages except for the mashups and replacing it with static maps. A switch to Open Street Map backgrounds would be a most welcome addition to this plugin.
I’m working on adding leaflet & nominatim, but it’s quite a conversion.
If you (and anyone else) would like to volunteer to test it, please send me an email. The initial version will probably lack support for KMLs and shapes, but otherwise be fully functional.
Sure. I’m working on something at the moment. Should be (more) free by Monday. Will email you later.
Fabulous. I don’t doubt it’s a lot of work. Happy to test but I am on the road next two weeks, glad to try things out after I return. Will be in touch.
Hi,
i want to renew MapPress Pro (what a good plugin !) but new Google prices are going to oblige me to stop the use of the plugin unfortunately.
An option with Open Street Map would be saving because MapPress Pro is vital for most of my websites.
Hope that a solution will be found for all happy users 😉
Thanks Cris
Best regardsHey Chris – any update on adding static maps to the plugin? If yes, do you have a target date or any idea if it will require us to “rebuild” each map, vs say a magic toggle that lets us switch to static without all the rework? 🙂 One can dream…. Thanks
Hi Chris,
Just saw this and I’d be happy to test on a test server. I have a site with more than 1,000 points now, so can certainly give it a try.For everyone following this, I’ve just released MapPress 2.49 BETA, which supports Leaflet, Open Street Map and MapBox, as well as Google Maps.
This is a new version with extensive changes. If you encounter bugs, please contact me and I’ll try to fix them as quickly as possible.
The new version is described here:
BETA DocumentationYou can easily switch between Google and Leaflet in the MapPress settings screen. Most features are identical, but Leaflet has the following limitations:
— Google Traffic, bicycling and transport overlays are not available
— Inline directions are not available. Directions are provided from Google Maps.
— Drawing tools for shapes and polygons are not provided. If shapes are created using a Google map, they will be converted to plain markers in LeafletThanks for your help and support, and I hope you enjoy the new release!
- You must be logged in to reply to this topic.