New Google Maps FEE
This topic contains 26 replies, has 15 voices, and was last updated by vid nado 6 years, 6 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: google maps
-
AuthorPosts
-
May 3, 2018 at 4:10 pm #428971
Hi Jenny,
Yes almost 200k requests is a lot, either traffic on your website is high, or something else wrong is going on.
Would you mind sharing a screenshot of your Google Analytics stats for the last 30 days?
Let me know,
Thanks
May 3, 2018 at 6:10 pm #428992The blog post is live: https://wpgeodirectory.com/google-maps-platform-changes-directory-developers/
we hope you find it useful!
May 4, 2018 at 4:12 am #429050Hi Paolo
Here is our analytics for the same period. We are quite a large site. We are not using the Geodirectory home page but have the maps on the top of all the directory pages and the side bar map on the listing itself.
May 4, 2018 at 8:21 am #429063I had a question about the google map API here:
https://wpgeodirectory.com/support/topic/is-the-open-map-version-comparable-to-google-anyone-using-it-now-google-req-cc/#post-429035At the moment if the google map api is not working (return an error like authorization failure) it will not switch to OSM automatically, correct? On my page it is not switching.
Best,
DirkMay 4, 2018 at 12:58 pm #429100What about BING Maps as an option? Zillow uses them???
May 4, 2018 at 2:13 pm #429119@jennie Thanks for that, its interesting to see. We will be able to reduce the single (details) page map loads to static maps (which are free) until when/if a user interacts with them and then load it dynamically. Also OSM must be looking attractive right now after calculating what you would have been billed if it was not free just now!
@dirk yes just now with an auth error the js fully loads then they do another call for the auth so its already loaded by the time we know it has failed and in most cases it would be silly to then reload OSM as they would cause 2x the loading rather than just fixing the problem. I hope they will implement this limit in a way we can intercept this before it loads fully but even if they don’t we could set it to detect it and then ajax call to switch it over to OSM for all the rest of the calls, maybe till the end of the month (or whenever limits reset)
@Tim its my understanding if you want to use Bing maps commercially there is a fee, also…. microsoft.
Stiofan
May 9, 2018 at 5:30 pm #429779Hello,
Note after 11th june, it’s not a per day limit but per month… so maps will cost… 🙂
June 1, 2018 at 6:24 am #433061Thank you for this wonderful Article! five nights at freddy’s
June 4, 2018 at 5:50 pm #433636Hey GeoTeam and GeoCommunity:
This Google Maps Platform thing may have broader implications for anyone using / relying on Google Maps … and especially the GeoDirectory community. Most of the discussions I have read here and around the web all seem to focus on the changes in the pricing model and the changes to the APIs.
However, I have not found anyone really discussing the revised Terms of Service for Google Maps that goes into effect on June 11, 2018 when the Google Maps Platform goes live.
Specifically, Section 3 of the updated Terms of Service concerning the License, restrictions on certain use(s) of the APIs and the data they return (defined as “map content”) are worth reviewing and considering their implications for your site / application.
I am not a lawyer or legal guru, but some of the things I read in the new terms are worthy of discussion. Please chime in with your thoughts and feedback. Here are the Links to the new Maps Platform Terms of Service and Service Specific Terms for various Maps Platform functionality.
- Terms of Service Link: https://cloud.google.com/maps-platform/terms/
- Service Specific Terms Link: https://cloud.google.com/maps-platform/terms/maps-service-terms/
I copied relevant portions of the Terms of Use and pasted it below my comments for convenience in discussing the implications.
Section 3.1 Grants the License. I see no issues with this.
3.1 License Grant. Subject to this Agreement’s terms, during the Term, Google grants to Customer a non-exclusive, non-transferable, non-sublicensable, license to use the Services in Customer Application(s), which may be: (a) fee-based or non-fee-based; (b) public/external or private/internal; (c) business-to-business or business-to-consumer; or (d) asset tracking.
Section 3.2 Adds “restrictions” on the License Grant for specific uses. From what I read, the sub-sections of Section 3.2 could create several issues for directory sites and site owners. Of primary concern are Sections 3.2.3 and 3.2.4.
3.2 License Requirements and Restrictions. The following are conditions of the license granted in Section 3.1. In this Section 3.2, the phrase “Customer will not” means “Customer will not, and will not permit a third party to”.
3.2.2 General Restrictions. Unless Google specifically agrees in writing, Customer will not: (a) copy, modify, create a derivative work of, reverse engineer, decompile, translate, disassemble, or otherwise attempt to extract any or all of the source code (except to the extent such restriction is expressly prohibited by applicable law); (b) sublicense, transfer, or distribute any of the Services; (c) sell, resell, or otherwise make the Services available as a commercial offering to a third party; or (d) access or use the Services: (i) for High Risk Activities; (ii) in a manner intended to avoid incurring Fees; (iii) for activities that are subject to the International Traffic in Arms Regulations (ITAR) maintained by the United States Department of State; (iv) on behalf of or for the benefit of any entity or person who is legally prohibited from using the Services; or (v) to transmit, store, or process Protected Health Information (as defined in and subject to HIPAA).
Section 3.2.3(c): Gives Google the right to review the site(s) / application(s) to ensure Compliance.
3.2.3 Requirements for Using the Services.
(a) End User Terms and Privacy Policy. Customer’s End User terms of service will state that End Users’ use of Google Maps is subject to the then-current Google Maps/Google Earth Additional Terms of Service at https://maps.google.com/help/terms_maps.html and Google Privacy Policy at https://www.google.com/policies/privacy/.
(b) Attribution. Customer will display all attribution that (i) Google provides through the Services (including branding, logos, and copyright and trademark notices); or (ii) is specified in the Service Specific Terms. Customer will not modify, obscure, or delete such attribution.
(c) Review of Customer Applications. At Google’s request, Customer will submit Customer Application(s) and Project(s) to Google for review to ensure compliance with the Agreement (including the AUP).
Now for the really critical stuff … what Google classifies as “Misuse” of the Services. Pay special attention to:
- Section 3.2.4(a)(i)-(iii),
- Section 3.2.4(b),
- Very important – Section 3.2.4(c) and especially 3.2.4(c)(ii), 3.2.4(c)(iii), and 3.2.4(c)(iv), and
- Section 3.2.4(d)
3.2.4 Restrictions Against Misusing the Services.
(a) No Scraping. Customer will not extract, export, or scrape Google Maps Content for use outside the Services. For example, Customer will not:(i) pre-fetch, cache, index, or store Google Maps Content for more than 30 days; (ii) bulk download geocodes; or (iii) copy business names, addresses, or user reviews.
(b) No Creating Content From Google Maps Content. Customer will not create content based on Google Maps Content, including tracing, digitizing, or creating other datasets based on Google Maps Content.
(c) No Re-Creating Google Products or Features. Customer will not use the Services to create a product or service with features that are substantially similar to or that re-create the features of another Google product or service. Customer’s product or service must contain substantial, independent value and features beyond the Google products or services. For example, Customer will not: (i) re-distribute the Google Maps Core Services or pass them off as if they were Customer’s services; (ii) create a substitute of the Google Maps Core Services, Google Maps, or Google Maps mobile apps, or their features; (iii) use the Google Maps Core Services in a listings or directory service or to create or augment an advertising product; (iv) combine data from the Directions API, Geolocation API, and Maps SDK for Android to create real-time navigation functionality substantially similar to the functionality provided by the Google Maps for Android mobile app.
(d) No Use With Non-Google Maps. Customer will not use the Google Maps Core Services in a Customer Application that contains a non-Google map. For example, Customer will not (i) display Places listings on a non-Google map, or (ii) display Street View imagery and non-Google maps in the same Customer Application.
(e) No Circumventing Fees. Customer will not circumvent the applicable Fees. For example, Customer will not create multiple billing accounts or Projects to avoid incurring Fees; prevent Google from accurately calculating Customer’s Service usage levels; abuse any free Service quotas; or offer access to the Services under a “time-sharing” or “service bureau” model.
(f) No Use in Prohibited Territories. Customer will not distribute or market in a Prohibited Territory any Customer Application(s) that use the Google Maps Core Services.
(g) No Use in Embedded Vehicle Systems. Customer will not use the Google Maps Core Services in connection with any Customer Application or device embedded in a vehicle. For example, Customer will not create a Customer Application that (i) is embedded in an in-dashboard automotive infotainment system; and (ii) allows End Users to request driving directions from the Directions API.
(h) No Modifying Search Results Integrity. Customer will not modify any of the Service’s search results.
(i) No Use for High Risk Activities. Customer will not use the Google Maps Core Services for High Risk Activities.
Then, there is Section 4.2 …
4.2 Compliance. Customer will: (a) ensure that Customer’s and its End Users’ use of the Services complies with the Agreement, including the applicable Services’ AUP and URL Terms; and (b) use commercially reasonable efforts to prevent, promptly notify Google of, and terminate any unauthorized use of or access to its Account(s) or the Services.
And then, Section 5.1 … Violations of License Restrictions
5.1 For License Restrictions Violations. Google may Suspend the Services without prior notice if Customer breaches Section 3.2 (License Requirements and Restrictions).
Section 11.5 regarding Termination and the clauses that survive Termination:
11.5 Effects of Termination.
11.5.1 If the Agreement is terminated, then: (a) the rights granted by one party to the other will immediately cease; (b) all Fees owed by Customer to Google are immediately due upon receipt of the final electronic bill; and (c) Customer will delete the Software and any content from the Services by the termination effective date.
11.5.2 The following will survive expiration or termination of the Agreement: Section 2 (Payment Terms), Section 3.2 (License Requirements and Restrictions), Section 4.5 (Data Use, Protection, and Privacy), Section 6 (Intellectual Property; Feedback), Section 10 (Confidential Information), Section 11.5 (Effects of Termination), Section 14 (Disclaimer), Section 15 (Indemnification), Section 16 (Limitation of Liability), Section 19 (Miscellaneous), and Section 20 (Definitions).
And finally, the Definitions in Section 20. I included only the ones that seem to be most applicable. It is important to note that Google defines the “Google Maps Content” as a component part of the Services covered by the License Grant and the License Restrictions.
20. Definitions.
“Account” means Customer’s Google Account.“AUP” or “Acceptable Use Policy” means the then-current Acceptable Use Policy for the Services at: https://cloud.google.com/maps-platform/terms/aup/.
“Customer Application” means any web domain or application (including features) listed in the Admin Console.
“Customer End User” or “End User” means an individual or entity that Customer permits to use the Services or Customer Application(s).
“Customer Indemnified Materials” means the Customer Application and Customer Brand Features.
“Google Indemnified Materials” means Google’s technology used to provide the Services (excluding any open source software) and Google’s Brand Features.
“Google Maps Content” means any content provided through the Services (whether created by Google or its third-party licensors), including map and terrain data, imagery, traffic data, and places data (including business listings).
“Indemnified Liabilities” means any (a) settlement amounts approved by the indemnifying party; and (b) damages and costs finally awarded against the indemnified party and its Affiliates by a court of competent jurisdiction.
“including” means “including but not limited to”.
“Intellectual Property Rights” means current and future worldwide rights under patent, copyright, trade secret, trademark, and moral rights laws, and other similar rights.
“Legal Process” means a data disclosure request made under law, governmental regulation, court order, subpoena, warrant, governmental regulatory or agency request, or other valid legal authority, legal procedure, or similar process.
“Package Purchase” has the meaning set out in the Service Specific Terms.
“Personal Data” has the meaning provided in the General Data Protection Regulation (EU) 2016/679 of the European Parliament and of the Council of April 27, 2016.
“Prohibited Territory” means the countries listed at https://cloud.google.com/maps-platform/terms/maps-prohibited-territories/.
“Project” means a Customer-selected grouping of Google Maps Core Services resources for a particular Customer Application.
“Services” and “Google Maps Core Services” means the services described at https://cloud.google.com/maps-platform/terms/maps-services/. The Services include the Google Maps Content.
“Service Specific Terms” means the terms specific to one or more Services set forth here: https://cloud.google.com/maps-platform/terms/maps-service-terms/.
“Software” means any downloadable tools, software development kits or other such proprietary computer software provided by Google in connection with the Services, which may be downloaded by Customer, and any updates Google may make to such Software.
“Terms URL” means the following URL set forth here: https://cloud.google.com/maps-platform/terms/.
“Third-Party Legal Proceeding” means any formal legal proceeding filed by an unaffiliated third party before a court or government tribunal (including any appellate proceeding).
“Trademark Guidelines” means (a) Google’s Brand Terms and Conditions, located at: https://www.google.com/permissions/trademark/brand-terms.html; and (b) the “Use of Trademarks” section of the “Using Google Maps, Google Earth and Street View” permissions page at https://www.google.com/permissions/geoguidelines.html#geotrademark policy.
“URL Terms” means the following, which will control in the following order if there is a conflict:
(a) the AUP;
(b) the Google Maps/Google Earth Legal Notices at https://www.google.com/help/legalnotices_maps.html;
(c) the Google Maps/Google Earth Additional Terms of Service at https://maps.google.com/help/terms_maps.html;
(d) the Service Specific Terms;
(e) the SLA; and
(f) the Technical Support Services Guidelines.
Given the new terms, is it still reasonable to use Google Maps Platform for a directory where members (customers) pay to get listed in the directory? It would seem that this sort of site is what Google is specifically trying to prevent from using its services … or any part of them … to create / operate this type of site.
Thoughts?
June 4, 2018 at 8:28 pm #433653Hi Craig,
I replied here: https://wpgeodirectory.com/support/topic/changes-to-google-maps-platform-terms-of-service/#post-433651
Let’s keep the conversation about the new terms on that post.
Thanks!
June 4, 2018 at 8:30 pm #433655Note: My previous post regarding the changes to the Google Maps Platform was re-posted as a new topic here:
https://wpgeodirectory.com/support/topic/changes-to-google-maps-platform-terms-of-service/
Please add your replies, thoughts, feedback, and suggestions to the new topic thread. Thanks!
August 30, 2018 at 10:51 am #444645Nice Post Thanks For Sharing!
https://vidnado.com.au/ -
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket