Crazy things you've found in Google StreetView

[empirestate]

- Tossed cars

And a woman talking agitatedly on the phone, no doubt to her insurance company.

[kkt]

It's not Streetview, but there's this:

Story about it:

https://www.airforcetimes.com/news/your-air-force/2021/09/17/b-2-bomber-crashes-in-missouri-after-in-flight-malfunction-none-injured/

[snowc]

It's not Streetview, but there's this:

Story about it:

https://www.airforcetimes.com/news/your-air-force/2021/09/17/b-2-bomber-crashes-in-missouri-after-in-flight-malfunction-none-injured/

I wonder if you can view its flight via Flightaware.

[KCRoadFan]

This doesn't refer to the imagery itself, but rather to the overall Street View interface. Anyway, there's a box at the top left that normally shows the street name and address closest to where the picture is, along with the city and state it's in. One thing I've noticed lately is that in some locations, this info is missing from the Street View interface - rather, it's just the word "Google". Has anyone else seen this?

By the way, I've reported the problem on Google Issue Tracker, but so far, no one has responded. What, if anything, can or should I do about this? As someone who loves to look around on Street View, this really bothers me. When might it be fixed?

[kphoger]

Has anyone else seen this?

Yes.  See here.

[hotdogPi]

Photosphere inside TD Garden. No, not the floating person. Look at the clocks. How much time is left in the period? Two different times are visible at that FOV, but pan around and you'll see at least five, all different. (And no, I'm not confusing the time of day with the game timer. I can tell the difference.)
https://goo.gl/maps/5W7n5XDYESMZNUWdA

[jakeroot]

Photosphere inside TD Garden. No, not the floating person. Look at the clocks. How much time is left in the period? Two different times are visible at that FOV, but pan around and you'll see at least five, all different. (And no, I'm not confusing the time of day with the game timer. I can tell the difference.)
https://goo.gl/maps/5W7n5XDYESMZNUWdA

The rink is like a game of Where's Waldo.

[Scott5114]

Photosphere inside TD Garden. No, not the floating person. Look at the clocks. How much time is left in the period? Two different times are visible at that FOV, but pan around and you'll see at least five, all different. (And no, I'm not confusing the time of day with the game timer. I can tell the difference.)
https://goo.gl/maps/5W7n5XDYESMZNUWdA

This, of course, is just an artifact of how the photosphere is constructed–it's just a bunch of photos taken from a single point with a normal camera, oriented in such a way that a full 360° view of the place is captured. Then all of the photos are edited together to form a single, somewhat seamless image. Since a normal camera cannot take multiple pictures at the same time, all of the pictures are taken one after the other. Normally, this is not readily apparent, but since there was a timer prominently displayed in multiple areas within view of each other, it became obvious that the photos were captured some time apart.

(This sort of thing would be less obvious with a true Google Street View camera, which has multiple lenses pointing in multiple directions so all of the imagery needed can be captured simultaneously. Photospheres usually do not use such a camera.)

By the way, I've reported the problem on Google Issue Tracker, but so far, no one has responded. What, if anything, can or should I do about this?

Buy Google stock so that your opinion is legally required to matter to them.

As someone who loves to look around on Street View, this really bothers me. When might it be fixed?

Whenever Google feels like spending the money to fix it.

[ErmineNotyours]

Come to the light!  Come to the light!

[roadman65]

Photosphere inside TD Garden. No, not the floating person. Look at the clocks. How much time is left in the period? Two different times are visible at that FOV, but pan around and you'll see at least five, all different. (And no, I'm not confusing the time of day with the game timer. I can tell the difference.)
https://goo.gl/maps/5W7n5XDYESMZNUWdA

This, of course, is just an artifact of how the photosphere is constructed–it's just a bunch of photos taken from a single point with a normal camera, oriented in such a way that a full 360° view of the place is captured. Then all of the photos are edited together to form a single, somewhat seamless image. Since a normal camera cannot take multiple pictures at the same time, all of the pictures are taken one after the other. Normally, this is not readily apparent, but since there was a timer prominently displayed in multiple areas within view of each other, it became obvious that the photos were captured some time apart.

(This sort of thing would be less obvious with a true Google Street View camera, which has multiple lenses pointing in multiple directions so all of the imagery needed can be captured simultaneously. Photospheres usually do not use such a camera.)

By the way, I've reported the problem on Google Issue Tracker, but so far, no one has responded. What, if anything, can or should I do about this?

Buy Google stock so that your opinion is legally required to matter to them.

As someone who loves to look around on Street View, this really bothers me. When might it be fixed?

Whenever  :sombrero:Google feels
like spending the money to fix it.

I bet if they tried to capture it on purpose, it would never come like this as Hollywood spends thousands to achieve such an effect.

[ethanhopkin14]

Not the craziest or even that unusual, just I personally never happen to catch passing trains when looking at street view. 

[roadman65]

https://goo.gl/maps/WNGEZWGCyxab9Amx6
Green Mountains along US 93 near Hoover Dam.

[KCRoadFan]

