News for hackers. Stuff that matters.
Re:How We reduced our Google Maps API cost by kartayyar on Saturday April 04, 2020 @04:06AM (#22776917)
This seems to be violating the Maps API terms of service?

https://cloud.google.com/maps-platform/terms

(a) No Scraping. Customer will not export, extract, or otherwise scrape Google Maps Content for use outside the Services. For example, Customer will not: (i) pre-fetch, index, store, reshare, or rehost Google Maps Content outside the services; (ii) bulk download Google Maps tiles, Street View images, geocodes, directions, distance matrix results, roads information, places information, elevation values, and time zone details; (iii) copy and save business names, addresses, or user reviews; or (iv) use Google Maps Content with text-to-speech services.

(b) No Caching. Customer will not cache Google Maps Content except as expressly permitted under the Maps Service Specific Terms.

Re:How We reduced our Google Maps API cost by xtony on Saturday April 04, 2020 @04:08AM (#22776924)
Caching is allowed (for up to 30 days). Here are the specific terms for the API in the article: https://cloud.google.com/maps-platform/terms/maps-service-te...

"Customer can temporarily cache latitude (lat) and longitude (lng) values from the Directions API for up to 30 consecutive calendar days, after which Customer must delete the cached latitude and longitude values."

Re:How We reduced our Google Maps API cost by cookie_monsta on Saturday April 04, 2020 @07:14AM (#22777584)
But lat/lng pairs are pretty useless on their own, particularly with a travel times app
Re:How We reduced our Google Maps API cost by DeathArrow on Saturday April 04, 2020 @04:56AM (#22777077)
That might be a mistake on their side which they might repair now that they started to ask for lots of money for the data.
Re:How We reduced our Google Maps API cost by wstuartcl on Saturday April 04, 2020 @10:38AM (#22778445)
rofl. funny.