Google Sightseeing takes you on tour of the world as seen from satellite, using the free Google Earth program, or Google Maps in your web browser. Each weekday your guides James and Alex present new weird and wonderful sights as suggested by readers.
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.
Thanks to Michelle, and apologies to Joe, who doesn’t like weirdness.
This form will auto-link URLs or you can use simple HTML, <a href="http://googlesightseeing.com">Like this</a>.
Link to specific places either as a Google Maps page or a decimal latitude and longitude written like this: lat/lng:55.949400,-3.200000.
If you've found an unrelated sight that you think should be posted in its own entry then use the suggestion form!
![World's Largest Saw [Updated]](http://media.googlesightseeing.com/wp-content/images/worldslargestsaw.jpg "World's Largest Saw [Updated]")
The weirdest and best of Google Earth is now available in the…
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:
Placemark: Google Maps / 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: Placemark: Google Maps / Google Earth
Yes, and slightly to the east of that, is another case of mismatched roads:
Placemark: Google Maps / 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)