2

The Google Maps API geocodes an address to a point. I can use that point to find the nearest panorama (street view) image. I can then determine the heading based on the two points and show the panorama pointed at the right house.

The problem is that in some cases such as corner lots, the closest panorama might be on a different street. For example, a house with an address of 654 NW 4th Street is on the corner of 4th and Greenwood. The closest panorama is showing on Greenwood instead of 4th so I get a picture of the side of the house instead of the house.

Am I doing something wrong here? Is there a way to get a list of panorama's so that I can find one that is on the correct street?

It's odd because the correct panorama shows if using Google directly. E.g.:

https://maps.google.com/maps?q=654+NW+4TH+ST,+REDMOND,+OR+97756

Here is a JSFiddle demonstrating the issue.

  • Looks like this has been asked and answered before on StackOverflow: Why are some street-view images from the wrong angle? Note, however, that one commentator suggests that this problem is a recent regression. – blah238 Oct 31 '13 at 1:22
  • Thanks, unfortunately this work-around does the same thing. The DirectionsService requires a lat/long start and end and I'm passing in the geocoded address as the end. The result tells the user to drive to the side street. You can see it here http://jsfiddle.net/shadc/RsaKw/. The end point is on Greenwood, not 4th. – shad Oct 31 '13 at 17:15
  • I see. You might want to post this to the Google Maps API issues list. – blah238 Oct 31 '13 at 17:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.