Tuesday, July 13, 2010

Google Earth 5.2 Thoughts

Sorry for lack of posts last week, my family is over from New Zealand so I took some time out.

GE 5.2 has already been reviewed well by Mickey and Stephan, I share their enthusiasm for the tracks, elevantion and slide in browser functionality. I've noticed some other features in the 5.2 Pro version (not sure if they're in the normal version) that IMHO deserve comment:

Table: (Tools > Table) This gives you a table view of the KML that you've selected in the places column so you can see the text in the description boxes of a number of placemarks at once, its similar in functionality to Northgates KML editor. Table isn't documented anywhere I can find and I was disappointed to find its read only, it really would be useful if you could use it to write to KML directly as per GIS tools and the Northgates tool.

GE gives you the ability to produce KML within the editor already but I'd love to see functionality where I could put time tags into KML without having to copy raw KML out to a text file.

Regionate: This is documented to a degree but it didn't tell me exactly what this functionaility does, e.g. it doesn't chop up paths into smaller segments. Maybe it only deals with placemarks?

I was also excited to see a contextual help button in the dialogue box. Contextual help in GE is something I've advocated before so I was disappointed to find its only in the Regionate and flight simulator dialogue box (given a cursory hunt around). Why not link to help files from all dialogue boxes?

Slide in Browser: Stephan makes a nice point about the slide in browser, I agree with him that maintaining the option of the split screen would be good. However, I think that the sliding browser screen would be excellent for using GE in presentations, set up a tour, fly into an area in GE then pan across a presentation slide in a browser from the web, use that to support your talk for a while then return to GE to continue the tour. I think Google should think about linking the Google Docs presentation tool with Google Earth in this way, I played around with the idea but currently:
  • It takes 2 clicks to open a presentation (open balloon, select link)
  • Opening a GDocs presentation in the GE browser currently crashes GE pro!
Polygons and Ruler: I was pleased to see that the polygon bug has been fixed, that was a real pain. Being able to save paths produced with the ruler tool is also smart.

Friday, July 2, 2010

Climate Change Talks

Previously I've enjoyed releasing something good on GoogleEarthDesign's birthday (It was 3 this week) so here's my latest big idea:

Climate Change Talks: A quick search of the internets revealed no one has done a set of video clips on climate change for education (apart from illegal snippets of 'an inconvenient truth') so I decided to do some. Some of the later ones are matched to the UK A level Edexcel curriculum. Here's the first one on the topic 'Is the Earth a Super Organism'.



It's better viewed in HD

Format: Climate change as a topic requires discussing abstract ideas such as positive and negative feedback as well as map based graphics so I went for Prezi.com as an alternative to PowerPoint and added clips of GEarth tours where useful. When a lot of your presentation isn't actually spatial its better not to base your content totally in a GEarth tour as it presents difficulties. E.g. importing, sizing and adding labels to an image in Prezi is a snap with lots of drag and drop controls whereas its a pain to do as an image overlay in GEarth.

Having said that, some of the other clips I have planned which are completely spatial in nature will be done just as GEarth tours and recorded as YouTube clips.

Here is the original prezi page:
(navigate by using the plus minus buttons that will slide out if you mouse over the right hand side or use mouse wheel and click and drag)




It's rather like viewing a GEarth file after watching a tour of the content. In the bottom left corner of each frame it has links to related topics that don't feature in the talk.

Death to PowerPoint: Lots of people have criticised PowerPoint for its slide analogy format, I think you can still do some useful stuff with it but I see their point. The nice thing about Prezi is that I can produce a mind map like poster and then take you around with added audio by recording it with demo software (I use Camtasia 7).

Pros:
  • I like the zoomable interface idea Prezi shares with GEarth tours
  • Prezi is very usable and Camtasia is not bad
  • Doing it this way I like the way I can be discussing one set of points but adding arrows to link back to earlier slides of content.
Cons:
  • Using 3 bits of software is a drag (GEarth, Prezi and Camtasia 7) and is time consuming
  • I don't like the way Prezi.com promotes the idea of rotating text all over the place, I've heard reports it makes people feel sick.

Video Clips in Education: I had a long think about how to present this content and I thought it worth listing my inspirations:
  • Hans Rosling: Excellent speaker with great use of technology
  • Lawrence Lessig: Great speaker, interesting and unique style but I'm not sure I like how linear it is.
  • Ken Robinson: Amazing, totally absorbing using just his voice. Good to remember that technology is not what makes a great talk, its the talk itself and the speaker.
Very interested to hear what people think.

Thursday, June 24, 2010

