Thanks for the replies. Yes , i do agree that if i want to know the toll information, i should go for directions. But based on the reverse geocoding result, i am running a report where for each point , i am showing whether its on toll road or not. For now, I am using Google's reverse geo-coding as a separate stand along appl. for getting address of lat/long.
Anyways thanks for your responses. It seems that I am asking for too much . On Jan 27, 11:39 am, "warden [Andrew Leach - Maps API Guru]" <[email protected]> wrote: > On Jan 27, 11:26 am, shah <[email protected]> wrote: > > > Thanx andrew. yes, i know that the direction details are included in > > the direction details but was wondering that why does the same toll > > information not available in the reverese geocoding response. > > Why should it be? Reverse geocoding simply gives an address for a set > of coordinates. No more, no less (provided it's worked!) > > > The > > problem is I have to plot markers on map and indicate whether the > > marker is on toll road or not but before that I have to perform > > reverse geocoding for getting the string address of the lat/long that > > i have. And i have no idea about whether the lat/long are on the toll > > road or not. > > Tolls are only relevant to directions, they're not relevant to points. > You're saying you need to know about tolls presumably because you need > to know whether you will encounter a toll getting to or from your > location. That's a directions function, not a point function. > > If you need toll information, you need to do directions. > > 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 -~----------~----~----~----~------~----~------~--~---
