Thursday, March 1, 2012

Colour in Maps

On my other blog I've previously touched on the use of color in maps:

In researching my currently running course on communicating with web maps I came across some other best practices, mostly via the chapter on color in Muki Haklay's book.




Background = Blue:  We evolved doing things like picking berries from bushes in Africa, its therefore not surprising that the natural background color of that African landscape, the blue of the sky, is one as one that we still naturally associate with background.  Note how the red water above comes forward compared to the blue version and swamps out the map detail around it (map courtesy OSM)



Color Wheel Opposites:  The color wheel is a representation of 'color space' with hue around the edge. When choosing colors for symbols (such as placemarks) that need to visually stand out from each other, choose colors opposite each other on the color wheel.  A well used variation of this is yellow and blue.


Thursday, February 16, 2012

Basemaps and Learning Curves

I'm up against the wall in terms of time still so short blog post today on a couple of topics both via James Fee.

Subtle Basemaps:  one of the basic problems with mashups has been putting data over a map designed for route planning.  Recently with Google maps API v3 and tools like tile mill people have started de-emphacizing background maps so that the data stands out better against the background map.  I agree with James that the OSM bright minimal style is a interesting development in this line of work.


I'd love to see some user test results to see how people fared working with a mashup based on this base map.

Learning Curves:  Also via James I read a great quote about teaching OS mapping software to students.
"One of the trepidations I have with teaching mapping courses using open source is that it usually requires some modicum of programming which is always way beyond the scope of any beginner class about making maps.  In addition, open source tends to favor linux or unix based tool chains that require config/make/make install tap dance before starting anything. This is akin to telling folks that they will need to forge their tools before they can start building a dog house."
Amen to that (emphasis mine).  I'm teaching web cartography at the moment mostly using Google Earth because I want them to learn about color, symbology and chart junk, not some abstract javascript that they will forget a week after the course is over.

The rest of the post goes on to explain why Sophia thinks TileMill for windows is a game changer.

Wednesday, February 8, 2012

Grids are good

Excuse the use of map inserts rather than screenshots, I haven't got much time at the moment.

Look at an old Ordnance survey map of the uk and you'll see it's covered by a thin, blue lined grid.  On recent map systems such as Google Maps and OSM there is no grid.  My discussion today argues that we should bring the grids back.

Grids No Longer Necessary?  To locate yourself on an old map such as OS a grid allowed you to use grid references.  Web maps produce points at the right place without such a grid so because a grid adds to the visual clutter of a map, we're best rid of them?

Nope.

Landmarks and Scale:  A grid is helpful because it gives a sense of scale to the map.  If you're looking at part of the antarctic


View Larger Map

 you have no sense of the size of what you're looking at.  Fix a grid of 1km spacing over the top and you can immediately judge distances.

Point Landmarks.  To locate yourself on a map your brain looks for known features and fixes your position in relation to this point.  Here in London that means that Londoners often describe an area in relation to underground (=metro) stations because that's how most of us get around.  The problem with this is that in tests it's found that people tend to position points that they remember by a landmark too close to the landmark.  So if my house was 1 mile away from Clapham South underground station if I was tested I'd tend to draw it closer, say 3/4 of a mile.

Line Landmarks Another way we locate points is in relation to line features such as a major road or coastline.  This has problems too.  Consider the question, which is further west of these UK cities: Glasgow or Cardiff?


View Larger Map

 Glasgow is towards top of map in Scotland.  Cardiff is due west of London and Bristol, you may have to zoom out or in a little 

Without looking at a map most Brits think that Cardiff is further west.  That's because they have a mental map in which the East coast of the UK runs north south whereas it actually runs NNW-SSE and they warp space to accomodate this misconception.

Grid Solution Because a grid runs exactly north-south and east-west it gets over the Glasgow-Cardiff problem.  Also, it minimises the underground station problem as it represents a continuous set of landmarks rather than discrete points (although this point is worthy of more testing to prove this is the case).  So a grid can deliver both a sense of scale and a landmark system which allows people to fix positions on a map and remember their positions correctly.

When to use Grids: I suspect that its more useful to use a grid in an area without a strong set of landmarks (desert, tundra) rather than somewhere with good landmarks, if you put a grid over US cities with their right angled street systems I imagine users would ignore the map grid because the street system provides such a good system of landmarks already.

Friday, January 20, 2012

National Rail into Google Maps in the UK

