> ... But my point is that with > street view there is a given image at every certain interval along a > street.
Sort-of. Let's say there's a Panorama at some interval (don't know what, it might vary). If you gave Streetview a lat/long corresponding closely to the 'centre' of some Panorama, what would you expect to see? It's open to argument really. A view of the target point from the next Panorama along, perhaps? Which one though? Or were you expecting to see in some random direction from the target point itself? I don't know which way it works, but I'd guess its rather more like the first ... Streetview assumes you want to see what's actually at the point you supplied, and gives you its best guess of a Panorama that includes it. In the absence of any other information though, you might well not be looking at the part of the Panorama that actually includes the point! It's up to you to arrange the view, for which you really need two points - the root of the Panorama (which you don't know until you get it) and the target point, so you can work out the direction. > 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, That's what I'm disputing. You also need to bear in mind the geocoder may point at the middle of the street, or to some vague kerbside area, not the middle of the property. Thinks; if it did point at the middle of the property, would that always give you the view of the frontage that you wanted? Even if it did behave the way you're describing, a single Panorama would of course cover several properties, but need the view aligning differently. As we said before, the maps.google.com geocoder is different. Furthermore I'm sure Google are smart enough to write their own application to do the clever stuff to align the Panorama view to a better view of the target than the default. In the API, you have to do your own clever stuff. Hence why I said Streetview not Addressview. > 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. Find out. Does the geocoder really return different lat/longs in your case? It certainly doesn't in many cases, its a more-or-less sophisticated guess. If they're different, are they at all accurate, or just extrapolations? There's a few vagaries going on here, why not pin down which one is giving you trouble. > 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 You should log an enhancement request then. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