on Blogging and Tweeting

This blog is coming up to 3 years old so I'm trying to make time to do some reflecting on the work to date. Today I thought I'd talk about why I'm still doing this after 3 years:

Lost Decade of GeoWeb Usability: A while back I compared the progress of GeoWeb usability with the history of web usability. Jakob Nielsen described the first ten years of the web as the lost decade where web design was awful and no one seemed to care. Whilst there are encouraging signs of an understanding of what makes great GeoWeb content (Axis Maps, Stamen Design, New York Times: example ) there is much more out there that is badly thought out IMHO. So I'm still here advocating good GeoWeb design.

Blog as Outward Facing Notebook: When I first started this blog I had grand ideas of getting lots of useful feedback based on the long lists of comments I was seeing on some other blogs. I don't get as much feedback as I expected and I now realise that its a power law relationship - a few blogs get the majority of the attention with lots of comments whilst the rump of bloggers get a loyal core following but less feedback.

However, this hasn't put me off the process, I actually blog because its a great way of forcing myself to keep decent notes on all kinds of map related stuff. The fact that I can turn it outwards and share these ideas with a larger community has some benefits but is mostly just a bonus, its use for me is mostly as a personal index which I search for something most days I'm online. I recently found I share this view of blogging with John Naughton, one of my favourite web/internet gurus.

Tweeting: As for tweeting, my motivation is much the same. I treat it as a micro-blog where I post all the links I may find useful in the future but don't have time to write up properly as a blog post.

Hits: The final bonus of blog keeping is seeing the hits, I've found it fascinating what people are interested in on my blog.

Wednesday, June 16, 2010

Blog New Look!

The blog has a new look from today, hope you like it!

Wednesday, June 9, 2010

Cloud GIS: Indiemapper review



Update 12/6: I spelt Indiemapper wrongly as Indemapper which I've now corrected. Thanks for the heads up Maarten.

