I don't know if this would actually help but it seems like it might be more efficient to do some simple calculations on the coordinates of each destination, to determine maybe the closest 3, then only get directions for those. Granted the result would be line-of-sight distance, and not by road, but that could save some load time or resources. Just an idea.
On Mar 17, 7:26 am, Osiris <[email protected]> wrote: > Hi, > > We are working on an web app which uses the Google Maps API. > > I know there are terms about having to display things on maps if we > use the service, and I need to know if our app would be breaking the > t&c's. > > Essentially we will get the users location (Via them entering the post > code and geo-coding it). Then we get their destination through a drop > down box. This journey is then sent to the directions handler, and we > get the directions. > > But what we also do is loop through every other entry in the drop down > box, to see which gives the shorter journey times (As coming from > different directions will change the results), then we place makers > over the map at the different destinations, and also list these on the > page with links, which, when clicked will show the relevant route > using the DirectionsService.setDirections() method (Having stored the > relevent direction result in a global variable). > > Is this allowed? Or is it breaking the t&c's? > > Thanks In Advance -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
