maybe. But then, under that context, caching the images for performance reasons, which is allowed, would also be a derivative work.
I guess it depends if they are seeing this from a code perspective, or an "end result' perspective. After all, wouldn't almost all uses of the API be "modifying" the supplied images? (I mean, even if you didn't use any custom markers getting really nitty-gritty, the device's themselves will be modifying and copying the image to display them) Wish they had more examples to make this more clear. The other thing that makes me skeptical/hoping it is allowed, is that the code to copy a bitmap from the mapView hasn't been overridden to disable it. Guess that could have been overlooked though. On Jun 28, 5:37 pm, Andrew C Leach <[email protected]> wrote: > On 28 June 2010 16:26, darkflame <[email protected]> wrote: > > > > > "10.2 copy, translate, modify, create a derivative work of, or > > publicly display any Content or any part thereof (for example, the > > following are prohibited: (a) creating server-side modification of map > > tiles; and (b) stitching multiple static map images together to > > display a map that is larger than permitted in the Maps APIs > > Documentation);" > > > What my code would be doing would be; > > a) Setting the mapView to a location. > > b) Taking a bitmap from it (including the logo etc). This would > > probably be done with the "getDrawingCache" which is a MapView > > function. > > That's creating a copy and a derivative work, though, isn't it? -- 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.
