Edit: Also it's $1,000 for commercial use, even to use with OSM data?
Where did you find the $1000 quote? I know you can have them hosted unlimited for $245/month but I was fairly sure it was free for self-hosted use.
If you select "commercial product or company web", you're asked to pay for it: https://i.imgur.com/TrAmju4.jpg
If you select any of the non-commercial ones, the newest map data you get is from 2017 (!).
I'm not against paying, but it's not free!
[0]: https://github.com/openmaptiles/openmaptiles/blob/master/REA... [1]: https://github.com/openmaptiles/openmaptiles/blob/master/QUI... [2]: https://nst.guide
See here: https://openmaptiles.org/docs/generate/generate-openmaptiles...
[0]: https://github.com/nst-guide/hillshade [1]: https://github.com/nst-guide/contours
I think the best open vector map style is OSM liberty [0]. My fork, which includes my generated hillshade and contours, is here [1].
[0]: https://github.com/maputnik/osm-liberty [1]: https://github.com/nst-guide/osm-liberty/blob/gh-pages/style...
Happy to answer any questions! (I’m a cofounder.)
You don't even show up in the "stadia" search results without the term "maps" added.
If it wasn't scary and expensive to sue Google for a name change, this seems like a case of Google (probably unwittingly) crushing your brand and trademark with their own.
Have y'all noticed a decrease in search traffic (or general brand/product awareness) since Google Stadia launched? And if so, do you plan to do anything about it?
Really cool product! Your maps look slick and super clean. :)
> Have y'all noticed a decrease in search traffic (or general brand/product awareness) since Google Stadia launched?
We've actually seen an uptick because of badly placed keyword searches for Stadia.
We also aren't exactly sure the best way to counter it, but we're working on figuring out the best way. We don't really have a legal resource, either, given we didn't have a trademark before Google Stadia came along.
$ curl 'https://tiles.stadiamaps.com/styles/alidade_smooth.json'
<html><body><h1>502 Bad Gateway</h1>
The server returned an invalid or incomplete response.
</body></html>
Very unfortunate timing there. We had a cache server wedge, and the failover mechanism didn't detect it quickly enough. We've diverted traffic manually and are working on bringing the bad region back into the mix after it went down.
Things should be working again now, at least.
Stadia Maps is pretty cheap. $25 gets you 25,000 map views per day or around 750k/month. $100 gets you 250k/day or around 7.5M per month.
Joe here from the Mapbox billing support team. Feel free to reach out to [email protected]. We can dig into your implementation with you to see if there are ways to limit your API consumption (and reduce your overall bills).
Things like limiting panning/zooming can help limit the number of tiles your end users load. Fewer tiles -> cheaper invoices
https://docs.mapbox.com/mapbox.js/example/v1.0.0/maxbounds/
There are other options as well. That said, it's hard to know exactly without taking a look at your map specifically. Let us know!
Their website is quite confusing though, if you ask me. A starting point might be https://developer.here.com/sign-up?create=Freemium-Basic&kee...
I have an app that uses Leaflet for rendering, and Mapbox purely for its raster tiles (both plain maps and satellite required). Mapbox has been cheap for us, at about $50/mo. But with the new pricing structure taking effect in December, it's now about $450/mo. I believe Google and Bing are both more expensive than that.
I've been considering setting up OSM, but I'd like to avoid having to run and maintain it.