Re: Google Maps API Web Services TOS

If it were truly about caching, you wouldn't get the directions from
Google until the first user actually requested a map. Preloading
directions that might or might not be viewed later, but stripping out
some of the info for republication regardless, just doesn't interpret
as permitted to me.
Have another read of terms 10.2 , 10.3 and 10.12

As Andrew points out, any users that are actually interested in
directions are going to be disappointed with what they get, and as you
point out they would then hit Google again for a more relevant route.
Doesn't seem to be any 'savings' there.

As you're not even giving door-to-door distances for the user,
estimating seems smarter and quicker.

--
You received this message because you are subscribed to the Google Groups "Google Maps API" group.
To post to this group, send email to google-maps-api@googlegroups.com.
To unsubscribe from this group, send email to google-maps-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.