« Disasters & Google | Home | Hazards of Web 2.0 »
I35W Bridge Updated in Google Maps
By Julie | August 7, 2007
Google Maps has already updated its directional capabilities to not use the I35-W bridge over the Mississippi River in Minneapolis.
Doubt they’ll keep up with all the surrounding road closures, given how day to day they are, but it shows a few things:
- Google learned from the outcry that occurred when the pre-Katrina satellite images stayed on Google Maps/Google Earth long past the destruction of the levees.
- There are clearly some mechanisms on the back end that can leave the appearance of a road in the map, but have it on a perpetual exclude.
Now, yes, you can still see a yellow interstate line where the bridge should be, and still is — albeit in the river, and not especially traversable. But if you try to set up a journey that would typically route you via that bridge, Google is automatically routing you via one of the currently preferred alternate routes. For instance, just route between Rosedale Center (10 Rosedale Center, 55113) and the Metrodome (900 S 5th Street, 55415). Google chooses a routing that has you exit from MN36 to Highway 280. If you attempt to drag the map line to take 35W, it will force you to exit at Stinson. It will NOT allow you to take the bridge.
Total distance, per Google’s preferred route: 8.4 miles.
I35W would normally be the preferred route. Note that MSN Maps still routes via the bridge, giving you a trip of 6.5 miles:
Given that some of the exits that Google will allow you to route via only re-opened Monday, this is fairly quick updating of the service. Certainly, this update is faster than the commute many Twin Cities residents will be experiencing for the next 12-36 months as the bridge saga continues!
I also note that Yahoo Maps and MapQuest, both of which are powered by Navteq/Teleatlas, also now realize that the bridge is a bad routing. Looks like MSN is late to the party… again.
Topics: MSN, google, local search, minneapolis, search engine features, yahoo |
