Technically, this is accomplished by displaying a KML file, generated with Google Earth, on the map. At the moment we're considering the value of adding information to the KML file - first and foremost, a line tracing the river itself seems called for. Perhaps also a polygon that describes the boundaries of the Mississippi River watershed? At what point do we consider adding other rivers/tributaries?

We've got an interesting "feature" with our KML file at the moment. Different browsers seem to display the three state-polygons and the one river-line in a different order, so each time you refresh the page, the river may flow under -or- over a polygon. While conceptually interesting, and adding a lot of fun to page refreshing, this isn't a desirable feature.

I haven't yet found a way to force the display order of KML objects on all browsers, so perhaps they'll need to go into separate files.

Things that are changing:

1. We've added two more stories! Check out the Minneapolis, St. Paul area to see them.

2. We've adjusted the introduction animation as it appeared to be causing some confusion with users.

3. We've tightened up the non-story content found in the horizontal menu.

4. We've changed the way that stories appear - they now come up as separate story windows. We're still working on their design, but think this is a big improvement that will give us a lot more flexibility in the future.

5. We've added Google Analytics so that we can see what y'all are doing and where you are going on the site.

6. We've moved the story markers on the map so that they are more accurate.

7. We redrew the polygons on the map that highlight the states that abut the river.

8. Finally, we've done quite a bit of behind-the-scenes cleanup.