The paper begins with a long discussion intent on classifying the kinds of questions one can ask of spatio-temporal data. The authors point to spatio-temporal data having three major dimensions: what, where, and when, and that a classification system natural falls out from this observation. Questions about the data are usually posed about one dimension given the other two (e.g. when did x happen at y?) with answers needed at various levels of aggregation (e.g. at specific points, over a range of points, or overall; they refer to this as the "search level") and with various types of comparisons/relations done on the results (they're rather vague about this bit). At the end of their discussion the authors decide to explore only those questions that focus on the time dimension: given a time (or range) what happened where?; or when did what happen where. Here's their handy graphical representation of all of this:
The paper then turns to briefly surveying existing exploratory techniques: querying (they focus on dynamic querying and filtering), map animation, and other visualisations to explore changes in locations, events, or attributes.
With these techniques in hand the authors get to the real meat of the paper and evaluate how each technique serves to answer the two general kinds of questions. In the process of doing so they to break down the two question types into more specific questions types, detailing various search levels and cognitive operations. For instance, an elementary when -> what + where question might involve comparing behaviours over the same time interval (e.g. "compare the movements of stork X and Y") or at distinct intervals (e.g. "compare the migration behaviours of the stork X in the years 2001 and 2002"). Each of these question subtypes are explained and matched to appropriate exploratory techniques, often with references to existing implementations.
This paper is another (seemingly b/c what do I know?) decent survey of existing software and techniques. It presents a slightly more principled classification (the question types) and evaluation criteria but is fairly light-weight on the analysis (it all seems rather ad-hoc), and provides no empirical backup for many claims.
There is one thing I can take away from this paper: that visual querying is more than just a visual represention of the query question. It's also exploration. This paper implicitly assumes this with its highlighting of techniques which blur the visualisation of the query and the results, à la dynamic queries.
The other take away is dead obvious but I'll state it anyway: the type of questions you're asking tell you (or contstrain, or inform) what exploratory/query techniques to use. Creating a novel SQL query visualiser might not be what climate scientists or grade 10 students need to answer their types of questions. It's worth mentioning all of this only because it highlights an important point for me: I need to get a handle on what questions folks can't answer easily (or aren't asking, but ought to).
2 comments:
Perhaps the paper mentions this, but there are a lot of aspects to the "where" query: compute viewsheds, adjacency, overlap, other computational geometry type operations, etc..
My feeling is that there is a profound difference between exploratory (high level) browsing of a dataset, and specific queries. The climate scientist is not interested in the high level as much as "what are the results in Tasmania for my rainfall predictions".
This is my problem with the "overview first" visualization approaches: the visualization should be goal-directed, and not force the user to browse around for the answer. The trick, of course, is to write a visualizer that can be generic enough to handle a variety of queries directly, without necessarily knowing beforehand what those queries will be.
At least, these are some of the problems we ran into with Shrimp and Jambalaya (at UVic).
Thanks Neil.
The trick, of course, is to write a visualizer that can be generic enough to handle a variety of queries directly, without necessarily knowing beforehand what those queries will be.
Yeah, that's some trick, alright. For the climate scientists, I probably need to know more about what types of things they're interested in or having trouble with.
For everyone else, I have no clue where to begin.
Post a Comment