Friday, October 5, 2012

Smart Educational Map Tool

I came across Gemma (Geospatial engine for mass mapping applications) by CASA at UCL.  Its a smart service well suited to educational use, it has three great functions available in order of priority:

  1. Easy to Build Mashups:  Enables the user to pull in useful thematic maps (from map tube) or other layers (from OpenStreetMap) and to create markers on top of them.  For example, you could map population density, show where tesco stores are and then tag interesting examples where tesco stores don't seem connected with high population.
  2. Greyscale Base Map:  One of my continual gripes about Google Earth/maps is that it isn't easy to avoid the visually busy satellite data/road base level data.  Gemma enables a greyscale map that allows location still to be seen but doesn't crowd out the view enabling the map producer to show more layers with clarity.
  3. Easily import in Mobile created data:  Its linked to an iPhone app so a student can collect data and easily feed it in.  I haven't checked out how this works but the idea is very promising.
The team deserves a big cheer IMHO.  I do have some grumbles:

  • Pull down options not search:  If its possible, I'd like to see the search option for OpenStreetMap replaced with a pull down menu as the default option, with a search available if you really want it.  Its a pain to have to guess what will pull up the right data, view the map, then go and delete the layer because it wasn't what you thought it was.
  • Layout:  I think the use of space could be more compact.  A lot of screen real estate is taken up by the header and the layers appearing at the bottom of the screen will also take up considerable space if you produce a number of them.  I found this old screenshot of Google Earth v4 (I think? - see below) which showed that their original design similarly lost screen real estate.  In the next version they abandoned the thick bottom panel after user comments.  

  • Simple Markers Needed:  The markers available are all complex visually with color grades and multiple colors.  This is OK for a few markers on a simple map but if you add in lots of markers then the screen will soon get busy visually.
However, overall its a great resource.  I notice that the project blog stopped in November almost a year ago, its a shame if there's no follow on funding to take it further and get it out of beta.

I usually promote Google Earth as the best tool for education, the three big pros of this project are something it would be great to see in GE in the future.

Friday, August 17, 2012

Crowdsourced Map Experiment


As reader's of this blog know, I am supervising a PhD student, Craig Allison (@theRedSorcerer).  He's investigating whether point collation techniques or heat maps can be understood by users or not. (previous post about the project)


 

examples of point collation and heat maps

We'd like to see which one is better from a usabilty point of view and we'll publish the results. With this in mind Craig has created a 10 minute test and questionnaire that would help us answer this question, it can be found at


Please have a go and pass onto others.

Wednesday, August 8, 2012

GoogleIO Map Design Talk Response

Below you'll see a session on map design (called 'master class in map styling') featured at Google IO this year discussing Google Maps.



I think they make some excellent points and explain how to put their ideas into practise code via js code examples in Google maps.  In the introductory section they discuss the map design process as being one where you;
  • Think about what data to remove
  • Refine the data that's left (e.g. adding selective emphasis)
  • Test the map for multiple zooms
which I think is very sensible.  I've blogged about the value of removing data myself.

These are the points they make in the rest of the talk that I particularly liked;
  • Lowest Zoom first design the lowest zoom first then edit other levels afterwards by stripping out data as you zoom out higher.
  • Roads as Landmarks its handy to leave roads in for orientation (at 27:00).  
  • Width Editing The ability to edit the width of elements is a new API feature and they show how it can be used effectively at 27:25.
However, I differ with their opinions on a couple of points:
  • Ocean = White  At 25:54 they change the color of the ocean and harbour water from blue to white saying this has less visual impact.  A desaturated blue is better IMHO because it blends into the background better than white and people naturally associate blue with water.
  • Parks = Gray  Similarly at 26:01 they change the color of parks from green to gray.  Again, people naturally associate green with a park and a desaturated green would fade into the background sufficiently while being easily interpreted IMHO.
