Monday, March 29, 2010

GI Usability Conference Talk and Notes

Google Earth Tours: Testing spatial content
View more presentations from mukih.
Muki has posted my recent talk slides along with the other slides from the day. They're cryptic without my audio explanations so I've produced some notes for you to read as you scan through the slides.


Thursday, March 25, 2010

GI Usability Conference and the Last Half Meter

Sorry for the absence of posts, I've been too busy over the last week or so but the activities that have kept me away have generated lots of ideas for posts that I'll be getting to shortly.

What is Usability of Geographic Information?: On Tuesday I was at the second GI usability conference (programme and links). The most interesting aspect of the day was comparing my own ideas about what GI usability is against others. To me, its about how data is visualised on screen which is most of what I discuss in this blog. To others it included data structures, metadata, interoperability, topics I think are important but didn't strike me as being 'usablility' before.

The Last Half Meter: Whilst the other definitions of usability I came across are important topics IMHO there is a lack of discussion/knowledge in the area of GI visualisation. To me the situation is nicely summed up by diagrams like this one:



It's a subset of a data flow schema about how a user queries a GI dataset and it's similar to a number of other diagrams I've come across by techies about GISs. in terms of getting the system to work you can clearly see the technical links, what database talks to what etc. but what is missing IMHO is any sort of consideration about how that data is displayed on screen and how the user will interact with it, if you will, the 'last half meter' between the user and the hardware. I want to know more about what will happen in the red box, for example:
  • How many screens will they need to navigate to post a query?
  • What happens if their query doesn't produce the answer they really wanted, how will they iterate to a better query?
  • How will documentation/help/FAQs be offered to them?
All the above are key questions that affect the overall performance of a GIS/user system but they are represented in the figure by a single arrowhead delivering perfect information to the user in a kind of Vulcan mind meld interaction. I think this shows the bias of techies to want to solve the straightforward technical issues like interoperability or speed of display but don't like addressing the messy issue of how the user interacts with the GIS.

In some senses this analysis is a bit unfair, I'm drawing a big conclusion from a single diagram but my argument predicts that you should see GI projects where they author has invested a lot of time in solving technical issues but not tackled some basic rules of cartography/usability. The Hurrican Gustav project that I reviewed is a perfect example and its by no means the only one.



Friday, March 12, 2010

Google Streetview Covers All Roads in UK

Via Ed Parsons I learn that the Google streetview car has been busy covering the length and breadth of the UK:

This is the Ford in Neen Savage, Shropshire, UK. I've spent many happy hours here throwing sticks for dogs to fetch from the river.

Google seem to have done all the rural public roads in the UK including dead ends and this rather fetching view of the flow country in the North of Scotland, I would guess the least populated area of the country

Its an amazing piece of work, I'm drooling at the educational possibilities, e.g. getting students to hunt for abandoned buildings in Scotland and Hampshire then comparing the results as an exercise in rural deprivation.

Streetview in Google Earth: You can also access the same data in Google Earth and incorporate it in a tour. This KMZ example is a location we take our students to and the tour could serve as a brilliant introduction or debrief for a field visit. A shame the tour doesn't activate the detailed imagery in the Streetview bubble but hey, the students can go back and explore for themselves later.

Streetview Tour HowTo: To produce your own streetview tour in Google Earth:
  1. Turn on the Streetview layer in the Places column. Select the streetview bubble you wish to use.
  2. Right click the Bubble, copy and then past into your Places column.
  3. Record a tour as normal, by double clicking the bubble in the main screen you will be flown to the centre of it.
  4. Save the bubble and tour in a file and you're done.
Well done Google! I'm fascinated to know how many cars it took to do this, it must have been a lot of fun doing too, well, except for the Luddite mobs defending middle England.

Wednesday, March 3, 2010

Panamap and Haiti VGI

A busy week so just a couple of links of interest:

There are still a lot of reasons for paper maps and panamap just thought of another:



I've been watching the Volunteered Geographic Information that has gone on with Haiti. Good to see some promotion for Haiti Maps on the BBC.


Wednesday, February 24, 2010

Flat Earth II



A while back I discussed the advantages of a flat version of Google earth inspired by the movie clip above. You can do it via the Maps API for flash but that requires technical knowledge. A much easier way to do it is to put a world map in Google Earth as an overlay and add placemarks and loops (loops howto). I recently did this for a client, here's a stripped down version



The nice thing about it is that you could put all kinds of world maps in then narrate them with a Google Earth tour. So you could show a thematic map illustrating how much aid per country is being given to Haiti, then fly into Haiti on the Globe to see how the money was being spent.

