A brief note. I’ve recently joined the UC Berkeley School of Information and now run the Information and Service Design Program (warning: web-site is a draft!). It is an exciting place and tremendously challenging, but offers some wonderful opportunities to learn much and expand efforts toward better data sharing and communication in archaeology. I’ll be blogging more as I learn more about good “service” design and technologies and organizational.
I also recently wrote a short article for iCommons, an international access to knowledge organization affiliated with Creative Commons. The article is about traditional knowledge and the Access to Knowledge movement. It looks at the clash of viewpoints between some indigenous peoples intellectual property rights advocates and advocates of the Digital Commons. But it also looks at how these interests can find some common ground on issues of education, development, and activism, especially when it comes to free and open source software and community building tools.
Now that I have all these new “I” organizations in my life (I School, iCommons), I feel that maybe it’s time for an iPhone, to start exploring mobile and location based services (see discussion by my colleague, Erik Wilde) and to put another “I” in my life. Unfortunately the iPhone comes with i-crappy contract restrictions and costs lots of i-money.
So, I’m looking eagerly forward to this new gizmo, Open Moko, as a very capable alternative. It’s a wholly open mobile communications platform. Seems like it could be incredibly useful for archaeologists in the field, sending up observations in real time.
If you are developing or using web-based tools or resources for communicating archaeology, or if you have ideas or opinions about this subject, please consider being a presenter or discussant in a “Web 2.0″ session at the next SAA meeting in Vancouver (March 26-30, 2008). Please review the abstract below and contact Sarah Kansa (firstname.lastname@example.org) if you are interested in participating. This session is co-organized by Sarah Kansa (The Alexandria Archive Institute) and Julian Richards (Archaeology Data Service & Univ. of York). The Alexandria Archive Institute is sponsoring the session by covering the cost of registration fees for presenters.
Session Title: Web 2.0 and Beyond: New Tools for Collaboration and Communication
Abstract: New technologies are transforming the way archaeologists communicate and explore the past. Many archaeologists have embraced Web 2.0 collaborative tools and services such as blogs, wikis and Flickr. Some are experimenting with web services to find ways to integrate different bodies of content, interfaces and tools. These new tools for collaboration and communication present opportunities for research and public participation in archaeology. This session aims to:
- Highlight current archaeological efforts implementing Web 2.0 technologies
- Discuss why certain approaches seem to “work” best for communicating archaeology
- Discuss the challenges of networking archaeological information (semantic, intellectual property, technical capacity, and social) and ways we can look beyond Web 2.0 in our discipline.
Reading the recent posts by Fennelle Miller and Kevin Schwarz got me to look into the spatial data a bit more closely. One of the issues that seems to crop up again and again is cost and complexity.
GIS data is still difficult to share dynamically over the Web, but things are changing. GoogleEarth, Google Maps, Open Layers, etc. provide great tools on the client side for viewing and interacting with spatial data (not just points too, but also vector lines and polygons). GoogleEarth and Google Maps are proprietary, but they are available as free downloads or free APIs. They also work with an XML format (KML) that is pretty simple, enjoys a wide user-community and can work with non-Google developed tools.
There are some tools for transforming the ubiquitous ESRI shape files into KML documents (the XML format used by Google’s applications for spatial data)(See this blog post at PerryGeo, see also the post’s comments). Here’s a link to some “how to” discussions on using PHP to read MapInfo (.mif) files to use with Google Maps. Here’s a link to an open source PHP class that reads ESRI shape files, the first step needed in converting them on a server to KML or other formats. The point of all this is that, with some development work, we can transform (to some degree at least) typical GIS data into formats work better on the Web.
Of course, GML (the community developed open standard) is a better choice for GIS data than KML. KML is needed for Google’s great and easy to use visualization tools, but GML is a much more robust standard for GIS data. GML also has the advantage of being an open, non-proprietary XML format. You’re not locked into any one software vendor and you have important data longevity advantages with GML. It should be noted that Open Layers (the open source equivalent of Google Maps) supports GML.
However, I’m not sure of the immediate need to go through all this effort. Sure it’s nice to have GIS data easily viewable on a web-browser or slick visualization tool like GoogleEarth. But the fundamentals of data access, longevity and discovery need to be in place first before we put lots of effort into online visualization.
Instead, we should look at some strategies to make our GIS data easier to find and maintain. And we need to approach the issue pragmatically, since overly complex or elaborate requirements will mean little community uptake. Perhaps we can look at ways of registering GIS datasets (ideally stored in GML) in online directories with some simple metadata (“information about information”). A dataset’s general location (say Lat / Lon point coordinates), some information about authorship, keywords, etc. and a stable link to download the full GIS dataset would be an excellent and simple start. Simple point data describing the general location of a project dataset will be enough to develop an easy map interface for users to find information about locations.
Such directories can be maintained by multiple organizations, and they can share/syndicate their content with tools such as GeoRSS feeds (RSS with geographic point data). It’s easy to develop aggregation services from such feed. You can also use something like Yahoo Pipes to process these feeds into KML formats for use in GoogleEarth! (We do that with Open Context, though it still needs some trouble shooting).
Also, Sean Gilles (with the Ancient World Mapping Center) is doing some fantastic work on “Mush” his project for processing of GeoRSS feeds. See this post and this post for details and exanples. Thus, simple tools like GeoRSS feeds we can contribute toward a low-cost distributed system that makes archaeological datasets much easier to find and discoverable with map-based interfaces and some types of spatial querying (such as buffers). This may be a good way to address some of Fennell Miller’s concerns about recovering and reusing all that hard-won geospatial data.
Of course, site security is an important issue, and finding ways of making our data as accessible as possible without endangering sites or sacred locations is important. I’m glad Kevin Schwarz raised the issue, and it’ll be very useful to learn more about how he and his colleagues are dealing with it.