Great,
> > > > 5) Save the polylines to a database > > > > Yes, but you may not be allowed depending on your purpose. Read the > > > Terms of use before putting too much effort in > > > I just went through the whole Terms of Service and could not find much > > on this. > > " ... must not: > .... > 10.3 pre-fetch, cache, or store any Content, ..." > > Directions are Content. Read the whole item for the exceptions, most > notably "except ... temporarily". So how about storing coordinates? I suppose this is content too but it would be points that are chosen by the user of the map. Imagine going to a map, clicking on point A, and point B. A polyline is drawn, but what's actually stored in the database were the original points the user chose. Then these points can be used to compute the routes each time the map is drawn in the future. Is this still against policy? If so, I don't see how any google maps out there with pre-stored routes is legal... For example, I remember coming across a site with bike trails. http://www.nycbikemaps.com/maps/nyc-bike-map/ > Have look at this, to get a feel for what can be done "easily" - > http://econym.org.uk/gmap/ > Have a look at examples for inspiration - > http://code.google.com/apis/maps/documentation/examples/index.html > and just don't be too ambitious with a first project - this forum is > full of people floundering because they don't go one step at a time. > > cheers, Ross K Thanks, I will. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
