sorry, I wasn't being clear about what we need. to give an example: 1) user uploads 50 images. they are already geotagged. they have filenames such as img_2365.jpg which are then used as the URL 2) we take each image and its geolocation and replace img_2365.jpg with the address corresponding to its location on the map, which comes from synchronizing the camera images with a gps track.
is that more clear? On Sep 17, 5:22 pm, Andrew Leach <[email protected]> wrote: > On Sep 17, 4:09 pm, Prague <[email protected]> wrote: > > > > > 1. can we easily pick out the street / city / country from the address > > and use only those to avoid any possible weird numbers which might be > > included there? > > Yes. Have a look > athttp://maps.google.com/maps/geo?q="555-main-street-chicago-il-usa"; > That may not answer the question, it's not exactly clear what you're > attempting to do. > > If you have only certain panoramas, you already know where they are, > so you should have server-side database which would locate the right > one based on a friendly url which you also know. There shouldn't be > any requirement to use a geocoder for this. > > > 2. on this demo > > pagehttp://gmaps-samples.googlecode.com/svn/trunk/geocoder/reverse.html > > i see that the reverse geocoding works great in the USA. but if you go > > to e.g. Prague, you get some nasty results - clicking on the streets > > gives you a nice street address but clicking (just a few pixels over) > > on a house gives you a "postal address" which is the name of the > > neighborhood + "postal number" - no street name or street number. this > > is far less ideal. I'm guessing there's no way to avoid this except by > > placing the map pin directly onto the street and avoiding houses? > > What you could do is use the GDirections service to force a location > on a street. Get directions from your click location back to itself > and use the location of the start (or end!) as the revised click > point. However, you should use the geographic coordinates to select > the panorama; you shouldn't reverse geocode to a street name in order > that you can generate a friendly URL from it. > > The methods you use should avoid the use of Google services as far as > possible, not only so that you don't deny resources to those who > genuinely need them, but also because (especially in my second > example, which uses two asynchronous calls) it's usually faster not to > use them. > > Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