Photosphere inside TD Garden. No, not the floating person. Look at the clocks. How much time is left in the period? Two different times are visible at that FOV, but pan around and you'll see at least five, all different. (And no, I'm not confusing the time of day with the game timer. I can tell the difference.)
https://goo.gl/maps/5W7n5XDYESMZNUWdA

This, of course, is just an artifact of how the photosphere is constructed–it's just a bunch of photos taken from a single point with a normal camera, oriented in such a way that a full 360° view of the place is captured. Then all of the photos are edited together to form a single, somewhat seamless image. Since a normal camera cannot take multiple pictures at the same time, all of the pictures are taken one after the other. Normally, this is not readily apparent, but since there was a timer prominently displayed in multiple areas within view of each other, it became obvious that the photos were captured some time apart.

(This sort of thing would be less obvious with a true Google Street View camera, which has multiple lenses pointing in multiple directions so all of the imagery needed can be captured simultaneously. Photospheres usually do not use such a camera.)

By the way, I've reported the problem on Google Issue Tracker, but so far, no one has responded. What, if anything, can or should I do about this?

Buy Google stock so that your opinion is legally required to matter to them.

As someone who loves to look around on Street View, this really bothers me. When might it be fixed?

Whenever Google feels like spending the money to fix it.

I checked in the affected areas. It has been fixed!

[webny99]

Here's one of the most incredible stitching errors I've ever seen: https://goo.gl/maps/Lji4B5uJ9jUdht2K8

I did a double and triple take before fully comprehending the error. Look at how realistic the duplicate CT 165 shield is, and note the "ghost" of the CT 138 shield just above it.

[7/8]

Here's one of the most incredible stitching errors I've ever seen: https://goo.gl/maps/Lji4B5uJ9jUdht2K8

I did a double and triple take before fully comprehending the error. Look at how realistic the duplicate CT 165 shield is, and note the "ghost" of the CT 138 shield just above it.

Yeah that is very seamless (especially since the trees above look fine).



Looking for a ride in the Google Car in Western Australia.

[ErmineNotyours]

Here's one of the most incredible stitching errors I've ever seen: https://goo.gl/maps/Lji4B5uJ9jUdht2K8

I did a double and triple take before fully comprehending the error. Look at how realistic the duplicate CT 165 shield is, and note the "ghost" of the CT 138 shield just above it.

Go back to the October 2018 image to see what should be pictured.  July 2019 made a similar error.

[7/8]

Hedge cut out for this street sign in Richmond, BC.

[empirestate]

Hedge cut out for this street sign in Richmond, BC.

These people have moats...

[ErmineNotyours]

Hedge cut out for this street sign in Richmond, BC.

Renton says hi.

[kirbykart]

https://www.google.com/maps/@42.590775,-72.30965,3a,90.0y,204.83508h,21.548775t/data=!3m4!1e1!3m2!1sRVpSMPDDn86YzBvUAggw0A!2e0
Found on MA 2A at MA 122 in Orange.

[Joseph R P]

Stumbled across this workers strike at a Mondelez factory once: https://www.google.com/maps/@37.4932146,-77.3529989,3a,90y,276.11h,75.05t/data=!3m7!1e1!3m5!1shQtJC5Cc3AoaoW4UZXL_Qw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DhQtJC5Cc3AoaoW4UZXL_Qw%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D35.157692%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192

[PurdueBill]

https://www.google.com/maps/@42.590775,-72.30965,3a,90.0y,204.83508h,21.548775t/data=!3m4!1e1!3m2!1sRVpSMPDDn86YzBvUAggw0A!2e0
Found on MA 2A at MA 122 in Orange.

I appreciate the number of 12-8-8s that have been allowed to remain at that intersection and the overhead street name blades for the nexus of the universe (North, South, East, and West Main Streets all intersecting).

It's not Streetview, but there's this:

Story about it:

https://www.airforcetimes.com/news/your-air-force/2021/09/17/b-2-bomber-crashes-in-missouri-after-in-flight-malfunction-none-injured/

I wonder if you can view its flight via Flightaware.

Reminds me of the tractor-trailer rollover on the ramp from US 1 to I-95 NB in Peabody, Mass that the overhead view managed to catch.  (This was the August 2019 rollover; there have been plenty there.)
https://goo.gl/maps/Ggd4PiKt8UyanPEK9

There are tons of weird stitching errors though not as amazing as the Connecticut signs one above; I only happened to notice this one once at first thanks to what appeared to be odd guardrail post spacing.
https://goo.gl/maps/oD1nGTEeWAypmnZr9

[Revive 755]

Future truss span on the Mississippi River for the Merchants Bridge overhaul in St. Louis

[CoreySamson]

Legendary.
https://goo.gl/maps/H7eeZUuyTpmJLWih7

It is Mexico, though. You can't blame them for trying.

[7/8]

Legendary.
https://goo.gl/maps/H7eeZUuyTpmJLWih7

It is Mexico, though. You can't blame them for trying.

I find it funny that there are three barbers side-by-side.