« March 2006 | Main | May 2006 »

NYC Homicide Map on NYTimes.com

The latest Faneuil Media project – a map of homicides in New York City from 2003 to 2005 – launched on NYTimes.com on Thursday night. Like the last project that we did, this one was built by Brian Hamman.

Each of these projects moves us a few steps forward. I think this is one of the most useful maps we’ve built to date. Who doesn’t want to know what's been happening in their neighborhood over the past three years?

This map is also very easy to browse. Brian did a great job of laying things out, and Samantha Storey, the Times producer we worked with, gave us great feedback.

The crime map also plots more data than anything we’ve done before – or any Google map on a high-traffic site that I can find. That challenged us a bit, but it’s working well now.

As always, let us know how you think we can build on this.

Pushpins

From National Geographic's web site:

"It is as if we shipped a map to someone and they stuck pushpins in it," said Bret Taylor, product manager for Google. "We provide the map, and other people put in the pushpins."

Yeah, that is what it's like.

Marathon Map on Boston.com

Yesterday we launched a new Faneuil Media project on Boston.com. It’s a Google map that displays the route of the Boston Marathon, as well as stages of the race and communities along the way. The package is in a popup here, or you can find it on the homepage or the marathon section.

This project was built by Brian Hamman, a graduate student of journalism at the University of Missouri. He did a great job and we had a great time working with him. (I particularly like the way he wove together all info bubbles along the route – it allows you to browse through the course as a fluid story.) Maybe at some point I’ll get a chance to blog about the very cool work Brian’s doing on “Social Presence” and online news.

Let me know if you have thoughts about the project and how we can improve it. I’m at rick at faneuilmedia.com.

New Faces of the Fallen

Washingtonpost.com just launched Faces of the Fallen, another great piece of database journalism. (A few months ago they published an Alito archive and a database of congressional votes. )

The RSS is a particularly nice feature – it gives people a way to connect to the report, as opposed to coming once, and never again.

Adrian asks what he can do to improve the report. I think it’s pretty great, but I think the next step is to study YouTube – to figure out how to package and distribute the most salient pieces of the database.

It’s a micro-chunked, article-level web. My friends get their news from the clip line above their Gmail. They’re not going to spend a lot of time wandering through a database, but they should see pages like this one (things over there are only getting worse).

Serendipity & the Times Redesign

Amy Gahran argues that The Times’ redesign is too disorganized.

That doesn’t concern me. I’m not looking for organized information when I go to the Times’ home page. There’s the nav bar, search and my feed reader for that.

I go the Times homepage because I want a random, interesting read – something serendipitous. On the new homepage there’s twice as much of that.

Journalists often lament the loss of serendipity in news reports as they move online. In this otherwise excellent lecture, Guardian Editor Alan Rusbridger accepts it as a foregone conclusion.

The new Times homepage is fire hose of serendipity.  Hopefully it will put an end to those laments.

Aging Buzzwords

Powazek kicked off a good thread yesterday about the growing uselessness of the term “user generated content.”

This got me thinking about another buzzword in a similar situation: mashup.

How can somebody with a blog named Mashalist complain about the term mashup?  Well, the discussion – and my thoughts – have evolved. 

First, I have no complaints about the verb mashup. My problem is with the noun. There are too many different “mashups” out there for the word to have any specific meaning.

When sites like Housingmaps and Chicago Crime began popping up about a year ago, mashups were mostly standalone applications independently developed by the type of people who would go register them on John Musser’s fantastic site. Some of these early mashups function as tools, others are actually content. 

Things are more complex now. Yesterday we learned that Google is integrating its maps with Real Estate listings from Google Base. (Could this be the work of Mr. Housingmaps, Paul Rademacher?) 

Mike Pegg called Google Real Estate a mashup, and the tool certainly fits the Wikipedia definition. Still, Google Real Estate is very different from the original Housingmaps – or any mashup that would appear on John Musser’s site. Google controls the data and the application does not stand alone.

Other companies are testing mashups (enterprise mashups), but even in this limited corporate universe there are a lot of different experiments (Fidelity housing maps ?!?). 

At the opposite end of the institutional spectrum, some of the original independent mashups (Frappr and Wayfaring) have taken on a social angle and grown into much more than an single page dependent on outside data and applications.

It’s exciting to see mashups rooting off in so many different directions, but as the range of applications grows, it becomes harder to speak generally about mashups. 

This is particularly true for business models. Greg Linden, Peter Rip, Richard MacManus and The Times all raise good questions about the viability of mashups as businesses. At the end of the day, the answers to their questions depend on the circumstances of specific mashups.

Part of me feels a little cheap guzzling up buzzwords and spitting them out after only a few months. On the other hand, I think it’s a good sign. It means the conversation is becoming more specific and we’re forcing our language to do the same.

New Google Maps Terms

As part of the new version of their maps API released today, Google is making the following updates to their terms:

  • No page view limits. Your site can get as many page views as you can muster. If, however, your site gets more than 500,000 page views per day, we ask that you talk to us before you launch so that we can prepare in advance to handle your traffic.
  • 90-day notice before any advertising-related change. The Maps API does not include advertising. If we ever decide to change this policy, we will give all developers at least 90 days' notice via this blog.

This is good news. The old 50K page view limit wasn’t a major constraint, but it’s helpful for that to be clear. The 90-day notice is also a nice gesture. Seems they’re aware of concerns like Adrian's.

Right now the Google Maps API seems to be used mostly for widget-of-the-month-type projects. It’s been hard to develop robust applications with opaque, restrictive terms. I think Google will be much better off when it provides the clarity and flexibility that businesses need to develop on their platform. Hopefully these changes mean they agree.