On Sep 17, 8:15 pm, Andrew Leach <[email protected]> wrote: > On Sep 17, 5:57 pm, Marcelo <[email protected]> wrote: > > > I just had to try my own suggestion, and it seems to work OK. > > *Your* suggestion?! :-) >
OOOPPSS!!! *LOL* Sorry Andrew. I missed that part of your post. :-) However, it is a technique I suggested to people many times before, for example: http://groups.google.com/group/google-maps-api/browse_thread/thread/0638cc6c86261373/324a3ee7587ab8b5 ;-) -- Marcelo - http://maps.forum.nu -- > Anyway, now I understand what's going on, I'd recommend not using a > geocoder at all. It was the suggestion for geocoding which was > confusing. > > I'd use a .htaccess file to redirect urls like 360cities.net/image/555- > main-street-chicago-il-usa to a script which looks up that url in a > database and determines that it needs to serve img_2365.jpg (or > whatever page you want). We go back to my first reply, which also > suggested using GDirections to snap to streets. > > The point about using geocoding to identify images (like > 54.354341_-2.235632_1.jpg) was that you could get *any* friendly url > -- not necessarily one you already knew about -- geocode its address > server-side and then fairly easily work out which image was nearest. > > 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 -~----------~----~----~----~------~----~------~--~---
