July 24, 2008
Last week I read yet another press release describing
how a company hides all of the complexity of GIS so that non-technical
people can use it. Why, in 2008, am I still seeing releases like that?
The short answer is: The vendor in question and many others clearly see
a market. The longer answer is more complex.
I experienced the first big leaps in making GIS accessible in the late
1980s/early 1990s. Back then, I used MapInfo on DOS and despite
flipping between text and graphics screens, I recall thinking, "This is
like a spreadsheet!" I also evaluated Atlas*GIS and had the same
experience. I wrote a note to my alma mater Penn State suggesting that
every geography undergrad should be a proficient user of such a system
before they graduated, much as they were proficient users of word
processing and spreadsheet applications.
A few years later, I joined ESRI and learned just how complex a system
could be, as I attended a weeklong Introduction to ARC/INFO class. I
got my first taste of UNIX and the command line, and the power
underneath. I'd seen a command line before in Minitab and later in
AutoCAD, but the nature and number of these commands were overwhelming.
Just a few months later, ESRI released ArcView 1, which my colleague
April Nichols described at the time as doing just five things. (Can I
remember the five things? I think so: add data, zoom in/out, classify
data, do queries, print maps.) That's how she demoed it, by ticking
down those five things. Audiences at these demos went wild.
Why did they go wild? In retrospect I think it had to do with
confidence. Those at the presentations perceived that they could master
ArcView 1. Whether, in fact, they could or not was immaterial; the fact
that they felt they could was enough. Let me jump ahead. I think that's
quite a lot of the appeal of Google Maps and Virtual Earth and other
comparable offerings. Few in the multitude of users of these
applications take full advantage of all the tools, but they can muster
enough confidence to get started and perhaps more often than not, get
the task done.
Where does confidence (or lack of it) come from when it comes to
software technology? I identify two main sources: experience and
hearsay. Experience is a key guide when tackling a new piece of
software. If you've used "something like" what you are faced with, your
confidence is likely higher (assuming you had some level of success
with the previous app). The more experience with "look-alike" and even
"not-so-look-alike" apps, the more confidence you have. I, for example,
was not intimidated by MapInfo because to me it was "like" Excel. Later
in my career, I mastered Quattro Pro (remember Lotus 1-2-3? Borland's
Quattro was "4."); it, too, was "just like" Excel.
Hearsay, I'll suggest, can have an even greater impact on confidence
than experience. There's nothing more powerful than someone "smart"
stating that a piece of software is hard to use. The first instinct is
to believe it! That technique is well-used in advertising to highlight
complexity and make some offerings appear "out of reach." Apple did
that years ago, highlighting the large pile of manuals that came with a
PC versus the one thin book that came with a Mac. Apple continues to do
that with its "I'm a Mac and I'm a PC" ads today. Some suggest that
those ads have helped fuel the "Vista is junk" sentiment out in the
world today, which many say is unjustified.
My expectation is that I'll receive fewer of the "we are making GIS
simple to use" press releases in the coming years. Why? Because of
confidence and hearsay. Confidence about learning and using technology
is at a very different level in today's young graduates. They program
cell phones, select and install their own software and manage their own
laptops (and have for years!). Their confidence is likely as high as
that of computer science grads when I joined the workforce.
When it comes to GIS in particular, I'm hopeful graduates will have
been exposed to many different software packages, databases, Web tools
and the like. We are certainly working on that at Penn State, where I
now teach. My experience with software vendors in putting together my
Comparative GIS course is that they are making software available in
unique and elegant ways for both educational institutions and students.
(One example: visit students.autodesk.com.)
I'm also excited about the growing use of open source GIS in education,
which I learned about at last
year's FOSS4G event. I'm sure it'll be a hot topic this year, too.
The hearsay part is changing as well, powered by, that's right, the
Web. There are more voices than ever talking about software today. It's
possible to converse with "people just like you" about their
experiences with software (or hardware or cookware...). Instead of
trusting a single authority or the wisdom of the crowds (or
advertisers), anyone can do effective research. Further, any vendor
should be able, without hesitation, to provide a serious potential
customer with an evaluation version to explore.
The final reason I expect to see fewer of these press releases is that
more and more vendors are putting the key parts of true end-user tools
right in the box. There's no need to build a quick and dirty viewer;
now there's one in the box, or available free via a browser, or
downloadable from the Web. You may need some consulting help to fully
tweak these offerings for your needs, but it'll hopefully be a far cry
from having a company build a full system just to make GIS available to
regular people.
|
Your Comments Post a comment All comments provided in this section are those of the individual who has created the post. These are not the opinions of Directions Media, its editors, staff or owners unless otherwise noted. Directions Media retains the right to edit or delete any comments posted herein.
|
|
||||||
| Adena, this is a very interesting comment, but it is noteworthy that you didn't mentioned the concepts of usability, or usability engineering. As I have noted many time and in my paper for AGI Geocommunity '08 (http://homepages.ge.ucl.ac.uk/~mhaklay/pdf/Usability%20and%20GIS%20-%20AGI%202008%20-%20Haklay.pdf), The real problem is that GIS vendors always focused on functionality and not on the interface. They very rarely bothered to look at usability engineering literature and principle like learnability (how fast you learn a piece of software), error tolerance or memorability (can you use a piece of software after few months of not using it?). These and many other usability aspects are clearly missing from GIS products. Think about how fast you can perform a simple task such as making a map from few common data sets if you are asked to do it not in 'your GIS' - the one that you are used to. Now compare that to your experience of Excel, 1-2-3 or Quatro Pro. As I've analysed elsewhere, one of the main difference between Web mapping 1.0 (ArcIMS, MapX or any other Internet map server) and Web mapping 2.0 (GYM etc) is in usability. In my opinion, usability is the core explanation of the explosion in mapping that we've seen since 2005. Web mapping 1.0 copied the interaction metaphors directly from desktop GIS, so it is very unusable for most people. We've seen it in usability experiments - terms like 'select feature for more information' and others are very confusing for most users. Once companies with usability evaluation culture, like Google, got into the scene, you end up with Google Maps and the like. Scrutinise carefully how My Maps guides the user through the digitising process and you can see what usability means. None of the previous generation of web mapping applications provided anything like it - and they were produced by GIS vendors... In short, you can expect vendors to continue and talk about ease to use until they are blue in the face - we just don't have a culture of usability within the GIS industry! Oh, and at Penn State go over to GeoVista - they can tell you a lot about usability and geovisualization... |
||||||
|
||||||
| Muki, I am in total agreement. I was sorely disappointed when I researched usability and UI design in GIS for a lesson in my course. I'd not seen your paper, which I will likely add for next semester. I currently have students real Spolsky for the basics. http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html One question you raise, that I did not: How will the usability success of Web 2.0 mapping (Google Maps) impact GIS vendors? Are you seeing changes in usability yet? I look forward to seeing you at AGI this fall. Adena |
||||||
|
||||||
| I remember when ArcView 1 came out. Many of us ARC/INFO Unix geeks were upset. We felt that ArcView if not nullified, then at least largely eroded our value. You just mastered ArcPlot? You can throw that skill away now… To take your Excel analogy further, the original electronic spreadsheet – a number-crunching tool, has grown, evolved and mutated into a multitude of systems. Most of them are not called spreadsheets any more. They are “accounting systems” with ever-increasing levels of complexity, designed for accounting professionals, often accompanied by a steep learning curve. Ease of use of software (and other) systems has been used in advertising those systems as far back as I can remember. But what is often (if not always) omitted, or forgotten, is asking: “Easy for whom, and to what end?” Easy for the casual user, or easy for the non-GIS-professional user (planner, engineer)? Usability means different things to different people. As GIS matures, it should (and it will recognize) that fact, just as the electronic number-crunching industry did. |
||||||
|
||||||
| Companies with established market share and strong user communities rarely 'reinvent' their core functions and semantics. Changing the fundamentals is counter to the culture of the company, and upsets the mindset of the user community. Changing the status quo alters business processes, which costs extra money. And no vendor wants to add extra cost, either direct or hidden, into their core value proposition. These are why spin-off companies and disruptive market entrants gain traction...it's in their interest to upset the status quo. It takes more skill to engineer simplicity than perpetuate capability. Too bad the market tends to reward the latter over the former. |
||||||
|
||||||
| I couldn’t agree more with the comments about confidence and usability. I remember seeing ArcView at ESRI’s office in the early 90's before version 1 of the product was released. At that time, I was working for one of the world’s largest energy companies and we were struggling to create a custom, easy-to-use GIS for end users within our company. To say ArcView was a great step forward in usability is an understatement. I had the same “Eureka!” reaction when I saw Keyhole for the first time in 2004, about a year before Google acquired it. I was frustrated by the limited functionality but overwhelmed by their innovation in usability and performance. We successfully implemented an enterprise Google Earth system for a Top 4 U.S. homebuilder – a user community that did not have the patience, training, or will to learn a more complicated GIS. Web 2.0 mapping technology will definitely have an effect on GIS vendors because it is already having an effect on GIS customers/users. Across every industry, we are seeing a demand for more usable GIS in corporate and public sector environments as a direct result of consumer tools like Google Earth/Maps and others. As a GIS veteran, I am excited about the evolution of GIS tools and the opportunities it creates to expand GIS use and expertise. |
||||||
|
||||||
| One big difficulty beginners have is understanding map projections. Not having to deal with projections is one of the greatest advantages for NeoGeo mashup-makers. Google just eliminates all that for its casual users. It's a huge gap between the users who dot in their fave jogging trails and coffeehouses, and the student explorers who go on to import files that would need to be reprojected before they appear over land and not the ocean. Any software that either explains map projections in some simple way, or takes care of them without much input from a beginning user, will get a usability boost over its competition. Once we understand projections, it gets harder to remember how big a barrier it can be for others. |
||||||
|
||||||
| Even though this will drive the discussion into the proverbial Moebius cycle, I can't resist. If all (ha!) data had metadata (ha!) the tools could be written to (re)project automatically. ...or we could just assume the World is a perfect sphere and warp things to fit. Oh, wait, Google already did...never mind. |
||||||