In an earlier post on web transit maps in London I noted that when you used the public transport route calculator on Google Maps it didn't include national rail.  That wasn't too much of a problem itself (it's obvious they were working on whatever licensing/data issues were holding up getting that data in) but my criticism was that the map didn't make that clear.

The discussion has now become academic as I learn via Ed Parsons that national rail trains are now included in their route planner.  Good work Google!

Friday, January 13, 2012

Will Zooming Break the Map?

My PhD student Craig has been testing university undergrads on interactive web maps.  His results have revealed the fact that:

  • Despite being set tasks that require users to zoom in to search effectively, some users don't use the zoom control
  • One user commented that s/he didn't want to zoom in as s/he might 'break the map' and 'not be able to get back'
Digital Natives? What is most interesting about this result is that these are undergrads, supposedly the 'digital natives' we hear so much about.  The fact that some of them can't use basic map controls means we need to think hard about web map design when our audience will include people with generally low IT skills.  A static, non-zoomable map may be the solution to go for even if it is less elegant as a solution.

Web Browsing Skills:  Will this issue continue in the future?  There's a useful analogy in the development of user skills in operating web browsers: I remember teaching introductory ICT to mature students in 2000, lack of understanding about browser features such as back buttons and URLs was common at the time.  That general lack of understanding has now disappeared because most people use browsers regularly.  Use of web maps has been common since around 2005 but their use is (of course) less common than browsers so I wouldn't be surprised if basic skills associated with web maps were taking longer to spread through the population than web browser skills took.

Thursday, December 22, 2011

Map Tales vs Google Earth Tours

Readers who have read my other blog Google Earth Design will know I promote Google Earth Tours (GETs), the ability to record a virtual trip around Google Earth as a good communication tool for maps. I came across Map Tales, a web map based service (More detail on Map Tales) that allows you to create a set of locations linked by a story.  I thought I'd compare the two as I think the idea of GETs on a web map is an interesting idea.

click to open the tour

GETs in Detail: Some key characteristics of a GET (and example above): 
  1. A recording of a virtual flight around Google Earth: camera orientation, location and altitude is recorded throughout and can be replayed. 
  2. Easy to produce simple examples (Click a record button, fly around, click stop recording).   
  3. Layers can be turned on and off 
  4. Pop up balloons with text, images, video clips can be triggered and closed automatically 
  5. To produce them Google Earth is pretty much essential  
GETs advantages over Map Tales:  The Map Tales service shares some characteristics of GETs, like them they are easy to control, produce and pop up information can be added easily (see 2 and 4 above).  A Map Tale differs slightly in that it has 'steps' - a window of information presented for a unique location and the Tale stops at each step.   There are major differences though: 
  • No Layer Control: in a Map Tale layers cannot be controlled which stops the author from useful structures such as having two markers from the map tale visible at the same time in an overview.  This is very useful in helping users track the spatial relationships between the points.  
  • No Paths: Not having layers also means paths, routes and roads can't be added.
  • More Sophisticated:  GETs have a wider range of features including being able to add audio, using streetview, 3D topography and flight speed control.






Map Tales' (see above or full size version) advantages over GETs : 
However, Map Tales have advantages because they're simpler:
  • No Software: you don't need to install any software  to produce a tale, it's all in the browser.  
  • Stepped controller is an improvement over the VCR control in GETs.  I find when playing a GET I'm often have to stop it at a place.  You can do this with GETs (as in the link from the screen shot above) but you need to add pauses by hand editing the KML.   
  • Editing a Tale: When you've completed your tale you can drag and drop the steps up and down the 'play' list.  This kind of simple editing is not possible in a GET.
  • Look:  The visual look of Map Tales is well designed and distinctive.  For simple tales I think this design adds value but for more complex tales I think the lack of control of the site design (e.g. size of info window) would be a problem.  To embed it above its size is a problem and it looks cramped.
Overall I think Map Tales is a useful example of how a simple form of map based GET could look.  If you want to produce anything but a simple tour I think GETs are definitely the to go.  In addition,  the inability to be able to view more than one marker at once or mark a line route is a serious disadvantage.  However, the ability to edit tales and the stepper control are interesting features and I think with the ability to control layers it could be a useful tool especially in education.

Wednesday, December 14, 2011

oMaps, Google Map edits and Google Map Update

Back from my break, had a great time in New Zealand and Australia although my brain still isn't quite in gear again.  Today I've three topics to discuss:

Off 3G Mobile Map use:  While I was away, my iPhone 4 was invaluable for navigating around.  Of course download fees on 3G outside of the UK for me are a daylight robbery so I limited myself to picking up data via WiFi hotspots.  There are two techniques I used:
  • Google Maps:  Navigate to the place you are going whilst on WiFi, so long as you have cached all the data you need, when you're moving in city the blue locator works and you can navigate around as normal.  However, if you only stay on one zoom level whilst on WiFi you can't zoom in when you're on the ground - only the zoom levels you've cached are available.  
  • OMaps:  The OMaps App on iPhone works with OSM data and allows you to define an area and cache all the tiles at all levels prior to getting there.  Its a bit fiddly, the tiles don't download quickly and you have to get the balance right between getting a big enough map and defining an area that's large with an unreasonable download time.  Once you're through these hoops its very useful.
Google on the Ball:  After my recent critique of Google/Bing/OSM maps with respect to the UK Houses of Parliament and Clapham Junction train station Google updated their symbolisation (discussed in more detail below) in both areas.  I suspect the changes to Clapham Junction were part of a broader update but the changes to the symbolisation of the Houses of Parliament look like they are a reaction to my comments and work much better.  That sort of reaction is impressive.

I just checked Bing Maps, no change to their map.   

Google Maps Update:  In the UK, Sweden, Germany and Finland Google have just added a major update to their map.  They point out in the post that map data has improved in terms of 
  • Water bodies 
  • Parks
After a quick glance at the UK map I also note some other changes I think they've made:


View Larger Map

  • More detailed train lines and a change in symbolisation to dashed lines (see above)


View Larger Map


  • Parkland, common land, university campuses, cemeteries are marked by different colored polygons (see above)

More data on a map obviously adds to its value but if the symbolisation is not well thought out you can get problems with visual clutter.  I'll be discussing this update in terms of map usability in a later post.