What is the crowd's opinion of
MapTiler Cloud?
From 3.5 billion comments
5 reviews of this app found across the web:
We created a simple calculator where you enter users per day, type of your app and it will give you the price (the new one, which will become effective as of 16. July 2018).
Hello :)
Does anybody have a Galls-Peter projection that I can use for web? if possible, I would like to be able to add layers and points to the projection. whatever I find, openstreetmap, gmaps, etc. is Mercator based.
I used https://www.maptiler.com/cloud/ which works pretty well for my needs, but it is Mercator based...
Thanks!
I built some geo features into an app and used Maptiler Cloud as the vector tile service. Great platform, I highly recommend it. I then used the Mapbox SDK to add in cool features like point clustering and heatmaps.
This chart was posted in /r/gis and I posted this response there as well.
---
This chart is misleading because "API calls" have different meanings across these platforms.
With Google Maps, when you load a map on a page, that counts as one API call. Regardless of the size of the map and how much a user interacts with the map, you always make one call.
With Mapbox and HERE, when you load a map on a page, you are charged for one API call for every four 512x512 tiles or fifteen 256x256 tiles that are requested (they call these "map views" or "transactions"). If your map is full screen on a desktop computer, it will likely need more than four tiles. As the user interacts with the map, more tiles are used. For a full-screen, interactive mapping tool, it's not out of the question to use 10–30+ API calls per session.
To get an idea of how many map tiles are requested with typical map interaction, look at this requests tool: https://www.maptiler.com/cloud/requests/?width=1200&height=700. Try to zoom out and find your home town and see how many tiles you consume. Divide that by 4 and that is how many "API calls" you'd make using Mapbox or HERE. On Google Maps, it would be one API call.
Small map that users won't interact with much? Mapbox is going to be less expensive. Large map where you expect heavy interaction? I suspect in many cases Google Maps will be less expensive. FWIW, I prefer Mapbox over Google Maps for non-pricing reasons, but I don't think this chart tells the whole story.
This chart is misleading because "API calls" have different meanings across these platforms.
​
With Google Maps, when you load a map on a page, that counts as one API call. Regardless of the size of the map and how much a user interacts with the map, you always make one call.
​
With Mapbox and HERE, when you load a map on a page, you are charged for one API call for every four 512x512 tiles or fifteen 256x256 tiles that are requested (they call these "map views" or "transactions"). If your map is full screen on a desktop computer, it will likely need more than four tiles. As the user interacts with the map, more tiles are used. For a full-screen, interactive mapping tool, it's not out of the question to use 10–30+ API calls per session.
​
To get an idea of how many map tiles are requested with typical map interaction, look at this requests tool: https://www.maptiler.com/cloud/requests/?width=1200&height=700. Try to zoom out and find your home town and see how many tiles you consume. Divide that by 4 and that is how many "API calls" you'd make using Mapbox or HERE. On Google Maps, it would be one API call.