Regions Solution

I've long been suspicious of regions as a solution to data overload. The basic idea is that you can define an altitude above which placemarks are not visible but below which they appear. This meets two separate needs, firstly it is a way of avoiding visual clutter on screen, secondly it means large data sets can be viewed without loading all the data at once. Neat.

The problem is that users with a low IT literacy skills may not realise regions are operating, they can click a layer in the places column and be annoyed that nothing appears because they are at too high an altitude to load the placemarks in. To my high IT literate readers this may seem a petty point surely they'll explore and find the placemarks popping up? No. They might not. They might click away and find the secret middle section to the magic roundabout theme tune*. In which case you've lost them.

I have a solution. Below is a zoomed-in a view of the Dafur default layer** which uses regions, notice the red one out on its own center of the image.


If you zoom out it will dissapear. But in its place a translucent magnifying glass placeholder tells you there is something worth zooming in to see in the square region it marks. Obviously this works best when there are multiple placemarks hidden under the magnifying glass placeholder.


The magnifying glass image overlay can be tagged with its own region so it appears at an altitude above the one where the placemarks appear. It should also be explained in an introduction otherwise users won't understand what it means which is as bad as it not being there in the first place.

*Non UK readers will struggle to understand the humour to this.
**Disclosure: I'm currently doing some consulting for USHMM on Google Earth.

Design Example: Wetlands

So over at Using Google Earth recently John posted a Google Earth project for use in a presentation about a conservation situation: authorities are seeking to place a landfill site in a sensitive area in California. It took me back to my masters degree in hydrogeology where we spent a lot of time looking at landfill design so I thought it would be an interesting case study: how would you convert John's file so it could be published as a web resource for the public?



Here's the original KMZ and here is my reworking

What I did:

1. Allow users to see some of the file structure, the original was just a closed folder which is fine for a presentation but doesn't encourage exploring when put on the web.
2. Change the name of the 'wetlands' placemark to 'introduction' and to give it a more meaningful camera icon - its main content is the photos and it serves well as an introduction to the project.
3. I marked out the proposed landfill site in purple with a black outline. This allows it to be easily distinguished from the background terrain and the other overlays without making it too bright (I tried red as a fill but it was too much).
4. Marked a series of zones on the map to give the user a sense of scale. These are simple rectangles but they would be better as 'buffer zones' (tutorial) showing all regions within 1km, 2km and 3km of the boundary of the landfill site. To generate these you need to use a true GIS package.
5. I turned off the boundaries of the land use types as they were different colors and so confusing to the eye. If I had the time I would have changed them all to be black and put them back in.
6. I also turned off the 'other' class of land use as I wasn't sure what it really was showing, strictly it should be everything else in the view but it wasn't.

Useful links for more discussion of these points:

• folders
• introductions
• art of map making (video)

Other Project Reviews by me
Dafur
Tree cover project reviewed in my talk

Further discussion about risk zones: I said buffer zones would be better than the rectangles, in fact even these could be improved upon to explain risk. What you really want is a model which takes account of tidal flows, the river flow and other factors to identify the risk of pollution at any point in the view. Without any modelling at all you can see that the hills are at zero risk of being polluted and it would be pretty difficult for the pollution to flow up river, most of the risk would lie downstream even into the sea beyond.

Craft of Google Earth?

On the Thinking aloud radio 4 (UK) program recently they discussed the idea of craft in modern society. Of the notable points they made were several relevant to design of Google Earth projects:

- Comparisons were made between computer programmers and traditional crafts such as pottery, musicians and architects. All of them require a detailed knowledge of related areas and to learn them requires constant experimentation and making mistakes. This is certainly true of building Google Earth (GE) projects, I know a lot about drawing icons because icons are important in GE projects. As for making mistakes, I'm always tinkering about with things that don't quite work in GE to get them looking right, I rarely know the 'right' way to do something complex before I start. One commentator even went so far as to carve 'creativity is making mistakes' in the concrete beam of his studio.

- Many craft people talk of knowledge and memory embedded in their hands. I told my Google Earth students this as a way of encouraging them to go out and experiment, if they don't practice building GE projects they are going to forget everything I've shown them very quickly.

- The discussions also involved discussing computer aided drawing and how it had affected architecture. Commentators felt that this introduction of technology has led to users forgetting about good design because they became infatuated with the tools. Another example is the appearance of microwaves in kitchens, remember all the fuss about the wonderful things you could do with this tool? It was only after lots of use we realized what its truly good for: warming up leftovers and cooking baked potatoes quickly. It's only after some time and experimentation that a community discovers what the tools can be best used for and starts producing valuable items again. IMHO we are well and truly in this period with virtual globes, I see lots of examples where I end up thinking someone just whacked a lot of data into GE because they thought it would be 'neat' rather than really thinking of what GE is actually good at doing to their data.

