On Fri, Aug 19, 2016, at 20:36, Selvakumar Periyasamy wrote: > > As per the business rules, We are not supposed to store the KML files in > publicly accessible site or Google Drive, etc... and load from there.
Your business rules conflict with the API Terms of Service, specifically 9.1.1: 9.1.1(a) Subject to Section 9.1.2 (Exceptions), your Maps API Implementation must be accessible to the general public without charge and must not require a fee-based subscription or other fee-based restricted access. This rule applies to Your Content and any other content in your Maps API Implementation, whether Your Content or the other content exists now or is added later. 9.1.1(b) Your Maps API Implementation must not operate (i) only behind a firewall; or (ii) only on an internal network (except during the development and testing phase); or (iii) in a closed community (for example, through invitation-only access). https://developers.google.com/maps/terms#9-license-requirements Thus 9.1.1(a) stipulates that your data must be publicly accessible, and 9.1.1(b) means that you cannot operate your maps only internally. The exceptions in 9.1.2 allow these restrictions to be lifted if you have a Google Maps for Work agreement or something similar. https://www.google.com/work/mapsearth/ The restrictions you have found in the API are by design. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-maps-js-api-v3+unsubscr...@googlegroups.com. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. Visit this group at https://groups.google.com/group/google-maps-js-api-v3. For more options, visit https://groups.google.com/d/optout.
