"Wrapper service" in the TOS means that some service provides map functions using Google Maps API such as tile, geocoding....etc. The application you want to create using Google Maps API, it doesn't seems like wrapper service. Because you provides information on the map, not map itself. So I think you can use map api.
On 2月15日, 午後1:42, Andrew <[email protected]> wrote: > Hi, > > I just started using the maps api and would like to make an app for > webOS, specifically for the Touchpad. My plan is to allow users to > search for businesses with Google Places, Yelp, and Yellowpages, show > their locations on the map and then get directions. I feel like this > doesn't constitute a wrapper of Google maps, but at that point it > becomes very tempting to also allow users to search for addresses. > Basically, I feel like this is a gray area in the terms and I don't > know how far I can go without it being considered a wrapper. Also, > there is no Google maps application for webOS, so is the fact that it > is a native application a substantial additional feature in itself? I > don't want to waste my time, so I'm wondering if anyone here can clear > this up for me? If I only allow local searches for businesses is it > definitely OK? If I decide to allow searching for addresses too, > would the additional local search services along with the advantages > of a native interface and on device preferences constitute substantial > additional features? Any help would be greatly appreciated. -- 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.