Data Density and Keys What I think they could have usefully added to their talk beyond the 3 major points they use above is discussion about coping with data density, i.e. the difference between a map mashup showing a few points and a map with hundreds of points.  At 28:46 they show a map mashup with some circles representing who likes cats or dogs at certain locations in San Francisco and at 29:00 they go on to dismiss the idea of using animal icons such as the ones in the image below (showing eagles and wolves from this post discussing icons) as being 'cheesy'.


They are quite right that A cat/dog icon could be naff but map icons have an inherent advantage over simple circles: you can work out what they mean without looking at a key.  You need extra information to work out that their red circle symbol = number of dog lovers.


That's not to say that simple icons like circles shouldn't be used, in fact they're very useful when there are hundreds of data points to plot (see above showing the location of Boris bike stations, further detail here), lots of icons on a map leads to the 'flock of sheep' problem (see below, the same Boris bike example)


So its worth using simplified icons when you need to show many data points even though they need a key to provide interpretation.  

Tuesday, July 17, 2012

Animated Maps: The Way Forward?

I didn't make it to Google IO this year but have got a lot out of watching the Google maps talk videos.  One announcement they made was a new type of map element; 'symbols'. These enable developers to animate Google maps more.  Ed Parsons has bigged up the possibilities and I agree with him that animated maps have great potential and that there should be more use of animated maps.  At the moment they are nowhere near as common as simple map mashups.  I've been researching map animations recently so today I'll share some thoughts.

The potential of animation in Maps:   Any graphic or text needs to perform a number of functions:
  1. Catch the eye of the user
  2. Lead the eye around the graphic intuitively 
  3. Communicate effectively
  4. Produce a memorable and/or emotional response if possible

