GETs in Detail: Some key characteristics of a GET (and example above):
- A recording of a virtual flight around Google Earth: camera orientation, location and altitude is recorded throughout and can be replayed.
- Easy to produce simple examples (Click a record button, fly around, click stop recording).
- Layers can be turned on and off
- Pop up balloons with text, images, video clips can be triggered and closed automatically
- 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.