That is what I had thought, but after messing with it for a while I had begun to confuse myself. Also I hadn't thought about some of the roads here on campus being private until this morning. So that is probably why, I will test that theory with maps.google.com and post back. If anything else it could help somebody else later.
On Mar 11, 8:06 am, "[email protected]" <[email protected]> wrote: > On Mar 10, 11:29 pm, daniel <[email protected]> wrote: > > > Sorry, I always forget the link. I am using Mike's tutorial on adding > > driving directions. > > > What I would like to be about to do is just add a street address, then > > it shows directions. I can do this on maps.google.com, I am not sure > > if that is geocoding or not. > > It is "Driving Directions". Geocoding is taking an address and > getting its latitude and longitude. Both the Driving directions and > the geocoding functions have quotas and "speed limits". If your > addresses are known (the parking lots and building of your school) > there is no benefit to geocoding. If it is a user's address, then > there shouldn't be any problem with using the geocoder (but geocoders > are not particularly reliable). > > -- Larry > > > > > Here is my link:http://wds.semo.edu/map/Map(2)/parking.html > > > On Mar 10, 6:52 pm, Ralph Ames <[email protected]> wrote: > > > > >I was curious about the benefits of geocoding. I was considering > > > >adding geocoding to my map, but I have a driving directions feature, > > > >but wonder what the difference would be in... > > > > ...how I am doing it verses > > > geocoding. > > > > How are you doing it? > > > > Ralph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
