Not sponsored by or affiliated with Google
Tuesday, 9th August 2005 by Alex Turnbull
This isn’t really an optical illusion, just an image mismatch on highway I-80 between Lincoln and Omaha, Nebraska, but it looks really freaky! It makes my head hurt.
Alex has decided that his title will be Senior Vice President of Stuff.
Exactly 20 years ago today, on the 11th February 1990, the anti-apartheid activist Nelson Mandela was released from a 27-year…
We’ve explored many castles in the past on Google Sightseeing – whether large, illegal or remote – but there are…
The Futuro House is a round, prefabricated house that was designed by Finnish architect Matti Suuronen in 1968. About 100…
Here in the United States somewhere (we think, we haven’t checked), we’ve found this random patch of land that we…
The continuing rollout of 45° “birds eye view” images across the globe1 has now revealed a real-life tragedy. On the…
In a country renowned for its natural beauty, one of the most spectacular landscapes is found along the Trollstigen (Troll’s…
Advertisement
It looks like the truck to the southwest of the split is going to hit the car to the northeast of the split. Look Out!!!
Here’s another example, that caused a major misalignment in Phoenix: View Placemark / Google Earth
The one above is just crazy.
On the one pooms mentioned, if you go right there are some really cool ghost planes in a major airport mismatch, and further right the mismatch makes for a very cool looking fuzzy strip through the middle of a large, full parking lot. If you go still further right, you will get to one of the original Missed Bridges.
that misalignment goes on for miles and miles. Look what I found way off to the east: View Placemark / Google Earth
Yes, and slightly to the east of that, is another case of mismatched roads: View Placemark / Google Earth I think they must have used an automatical algorithm for matching the images, and it made the two mistakes that I’ve posted, resulting in a major misalignment.
it is really freaky. google map always have the error.
Looks like this one has been fixed! (Probably quite a while ago, going by the date of the last comment)