Yes, that's how the whole maps API works - you feed addresses through the geocoder to get lat/long coordinates. But my point is that with street view there is a given image at every certain interval along a street. The SV image that's supposed to load is the one with the closest lat/long coordinates as the ones spat out by the geocoder, which converts the addresses to lat/long. My point is that if you put two different addresses in the geocoder it should be giving you different lat/longs. Well in this case it always seems to give me the same lat/long no matter what the nearby address is, or alternatively if the geocoder is giving different lat/longs then only the same SV image is loading. I should be able to call SV using an address with the geocoder, and I don't want to call it directly with lat/long because that would require me to redo a ton of PHP on my site and in addition regular users when they are putting in a property won't be using lat/long, they will be using an address so the use of the geocoder is necessary anyways.
My question still stands - why does it keep loading the same SV image with certain addresses when there are other SV images available closer nearby? On Aug 9, 10:57 am, Rossko <[email protected]> wrote: > > I completely agree with you that Streetview is not Addressview - but > > what I don't get is why in this case why it is that when I'm feeding > > streetview different addresses, such as 120 N Illinois, 114 N Illinois > > But you don't feed Streetview addresses ; you feed it lat/longs (and > an optional PoV). > Look into what lat/long you are giving it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
