How Mapbox Is Winning Over Developers to Challenge Google's Mapping Dominance
forbes.com
forbes.com
https://openmaptiles.org (only map tiles)
https://stadiamaps.com (map tiles, static maps & routing)
https://www.thunderforest.com (only maps)
https://geocoder.opencagedata.com (only geocoding)
https://geocode.earth (only geocoding)
A laundry listing: https://switch2osm.org/providers/Tile providers are very thankful for the excellent rendering libraries built by Mapbox, Mapzen, and the Leaflet project. Most maps either use Leaflet.js or MapBox GL JS (open source) for their rendering agent, now that Mapzen is defunct (although their rendering library, tangrams, is now open source).
(I am a co-founder of Stadia Maps.)
co-founder of OpenCage here.
It depends heavily on what your use case is: forward or reverse, which part of the world, what level of granularity, etc. Google offers a great geocoding service, no doubt. But you also have to pay their price, and obey their terms and conditions. Their great service is overkill for many very common use cases, at least those that we see from our customers.
Anyone who wants to try us out, our demo page is here: https://geocoder.opencagedata.com/demo
Does that imply variation in coloration based on elevation? (Just making sure I understand your question.) We have limited support for basic hillshading and are actively looking into contour lines. Coloration for various elevations is something we do not currently offer (nor am I aware of any other providers), but it is something we would be willing to investigate.
Depending on what precise application you need, this may be possible one the web using our normal vector maps and contour lines.
Another use case that I've been searching for is a tile set not of images, but of just elevation data. So that I could implement something similar to google earth's lat/lng/elevation info wherever your mouse cursor is.
https://en.wikipedia.org/wiki/Shuttle_Radar_Topography_Missi...
The format is very simple to make sense of. Each file is an array of 16 bit integer values in meters, and it maps 1x1 degrees areas. Each file contains 1201x1201 or 3601x3601 samples depending on resolution. The first/last row/columns of adjacent files overlap that’s why non-round numbers.
Both SRTM and tiles use Mercator projection, i.e. mapping them together is very simple, too. In the embedded software I’ve developed, I’ve layered SRTM-derived data on top of OSM tiles, worked quite well and wasn’t too hard to implement. Even though due to very slow target hardware (500MHz CPU, 256MB RAM, slow flash storage), I had to invent more optimized format for SRTM data (dense array of 32x32 tiles taking exactly 2kb/each, aligned by disk sector), and implement an offline converter.
> including for example the USGS high res DEM where available
I haven’t personally compared them, but before picking SRTM for that embedded GIS project I’ve read about them, and concluded SRTM is more reliable. Also the resolution is more or less the same, SRTM offers 25m horizontal resolution, that’s pretty high, IMO.
(Full disclose I'm the author)
If we can’t offer something, we’ll at least be able to point you in the right direction!
Which zoom levels do you need? What coverage?
Check out https://www.mapbox.com/help/access-elevation-data/ for more background and let us know @Mapbox if you have questions!
Note - I work at Mapbox
See https://openmaptiles.com/satellite/. Next step is merging in very detailed aerial photos for US and EU - often with 1m or 25cm/pixel resolution.
It is going to be available for both self-hosting and as part of the hosting platform https://tilehosting.com/
Individual engineers at these places do not have the power to make decisions about which map software to use, which are often six- or seven-figure contracts. Mapbox offers a service that is comparable to Google Maps in terms of price, quality and flexibility. From a technical standpoint, there are pros and cons to both services; Mapbox's toolkit is more modern than Google, which means documentation is a pro for Mapbox but legacy browser support is a con (though it's just a minor annoyance).
Where they far outstrip Google is in sales and customer support. Google Maps won't bat an eye for you, even if you're paying them millions of dollars a year. The Mapbox team, in contrast, will devote developer time to answering your questions, respond to GitHub issues for you in a timely manner, and even create new plugins and repos if you have a legitimate need. That is their big advantage and that is what is driving adoption.
Source: I was employed at a medium-sized internet publisher, and tasked with evaluating Mapbox to replace Google Maps, was a primary developer working on the switch-over, and even wrote a blog post about the experience [0]. They even invited me to their office to work with them for a day (which, regrettably, I wasn't able to follow up on).
[0]: https://blog.rentpathcode.com/webpack-progressive-enhancemen...
Also, part of the Google Maps Platform launch is that support (as in, being able to file tickets and get answers) will be extended to all users: https://mapsplatform.googleblog.com/2018/05/introducing-goog...
Disclaimer: I used to work on Maps Support at Google.
We did have a paid package with Google Maps. Good to hear that Maps is amping up their support.
If you wanted this on GMaps, you were stuck rendering all your vectors to image tiles, hugely increasing the size. MapBox's vector support made this very easy! It may be that Google/free options have caught up in this space, but I haven't re-evaluated in a few years.
I think MapBox could also be a winner in the GIS space as the GIS options have not made the most graceful move to the web.
Also, there was a great interactive style editor (https://github.com/tangrams/tangram-play), although it seems the demo site is broken now :-(
It really is. I've done a lot of work in the web with various rendering engines, and it's hard to beat the quality of MapBox GL.
Also, if anyone from Mapbox is reading this, you need to be more clear about what is considered "commercial". At the top of the pricing page you define a commercial app as:
Paid web app or website (fee or subscription)
Private web app or website with restricted access
Asset tracking app or website to monitor people or things
But then lower down on the page, you seem to indicate a more permissive definition: If your app is for internal business use by employees,
or if it is not accessible or functional for members
of the general public then we consider that a
Commercial app.
Even with these two definitions, it's not clear how this pricing works for freemium websites or websites paid for by advertising.There are some other alternatives that are more truly "pay as you go" or have affordable tiers for commercial apps:
TomTom - https://developer.tomtom.com/store/maps-api
MapQuest - https://developer.mapquest.com/plans
Stadia Maps - https://stadiamaps.com/
There is also MapFit, which says it has "Clear pricing that scales with you" but doesn't actually explain any of their pricing:
If anyone else has good alternatives that are affordable for solo devs, especially ones with good alternatives to the Google Maps Places API, I'd love to hear about them.
For instance, Foursquare has a pretty good places API we've used before.
Yeah. :(
This problem seems to extend to the whole industry. Everyone charges big bucks to even very small players. We want to solve pieces of that we can, but it's a tough road to build quality databases.
I find it interesting how often people (myself included) are willing to consider spending hundreds of dollars on a product or service, but aren't willing to take 30 seconds to send an inquiry email or ring a sales line. Possibly it stems from cynicism (or from a perception that "if you have to ask, you can't afford it") but a few times now I've grumblingly made contact with a supplier only to find that the prices are very reasonable and they're great to deal with.
Now I understand custom pricing has to be implemented at some level, but you usually see multiple pricing tiers before it kicks in.
Pretty amazing how little such a big brand is actually worth.
But in general, definitely look closely at the forbes.com/sites articles.
I know directly of at least one recent instance where a local news company was not allowed to interview a professional directly related to a story it was airing...because one of their big advertisers wouldn't allow anyone in that field to be interviewed unless it was an affiliate of theirs.
I'm being purposely vague there, but even the reporter was really upset about it.
I've always enjoyed chatting with their engineers about vector graphics stuff. :)
Google maps is no longer good for hobby projects as the free tier is so low.
It's like they're trying to drive away everybody but but big enterprise shops.
If you don't want to serve any customers making under $10M, then other companies serving those customers are not your competition. At least not today. Is there a risk they might take their broader customer base and use it to compete with you upmarket some day? Yes. But that's why you do things like build a brand, relationships, technologies, and other competitive advantages within your niche.
Fancy steakhouses generally don't worry about McDonald's. (Not that this is a perfect analogy to Google vs MapBox. Just speaking generally here in response to your general point.)
Didn't that happen just a week or so ago? I don't think this can be attributed to the pricing change this early.
Mapbox's free tier only gives 50k map views, and only for non-commercial apps. If you're a paid app, you also have to pay $499 per month on top of your usage.
I like what they're doing, and wanted to use them for a web app with restricted access, but certainly not going to pay $499pcm for a side project.
Mapbox feels really good. API, docs and rendering performance all of this is really good. Although it's not an obvious choice if you are starting fresh. I personally find the pricing impossible to digest. Probably sounds reasonable for well-founded startups from developed countries. If your doing a bootstrapped product and can't pay 500$ it's not for you.
Google Maps. the v3 it's here for a while. The API feels good, but not great, Stack Overflow is your documentation. Rendering performance is bad, rendering performance with (many) markers without some hacks is terrible, rendering performance on mobile is even worse. I'm trying to figure out what new the pricing means for me.
Leaflet and OpenStreetMap look like a better choice for all hobby projects and small product from now on.
What do they mean by that?
https://www.mapillary.com/imagery is using image recognition for traffic signs and lists Mapbox as a user.
Curious quote. A flywheel stores energy. What does that have to do with a system learning as it's used? Also curious phrasing. "That flywheel"? Which flywheel?
I'm not an expert, and I'm not sure that this in fact a valid interpretation of that concept, but I know that it's a popular concept in certain business circles.
http://www.samseely.com/blog/2016/5/2/the-amazon-flywheel-pa...
Google's entire advantage here is the amount of resources they've poured into their data; nobody else has been able to match it so far.
EDIT: After doing a bit of poking and prodding, it does seem to be a lot better than it used to be.
My company (https://stadiamaps.com) does that. OpenMapTiles (https://openmaptiles.org) sells vector tiles you can use. There a many more over at https://switch2osm.org/providers/.
Web Renderer: https://github.com/tangrams/tangram Native/Mobile Renderer: https://github.com/tangrams/tangram-es
Native renderer can be accessed for android through gradle, ios through cocoapods and even available on raspberry pi.
Scene file documentation: https://github.com/tangrams/tangram-docs https://mapzen.com/documentation/tangram/ (still seems to work :D)
Scene file authoring tool: https://github.com/tangrams/tangram-play Which continues to live at http://tangram.city/play/
One of the great features of tangram is to embed any glsl shader in the scene file, which gets injected during rendering and "transforms" the map rendering and the map experience to a all new level, giving the some great flexibility cartographer/designer/developer will like.
As an example check this demo "tron" scene: https://tangrams.github.io/tron-style/#15/37.7926/-122.4003 (source: https://github.com/tangrams/tron-style)
Tangram had some great consumer base including this amazing project called StreetComplete (https://github.com/westnordost/StreetComplete/). Check it out and use it to improve osm street data.
Also mapzen's geocode engine Pelias, continues to live as geocode.earch, which it out at https://geocode.earth/.
Disclamer, I used to work for mapzen on the tangram-es (native rendering) project and still supporting the project in the open source world (along with other tangram-es developers).
If anyone interested has any questions, you can contact me @tallytalwar on twitter.
(Full disclosure: used to work at Mapzen)
It's like they don't want to show it.
Note - I work at Mapbox.
Also since I'm a Safari user I figured I'd try Google Maps in Chrome as well to see if Google Maps' lag was due to Safari and nope, Chrome is actually way laggier than Safari.
I have a messy address list I would like to geocode, but not sure where to turn
I consider Carto and Mapbox to be tangential services in many respects.