Unfortunately, this is probably against the Google Maps API Terms of Service.

[Kerrick]

https://developers.google.com/maps/terms

10. License Restrictions.

10.2 Restrictions on the Types of Applications that You are Permitted to Build with the Maps API(s).

10.2 (a) No "Wrapping."

You must not create or offer a "wrapper" for the Service, unless you obtain Google's written consent to do so. For example, you are not permitted to: [...] (ii) create a Maps API Implementation that reimplements or duplicates Google Maps/Google Earth. For clarity, you are not "re-implementing or duplicating" Google Maps/Google Earth if your Maps API Implementation provides substantial additional features or content beyond Google Maps/Google Earth, and those additional features or content constitute the primary defining characteristic of your Maps API Implementation.

[graingert]

Everyone knows APIs can't be copyrighted

[Kerrick]

It's not a copyright issue, it's a service availability issue. Google is well within their rights to revoke API access to any developer caught using gmaps to access the Google Maps API.

That said, the likelihood of them doing so is slim to none. It's still an issue to be aware of.

[graingert]

I think this is just preventing people hosting a copy of google maps and not a client library

[Kerrick]

No, this applies to client-side libraries. OpenLayers required a specific letter from Google saying the terms didn't apply to them (but will apply to others).

[graingert]

odd, in that case making a wrapper to open layers is probably the only way to do this while staying within the license restrictions

#16 (comment)

[Kerrick]

Protip: If you comment about an issue by typing #16, it'll get a reference notification in their thread. :-)

[Kerrick]

odd, in that case making a wrapper to open layers is probably the only way to do this while staying within the license restrictions

Or, @hpneo could request a similar letter.

[hpneo]

I'm going to study the Open Layers API and others map services to see if it's possible to implement wrappers for these services.
Nevertheless, I've thought of requesting a permission from Google.

[honzzz]

Has this issue been resolved? Did you get permission from Google? I would love to use gmaps but this seems to be a dealbreaker.

[neersighted]

Even though I love this library's concept, I cannot use it because of Google's TOS. @hpneo, is there any chance of the afore mentioned letter?

[bradgreens]

I've written and have seen many private wrappers to Google Maps. It's the only way. Let me ask, is a single function a "wrapper"? How can you not "wrap" some functions together, to manage the API?

If it's a big deal, copy the source(s) you desire and forget the TOS if you're worried. I'm not trying to deter the project, just saying that any functions which surround the Google Maps API would theoretically be questionable. And that, is an unrealistic warrant against allowed usage. Is $(function(){}) a wrapper?... ...

[fedeghe]

really deadlock, had no idea, thanks

[sobrinho]

I think You must not create or offer a "wrapper" for the Service means you cannot create a service that wraps the the Google Maps, it isn't related to the API.

For example, My Application > 3rd Service > Google Maps.