The first of our series on “Cartography and the GeoWeb” covers the cartography of GeoWeb base maps - one of the most obvious places cartography is applied on the GeoWeb. The tiles from Google, Yahoo and Microsoft are nearly ubiquitous in map mashups. As each of the technology giants got into the mapping game, they had to make many cartographic decisions on how they would present data on a map. This leads to a myriad of mapping option ranging from the color palette selected for map elements, to font and to the placement of labels on the map. To see the effect these different choices can have on a base map, check a comparison of cartography for the street base maps of the three providers below:

yahoo_maps_cart

Yahoo Maps

msve_map_cart

Microsoft Virtual Earth

google_maps_cart

Google Maps

When it comes to cartographic design I would rank it 1) Yahoo 2) MSVE 3) Google, which should not be too surprising since Yahoo! hired a bunch of cartographers to design theirs. Since Yahoo! unveiled their new cartography, Google has introduced terrain view and MSVE has added elevation reliefs to their maps as well - although I cannot for the life of me find a reference to when the upgrade happened.

While the race for more content, and sometimes more cartography, has raged amongst the big three providers, there has been a backlash in the developer community. This was most poignantly seen in Paul Smith’s “Take Control of Your Map” article on A List Apart. As you can see in the screen shots above, the base maps from Google, Yahoo and Microsoft have become pretty crowded and dense. Many Web designers would like to control the design on their maps the same way they do their Web pages leading to a movement to “roll your own maps”.

This movement has leveraged the pioneering work of OpenStreetMaps to create their own independent base maps for streets. The OSM effort led to creation of applications like Mapnik and Osmarender to style the GPS data they collected for the project, although both are some what notorious for their lack of usability. This has not stopped EveryBlock from using Mapnik to make custom maps for their data.

everyblock_map_carto

The map is definitely less busy than the big three providers, and I believe suits EveryBlocks purposes well, although I might have gone with a different color combination. The beauty, though, of EveryBlock’s approach is that if I wanted another color sequence, I could take Mapnik and OSM data and have at it. I believe it is just one of the many examples we’ll see democratizing cartography - allowing the public to “roll their own”.

Popularity: 27% [?]

6 Responses to “The Cartography of GeoWeb Base Maps and “Rolling Your Own””

  1. Christopher Schmidt Says:

    Everyblock doesn’t use OpenStreetMap data, or at least, they’ve always said that they don’t in the past.

  2. Tom Carden Says:

    What Chris said. Everyblock, as far as I can gather, use geodata that they’ve acquired from the cities directly. Many cities offer geodata in this way.

  3. Sean Gorman Says:

    Sorry poor writing. I meant that if I wanted to make my own personal version I could use OSM data and Mapnik, not that EveryBlock used OSM data. Although the bigger point is it could be any data source and you could style it as you see fit.

  4. John Fagan Says:

    I like what EveryBlock are doing with their own map style, but then in defence to the “the big three providers”. The EveryBlock minimalist look becomes a bit too minimalist as you move to the suburbs:

    http://nyc.everyblock.com/locations/zip-codes/10307/

    If EveryBlock want to eventually expand to national or international coverage (which i imagine they do). They might find they have to make compromises in their cartography which might reduce the differentiation gap they currently have.

  5. NeoCartography and Thematic Mapping: Is 3-D Crap? | Off the Map - Official Blog of FortiusOne Says:

    […] with the cartography series we are going to cover the use of thematic mapping on the GeoWeb. There has been a pleasant up tick […]

  6. Sean Gorman Says:

    Good point John - I think on of the big challenges with cartography on the GeoWeb is that the page users look at is not static, so the same base cartography has to work for both heavily populated areas and sparsely populated areas. In paper and even GIS cartography the user was usually constrained to just what was on the page but on the GeoWeb they can roam and explore to not only different geographic locations but zoom in and out to different levels of details Despite my cracks at the base layer cartography in slippy maps the ability to change map generalizations to different levels of zoom has been a huge innovation.

Leave a Reply