> is legal to store "Get Directions" results in a database? and if
> necessary process this data in some way?
Going by the old terms and advice from Pamela a year or so ago, I was
under the impression that we were allowed to store Get Directions
results in our database. In fact I didn't ever get around to storing
the textual directions ("turn right", etc.) but I nearly did. I do use
the Get Directions facility to snap routes to follow roads when
drawing routes in the API. So I am storing the lists of points
returned by Get Directions. This (a) saves load on Google's service,
and (b) records a snap-shot of the route at the time is was made, so
it doesn't change with time (or with changes in the Get Directions
algorithm).
Hope this is still allowed, as snapping routes to follow roads makes
it so much quicker for people to enter routes into my site's database.
My system allows people to switch this feature on and off, so they can
define routes that don't follow roads, or which follow roads that
Google doesn't know about. I've seen other route sites that do the
same.
Pamela, is it no longer allowed to store the data from a GDirections
result object? If so, any site that allows people to draw a route,
using GDirections to provide a "snap to roads" functionality, will now
be in breach of the Terms. Would we also have to delete any such data
stored in the past? This could be a bad blow to many cycle route
sites...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