Introduction: Indiemapper is an online GIS from Axis maps, it compares with services like GeoCommons (my GeoCommons review) and the newly released ArcGIS Explorer online (James Fee's review).

I was really excited to dive in and experiment with it as it promised to enable good map design practices. Sure, you can still make ugly maps with it if you try hard but the defaults will nudge (in the sense of this nudge book) you to make good design decisions and contextual help is there to inform you of good design practice. No one will be surprised to hear I think this idea is a Very. Good. Thing.

I discussed Indemapper with Mark Harrower on a conference call before writing this review.

Pros:
  • Good Map Design as Default: By integrating colorbrewer and typebrewer into the package and providing design advice in contextual help they've produced an app that promotes good design. Yay!
  • Cloud Based: This is aimed at people who don't need the full power of desktop GIS and its a cloud based service so you can access you work from any computer.
  • Group Working: Is also possible and I can see lots of potential for this.
  • Contextual help: As well as supporting good design, contextual help is a real usability plus - instead of having to waste time finding the help section that deals with your particular problem, a contextual help button takes you straight to what you need.
  • Integration with PhotoShop: Axis maps have made a point of making it easy to export from Indemapper into other software such as photoshop.
Sort of Neutral:
  • Projections: Indemapper is promoted as being good at handling projections. I can see where Axis is coming from about this but I don't think projections are as important as they make out.
Cons:
  • No User Manual (yet): Mark explained to me that one of the audiences they had in mind for Indiemapper was for people not expert in GIS who don't need full GIS functionality. For those people the GIS like interface is intimidating, they really need a set of step by step tutorials on howto make a map with Indiemapper. Contextual help just doesn't fill the need properly. Mark said they had a series of video tutorials planned covering this.
  • Free for Educational Users: All Unis I know will have GIS teaching materials authored for Arc. IMHO to persuade a tutor to switch to Indiemapper for teaching the educational licence cost has to be zero and at the moment, its just a reduction. Both ArcGIS Explorer online and GeoCommons are both free.
  • Desert Fog on Startup: When first opened Indiemapper has a blank screen. For users who have been making maps in NeoGeo tools like Google Earth or Google Maps, they will be confused and a little intimidated that there isn't a base layer visible. Better to have a default layer visible that users can change than a blank, desert fog screen.
  • Static Maps only: Indiemapper isn't designed to produce interactive maps. Mark said this was something they would consider in the future. I agree with him that there's a ton of applications for static maps but I'd like to see some simple interactions possible - clickable pop up balloons with simple html would do.
  • GIS Metaphor: Indiemapper works on a GIS metaphor in that a database is linked to a map. If you open a few layers and click on a point you will pull up the normal GIS attribute table. This is second nature to anyone who's worked GIS but newbie map makers will be confused, attribute tables and how it links to a map are quite a complex concept to understand and manipulate. Mark explained to me that the design team spent time discussing if there was a better way to organise a map than layers. I agree with their decision to use layers as the way to organise the map, I can't see a way around that, but I think they could have adopted an interface where data is still arranged in layers but the underlying data structure (XML as it happens) is hidden from the users view by simple screen interactions. Google Earth operates in this way, you don't get to see the KML with simple main screen operations.
Unlike my other criticisms, altering the GIS metaphor is probably a big structural change, so I doubt its worth implementing. That's OK so long as they make sure the issue is well covered in the video tutorials.

When Indiemapper is supported by video tutorials and able to produce simple interactions it's a tool I'd definitely consider for my teaching and for producing my own maps.

Wednesday, June 2, 2010

Google Earth Tours in Geog. Teaching III

This is a 3rd of a 3 part series. Part 1 was introduction and started the 'rules of flight'. Part 2 finished off the rules of flight. This post covers audio, annotations, testing, use of layers and a literature review that covers all three posts.

3. Audio:
Research shows that an audio commentary is much easier to understand than a narrative delivered via on screen text. Labels identifying major sections of the animation also add value. However, adding background music has been shown to be valueless - it's just a distraction in an educational situation.

Audio and visual elements should match in a GET because you shouldn't make users interpret two different presentations at the same time. A critique of a GET which did not follow this advice can be found in an earlier blog post of mine under the heading; "Talk about what's on Screen"

Audio Practicalities: I describe how to produce an audio GET in this tutorial

4. Annotations:
If the GET audio track has a descriptive line like 'and here you can see the extent of the Scottish Highlands' use an on screen marker such as a polygon to draw the viewers eye to the location concerned. Annotations like this should be used throughout tours, its easy to learn about a study area by doing a tour and forget that your users haven't formed a cognitive map. Annotating what you're discussing is a solution to this.

5. Testing:
Despite the best intentions, and having created a GET that you think looks and sounds excellent, often users miss elements that you thought you had made obvious or they misinterpret the message of the tour in ways that the author had not considered. The only solution is to test 2 or 3 typical users before releasing your GET, fortunately, this is much quicker, simpler and cheaper than you would imagine following Hallway testing guidelines.

6. Use of Layers:
A layer refers to a set of data, examples include: a thematic map showing voting by region in an election or a set of placemarks showing locations of pizza restaurants. If you wish to explain a complex map which is made up of a combination of layers e.g. showing that right wing voter States in the USA have more pizza restaurants in them, you will need to use multiple layers. It helps your users if you turn the layers on one by one in your tour explaining what the screen is showing as you go. Showing them all the layers at once and trying to explain what they are seeing is less clear.

Sometimes layers are complex enough to require annotations themselves (e.g. circling an area of particularly dense concentration of pizza restaurants)

Layers Practicalities: In running through a tour to record an audio it can often help to collect separate layers into a folder. When running through the tour you can then select a camera view for the folder and turn all the elements in it on and off at the same time. For example, you could put the pizza restaurants layer and a polygon annotation mentioned above in one folder.

Literature Review: In writing this series I did a literature review which the academics amongst you may find useful. I've expanded it since writing this.




Friday, May 21, 2010

Google Map Styles

I've been keeping tabs on the Google I/O conference via twitter and the blogosphere. I'm very pleased to see that they've announced that in the latest Google Maps API v3 you can apply styles to Google Maps. Here's an example produced by Programmable Web a developer outside of Google:


This is a move I suspect is driven by Cloudmade, a competitor using OSM (Open Street Map) data. They've introduced the ability to style maps already, here's a nice muted example (Pale Dawn) that would work well if your background map was adding too much visual clutter:

So competition from Cloudmade has driven the development of features that help in the design of maps. Good. But I have a grumble:

No Usability Advice: The post discusses how you can now match the map color scheme with the surrounding web page and make your map 'stand out from the crowd'. Whilst web page styling is important the post doesn't discuss anything about how use color to improve map usability: having a common theme between web page and map isn't much use if it makes your map impossible to use.

Red Fail: The post illustrates the new functionality with an example which misuses color:


amongst several criticisms I could level at it the clear fail is that the sea is the same color as Yosemite National park making it look like California is a peninsular.

To Be Fair: A 'hello world' example illustrating new functionality isn't meant to be polished but the implication I read into the post is that map usability doesn't matter whilst standing out from the crowd does.