Trick for the KML savvy: If you produced a tour that flew from a flat view like this out to country, you can edit the tour flyto so that it happens in a fraction of a second, users would then be unaware they'd flown out of a model map to get to Haiti.

Better than Screen Overlay: It makes for a better presentation than a screen overlay because you can add any sort of element above the ground overlay including loops, placemarks (as I've done here) and even other screen overlays.

Flat Map with Tours: One of the good things about this idea is that you can present a flat overview with 3D features like loops or Sketchup Models and in a tour, fly from the flat map out to the globe and zoom in on a particular country. So you could start with a thematic map showing how much individual countries were donating to Haiti then switch back out to the 'real' Google Earth and fly in on Haiti itself to see how the money was being spent.

Tip for the KML Savvy: You could even edit the flyto tag speed to be a fraction of a second, this would take the viewer from the flat map to a high view above the country without them even being aware that they've moved between transitions.

Thursday, February 18, 2010

Tuvalu Flooded in Google Earth


Tuvalu is a Pacific island famous for being vulnerable to global warming induced sea level rise. I've discovered in Google Earth, its already sunk a long way! A case of the model of the sea floor not being accurate enough in Google Earth. See more in this tour (needs GEarth v5+).

Other Sunken Islands: Previously I spotted the Scilly islands were underwater off the coast of Cornwall.

Friday, February 12, 2010

Global Warming, Snow and Ice tour


Lisa Ballagh of NSIDC wrote to point out their new 'Climate Change Tour of Cold Places', its a tour in Google Earth. She asked for feedback so I thought I would review it as a post. She also says she found my series of tour tutorials very useful, glad you liked them Lisa!

Overall Comments:
  • Good Work!: A lot of work has gone into this, overall I think its successful and informative.
  • Good Topic: Climate change of cold places is an excellent topic to tackle in a virtual globe because its very spatial (e.g. permafrost is more common closer to the poles). Also, people don't generally look at the poles on a globe so its good to get flown there to consider them.
  • Convert to YouTube: Given the amount of effort involved, I would definitely convert the tour into a YouTube clip as well. See discussion on this point.
  • Too Long: I think if NSIDC tracked how users access the tour they would find that its too long and that users were stopping part way through. 3 minutes is my guess as a good length of tour in this sort of instance, a solution is to split off the tour into separate parts as was done in the Colombia bridges tour.
  • Other Great NSIDC Content: On the same page as the tour page as the tour but lower down, the "Sea Ice: Daily Concentration and Extent" KMZ project is still one of my favourite GEarth projects.
Numbers in the next two sections refer to time in the GEarth tour itself

Pros:

  • Auto Play YouTube Clips: The use of youtube clips in the tour that automatically play (e.g. 8.47) is inspired. I'll be stealing that code and using that trick myself!
  • Good Start and End: Use of start screens, end screens, advice to turn audio on and which layers to select is well thought out.
  • Good Images: Good images have been selected for use in the tour, especially the retreat of glaciers.
  • YouTube Clips add Human touch: I think the youtube clips themselves add the human touch to the tour, making the content more accessible.
Cons:
  • (6.33) Fix Photos in Position: At 6.33 an image of Muir glacier slides across the screen showing before and after of glacial retreat. It would be better to fly into the Muir glacier and find the position from where the photo was taken and then overlay the before and after images one by one so they mimic the GEarth view. This gives users a sense of where the glacier is making it more memorable.
  • (7.12) Flight too Fast: Flights from A to B should be looped to include a high altitude view. This helps viewers work out where they've come from and where they're going. They should also be less fast than this one - most users won't follow where they are going at this speed. However, having said that, other flight segments within the tour were timed correctly.
  • (4.41) Split Attention: At this time the audio is describing something about glaciers while the placemark label asks the question, "why is Greenland called Greenland?". Users will be distracted by this, it's best not to split their attention, one way around the problem is to make the placemark only appear on screen when the audio track asks the question.
  • (4.41) Placemark vs Polygon: In discussing Greenland it should be marked as a polygon across the whole country with a camera view showing the whole country rather than the placemark shown at low altitude. A popup will work just as well from a Polygon.
  • (10.13) Timeline Labels and Annotations: To give viewers a sense of the time of events you could add labels for the times of each image. The timeline labels just aren't big enough to follow clearly. You could add annotations to show the physical scale (Rhode island outline over the ice?) and also add a polygon annotation to show the original extent of the ice shelf. The polygon island annotation should persist throughout the animation as the shelf disintegrates.
To summarise, this is a good tour with some innovations I'll be copying in the future. Although there are some cons I think they're quite minor points and don't distract from the quality of the work overall.