On 6 January 2013 23:49, Barry Hunter <[email protected]> wrote:
> To be honest not sure you 'can' be in compliance.
>
> Firstly the (free) Directions API may ONLY be used to display information on
> a Google Map, on a public website. You cant use it to just get information
> for use outwith a Google Map.
>
> You can relax the requirement for the map to be public by purchasing Google
> Maps for Business (or maybe as a non-profit can get a grant) - but that
> doesnt help with the map requirement AFAIK.
>
> So you could get close by making the it an interactive application -
> displaying routes on a map (and NOT exporting the data for use elsewhere) -
> but would then would probably need to be public.

It would definitely need to be public, and you do need to show a map.
[Or, with the Directions API, the table of routing data. A map showing
the route is a nice touch though]

What you may be able to do is to make the entire application public
but have an option for logging in. Without logging in, you can use
route-planning, distance calculation, whatever; when users are logged
in they *also* get a Submit button which allows their data to be sent
back to your accounting system. If that's the only difference between
not logging in and logging in, you will probably be ok [but this is
not legal advice; you'll need to satisfy yourself that this is the
case]. If you have a map, you might get your drivers to adjust
Google's route on the map, if they have had to go a different way, and
you could record this.

Logging in might also allow drivers to get details of their next
appointment and the route's "From/To" boxes filled in for them, and
have the map show the route. Without logging in, those boxes remain
empty to be filled in manually in order to get the route on the map.

Basically what you need to do is to provide a public version of your
route-planner, and then bolt on server-side data access for logged-in
users.

I have a feeling that may be a major change in system design, though.
If it's too great, then an alternative solution will be necessary.

-- 
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.

Reply via email to