Introducing Mapbox GL
mapbox.com
mapbox.com
You might want to use a nice HTML5 video instead of a .gif, then. It didn't make for a good first impression.
I said, "as far as we know, nothing like this has ever been done before". Good thing the presentation was last week I guess...
Could not find compiler set in environment variable CC:
gcc-4.8.
I'm running gcc-4.9. I got it working by doing: ln -s /usr/bin/gcc ~/bin/gcc-4.8
ln -s /usr/bin/g++ ~/bin/g++-4.8
I'm not saying this is good practice, but it works.Also need to make sure python means python2.
in the python scripts to get it working under archlinux. If this works on the other platforms, that might be a good change.
This is a pretty standard practice and the reason that it's set to "gcc-4.8" rather than "gcc" by default is because it requires real C++11 support in order to compile.
It's funny to see all the usual 2D suspects in the source (clipper, GLU tessellator). They used a distance-based edge shader for antialiasing, so it should look much better than MSAA.
I'm not sure why there's a bias factor of 2 in the "raster" fragment shader -- looks like it might have been added by accident. It's interesting that they use both the stencil and depth buffers for clipping -- I hope they do a write up on some of the techniques they developed!
Yes, that was an accident. Thanks for noticing! We definitely have a lot of information to share about the process. Regarding clipping, we're not sure yet whether what we have right now is the best thing; there will certainly be improvements in that area.
http://wiki.openstreetmap.org/wiki/Android
Unfortunately AFAIK most of them are missing many of the things that makes Google maps useful. Real time traffic data, real time road closure data, updated public transportation schedules and closures, search by something other than address, ...
Also I believe online vector based maps teams found that vector map data was actually larger than tiled map data. I thought as you did lines = smaller but lines + colors + line weights + building outlines + elevation contours + street names + road direction info etc adds up were as jpeg tiles can be pretty lossy.
http://www.engadget.com/2010/12/16/google-maps-5-0-hits-andr...
I assume this is for performance purposes, but it makes the map feel much less usable than Apple Maps in my opinion.
For comparison:
Apple Maps: http://i.imgur.com/jqPHej2.png vs Mapbox Maps: http://i.imgur.com/rVH775b.png
The default stylesheets should look good and work well out of the box. Then if you have the time and manpower to customize them further great.
Man I love the stuff that MapBox puts out. High quality.
My user agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36
I'm running on 15'' macbook pro, OS X 10.8.5 on a 2.2GHZ i7, with 8GB of memory.