You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But if you click on that link, you get the following with a message "No street view imagery available here":
From looking at the image and street intersections, I was able to derive the actual location, which is (Google Maps Link):
Any ideas why this might have happened @misaugstad? Is this just a one-off problem or did GSV maybe change their API a bit? Or why can't we access the exact pano? It seems like it does indeed exist here.
The text was updated successfully, but these errors were encountered:
Oh that's really weird, I'm not sure what's going on! I just tried this out and managed to reproduce a few times. At least with the ones that I was able to do, the images were at approximately the same location, just from a different period in time. Though from your example it looks like it might be a totally different location.
It works when setting the pano parameter to the pano id instead of specifying the viewpoint coordinate ... Are there any downsides of switching to pano instead of viewpoint? (If not, I can make a PR with the fix)
No idea why we wouldn't have been using the pano ID already, so we would definitely welcome a PR!
I love the "View in Street View" option that we have; however, I ran into a problem with it this morning.
In Gallery, I was viewing this image:
Then I clicked on "View in Street View"
But if you click on that link, you get the following with a message "No street view imagery available here":
From looking at the image and street intersections, I was able to derive the actual location, which is (Google Maps Link):
Any ideas why this might have happened @misaugstad? Is this just a one-off problem or did GSV maybe change their API a bit? Or why can't we access the exact pano? It seems like it does indeed exist here.
The text was updated successfully, but these errors were encountered: