On Jan 21, 5:17 pm, seamusmorton <[email protected]> wrote: > 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
Hmm. I don't think it's been mooted to use the API to construct a URL to create a static map. The feeling (as in that Issue) has been that everything would be done server-side and a static map would be used because the client couldn't run Javascript. If the client can run Javascript, then use an ordinary dynamic map. However: something like IE Mobile *can* run Javascript but can't cope with the full Maps API, so this might be a compromise arrangement. There is this in the Terms: 10. Except as explicitly permitted in Section 7, you must not (nor may you permit anyone else to): 10.1 access or use the Service or any Content through any technology or means other than those provided in the Service, or through other explicitly authorized means Google may designate; Parsing HTTP headers falls foul of that; but if you can use a GDirections object and examine each GStep in that, it would be ok. 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 -~----------~----~----~----~------~----~------~--~---