Powers of 10

This film about the very small to the very large popped into my head last week, I remember being fascinated by it as a child which is probably linked to my current interest with Google Earth. It was created by Ray and Charles Eames who were brilliant designers in a range of areas.



I thought it would be interesting to try and recreate the squares so you could fly through them in in Google Earth with the film itself as a placemark. Unfortunately a cycle track runs through the area of the original picnic - blasphemy! IMHO there should have a plaque there to commemorate the site :) (maybe there is?). To deal with the cycle track I put in a couple of screen shots from the film as overlays at the one to ten meter scale. Its for fun so I did the squares by eye rather than calculate them precisely, for example the last 10,000km square is a fair bit smaller than the stated scale, it's as large as I could make it. You are limited to only a few orders of magnitude by the scale of Google Earth but it was still fun to do.

Powers Of 10
(Note: you may have to right click, 'save as' and then open the file from the saved location - I have an unresolved problem with it not opening automatically from my browser)

The fame of the film seems to be continuing, for more details click here.
______________________

Later: Frank of Google Earth Blog just emailed to say what I thought was a browser problem with the file (and hence local to me) is a MIME type error. I've replaced the link to one to his servers above, he's done some work on improving it too.

Hallway Testing

In my AGU talk the other day I end by saying that the most important point to remember about design in virtual globes is that although I have lots of ideas about what works in Google Earth to make good design, testing is the final word on effectiveness. I recommend Steve Krug's book 'don't make me think', it was an inspiration to me about web page design at the time where Google Earth was a twinkle in Michael Jones' eye and most of the principles map across to Google Earth projects.

I find the technique of testing I outline has been written up in peer reviewed literature and is actually known as hallway testing from the idea that if you pull 6 people randomly from any hall way and quickly use them to test your application/web page/Google Earth project you can identify 95% of usability errors.

I also looked up paper prototyping, a technique that I came across in the Open University (UK) where you prepare web pages scribbled on bits of paper and model how it would work as a web page by switching paper sheets when the paper buttons are pressed. Not only effective but a lot of fun. Robin Good has a good intro.

Like tidying your office and managing your time properly testing is not something people are naturally drawn to do but they reap the rewards if they do.

Contextual help - BestTos

So when I was at AGU in December I met a few people from Google. After my talk, one of them who had some responsibility for KML asked me 'how could we change the design of KML to incorporate your ideas on design?'. KML, for those who don't know, is the type of code that Google Earth uses to record the data that it lays on top of the satellite data. The question really stumped me, most of what I talk about on this blog could be best promoted by Google Earth staff changing the Google Earth tutorials, some changes in the way the Google Earth itself works could also help (e.g. timelines) but changing how KML works doesn't really help. I've had a long think but I still can't think of any major changes worthy of mention. However, it did get me thinking about how to change Google Earth the program to help design.

The idea I came up with is contextual help. The program I know this from is Moodle, an open source Learning Environment, it has little orange question mark icons, the screen shot below shows you one and the the window that opens when clicked.

Contextual Help Screen Shot from Moodle

Its a neat way to show help: not sure what an option means? Click the yellow question mark to find out directly rather than having to look it up in help. Nice. But wait! contextual help does more, it mixes in best practice as I've circled in red, so it not only tells you how to do something but how best to do it as well. This would work wonders in Google Earth, when you are designing a placemark you could have a little contextual link by the icon button which tells you some basics of how to design an icon well with links to more details on a web page somewhere.

In fact that's a term that we should see more of, there are lots of 'how to' blog posts (or HowTos) but we also need BestTos.

Talk: Design in Google Earth

As promised, this is a link to an movie clip version of my talk at the American Geophysical Union(AGU) last month:

In it I use as an example a Google Earth project by Mark Mulligan who designed it primarily to be used by experts rather than the public. This link opens my new version.

Tree Cover Change Tour

I've added a few tour placemarks, the idea is that users open the file, read the introduction, get shown what they can see with the data and then go on to explore themselves. I talked to Mark about using his file and he was interested in what I've done with his work. It made me look again at the huge volume of material he has produced and I found some gems that I'll be using in the near future.

Technical Notes on Talk: I produced this by recording my PowerPoint presentation with Captivate software and converting it to flash as it allows me to capture the custom animation features of my talk. If anyone knows a way to capture these features and convert to a web friendly format, I'm interested to hear how.

Presentation Points: I think the presentation works well overall, its shorter than the original and I avoid the natural hiccups that would occur if it had been recorded live. However, recording narration slide by slide leads to my voice changing within the talk and I still have to work on a way to sound less wooden.