Hi andrew, thanks for your reply. HTTP access to the driving directions is not available directly but when making the request from the API it sends back the direction string in the header and it can be extracted.
I know it's not really meant to be used like that but that information is made available to me in the API so I didn't think it would matter how I used it. The only problem that I can see from Google's point of view is the extra load put on the server by plotting a lot of points but then it does allow me to plot up to 50 >From a technical point of view there is nothing stopping me from doing it, I know because I've already made a working prototype. So do you see any legal problem with me using the driving directions in this way? warden [Andrew Leach - Maps API Guru] wrote: > On Jan 21, 4:19 pm, seamusmorton <[email protected]> wrote: > > Hi, I'm developing an application that will use the static maps API > > and I have a question regarding the T&C. > > To do what you want you will be needing HTTP access to driving > directions. That's not currently on offer. > > Apart from that small difficulty, it would probably be fine. Add your > star to Issue 235 > http://code.google.com/p/gmaps-api-issues/issues/detail?id=235 > -- you'll see a suggestion remarkably like your proposal at comment > #50. > > 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 -~----------~----~----~----~------~----~------~--~---