We can argue about how good this list is but I think its generally true (I've paraphrased it  from a book on graphic design 'White Space is not your Enemy').  

Movement always catches the eye (think blinking cursor) so map animations always do well at [1].  They can also be extremely effective at communicating effectively [3], the gap minder animation below is geographical information although strictly it isn't a map.  IMHO its very effective at communicating the story of how most countries have developed considerably in the 20th century and its also easy to pick out individual countries from the animation.



I also like this animation of the spread of post offices in the US (although its probably better watched at a higher resolution than I have here)





Downsides to Animation in Maps. However, there are a number of problems with animations.  

- Going, Going, Gone:  Unlike a static graphic, the information is only visible for a fixed amount of time so the user has to see the information, make sense of it and remember it before the animation moves on.  With a well designed graphic, such as Edward Tufte's diagram showing the development of storm clouds, all the information is available for review and elements are constantly visible.



one of the nice aspects of the post office map above is that it keeps the dots on screen after they've appeared which mitigates this problem somewhat.
- Pat Head, Rub Belly:  The kids game of trying to pat your head and rub your belly at the same time illustrates another problem known as split attention - we find it difficult to do or follow multiple things happening at once.  An example is the map based animation at 55 seconds in this clip showing rainfall and taxi location at once.






Solutions:  There are a few solutions to these problems:

- Simplify Icons/other symbology:  Animated maps need to be simplified as much as possible, an easy examples include making icons plain shapes such as rather than a more meaningful bike shaped icon.  The background map on which the data is being animated can also be simplified e.g. removing colored roads.  The post office map above is a good example of both of these things.
- Play Slowly:  In complex parts, slow down the speed the animation is playing at.  This needs to be done with clear signalling otherwise they could miss that it was happening. 
- Annotate:  If something interesting is happening on a screen full of changing data (the split attention problem) a labelled arrow drawing the user's eye to the correct location on screen can be very helpful.

Conclusion:  Map animations can be very powerful but they need to be implemented carefully with a user centered focus.  See this post for more detail and Mark Harrower's discussion

Tuesday, June 26, 2012

Apple Maps and 3D

So since I last posted here there has been a lot of to and fro about 3D in mobile maps.  I won't get into discussing the Google vs Apple rivalry as this has been well discussed elsewhere .  What I'm interested in is what is the long term value of 3D on maps.  Consider this video



it shows two 3D features I want to discuss here, 3D full color and 3D grey blocks.   I've discussed these issues before but its worth revisiting considering the new Apple example.   The full color IMHO is just showy, I can't see people pulling up this kind of imagery on their mobile devices whilst on the move, its just too visually complex.  I think everyone is going to play with it when they first see it on a device and then revert to something more visually simple when completing navigation tasks.

The more interesting feature is the 3D gray blocks.  Of course these aren't an Apple breakthrough, they've been on Google maps for a while:



Gray blocks for buildings (either of the Google or Apple variety) are visually simpler than full colored buildings and so may form an extra layer of information which users can use to navigate with.  I think the simple Apple gesture needed to make 3D snap on or off is good, this may make it something users can turn on when they are on the move and think it could help them navigate.

However, I think the buildings examples used in the demo had distinctive shapes so the grey blocks view looks very effective.  The feature may be much less use in a more normal city scape where building shapes are squarer and much more uniform.  So for navigating around a city, I'm yet to be convinced 3D gray blocks are a game changer.  And of course, out of the city, the feature really loses its value as buildings big enough to act as landmarks are much rarer.

More interesting is when navigation moves indoors, then shape of rooms and corridors becomes much more important for navigation IMHO.

Thursday, May 24, 2012

GOV.UK and Maps

Posts have been thin on the ground recently because I've been busy teaching a new course at the Uni.  However, its all over bar the exam marking now so I'm hoping to be more active here.

A friend has been involved in putting together GOV.UK - a site that provides the public with information from the British Government and acts as a clearing house to councils and other public bodies.  I really like the site, one of the key characteristics is that the designers have clearly focussed on user's needs.  I've had a quick whizz around looking for ways maps are, or could be, implemented in the site and a few thoughts spring to mind:

One Map, Many Points:   In the neighborhood section of the map you can enter your postcode and find services around you.  The site delivers you a list of possible local services, in the example below, we're looking at computer training courses:


As you can see, you get an individual map for each location.  It would be much better to provide one map with all the suggested services as markers with a linked list to the left of the screen (much as Google Maps and other services already deliver search results) with your entered post code shown as well.  This would enable the user to see which service is closer or if its close to their work commute route.

A nice add on to this would be travel time estimation circles centered on the entered postcode as found on TFL's 'Why not Walk It' maps.

Map Wiki: I also noticed that the site doesn't link users to useful map wiki or VGI (Volunteered Geographic Information) web sites such as FixMyStreet.  This enables the public to easily alert councils in the UK to problems with public spaces such as fly tipping or potholes because they interface with a map which is much easier than filling in a form.  I suspect that the remit for gov.uk limits their ability to have done this since they link out to councils sites for this sort of service and councils may or may not have chosen to use a site like FixMyStreet.  

Map as Spine:  The way GOV.UK is organized is centered around search and text based categories.  There's nothing wrong with this structure, I'm sure its what most people want to use.  However, I wonder if a map based structuring would add value as an extra way of organizing the data?  Instead of entering the site wondering how to answer a specific question, maybe people would like to mine the information to make broader decisions such as where in London would I like to move to?  A series of maps based on each area could be very useful showing people how well an area is serviced by the public sector and data from within the site could be used to populate the map.


Thursday, April 26, 2012

Color Blindness and Color Blends

I came across these color blends in a post on the web today (to save blushes, I'm not linking) from a mapping developer.  Here's what they look like to the majority of us



and here's how 6% of the male population see it (via the excellent color oracle freeware)


clearly the bottom two blends will be very difficult for color blind users to interpret.

Color blindness is a lot more complex than I've explained here but generally blends from yellow to blue are much better than reds to greens.  More info on color blindness in maps here.

If you're interested in the more general uses of color in maps, the Haklay text book has a good couple of chapters.

Wednesday, April 4, 2012

Usability Problems with Zeros on Cluster Maps

Please excuse the lack of post recently, I've been particularly busy with teaching over the last month.

Some Experimental Results: My PhD student Craig has some results from a usability experiment on the UK Crime Maps site.  It's too early in the analysis to discuss in detail but one aspect is coming across very clearly: users are getting confused by the representation of postcodes with no crimes on cluster maps (explanation of cluster maps).




Problem:  When you zoom in on an area in the crime map, you are presented with a view as on the left.  The number of crimes in the last month is shown for each postcode as a number in a blob, e.g. for the postcode mid left (above Thurleigh Rd) there were 4 crimes.  The problem with this visualisation is that the boundaries of the postcodes aren't visible.  If you look on the right I've illustrated roughly where two of the postcodes are with dotted red lines.  The postcode on the left has 1 crime, the one on the right (Devereux Rd) has none and so hasn't got a blob at all.

When users were asked to pick out the postcode with the least crime on the actual crime map (left) they failed to understand that no blob = no crime and identified the blob with the lowest number as the postcode with the lowest crime.

Solution:  On collated point maps zero crime postcodes should be represented by blobs with zeros in them.  

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.

Wednesday, November 16, 2011

Blog Break

I'm downing tools for a while but I'll be back 2nd week in December.

Google, Bing and OSM Maps: Train Station Symbolization

As part of my research for last weeks blog looking at how the three maps in the title handled symbolization with zooming, I had a look at some other locations in London.  The one that stuck out for me in terms of usability was Clapham Junction Train station at a low altitude zoom level.  This is a local station of mine and also happens to be the busiest station in the UK with over 100 trains an hour.  With so many passengers it makes sense that it should be mapped well.

The User's Needs when Zoomed In:  What is a general user looking for if they access a web map of this station?   If they are zoomed in close then chances are they are searching to answer these questions:

  1. Where is a station entrance with temporary parking? - I want to drop off someone by car.*
  2. Where is a station entrance handy for me?  - I'm getting to the station by bus/bike/foot?* 
  3. Where do I find food/drink/toilets/cash machine?
If they are changing trains at Clapham they will probably follow the station signs rather than looking at a web map so 'where is the platform I need?' doesn't get onto the list. 

Entrances and Exits are Key: So from a user's point of view I think the primary information that a map of this scale should show are the station entrances and exits.  If the user question is [3] then they still want to know about exits/entrances since often services are ouside the station and they will have to get in and out.  Using the above list it seems to me that the map could also usefully show temporary parking, bus stops, cycle racks, food outlets, toilets and cash machines.  However, the symbols showing these services should be secondary in visual impact to the entrances.

Let's see how the map providers fare in meeting these user needs:

Entrance locations: Before we begin the review we need to understand a little about the entrances to the station.  On the Open Street Map below I have added the four entrances to the station as red squares.  Its also important to know that the Brighton Yard entrance (bottom) is relatively new compared to the others.


Open Street Map of the Station:


First up, Open Street Map is packed with detailed information.  All the entrances are marked except Brighton Yard, however, they are symbolized weakly as dotted red lines and are difficult to pick out.  Services are marked on the map at many locations although I note that food outlets on the platforms and the access bridge are missing (I've now added them myself, because that's the point of Open Street Map).  There is no opportunity to click symbols and access further information.

Whilst Open Street Map has done well in terms of having the information available, my problem with this map is that it shows too much.  Most of the information is there but by packing all the data onto the map it becomes visually complex and the entrances are not emphasized.  A particular problem is the rail tracks: all the lines and sidings are shown but the location of these has no use for the average user as they will be navigating within the station guided by signs within the station.  Also, the dashed line symbolisation just doesn't work when the lines are packed together.

I discussed the 'too much' information problem in a previous post.


Google's Map of the Station:



Google's map is far clearer when compared to the Open Street Map but important information is missing and the symbolisation is confusing.  It shows roads and bus stops clearly but other services aren't well marked.  Entrances to the station are missing.  The multiple rail lines have been reduced to two which show the general directions of the lines leading out from the station - much better symbolisation.

My main problem with this map is that rather than use a polygon and a single marker to show the station (see last weeks discussion), Google has a confusing group of 3 markers.  You would be mistaken for thinking the station was quite small and in three separate locations.  In fact it's one large station that covers most of the above map, as you can see from the Open Street Map.  Click the rail station symbol and you are not linked to anything to do with the station but see information about the nearest buses.  Very odd.


Bing Map of the Station:



Bing's map is similar to Google's in terms of clarity:  Few train lines are shown, roads are clear and easy to see.  Bing also uses a single marker at the main St John's hill entrance which is logical and an improvement on Google's map.  When clicked this station symbol links to a route calculator which is more sensible.  

However, the other entrances are not marked and no services are marked.  At this zoom level I would expect at least some services marked and the lack of entrances is a real issue.


Conclusion:  I've outlined why I think at this scale of map, the key information users need about Clapham Junction station is the location of the entrances.  The maps vary in how many entrances they mark but none of them show all of them with the required level of emphasis IMHO.

Looking at other data that could be usefully marked on the map; Open Street Map has the most detail but it is presented in a visually complex way.  Bing maps goes to the other extreme with a very clear map but showing little useful information.   Google's approach of mixing some service information on a relatively clear map represents the most sensible approach but they have used some very odd symbols in the process.


*Obviously 'entrance' could be replaced by 'exit' in these questions for journeys going in the other direction.  For clarity of discussion I just describe outgoing journeys in this post as return journeys are exactly the same from a map point of view.

Tuesday, November 8, 2011

Google, Bing and OSM Maps: Zooming Symbolization

How Symbolisation changes with Zooming Out: A couple of weeks ago I sang the praises of Google’s 3D building symbolisation. I said putting 3D building models into Google maps with a faded gray coloring could really help people using their maps to navigate around a city. Such models represent symbolisation: the simplification of reality (3D buildings) into simpler symbols that help understanding. This week I look at how the symbolisation of buildings changes as user’s zoom out from a close in view.  I'm assuming that the user is doing some sort of navigation task again and I compare
  • Google maps
  • Bing maps
  • OpenStreetMap
Change Sucks: The first thing to point out is that evidence from my PhD student Craig’s work on the usability of maps shows that changing symbolisation as users zoom out makes it difficult for users to track what’s going on. So any sybmolisation change, say from a building polygon to a point symbol, has a mental  ‘cost’ to it, symbolisation should only change where there is good reason to do so.

Polygons to Points: So how should building symbolisation change as a user zooms out from an urban landscape? A good best practise is to have buildings represented as polygons at low altitude. As the user zooms out, the polygons become difficult to differentiate visually so it makes sense to change symbolisation to a labelled point. This is exemplified by Google’s rendering of the White house as in the screen video below. (apologies for the quality and varying sizes of the videos below, I'm experimenting with a new screen capture tool and haven't got it all worked out yet)




Points to note:
  • The symbolisation starts out as a 3D gray model
  • It switches to a polygon on zooming out
  • At all times the building is represented by a labelled point. As the user zooms out the polygon disappears and we are left with just the labelled point.
Its pretty faultless, every change in symbolisation is helping the user and it's an intuiative system.

Parliament by Google: So how does the white house example compare with the UK seat of government, the houses of parliament?



Oh dear, nowhere near as good.  A clear glitch that all labels and symbols disappear at altitude.

Parliament by Bing:  How does that compare to Parliament by Bing Maps?  Bing uses a different approach, instead of having one base map that switches symbolisation as you zoom out they have incorporated an old static style road map as the base level which changes at altitude to what amounts to a completely different map.



As you can see, the symbolisation at the lowest level is better than Google's Houses of Parliament but less good (IMHO) than Google's White House.  As you zoom out, the symbolisation stays the same which is easy to follow as a user, but the view becomes very cluttered.  The switch to a completely different map system is clumsy at best.

OpenStreetMap:  In comparison OpenStreetMap does well at low altitude with good labeling (shown here as an image rathe than a video):



Their approach is to have labels without points which then disappear at altitude while the polygons persist.  I think a labelled point at high altitude is the better system.  This alternative technique isn't too bad visually as the polygons are a neutral color and, as we've discussed,  keeping symbols the same helps users understand the map.  However, if the polygons became paled out at high altitude (so they blended in with the background) then they would work better IMHO.  This is because the road network operates as a landmark system at altitude so needs to become visually dominant over the buildings. 


Conclusion:  I wouldn't want to generalize to judging the quality of these three mapping systems on the 'Houses of Parliament' test.  As we've seen with Google, the quality can vary from place to place.  Its also easy to pick holes with mapping systems in this way, there's an enormous amount of work in producing intelligent symbolisation for multiple zoom levels across the entire globe and the visibility of polygons, labels and points at different zoom levels has to be automated in some way.  However, IMHO the symbolization could be improved in all of these three map systems and the building is important: its the seat of government in a G20 country and a major landmark in a world class city.    

Wednesday, November 2, 2011

Streetiview vs Streetside from a users point of view

So there has been a lot of blog posts on the internets comparing Bing's Streetside with Google's Streetview.  Mostly these cover technical and privacy points:


Streetview: Much larger coverage (certainly in the UK), Full 360 degree view




Streetside:  Avoided some of the privacy controversy by targetting 'super public' areas such as city centres rather than residential areas.  Viewing is more limited to a row view of buildings that slides by.

No one has covered the usability issues in detail so I thought I'd make some observations, to do this I need to go off on a bit of a tangent into 3D virtual environments:

Less Control = Easier to Use:  I've just finished a draft of a paper in which I reviewed Google Earth Tours.  One thing I discovered in the literature is that in 3D environments (Google Earth, Second Life) the 6 degrees of freedom* that a user needs to control can cause problems of usability:
  • Walls aren't solid: Users can crash through model walls which is disorienting
  • Desert Fog: Users end up very close to a plane surface like the ground, they can't see any features to orient themselves or guess scale - they are said to be experiencing desert fog.  
  • Peripheral Vision:  Because of the limited computer window into the environment they miss visual clues from their peripheral vision that they pick up in the real world (better in a CAVE setup or similar of course) 
Limiting their degrees of freedom of movement can help users avoid these issues.   An example is a tower in Second life - if a user can be 'locked' into moving around it so they can only fly a fixed distance from the tower and their vision is locked directly towards the tower they would avoid some of the problems listed above.  Their degrees of freedom have been reduced from 6 down to 2 (they can only fly up/down outside the tower, orbit it left/right) but they can still explore it.  Even more radical in a Google Earth tour users only have VCR play/pause/rewind controls effectively reducing their freedoms of movement down to 1.  

Streetside Constrained Freedom:  Streetside has taken the same 'constrained view' approach.  They allow a user to only look directly at the side of the road, this is sensible as in a cityscape as this is the most useful view.  To switch view to the other side of the street you simply click a little 180 degrees view button which zooms you around.  Streetside:
  • Mutiple Controls: Avoids problems of having to operate multiple controls (in Streetview they may expect double clicking to zoom them into a photo view, in fact it moves their position)
  • Look Sideways: Allows users to move along a street whilst looking at buildings.  In Streetview users have to face foreward to move foreward, to look at the buildings on the side of a road they need to stop and turn.
UPDATE 3rd Nov:  Actually that's not strictly true.   Streetside offers 'slippy slides' of the street going past which is better than Streetview's click-refresh operation.  However, you can arrange Streetview so you're looking side on to the street and then click the arrows so you move along.  Its quite clever actually.   
  • Fast: Allows users to whisk along a street in a zoomed out view faster than moving through Streetview (in a little informal test I did myself, see the zoomed out view that allows this in the above screenshot )
However, this comes at a cost.  Streetview has the advantages:
  • Less Disorientation: I think its easier to become disorientated by moving down a street only looking at one side.  Certainly for testing out a cycle route across a town, Streetview is more natural and would be the better tool.
  • Photo stitching is better in Streetiview, in Streetside I noticed whole streets warped out of view.  This may be a technology issue that is solved soon but at the moment it's a real issue.
  • 3D Buildings: While looking at Streetview, Google Maps also supplies 3D building models (earlier post on this topic see screenshot above) which further helps with orientation. 
Conclusion:
I think the Streetside approach is very sensible and may well be better than Streetview in cities.  However, outside of urban areas you would need to use Streetview as the side of a road becomes far less interesting.  IMHO the best product would offer both these approaches.  


*Avatar: up/down, forwards/backwards, left/right
  Camera orientation: yaw, pitch, roll

Tuesday, October 18, 2011

3D buildings as Landmarks in Mobile Maps

Maps and City Navigation: Today I’m going to be looking at ways of including buildings as landmarks for user’s trying to navigate an urban landscape.  How important are landmarks for navigation and recall?  its relevant that memory champions who can memorize the sequence of a deck of cards in a minute use spatial landmarks as a system to aid their recall:  The memory palace technique has the user walking through a building well known to them imagining vivid tableaus such as a moonwalking Einstein (the title of an excellent book on memory) happening in different rooms.  The technique taps into our spatial memory system and shows how powerful landmarks can be. 



Google’s 3D buildings as Landmarks:  As an example I really like google's 3D buildings in google maps (see above, bottom screen shot). In a city scape the buildings can carry important landmark information for users trying to orient themselves using a map on a mobile device. A 'you are here' marker from GPS readings can make such orientation irrelevant but cities can cause a GPS trouble because of the 'urban canyon' effect so landmarks are still important.

You could choose to put full color 3D buildings onto a mobile device map as landmarks but this has issues that are useful to consider: 
  1. Device processing time: full color models would slow the device down, the data bandwidth needed is very demanding. 
  2. Visual processing: full color 3D can be complex for the user to process cognitively, for instance the color and structure of the buildings would make it more difficult to see the road pattern below.
  3. Bird’s eye View:  For way finding, the bird’s eye view of a building is often not its most salient feature visually.  It is often the view from the pavement (sidewalk for US readers) like the colorful facade of the building or the grand doorway that provides the memorable image a user can latch onto (see top part of image above which relates to the location shown on the map).  
Google’s gray, plain rendering of buildings in 3D is a good solution to the first two issues but fails on the third.


Interesting 2D Alternative: Another way of including buildings in maps so they can be used as landmarks is to use photos.  A photo of an interesting building from road level at a node (road junctions or other important route points) mimics streetview functionality but pulls out the best landmark features of the view at that node (see top part of the image above which is taken from the streetview image of the map below). When a user trying to navigate a city reached such a junction and had a choice of routes she could locate herself using the building photo.  IMHO this addresses the three problems listed above but unfortunately it introduces another issue:  what makes a good visual landmark requires human input whereas Google’s gray building layer can be produced automatically.


    Interesting 3D Alternative:
    A second alternative is to move into sub 3D view as illustrated above. Selected buildings at nodes are shown, they are rendered in gray at an enlarged scale (from a post by Digital Urban )

    If you follow the link to the post you can also see the image placed into a zoomable Google Maps interface but at a 45 degree angle, this has a lot of potential for navigation but it has issues:
      • Plan View: A plan view is better for viewing roads
      • Single Direction View: You can only see the building from one compass angle direction (North Eastwards in the above image).  Often from ground level it’s a street level feature like a large doorway that is most salient to the viewer.  Unlike features such as the Gherkin (the torpedo building in the above image) a model of a doorway doesn’t make any sense viewed from the wrong direction.  
      Usability of 3D maps in Navigation:  Related to our discussion of 3D in navigation, the comments on this post of mine about a 3D map of Southampton University's campus are interesting:  they suggest that 3D may be causing usability problems for those who are not familiar with maps .

      Conclusion: Google have to provide a base map for any journey that their journey planner may suggest to a user that works on a mobile device.  Overall, I think their current solution is arguably the best given the need to produce their maps automatically and addressing the three issues I list above.  Where it would be worth trying out the alternatives I've suggested in this post would be a map for a particular route e.g. a map informing people how to get from a particular train station to a museum.