Here are some of the issues, ideas and observations from this year's event, prompted by just six speakers.
Mixed audience. The mix of the audience at this event always impresses me. There are academics, local and state GIS people, non-profit representatives, and staff from consulting firms large and small. Most of these people clearly like to think outside the box; I met a few programmers, but they were very low key. The discussions and the questions don't get technical. It's almost as though this event is a "holiday" or "retreat" from the details of technology; here, we take a step back to see what we do in a broader context.
Authoritative Sources. The challenge of using "authoritative" geodata along with user generated data came up several times. How will we manage them? Are both useful? Allen Carroll, chief cartographer at National Geographic, was among those who noted the issue, but he didn't seem to be concerned about his job. This conversation also prompted discussion of transparency in data sharing and use. We need to document both the sources and processes used when summary maps are developed, explained Eric Sanderson of the Mannahatta Project, a project of the Wildlife Conservation Society (more on that below). He noted in response to an attendee question that we also need to be clear on which maps are designed to reflect the current state of things, versus those that are artists' renderings or made from predictive models.
Video Games and Geotechnologies. The Mannahatta Project story mesmerized the audience. The idea? Get a sense of what Manhattan Island (Mannahatta is the name the Lenni Lenape people gave the island) looked like before Hudson appeared. With geodata in hand and a recreated landcover, the next step is to share how different this area looked in the past. We saw a short photorealistic video made by combining the 3D GIS data, with fully rendered trees, into a video game engine. Wow. I learned, however, that it was a very expensive process. Sanderson shared another innovative way to depict this historical scene using a 300-foot scale model of the island in its primitive state. You walk on a clear floor that is mapped with modern-day New York City. You look down through the floor to see what that space used to look like. A simpler, perhaps more affordable outreach option: put photorealistic graphics on bus stops that would recreate the actual view some 300 years ago. This session prompted a conversation I've had several times with GIS users, especially those involved in 3D: When will we convene an event for 3D GIS people and video game developers to try to understand and learn from one another?
Why do we all look at our house first in a mapping app? I guess I never thought much about it, but Ed Parsons noted that it's a way to build trust. If the application or website "gets it right," that builds a level of trust. With that assurance, we can go explore areas that are less familiar.
The implications of public and private organizations hosting and sharing large geodatasets. We didn't get to delve into this topic in any of the panel discussions, but it came up several times in my conversations. One issue: If the dataset is large and in high demand, it may cost quite a lot to host it and it may bring down the servers! That would prevent a local government, for example, from doing its primary work of serving its citizens. Clearly, there are many layers beyond deciding to share geodata that need to be explored. Making it findable on the Web is just the beginning.
Who knows about Fire Eagle? I think it's one of the more interesting geo technologies in some time. We covered it in a podcast when it was announced and there's been definite buzz in the developer community. Still, as I expected, few in the audience (two, to be exact) admitted to being able to explain what it does. That's too bad. I don't say that because I think geospatial professionals will necessarily use it in their development or day-to-day work, but rather because of the tactic it takes in addressing development, privacy, findability, accessibility and portability challenges in today's data sharing world. (I cover Fire Eagle and other topics in this week's podcast. It's a short summary of my presentation at the Summit.)
[Disclosure: The Summit organizers covered travel, lodging and a gift - a signed copy of Virga's book.]