The majority of the people who interact with OSM will get a perception of it that's biased by the presentation. Even with the MapQuest Open style, Google Maps, to me, are far more pleasant to look at and easier to understand. The text seems to be rendered in a better, more readable way, and GMaps has a better handle on decreasing contrast for things that aren't that important, allowing more important features to stand out.
You can tell me that I shouldn't care, because you provide such awesome data, and I'm tempted to agree, but my reptilian brain will give me opposite feelings every time I try to look at your maps.
OSM doesn't have to "sell" their maps. It's the folks like Telenav that need to make their maps look better.
They certainly do if "I’d like it to get OSM to seven billion contributors in the next year or two"
There needs to be separate organizations to package and distribute this data and make apps for it. (A web map project will have different needs than an offline phone navigation app. OSM shouldn't try to gain/maintain domain expertise in everything.)
I think its a good example of data > render, with ux in the front of mind. Unfortunately we are good at the read case, not as good at the contribute case.
If you want seven billion people using it, it's going to be quite necessary to create a consumer-facing canonical front-end.
I'm sure you can get lots of volunteer hackers to contribute if you throw up an MVP on github.
Instead, there's room for Valve's SteamOS, Google's Android, Google's ChromeOS, Canonical's Ubuntu and many more, both commercial and community focused, competing in some ways, collaborating in others.
This announcement is one company that did exactly that, and provided a consumer-facing product built on OSM, who just got bought by a bigger producer of consumer-facing products who intend to do the same on an even bigger scale.
libpcap has tcpdump. linux has ubuntu. http has nginx (and previously, apache).
It would be great if there were a canonical frontend stack for OSM that we could all hack on to make as usable as Google Maps. It should be hosted somewhere central but also ship with easy chef or puppet configs to deploy a stack yourself easily.
I'd get tons of use out of something like that, and I'd contribute to the code, too.
Monolithic engines are great for getting 80% of what your exact requirements are, then you're stuck with a bulky system that you're probably only using 10% of, and it doesn't do the other 10% of what you need.
Something like leaflet.js is nice because it gives you a simple way to present layers on a device, and it's modular meaning you can plug in extra behaviors or develop your own easily.
If a similar approach were taken for the other problem areas, like route finding, traffic monitoring, etc, I'd much prefer that over a bulky platform I'd never want to use the entirety of for any one project.
Of course once these modular components mature enough, no doubt soon, they will be packaged into some service that with a few simple clicks of a button generates the right combination to suit your requirement.
tl;dr OSM should do the data collation and serving and be good at that. Other services should spring up to do their magic with that data. And yet other services should provide easy ways to thread it altogether for a whole world of possible use-cases. (all IMHO of course...)
And this article is the equivalent of say, Canonical taking Debian and saying they're going to make an easy to use desktop linux from it. It will almost certainly be more "polished" and end-user focused than openstreetmap.org, because they serve two different types of users.
Interestingly Wikipedia are actually a user facing front-end for OpenStreetmap data, in fact they have at least 4 projects using slightly different tech to put different front-ends on OSM as appropriate for their usage, e.g. the official Android app uses MapQuest OSM tiles to show articles that relate to your physical surroundings:
https://play.google.com/store/apps/details?id=org.wikipedia&...
and the german wikipedia has a couple of gadgets in the top right hand corner to show the geographical context of the articles:
http://de.wikipedia.org/wiki/Kongo_%28Fluss%29
They also extract a lot of vector data from OSM to hand built appropriate maps and diagrams for articles:
http://commons.wikimedia.org/wiki/File:Aruba_travel_map.png
Again, not always what I'd call polished, but they're making creative use of map data, rather than putting some pins on Google Maps (or on an OSM based clone) and that's a good thing.
This is quite belittling to the thousands of hours professionals have put into the OSM tools, infrastructure & interface over the years.
But this is hacker news, home of armchair pundits.
Mapbox comes to mind, but it is a proprietary service, not open source.
I guess I'm wondering why enabling people to build an entirely free/oss mapbox isn't near the top of their priority list.
If you want to render polished maps, you use Mapnik (developed outside, creators hired by Mapbox), probably creating your stylesheets in CartoCSS (developed by Mapbox) and using the friendly TileMill wrapper for prototyping (developed by Mapbox). If you want to do routing, you use OSRM (developed outside, creator hired by Mapbox). And so on.
So for your question, there absolutely is such an open source tool, and it's called Mapnik. Download it (maybe as part of TileMill) and have a play.
Of course you are. That's why there is a comparison of OSM and Google Maps smack in the middle of the blog post we're all talking about. User mindshare matters as much as developer mindshare.
A solution is to make the tiles half the size, but then all the labels are tiny. In addition to this, I dislike Mapquest Open's tiles because they're subject to jpeg compression. Unfortunately, it's the only free tile service out there without usage limits.
The rendering style you picked is certainly different than Google's. MapQuest Open's rendering style is pretty darn close to the Google Maps link you pointed at [0], and other map providers like MapBox let you build maps with styling how you like it in just a few clicks (including picking English labels when known). I made one just now [1].
We don't do a great job of making the point when you arrive at osm.org, but we aren't competing with Google Maps. We're competing with Navteq/Nokia and other map data providers.
[0] http://www.openstreetmap.org/#map=16/43.5883/39.7236&layers=... [1] https://a.tiles.mapbox.com/v3/iandees.h675i5pf/page.html?sec...