Tag with del.icio.us
News & Coverage
Sponsors

Diamond Sponsors

  • MapQuest
  • Google

Platinum Sponsor

  • ESRI

Gold Sponsor

  • Garmin

Silver Sponsors

  • 3Dconnexion
  • deCarta
  • DigitalGlobe
  • Fatdoor
  • Leica Geosystems
  • Microsoft
  • Quova, Inc.
  • Schmap
  • Skyhook Wireless
  • TeleAtlas
  • ULocate
  • University of Alaska

Map Sponsor

  • Ask

Media Partners

  • Conference Guru
  • GISuser
  • Google Earth Blog
  • Google Earth Blog
  • GPS World
  • Imaging Notes
  • LBSzone.com
  • LPS Media
  • MobileLocalSearch.net
  • MP2K Magazine
  • OSTG
  • R&D.CNews
  • SymbianOne.com
  • VerySpatial
  • Web Host Industry Review

Sponsorship

For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at

Download the Where 2.0 Sponsor/Exhibitor prospectus (PDF).

For Media Partnership opportunities, please contact Avila Reese

Where 2.0 News

To stay abreast of Conference news and to receive email notification when registration opens, please sign up here.

Where 2.0 Ideas

Send your suggestions for speakers, topics, and activities to or post them on the Wiki.

Press and Media

For media-related inquiries, contact Dawn Applegate at

User Groups

For user group related inquiries, contact Marsee Henon at

Photos from Where 2.0 2006

Session

Mapping the Maximum City

Schuyler Erle, MetaCarta

Date: Tuesday, May 29
Time: 9:15am - 9:45am
Location: Imperial Ballroom

Mumbai, India, is described in the title of a recent book as the "Maximum City." With over 14 million people, Mumbai is one of the largest and most densely populated urban areas on the planet. Over the past few years, architects, urban planners, and activists from the Collective Research Initiatives Trust (CRIT) in Mumbai have painstakingly assembled rich geographic data sets detailing information about the city down to the building level. This data has been used to devise and promote alternative development plans for housing some of the city's seven million squatters and slumdwellers. Now that the data exists and is publically available, how can CRIT ensure that it continues to be maintained and developed into the future?

Yochai Benkler has written at length about open source software development and its extension into what he calls generalized "commons-based peer-production," to distinguish collaborative projects like Wikipedia and the Linux kernel from traditional modes of strictly commerce-driven economic practice. The history of commons-based peer-production on the Internet has yielded some insight into the types of organizing structures these projects use to grow and evolve in the absence of the traditional carrot-and-stick arrangements of business and academia. Tim O'Reilly loosely terms these structures "the architecture of participation," but is the definite article he uses somewhat misleading? In looking at existing common-based production modes, we see not merely a single architecture of participation, but many different ones, composed of related practices.

As if it weren't enough to simply pose the technical challenges of mapping a city of millions with no budget to speak of, the Mumbai Free Map project also uncovers interesting questions on the collaborative development of structured data sets. How can we maximize the benefits of distributed collaboration, while mitigating the risk to quality and accuracy? How can a community composed of disparate interests not only aggregate data usefully, but also evolve information designs that best embody the data it seeks to collect? By considering the possible architectures of participation reflected in projects like Apache, Wikipedia, Advogato, and OpenStreetMap, we can begin to envision a set of "design patterns" -- a term taken from the field of architecture itself -- for implementing commons-based peer-production. As more and different efforts like OpenStreetMap and the Mumbai Free Map undertake to explore these design patterns, the origin, role, and conception of "geographic data" (as we think of it now) seems likely to undergo a radical shift.